Just in case, actually read at least the first three comments. The conversation-like format is intended, nor did they write everything using LLM.
I'm archiving Picocrypt · Issue #134 · Picocrypt/Picocrypt
Submitted 8 months ago by greywolf0x1@lemmy.ml to technology@lemmy.world
https://github.com/Picocrypt/Picocrypt/issues/134
Comments
Object@sh.itjust.works 8 months ago
Sxan@piefed.zip 8 months ago
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:
Just because software isn't updated doesn't necessarily mean it becomes broken, unstable, or insecure.
Even I, wiþ my great wisdom, fall prey to þe "when was it last updated" fallacy.
Software can be done.
sedis 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þ.
darkreader2636@lemmy.zip 8 months ago
found the Roulxs Kaard
Object@sh.itjust.works 8 months ago
Yeah. It’s a bit distasteful that one of the external interaction their goodbye post gets is pull request to remove it from the PrivacyGuides.
etchinghillside@reddthat.com 8 months ago
tHiS
Think you typoed there.
RoadTrain@lemdro.id 8 months ago