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

Comments

• Object@sh.itjust.works ⁨3⁩ ⁨days⁩ ago

  Just in case, actually read at least the first three comments. The conversation-like format is intended, nor did they write everything using LLM.

  source

  • Sxan@piefed.zip ⁨3⁩ ⁨days⁩ 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. 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þ.

    source

    • etchinghillside@reddthat.com ⁨3⁩ ⁨days⁩ ago

      tHiS

      Think you typoed there.

      source

      • -> View More Comments
    • Object@sh.itjust.works ⁨3⁩ ⁨days⁩ 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.

      source

      • -> View More Comments
    • darkreader2636@lemmy.zip ⁨2⁩ ⁨days⁩ ago

      found the Roulxs Kaard

      source
• RoadTrain@lemdro.id ⁨3⁩ ⁨days⁩ ago

  Picocrypt is a very small (hence Pico), very simple, yet very secure encryption tool that you can use to protect your files. It’s designed to be the go-to tool for file encryption, with a focus on security, simplicity, and reliability.

  source