Oops

Context

You're viewing a single thread.

30 comments

This actually sounds pretty similar to what happened to feddit.de - the former main admin/infrastructure owner stopped being active, and eventually the active admins had to move to feddit.org when technical difficulties sprang up that they couldn't solve with their access level.
~~Only difference is that feddit.de didn't go up for auction, it's still running just with minimal user interaction.~~ Apparently it was somewhat recently deactivated.
- Only difference is that feddit.de didn’t go up for auction, it’s still running just with minimal user interaction.
  Doesn't appear to be, there aren't any IP addresses associated with feddit.de.
  sh
  
  ~> dig feddit.de any ; <<>> DiG 9.18.30 <<>> feddit.de any ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 49617 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;feddit.de. IN ANY ;; Query time: 780 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) (TCP) ;; WHEN: Tue Feb 11 21:51:08 GMT 2025 ;; MSG SIZE rcvd: 38
  
  You know it's the Fediverse when you see people using dig instead of nslookup.
  
  No need to point a finger at anyone.
  
  I just don't dig the way nslookup outputs its answers.
  
  It is the most unparseable. And are you using a Unix or Heil-Tim Cook-flavored variety?
  Unrelated kinda but I use nslookup because I thought it was more widely supported out of the box than dig?
  
  I use a GNU system, which as we all know isn't Unix.
  Unrelated kinda but I use nslookup because I thought it was more widely supported out of the box than dig?
  I don't think I've ever been in a situation where nslookup was available but dig wasn't. On Fedora, they're in the same package.
  
  Oh, that's new. Was definitely still running last time I checked 1 or 2 months ago.
- it's still running
  It totally isn't.

30 comments