this post was submitted on 07 Jun 2025
461 points (96.9% liked)

Technology

70997 readers
3419 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
L4s@hackingne.ws
461
Slrpnk instance is down till mid July; they might relaunch their server on piefed. (programming.dev)
submitted 22 hours ago* (last edited 22 hours ago) by Pro@programming.dev to c/technology@lemmy.world
77 comments fedilink hide all child comments
 

Source. Thread.

you are viewing a single comment's thread
view the rest of the comments
[–] nickwitha_k@lemmy.sdf.org 5 points 10 hours ago

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.