6 ms·
"4. A user is a feed. So the name points to a feed." What if the user wants to have more than one feed? Or wants, sometime down the road, to have routable res
by dasht 14y ago
"4. A user is a feed. So the name points to a feed."
What if the user wants to have more than one feed? Or wants, sometime down the road, to have routable resources that are not feeds?
Wouldn't it be better to say that a user name is a user name and that a default feed name can be automatically built given just the user name?
- mapgrep 14y agoThis makes the "Twitter-like" system less "Twitter-like". Don't get me wrong, I see your point, and I can think of a technical solution (point to OPML feed collections instead of feeds), but the further this gets from the original popular thing (Twitter) the less support and momentum it's going to have, imho. On Twitter it's one stream per user, and that keeps things simple. And simplicity is a huge part of the value add of twitter.
- dasht 14y agoI agree that "emulate the user==feed simplicity of twitter" is the best counter-argument to "make the user name distinct from the feed name for greater flexibility" position. But here: In twitter APIs, can't you get something like, say, a user's avatar image by keying off the user name? So, even on twitter, a user name maps to multiple different things -- not just a single feed.