(Post a new comment)
(Reply to this) (Thread)
(Reply to this) (Parent)
(Reply to this) (Parent)(Thread)(Expand)
(Reply to this)
Allowing people to turn off syndication is good. Allowing people to block bots is good. Pretending that they meant to turn off syndication when they ask to block bots is very bad.
Some sort of no-robot extension needs to be added to RSS and Atom in order to properly fix this bug. And I'm totally against any fix that pretends that bot blocking means no syndication. That's not a fix, that's purposely adding a bug.
Now there is a fix I would accept, though it would be kind of silly and poor. That would be to check the User-Agent field for known bots. LJ would then refuse to hand them the feed by returning the appropriate 'access denied' HTTP header.
This is a little off-topic, but why to the Blog Search result links take you to a page that then does a refresh to the real page? Some inspection shows that the Location: header is there but it's being served as HTTP status code 200 rather than 301 or 302 so my browser is ignoring it. If it's sent with 301 or 302 (or one of the other, similar 3xx response codes) it'll be much more useful to user-agents which aren't browsers as well as being less lame in those that are.
Event that solution isn't brilliant, because not all LiveJournal-based sites actually uses the user vanity domain functionality. It would effectively disable the machine-readable data completely on those sites which don't.
(Reply to this) (Thread)(Expand)