Live data from Hacker News

Open Social

overreacted.io

91–100 of 409 posts

Re: Open Social

#91

99% of social media users don't care about any of this. If it's one extra step or configuration they need to learn, or includes a word like "protocol" that they need to understand, they won't use it.

That's one reason why Bluesky has gained a lot of traction. All of this is under the surface, not something you need to care about unless you want to.

I would contend not all of it is under the surface

The Bsky team regularly highlights other apps, custom feeds, and moderation choice

Re: Open Social

#92
post #45

Earlier quoted context omitted.

How about DNS on a blockchain?

https://docs.ens.domains/learn/protocol/ Supporting DNS all up should be possible but organizing the other decentralized services (compute, storage) is the hard part

The name service is easy, namecoin did it more efficiently than ENS a decade ago.

The decentralized services need not be attached to some blockchain due to the resource constraints. But there are examples like Filecoin and such.

Re: Open Social

#93
post #2

This is such an important idea -- and yet I feel like the hyper-individualized "bluesky" implementation pictured is a less good practical idea than Mastodons more "server/host" way of doing things. I get that theoretically the two should be similar or even identical in practice, but I feel like the way Bluesky goes so hard at "literally individuals maintain control over their own stuff" is kinda too hard for most, an…

In my view the atproto approach asks the users to make fewer required complex decisions, but gives them the freedom to make many voluntary ones. If someone wants to use a particular application, they basically just need to sign in. If they don't have an existing ATProto account, they can just make one, in the flow of the application they're signing into. Later they can chose different clients, or different infrastruc…

I mean, this might depend on who your intended audience is? As perhaps pie-in-the-sky my desire is, I'd like to see one of these things replace twitter (as opposed to smaller communities.)

And it seems to me that the more frictionless model is the one that looks like something people are used to; just "sign up with a thing."

That does leave the interconnection to the servers and others, but that may be how it has to be?

Re: Open Social

#94

Sadly, it's hard to imagine a world where something like this will ever catch on. The target audience for "traditional" social media is very different from the niche of people who want decentralized social media. Most people just use social media as a means to an end and don't really care about the systems behind it. If the answer is that most people should just make a bluesky account, that defeats the whole purpose…

[flagged]

u mad?

Re: Open Social

#95
post #43

Earlier quoted context omitted.

A free of cost TLD is probably not practical. There are some special things that go along with being a TLD and being in the public suffix list: https://github.com/publicsuffix/list If you drop the TLD part though, you can do whatever you want with any domain you want, up to and including handing out free subdomains to anyone who asks. As usual, though, if you try to do this, the dark internet will make you regret it…

Why can't it be a keypair like a .onion domain? DNS is not a sybil resistance mechanism

Because .onion isn't a DNS domain. It uses the same syntax but you have to be on Tor for it to work and it does something completely different than DNS resolution. I read the original question as specifically about having top-level domains, not "something like domains that works on a special network".

Special networks can do as they like, but then they won't be DNS.

Re: Open Social

#96
post #2

This is such an important idea -- and yet I feel like the hyper-individualized "bluesky" implementation pictured is a less good practical idea than Mastodons more "server/host" way of doing things. I get that theoretically the two should be similar or even identical in practice, but I feel like the way Bluesky goes so hard at "literally individuals maintain control over their own stuff" is kinda too hard for most, an…

I've tried to lightly allude to Mastodon here: >Social aggregation features like notifications, feeds, and search are non-negotiable in modern social products. Conceptually, Mastodon is a bunch of copies of the same webapp emailing each other. There is no realtime global aggregation across the network so it can only offer a fragmented user experience. While some people might like it, it can't directly compete with cl…

Yeah, the goals of atproto are REALLY GOOD ones. The only thing I'm skeptical of is the extent to which "centralized state of the world" really needs to be a core of the protocol -- and does that sort of thing introduce the same kind of centralization that makes it vulnerable to enshittification?

My gut is that IT DOES. Put differently, there's presently nothing about TECH of the Mastodon model that prevents building tools that achieve similar "centralized everything" goals on top of Mastodon; only, you know, people and trust, the easiest part .

Mastodon's probably the best long-term model and it's email that makes me think that.

Re: Open Social

#97

I feel very conflicted about this work. On one side I find these ideas extremely compelling. This is aligned with the Indie web body of work, that pictures anyone having a personal website of their own content and ownership over that. And this page an article are beautifully put together. On the other hand, we haven’t really seen a lot of developers adopting these standards for their own projects (like using this for…

There's still some more work to do to make the developer experience simple enough that it's a no-brainer for people to pick ATProto up in anger. But there's a lot of work developing on that front, and the next 6-12 months will be super exciting to watch. The longer story is that most people don't understand that ATProto is more than just Bluesky, and the usecases are wayyyyyy broader. That's going to take more time t…

Absolutely. In fact I’d love for my startup to run our own atproto instance separately from Bluesky, but it still looks like quite a lift. Lmk if you have some recommendations.

Basically our thing would give that ecosystem the ability to have personal pages that can look like Patreon, YouTube, Instagram and others

Re: Open Social

#98
post #71

Earlier quoted context omitted.

I'm not sure what that means, can you give examples of good and bad incentive structures in this context?

sure, https://x.com

So mysterious, so edgy. Hope you at least feel better, because you've utterly failed to communicate a coherent idea.

Re: Open Social

#99

I feel very conflicted about this work. On one side I find these ideas extremely compelling. This is aligned with the Indie web body of work, that pictures anyone having a personal website of their own content and ownership over that. And this page an article are beautifully put together. On the other hand, we haven’t really seen a lot of developers adopting these standards for their own projects (like using this for…

You are correct, and yet depends on ourselves to popularize and make this tech happen. Maybe, just maybe a newer startup out there will have a CEO/CTO that is deeply influenced by open social and delivers a success app that reaches the masses. One never knows, but for sure it won't happen when we do nothing.

Has the experience of spinning up an instance been simplified?

Re: Open Social

#100

Earlier quoted context omitted.

That's one reason why Bluesky has gained a lot of traction. All of this is under the surface, not something you need to care about unless you want to.

I would contend not all of it is under the surface The Bsky team regularly highlights other apps, custom feeds, and moderation choice

The important part is that you don't need to know about any of this to use the service. Of course, the protocol enables user-level features.
Post reply on HN