I thought I’d check out Microsoft Max, but Don Dodge says it doesn’t support OPML.
What? A new RSS aggregator that doesn’t even import OPML?
I’m beyond surprised, and won’t check it out. I’m sure it looks beautiful (as everyone is saying), but without OPML support what value does it bring to me?
I knew we would be in the press this week with the release of v1.3 of the Digipede Network and announcing our recent deal with Digital Dimension.
What I didn’t know is that our product was going to receive an Editor’s Choice Award for Price / Performance.
A pleasant surprise! Thanks, GridToday.
I guess I’ve been asleep at the aggregator. Actually, just busy driving a release; anyway, I see from Kevin Burton that Rojo has been acquired.
In addition, Kevin puts on his 20/20 hindsight spectacles to praise himself:
In hindsight, I don’t ever think Rojo was given the credit it deserved. Feed search in particular. In fact, earlier this year when Ask/Bloglines released their feed search it was pointed out that Rojo had been doing the same thing for months.
Just kidding you, Kevin. Congratulations — I hope this acquisition is good for you.
Don Dodge asks if newspapers and magazines dying? I guess Steve Gillmor would say, no, they are already dead. Robert Scoble doesn’t read them.
But that doesn’t mean they don’t still have legs. Hell, I read them. Maybe that is why I’m behind in my news aggregator.
I read National Geographic, sometimes Discover (some of the articles are good), whatever tech magazines they keep sending me, Dr. Dobbs, and then whatever magazines my wife reads. Occasionally I read a guitar magazine. And almost anything on an airplane.
That is, now it is 1. I started blogging on September 3rd, 2005 just before going to PDC05. Back then the blog has a different name (Mind From R. Wandering) and was hosted elsewhere, but it is essentially the same. According to WP Admin, this is my 193rd post.
If my readership continues to increase at even a fraction of the same rate, everyone in the universe will be reading my blog within the year.
Long live the divide-by-zero joke. 😉
Tags: blog
If this blog has a topic, this is certainly off it.
I have recently been listening to the musical version of the War of the Worlds. This was given to me as a present by my sister last year. I had never heard of it before, but I guess it was big in England at some point (it was released in 1978). Kind of campy and fun, it’s kind of a disco / rock opera clearly influenced by Jesus Christ Superstar.
I’m not really into musicals, but in the right mood you can coax me into singing “Heaven on their minds.” But, I’m straying off the off-topic.
The music of this piece is too upbeat. It completely misses the horror you would expect from a Martian invasion. It is just too upbeat. While listening to the words:
With the smoke of battle clearing,
Over graves in waves defiled.
Slowly disappearing,
Farewell Thunder Child!
I’m feeling:
Hey, yeah, we’re all going to die! Yeah!
And now, back to your regularly scheduled program.
In a post about Akismet being out of commission, Robert Scoble notes that it has blocked 64,000 comment spams for him. This is since he moved to WordPress (approximately 321 days ago). Akismet has blocked 45,000 for me (over approximately 259 days). This means that my blog has 89% of the readership of his, right?
Of course these are the lowest type of “reader”: the spammer bot.
Look out, Robert, here I come!
Perhaps this means that some spammer bots avoid WordPress.com hosted sites (mine is self-hosted). If this is true, that is another bonus of WordPress: more spammers avoid it from the get-go.
WordPress and Akismet really rock.
Dan writes about the new version of the Digipede Network coming out soon:
But, most exciting: we’re getting ready to release the Digipede Network 1.3 next month. The development for this release has gone very well (mostly due to Rob, his adoption of some agile development techniques, and his devotion to automated builds and tests). We’re on schedule for a September release.
Thanks for the nod, Dan, but it is everyone on the team making this release happen — even you 😉
I am out of facility for the next week. Off the grid. Disconnected. Laptopless and without an Internet cafe. I expect lousy cell connectivity.
In Antarctica?
Nope, just on vacation with the family.
Tags: blog
Recently I complained about how the XmlSerializer treats the ObsoleteAttribute.
My desire was to deprecate a property with ObsoleteAttribute without it being ignored by the XmlSerializer. I still think that the attribute should be ignored for serialization, but here is a workaround:
Before:
[XmlAttribute]
public bool A { ... }
After:
[Obsolete("This property has been deprecated; use property B instead.")]
[XmlIgnore]
public bool A { ... }
[XmlAttribute("A")]
[EditorBrowseable(EditorBrowseableState.Never)]
public bool DeserializingA { ... }
[XmlAttribute]
[DefaultValue(false)]
public bool B { ... }
The ObsoleteAttribute tells the compiler to issue warnings to developers about the old property (and, as I said above, the XmlSerializer also ignores it).
The XmlAttribute.Name property directs the serializer to read a property from an XML attribute with a different name.
The EditorBrowseableAttribute hides the deserializing property from Intellisense. You can also hide it from the debugger using the DebuggerBrowseableAttribute (not shown).
The example shows this for XML attributes, but the same approach will work for other XML elements.
Not too much extra work, though I would still prefer the XmlSerializer to just ignore the ObsoleteAttribute.
FriendFeed Status
About me
Main feed
Email subscriptions