Earlier quoted context omitted.
I have zero idea what your link has to do with the original post, which seems to just be the Gleam language on some new version control host?
Exactly, even if one doesn't know about either of these things (gleam & tangled), all it would take is one or two searches or even better they just visit the homepage. I suppose people have become so used to reading llm generated bluff that simple things don't appeal/make sense to them anymore.
Gleam Is Now on Tangled
151–160 of 162 posts
Re: Gleam Is Now on Tangled
#152I 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.
If you click on the title, it will tell you more. Gleam has had many dozens of front page posts here. Tangled is a niche GitHub alternative, but has also had previous history.
Re: Gleam Is Now on Tangled
#153What the fuck is this? It's a git repo. The interface pisses me off
Re: Gleam Is Now on Tangled
#154This post needs a bunch more context; right now it's only immediately accessible to people who don't need the announcement [1]. [1] https://knowyourmeme.com/memes/curtains-for-zoosha
Re: Gleam Is Now on Tangled
#155Earlier quoted context omitted.
Headline reminds me of Poob. https://knowyourmeme.com/photos/3056633-poob-has-it-for-you
Makes me nostalgic for the old days (2000s and early 2010s) when everything was WordWord. Facebook, Instagram, Myspace, Dropbox, etc. Now it's just normal words without vowels. The Grindrification of naming.
Re: Gleam Is Now on Tangled
#156Earlier quoted context omitted.
Tangled is also VC funded, something to consider.
It doesn't really matter, you can host your own knot (git backend), spindle (CI/CD worker), and there are already alternative apps to access the same public, consumable records without centralized infra: https://untangled.wisp.place/
Re: Gleam Is Now on Tangled
#157Earlier quoted context omitted.
It doesn't really matter, you can host your own knot (git backend), spindle (CI/CD worker), and there are already alternative apps to access the same public, consumable records without centralized infra: https://untangled.wisp.place/
It matters a lot. As seen with GitLab and countless other projects.
If Tangled the company made a decision you didn’t like, you could continue to use the software and keep your social graph, repositories, etc. without them. That’s simply not true with GitLab, it’s a closed ecosystem by instance. Tangled is not that.
Re: Gleam Is Now on Tangled
#158Earlier quoted context omitted.
We all know why... as a condition of some monetary support. It does give a sour taste, really shows what core values are: money > community. I'll just focus on using elixir for a project instead.
No I don't know this. Do you have any source for that?
Re: Gleam Is Now on Tangled
#159Earlier quoted context omitted.
I agree (with caveats and not as strongly), but claiming no utility is a bit much.
> They reinvented a worse Twitter (it failed) Bluesky has 9-11x times the number of total users as Twitter did three years after its launch. It has somewhere between 15-20x the number of MAUs as Twitter had. It has not failed even a little bit. > Now they're trying to reinvent a worse GitHub (not off to a great start) You seem to think this is the same group of people who started Bluesky. You’re wrong. Not only that,…
Re: Gleam Is Now on Tangled
#160Earlier 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.
It does look like Tangled currently does those in a weird way, ties to the issue owner rather than repo - but here’s a proposal to fix: https://leaflet.pub/p/did%3Aplc%3Axasnlahkri4ewmbuzly2rlc5/3...
Doing some weird distributed join across all your committer’s PDSs seems a bit weird, and the semantics of cross-referencing issues seems gnarly in that world.
I think I’d be OK to model a PR as a tweet, it’s more owned by the sender. But issues seem like they should be owned by the repo for sure.