You can't "follow" websites and get a uniform chronological feed of updates. That's partly why RSS exists, though it also doesn't give you a uniform feed of updates. That has to be constructed client side by downloading all updates for all subscribed feeds.
> It also describes NNTP
Which also doesn't provide a uniform feed of updates.
> That has to be constructed client side by downloading all updates for all subscribed feeds.
Either the Twitter frontend or app has to do this, because Twitter is a web API. So either Twitter isn't a new protocol or every blog, forum, etc is a new protocol, with isn't really an interesting statement.
>> It also describes NNTP
> Which also doesn't provide a uniform feed of updates.
If it helps to find middle ground, I do think the AT protocol is a new protocol. I don't necessarily think it's a good idea or an improvement on NNTP, but it at least isn't just a microblogging website.
You can't "follow" websites and get a uniform chronological feed of updates. That's partly why RSS exists, though it also doesn't give you a uniform feed of updates. That has to be constructed client side by downloading all updates for all subscribed feeds.
> It also describes NNTP
Which also doesn't provide a uniform feed of updates.