111–120 of 162 posts
I have no idea what Gleam or Tangled is, so for me this headline might as well be an article from The Onion satirizing HN. I also refuse to believe any of these two things are large enough, like say Postgres, that one can claim everyone should know it. Surely writing an informative headline for ”hackers in general” can’t be that difficult.
Picture this: someone “moderates” your bluesky account for some unrelated reason and you’re no longer able to manage your own source codes…
Isn't that the same as Github "moderating" my Github account for some unrelated reason? Also, since Bluesky is decentralised, can't I just host my own data?
Bluesky’s decentralisation is a “yes but it’s complicated and you can’t _just_ do anything”. I like that they’re experimenting with “apps” but source control feels a bit too far.
I'd love to hear why they chose a VC funded forge over e.g. Codeberg. Doesn't really fit the 'friendly language' claim IMO
"being on tangled" really just means "publishing sh.tangled.* atproto records" the beauty of atproto means that you are in no way tied to the VC funded company behind the web app available at tangled.org. you merely publish your git repository using a protocol that this app will pick up and present with a nice UI any other app that speaks atproto and looks at those same sh.tangled.* records will be able to access eve…
This is false: you’re tied to both tangled (unless you want to self host a forge, which if you did you wouldn’t have picked tabgled) and Bluesky for your login to keep working (unless you want to self host a complex constellation of social media components).
Earlier quoted context omitted.
"being on tangled" really just means "publishing sh.tangled.* atproto records" the beauty of atproto means that you are in no way tied to the VC funded company behind the web app available at tangled.org. you merely publish your git repository using a protocol that this app will pick up and present with a nice UI any other app that speaks atproto and looks at those same sh.tangled.* records will be able to access eve…
> the beauty of atproto means that you are in no way tied to the VC funded company behind the web app This is false: you’re tied to both tangled (unless you want to self host a forge, which if you did you wouldn’t have picked tabgled) and Bluesky for your login to keep working (unless you want to self host a complex constellation of social media components).
Earlier quoted context omitted.
this is like complaining that you can't login anywhere because google banned your gmail account...
And we don’t complain about that because nobody uses “sign in with google” for mission critical stuff. It’s absolutely a choice to tie all your things to a single corp.
Earlier quoted context omitted.
I’ve been testing Radicle and it’s more focused on the distributed protocol for federating git repos, I.e. the data plane. The social / coordination control-plane angle is really thin, following users and repos goes by opaque IDs, etc. It could be a better solution for agents that don’t bounce off such mundane complexity. It could be better for private repo federation (eg private collective or agent swarm.) I’m inter…
Issue and PR content are not social artifacts, they belong in the repo or at least its hosting instance. Likes and activity feed are the sort of thing that belongs in the social layer.
Earlier quoted context omitted.
"being on tangled" really just means "publishing sh.tangled.* atproto records" the beauty of atproto means that you are in no way tied to the VC funded company behind the web app available at tangled.org. you merely publish your git repository using a protocol that this app will pick up and present with a nice UI any other app that speaks atproto and looks at those same sh.tangled.* records will be able to access eve…
> the beauty of atproto means that you are in no way tied to the VC funded company behind the web app This is false: you’re tied to both tangled (unless you want to self host a forge, which if you did you wouldn’t have picked tabgled) and Bluesky for your login to keep working (unless you want to self host a complex constellation of social media components).
this is true today only because nobody has made an alternative "frontend". but the data is there, public, for anybody to see. they can't take it from you even if they really wanted to. in fact, tangled has been working on making it easier for such third-party "frontends" to exist: https://blog.tangled.org/bobbin/
> and Bluesky for your login to keep working
you seem to be misinformed. "your login" is handled by your PDS, whichever it is. self-hosting a PDS doesn't require you to host anything beyond a sqlite database and a websocket connection. they are easy and very cheap to host, nothing like a "complex constellation of social media components"
today you can already 100% use atproto apps without having any ties whatsoever to bluesky:
- data: non-bluesky-hosted pds (either your own or some other host) for your data
- identity: the did:plc directory is managed by an independent swiss association, but you can even use did:web if you really want to
- relays/apps: blacksky is an example of a fully independent stack
https://discourse.ubuntu.com/t/gleam-and-the-value-of-small/...