Live data from Hacker News

Open Social

overreacted.io

111–120 of 409 posts

Re: Open Social

#111
post #62

Earlier quoted context omitted.

I am deeply concerned about the apathy people have towards the idea of ownership, openness and interoperability. It gives the idea that people just want to be fed TikTok and Instagram reels. Can you expand on this feeling? Why is it deeply concerning? Why should people care about the abstract concept of data ownership? People were totally fine when they had zero ownership or agency over media and they were fed TV, bo…

It matters because your posts aren’t just entertainment in the moment — they’re your history, your proof of existence online. Platforms treat them as disposable. If Instagram dies or bans you, your years of photos, writing, and connections vanish. Owning your data means your work and identity survive these issues, if you want.

An example: I have been a Swarm user for like, fifteen years. As soon as atproto has private records, I'll want to set up syncing that data into my PDS. It's kept track of a huge part of my life, and losing that would be sad.

Re: Open Social

#112
post #47

I'm starting to feel many of "next big Twitter to fill its power vacuum" projects are tackling the problem slightly wrong - they all perfect the Twitter feature set, then hit the wall with user growth and content deprivation chicken and egg problem. People gather where there are others and that's still around the rotting whale. That OpenAI timeline thing that just launched is more better approach, it solves content p…

...and this is why Nostr is different! You can build basically anything on it. A blog, a Twitter like application, a streaming service, messaging apps, the sky is the limit!

Here's a selection of things built on the protocol: https://nostrapps.com

Re: Open Social

#113
post #30

Wow, I always imagined Activitypub to be the better protocol and AT a cheap knock-off, but reading this article made me realize at is, actually, way better - primarily because multiple programs can access the same identity. This is really a great feature to have! This article was a real mind-opener for me.

[dead]

So email threads but on a web page, and filtered by subscription instead of senders/receivers. Clever.

How can I add this to my website?

How do you facilitate discovery? IE, what if I want to know about replies people have made without subscribing to their /social page?

Re: Open Social

#114
post #47

I'm starting to feel many of "next big Twitter to fill its power vacuum" projects are tackling the problem slightly wrong - they all perfect the Twitter feature set, then hit the wall with user growth and content deprivation chicken and egg problem. People gather where there are others and that's still around the rotting whale. That OpenAI timeline thing that just launched is more better approach, it solves content p…

...and this is why Nostr is different! You can build basically anything on it. A blog, a Twitter like application, a streaming service, messaging apps, the sky is the limit! Here's a selection of things built on the protocol: https://nostrapps.com

Nostr is not different from atproto in that sense because atproto also supports arbitrary applications (the article uses Leaflet and Tangled as examples). There's a good comparison of atproto vs Nostr: https://shreyanjain.net/2024/07/05/nostr-and-atproto.html

Re: Open Social

#115
I'm a little saddened to see that each app has it's own collection type, even if they are able to use each others collections. That means that apps will only interoperate to the extent that they are explicitly designed to.

One of the beautiful (but perhaps not that practically relevant) things about ActivityPub is that a Mastodon user can subscribe to a Pixelfed user without anything special being done. It's like if Twitter, Instagram, Reddit, YouTube, and Substack all automatically interoperated.

Re: Open Social

#117

I'm a little saddened to see that each app has it's own collection type, even if they are able to use each others collections. That means that apps will only interoperate to the extent that they are explicitly designed to. One of the beautiful (but perhaps not that practically relevant) things about ActivityPub is that a Mastodon user can subscribe to a Pixelfed user without anything special being done. It's like if…

See https://github.com/lexicon-community for the effort towards common lexicon

Re: Open Social

#118
Yes, it’s interesting but there is no way the instantiation of the protocol (Bluesky) remains free of investor influences. It would require a great deal of capital for anyone to recreate the “network” in such an eventuality. So yes, it’s cool but not really Open.

Re: Open Social

#119

I'm a little saddened to see that each app has it's own collection type, even if they are able to use each others collections. That means that apps will only interoperate to the extent that they are explicitly designed to. One of the beautiful (but perhaps not that practically relevant) things about ActivityPub is that a Mastodon user can subscribe to a Pixelfed user without anything special being done. It's like if…

See https://github.com/lexicon-community for the effort towards common lexicon

Yeah, atproto pushes this down to be a community/governance issue. Nobody is preventing apps from working out a common standard and supporting it. However, nobody is forcing them to do that either. So it will play out with natural dynamics. What atproto ensures is that there's a convention for strongly-typed foward-evolving schemas and how they get validated (and reverse domains specify the authority). But ultimately cooperation is up to the community.

Re: Open Social

#120

All of this is meant for 100% public data, right? Or is there a concept of visibility control? Can I create private communities, with data flowing just inside?

For now, yes, only 100% public data lives on the protocol (you can still, of course, augment protocol data with the stuff you hold in the DB). In the future, the plan is to also enable some types of private data on the protocol. See these recent notes from Paul on the state of things: - https://pfrazee.leaflet.pub/3lzhmtognls2q - https://pfrazee.leaflet.pub/3lzhui2zbxk2b

There is also a Working Group that just formed to push the envelope on private data / permissioned spaces

Links to my own efforts on this

- https://github.com/blebbit/atproto (fork)

- https://youtu.be/oYKA85oZc8U?si=DIf09hu8-REw-yHj&t=3758 (presentation I gave last week)

Post reply on HN