Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It's a business now. You can't go back and reinvent it now, which is clear from my comment above. But that wasn't always so. In 2006 it wasn't so. I remember those early days when only nerds were using Twitter. Now, you can't sustain a business that way, I know that. But Twitter was always supposed to be minimalist and web-enabled SMS. It's a shame, IMO, that because of "monetization" they have to make all these moves to make it more complicated and harder to surface useful information and conversations. Promoted tweets that are intrusive. Cards. Etc. I think there was a time when Twitter could have been "rolled in" to the public Internet in a way that would be more open and free of this grasping for a profit strategy. That time has passed, and it's sad.


> I think there was a time when Twitter could have been "rolled in" to the public Internet in a way that would be more open and free of this grasping for a profit strategy.

Hey, I remember such a time. I remember when Twitter was the "in" thing, and "everyone" (read: only techies in the Bay area) was using it. I remember how lots of conventions that are baked into the system today (@ notation for user references, "RT:" for retweeting, etc) were organically generated community standards.

All of that said, Twitter as a system had major hurdles to overcome to become a utility in the way that you want. But assuming that they published a standard, and created some sort of federated system (e.g. XMPP) how would this be anything but a money-sink? Would Twitter still be in use today? Would Facebook have copied most of what the public wants out of Twitter, and that would be it? How expensive would it be for a major provided of "Twitter Protocol Service" to maintain an SMS gateway? Would anyone actually pay for this service? What about inter-node security? Would we see something akin to the joke that is TLS between SMTP servers?




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: