TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Big Tech's Takeover and Destruction of Open Protocols and Networks

50 pointsby listenfasteralmost 2 years ago

4 comments

lapcatalmost 2 years ago
Don&#x27;t forget the biggest corporate takeover of them all: HTML, which is now effectively owned by Apple, Google, and Microsoft via WHATWG and their web browser dominance.<p>See also <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=36854114">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=36854114</a> and <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=36862494">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=36862494</a>
d--balmost 2 years ago
Google didn&#x27;t kill RSS. If RSS was so great, there were plenty of readers available that people could have jumped to. RSS died because it became yet another channel for ad delivery and shitty content.<p>XMPP wasn&#x27;t killed by Facebook either. XMPP never really caught on in the first place. Not in the way RSS did. IIRC, XMPP started because people were using 20 different chatting apps which were basically the same app under a different banner (icq, msn, yahoo, etc.). And it was a pain. People used aggregators to connect to all these different networks at once. And so, the Jabber guy thought it could be good to have a protocol so that people can use the app they wanted to connect to a single network. But that never happened in practice. Facebook may have built a bridge to implement XMPP, just in case it lifted off. But once it was clear that XMPP wasn&#x27;t going anywhere, it made sense to dump it. And then whatsapp came along, and it was a vastly superior chat app, and people used that and that was it.<p>Meta&#x27;s Thread may be different. Because this time, they probably know a little better. Thread connecting to Mastodon is a clear way for them to fill their feeds with desillusioned ex-Twitter users&#x27; content. So I am all for the blocking of Thread.
评论 #36873454 未加载
评论 #36875579 未加载
评论 #36880140 未加载
endgamealmost 2 years ago
A federated protocol on its own is not stable. As a matter of hardening these protocols against EEE attacks, federated protocol designs probably need to bake in a mechanism which provides incentives for people to run their own servers. I&#x27;m not sure exactly how you&#x27;d do this in a way which avoids Sybil attacks and doesn&#x27;t require cooking the planet. Ideally you&#x27;d want something like granting network privileges to a server proportional to the log of its user base?
评论 #36872976 未加载
dxsalmost 2 years ago
Then he says &quot;If you have found this article worthwhile, please share it on your favorite social media. You will find sharing links at the top of the page.&quot;<p>[Facebook] [Twitter] [Reddit] [Linkedin] [Hacker News]