51–60 of 83 posts
I have to go to all the trouble to maintain my webserver and setup DNS, then go to twitter to read others? Why is this not a big deal?
But in the long run you won't beat Facebook and Twitter by merely replicating their functionality.
Why not email (SMTP/IMAP)? Deployed, standardized, widely supported.
http://static.scripting.com/myReallySimple/linkblog.html
It's great, except it's completely unusable due to it being a huge download of a page full of disparate links with no organization other than by date.
The trick is not in writing something like this, it's in making the information aggregated and easily organized.
More here: http://GoPalmetto.com/
He mentions the lack of a notifications system. Isn't there room in this open system for a ping type notification service or group of services? The benefit for such a service to be free would be that they could aggregate the data and mine it as twitter does. Then clients could fail back to polling should this service not be available.
pubsubhubbub A simple, open, server-to-server web-hook-based pubsub (publish/subscribe) protocol as an extension to Atom and RSS. Parties (servers) speaking the PubSubHubbub protocol can get near-instant notifications (via webhook callbacks) when a topic (feed URL) they're interested in is updated. The protocol in a nutshell is as follows: - An feed URL (a "topic") declares its Hub server(s) in its Atom or RSS XML fi…
Earlier quoted context omitted.
But there are celebrities and that hot girl from high-school within that walled garden.It sucks and i wish the products were better and more open but the bar for entry is mostly user draw, and T&A is what draws them in.. *edited for spelling >_>
You just made me think of something. The common folk may as well continue using Twitter, and you're right about the bar to entry. We few, the vanguard of openness and reliability, can use approaches like Dave Winer's to provide an open, durable parallel "Twitter-like ecosystem" that integrates with Twitter—and once Twitter goes away (and Facebook and Google+ and even SMS) we will integrate with its successor—or hopef…
Isn't this exactly the problem? Keeping a service alive in perpetuity is missing the point because it's the communication that's important, not the service upon which the communication flows... Human communication is inherently temporally limited. If you ignore that, you're not gonna be heard now, which makes you even less likely to be heard in the future.
EDIT: I guess I'm just saying: nobody reads old messages on this sort of service. If you're not targeting "now", you're starting off with an immense disability.
"3. To identify users -- please use DNS." Using DNS to identify users is unwise, in my opinion, because it means that people won't own their own on-line identities -- they'll have to rent them and for real money, too. And if some users are assigned a sub-domain on a shared domain, their identity won't be portable. I think it is worth doing a little extra work to make a user name system that doesn't have those problem…
DNS has the virtue of being here now, being tested and refined over multiple decades, and offering a choice between subdomains for free or portability for a nominal annual cost. It's not perfect but it's good.
"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?