• 0 Posts
  • 8 Comments
Joined 1 month ago
Cake day: June 30th, 2025
  • CocaineShrimp@sh.itjust.workstoOpen Source@lemmy.ml•[app] SOS flashlight
    3·
    5 days ago

    To add onto that: dots are short, dashes are long. So if you’re using a flashlight, or something else, it would be:

    short, short, short, long, long, long, short, short, short

    Then include a small pause (1-3 seconds) once you’ve sent the SOS before repeating. You want to continuously repeat this for as long as you can until you know someone’s received your message.

  • CocaineShrimp@sh.itjust.workstoFediverse@lemmy.world•We are mainstream now🔥English
    241·
    5 days ago

    As much as I want to see Lemmy and the rest of the fediverse flourish; at the same time, I hope it doesn’t.

    Once the fediverse becomes popular and gains main-stream attention, the billionaires and political twats will flock towards it and try to monetize it; Morons will flood the fediverse with memes and AI slop worse than !lemmyshitpost@lemmy.world (you know what you’ve done); corporations will start spamming ads for their shitty products; and scammers will start setting up bot nets to coerce users into sending them money to their new AI waifus.

    The unbearable weight of all the garbage entering and attacking the fediverse will drive moderators out the door, leaving servers as wastelands of junk. No longer interesting, no longer human. Just trash, like how Reddit, Facebook, Instagram, etc… are today.

    So yes, I’ll welcome friends and family into the fediverse with open arms. But I really hope we don’t start getting too many shout outs

  • CocaineShrimp@sh.itjust.workstoSelfhosted@lemmy.world•Upgrading Paperless-ngx several revisions behindEnglish
    6·
    16 days ago

    I haven’t gone through your specific case, but generally what I do when doing a major update with potentially breaking changes:

    • Read the upgrade guides, if they have them. Some devs will put them out if they know their users will encounter issues when upgrading. If they don’t have an upgrade guide, there might be some in the change logs. Going from 1.17.1 to (assuming) 2.x.y, check the change logs at 2.0.0.
    • Backup everything. I’d recommend doing this on a regular basis anyway.
    • (If you’re running it in a docker container) Setup a second instance, restore the backup, then run the upgrade. You’ll be able to check to see if it breaks at all. If it works, you can just destroy the old one and use the new one
    • (if you’re not running it in a container) with the backup, try upgrading. If it breaks, you should be able to uninstall & reinstall the old version, then restore the backup
  • CocaineShrimp@sh.itjust.workstoLinux@lemmy.ml•OS Backup - what should and what should not be backup'd?
    16·
    26 days ago

    I usually only keep documents and media. Programs can be redownloaded and reinstalled (and it might be better to reinstall them in case you move to a new OS anyway to ensure compatibility).

    For docker specifically, only keep stuff that’s specific for your instance; which you normally setup as an external volume anyway. Docker is designed such that you should be able to nuke the container, and all persistent data is restored via an external volume on the host. If you’re not doing that, you should immediately go and set that up now (to get the data out safely, setup a volume connection such that the container path is new - that way you don’t accidentally destroy what’s there, copy the stuff you need out, then readjust the path so it’s correct)