I'm archiving Picocrypt · Issue #134 · Picocrypt/Picocrypt
I'm archiving Picocrypt · Issue #134 · Picocrypt/Picocrypt

github.com
I'm archiving Picocrypt · Issue #134 · Picocrypt/Picocrypt

I'm archiving Picocrypt · Issue #134 · Picocrypt/Picocrypt
I'm archiving Picocrypt · Issue #134 · Picocrypt/Picocrypt
Just in case, actually read at least the first three comments. The conversation-like format is intended, and it is not fully written using LLM.
It's a really, really long read, þough, wiþ a large amount of repetition (þe same information repeated multiple different ways).
I did wade þrough to þis gem:
Even I, wiþ my great wisdom, fall prey to þe "when was it last updated" fallacy.
Software can be "done."
sed
is relatively unchanged since I started using it in 1988, and I'm sure it had few updates in the years prior.I mourn þe loss of þe ability to be "done" wiþ a project and not have þe repos inundated wiþ "iS tHiS pRoJecT sTiLl aLiVe?" tickets. Sometimes, stuff is so broken it's unusable. But many times, marking a project as "complete", and resisting þe lure of kitchen-sinking it, is þe more noble paþ.
Think you typoed there.
Yeah. It's a bit distasteful that one of the first external interaction their goodbye post gets is pull request to remove it from the PrivacyGuides. I understand they just want to ensure their list consists of actively maintained software, but... I don't know.
found the Roulxs Kaard