brw

> As time goes on we are re-assessing the idea of users owning what is "collaborative data" (issues, PRs, etc.) on their PDSes - soon may come the day that an issue also lives on the knot as a source of truth, with an accompanying pointer record on user PDS to attest that it's theirs.

from https://tangled.org/tangled.org/core/tree/master/knot2

Remembering mayhem blog.metabrainz.org

7 brw 8 months ago 0 comments

Comment · 8 months ago

Most AUR helpers (well, the ones I've used at least, those being yay and pacaur) include the option to show a diff of PKGBUILD (and other provided files) for AUR package upgrades

Comment · 9 months ago

Yea I was pleasantly surprised by how simple the code is when I read it. Honestly a great example of what termbox2 is capable of. Very nice!

And now I know about termbox2, which looks very cool. Looking through the example projects[1] in the README I also found ictree[2], which does exactly what I was looking for yesterday (turning the output of `find` into an ncdu-like/interactive tree interface). I didn't manage to find something for that through googling around or asking LLMs, but thanks to you posting this here I did, so thanks!

[1] https://github.com/termbox/termbox2#examples

[2] https://github.com/NikitaIvanovV/ictree

Comment · 9 months ago

This one does not have a sign-up wall no, however some of their other articles do (e.g. https://www.404media.co/inside-the-telegram-channel-jailbrea..., also from today)

Comment · 9 months ago

I've asked dang about this before and he answered that it gets killed automatically because of the sign-up wall on some of their articles and that their articles weren't considered suitable for HN in the past:

> does that mean every 404media.co article submission gets killed immediately by software and has to be vouched for before people can vote/comment on it?

Yes.

> Is that the case for every site with a signup wall as a sort of penalty

It depends on whether there are workarounds. Last I checked, 404media.co didn't have those. Your counterexample proves that it does, at least sometimes. Or maybe they changed something?

I'm open to unbanning that site but I'd like to be more sure than I am that this will continue to be the case in the future; and I guess I'd also like to see a few more good (for HN) articles from there before unbanning it. For a long while, all the articles I saw were pretty shallow and fluffy.

That was in 2024 so perhaps it's time for a re-evaluation. I'll shoot him another message.

Comment · 9 months ago

What about changing the committer timestamp slightly until you find a match like https://github.com/mattbaker/git-vanity-sha? That would make it entirely invisible

Comment · 10 months ago

I totally agree! This is actually a very good summary of the value prop for atproto honestly. Definitely saving this. ("credible edit" -> "credible exit" I'm assuming.)

It certainly took a while for me to grasp how all the different components in the atproto stack function and work together, but the decoupling actually makes so much sense and I've also become a huge fan of it for all of the reasons you mention. It really feels like a natural extension of Web 2.0 to me.

Re: Tangled

Tangled does actually host a default knot server at https://knot1.tangled.sh. You should be able to select it when you create a repo?

But yes Tangled's component infrastructure is kind of unique. Only the social data (issues, PRs, comments, stars, follows, etc.) is stored in your data repository on your PDS. The git server requires a separate "knot" server.

It's described a bit more in-depth here[1]. As far as I understand it's basically just the git repo hosting part of Tangled's AppView, split off into its own thing to make it possible to self-host it. This means you stay in control of your repo data but also get the benefits of having an actual server with a remote git repo as the authoritative source for the purpose of collaboration, which is what people are generally used to when collaborating using git.

You're probably correct in that the "normal" way would be to have the Tangled AppView act as the git server, but have it store the remote git repo on your PDS. But as records in your PDS data repository are either JSON documents or unstructured blobs I guess it's kind of hard to use that for a git repo, which is largely filesystem dependent. I imagine it would require some kind of translation layer. Or something like git-bundle[2] maybe?

[1] https://wilb.me/3lzyhogtv2s2r

[2] https://git-scm.com/docs/git-bundle

Comment · 10 months ago

On that note there's also https://tangled.org built on atproto which (kind of?) solves that. You have one identity (the same one for all atproto apps) which you use to interact with any tangled repository (including those on self-hosted servers).

With its support for self-hosted CI runners it could also be a good alternative for people looking to move now that GitHub has decided to charge for those.

Comment · 10 months ago

Blacksky's AppView did get a mention in his 2025 predictions review[1], but perhaps it's not exactly considered "self-sustainable" yet? I haven't kept up with it in a while either so I'm also not sure on whether it is or isn't.

[1] https://www.timothychambers.net/2025/12/20/my-open-social-we... (at the very bottom)

brw

Recent submissions

Remembering mayhem b blog.metabrainz.org

Remembering mayhem blog.metabrainz.org