April 10, 2006
@ 02:53 PM

Via Shelley Powers I found out that Mark Pilgrim has restarted his blog with a new post entitled After the Bath. Ironically, I didn't find this out from my favorite RSS reader because it correctly supports the HTTP 410(GONE) status code which Mark's feed has been returning for over a year.

Mark Pilgrim's feed being resurrected from the dead is another example of why simply implementing support for Web specifications as written sometimes bites you on the butt. :)


Monday, April 10, 2006 3:23:37 PM (GMT Daylight Time, UTC+01:00)
http://diveintomark.org/xml/atom.xml is still gone.
Monday, April 10, 2006 3:30:50 PM (GMT Daylight Time, UTC+01:00)
As is http://diveintomark.org/xml/rss.xml which is what I was subscribed to.
Monday, April 10, 2006 5:29:24 PM (GMT Daylight Time, UTC+01:00)
What alternative do you propose? Would you rather continue polling Dive into Mark once an hour over the span of the 13,080 hours where it had no feed?

Pity that would have been fruitless, since the old locations remain Gone.

Pointing at problems is easy.
Monday, April 10, 2006 5:31:49 PM (GMT Daylight Time, UTC+01:00)
Really? That's Interesting. I should have checked before posting but it does point out an interesting problem of what to do if a page is resurrected from the dead.
Tuesday, April 11, 2006 5:56:04 PM (GMT Daylight Time, UTC+01:00)
Enterpreis-grade solution arcitechture:

blogger->blog engine->network such as IRC,usenet or search publish service (google)<-blog subscriber/reader

1a.when IE or news software contacts the publish event caching network (or IRC)

1b.blog subscriber gets events (event= update notice of blog with URL) (in irc messages "events" are cached if you are offline).

1c. client software knows blog x has updated or back from dead

1d. (optional) client pass info to blog about reading

2a. when blogger blogs, the engine (Communisty server) passes the publish/update event to the network (irc,google,NEWS grp and such)

It is BEST to use IRC or NEWS GROUPS because the servers do not posses central authority and thus GOOGLE cannot know what blogs you are reading.

Full blog entries (not summary) can be ENCRYPTED such that to read the blog you need time coded key, upon fetch of the key, the blogger knows you are reading the blogs.

Secure enterprisey system architecture blogging paradigmism.

(oh wait, it is not first of april?)
Comments are closed.