nickwitha_k (he/him)

  • 1 Post
  • 17 Comments
Joined 2 years ago
cake
Cake day: July 16th, 2023

help-circle

  • I get it but don’t “get it”. I suppose I tend to think in terms of small groups rather than manipulating crowds of rubes that have been keeping in a state of perpetual outrage through decades of right-wing talk radio and TV, and are so desperate to be told what to do that P. T. Barnham would say “Hey now, that crosses a line.”

    I’d still suggest that it might be less charisma and more an audience so primed that they’re near auto-ignition being subjected to a Hitler-fanboy who picked up a few things from professional wrestling.

    Then again, I also don’t “get” celebrity worship and numerous other NT things.




  • I’ve done a lot of SysAdmin and DCOps stuff in the past so, thought I’d give you some plausible suggestions (haven’t dug deep into Lemmy DB stuff and DNS/Federation of the stack, so not sure all is practical).

    Scenario 1 - Preserve and merge when access is restored

    Setup

    • Spin up two VMs/VPS (or one that has enough grunt for two Lemmy servers). Call them robak.slrpnk.net and slrpnk.net and point DNS appropriately.
    • Pull federated content from other instances and place it on robak, set as read-only.
    • Sync important comms to (new) slrpnk.net without content.
    • Allow users to sign up, vetting as possible (all mods). Keep a list of those that are vetted (call it vetted.list). Inform all users that any non-vetted users will have their content dropped when access is restored.

    Merge!

    • Once access is restored, ensure that (old) slrpnk.net is set to read-only.
    • Schedule a maintenance window (announce more time than you are likely to need).
    • During the maintenance window, put (new) slrpnk.net into R/O, or just block external access.
    • Query the db on (old) slrpnk.net for all users.
    • Subtract the vetted users from vetted.list from the list.
    • Drop all records from the resulting list of non-vetted users from (new) slrpnk.net.
    • Insert the records from vetted and new users (those without conflicts) into the DB on (old) slrpnk.net.
    • Validate that everything is working
    • Cut over DNS and spin down the new VMs/VPS.

    Scenario 2 - Server is in DC or Admin able to facilitate access

    • Get a db dump/backup.
    • Spin up temporary slrpnk.net on a VM/VPS.
    • Use backup of temporary server to restore data to original, when possible.







  • Gabapenten has can have serious side effects for some people, dont just go get some and go “o we gonna be good.”

    FTFY. Everyone’s brain chemistry is different. For some, it can be a lifesaver in low doses for anxiety, for some (like me) it can be used as an adjunct to acetaminophen/paracetamol in a combination that is more effective for pain than opioids (had a minor hemorrhage in an adrenal gland - not fun), and for others it can cause extreme depression and other behavior changes.

    Noone should take it without the supervision of a medical professional.