News for hackers. Stuff that matters.
Re:Dave Winer: An open Twitter-like ecosystem by dasht on Friday July 27, 2012 @02:46PM (#4302977)
"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 problems.

Re:Dave Winer: An open Twitter-like ecosystem by mapgrep on Friday July 27, 2012 @05:35PM (#4303701)
Inventing a new identity system that features 1, portability and 2, end-user price of $0 is surely possible, but surely more than "a little extra work."

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.

Re:Dave Winer: An open Twitter-like ecosystem by dasht on Friday July 27, 2012 @06:13PM (#4303830)
To avoid building in a dependency on DNS does not require that the identity system problem be fully solved, first. It only requires ensuring a good abstraction barrier before too much code propagates that depends directly on DNS. For example, perhaps, URIs.
Re:Dave Winer: An open Twitter-like ecosystem by pyre on Friday July 27, 2012 @07:44PM (#4304082)
Why can't the usernames be like email addresses?

  send email to [email protected]
    => lookup example.net
    => pull MX record
    => route email to example.com
Looks like a SRV record[1] could be used for this.

[1] http://en.wikipedia.org/wiki/SRV_record

Re:Dave Winer: An open Twitter-like ecosystem by carols10cents on Friday July 27, 2012 @11:03PM (#4304557)
Is the webfinger protocol [1] like email addresses in the way you're thinking of?

[1] - https://code.google.com/p/webfinger/wiki/WebFingerProtocol

Re:Dave Winer: An open Twitter-like ecosystem by dasht on Friday July 27, 2012 @09:35PM (#4304386)
"Why can't the usernames be like email addresses?" [in the sense of querying DNS to find them].

In this context we're talking about what it takes to avoid relying on DNS (because DNS is a centralized, highly politicized system). Your solution would still rely on DNS.

Re:Dave Winer: An open Twitter-like ecosystem by pyre on Sunday July 29, 2012 @01:43PM (#4309114)
A system which relies on DNS, but in which anyone can setup a node seems better than a system that relies on DNS but only has one centralized node (Twitter), no?

In a truly decentralized system, you're not going to be able to have readable unique names without collisions. Why? What happens when the network splits, then people on either side of the split setup the same username. How do you rectify this when the network rejoins? How do you know that the network has split vs. a node going offline (if you wanted to do something like shut down new usernames until the network was whole again)?

Re:Dave Winer: An open Twitter-like ecosystem by dasht on Sunday July 29, 2012 @03:01PM (#4309349)
"A system which relies on DNS, but in which anyone can setup a node seems better than a system that relies on DNS but only has one centralized node (Twitter), no?"

The concern here is that whoever is currently leasing the domain name has authority over users' identities. A better system would let users own their identities outright.

"In a truly decentralized system, you're not going to be able to have readable unique names without collisions. Why? [....]"

This is a well explored topic. A good place to start might be to look up "Zooko's Triangle" and then go forward from there towards various ways people have figured out to deal with such problems. (Zooko's wasn't the last word.)

Re:Dave Winer: An open Twitter-like ecosystem by sp332 on Friday July 27, 2012 @05:44PM (#4303736)
That's true of email as well, though.