@Gargron OK, so have some encouraging news. Changing the Ruby version seems to fix the DNS lookups. when I test it out now I get the following:
https://pastebin.com/k2LNCfKz
^^ on the 2nd to last line, it says the table size is empty which is good news.
Unfortunately the workers are still "stuck", but the TID# is much longer than before. I'm assuming to manually try this in the ruby console, would it be correct to test it with:
ActivityPub::ProcessingWorker.new.perform(106...)
?? (or no)
@jeff :AAAAAA:
I don't really know where to go from here. I suppose you could keep trying to run those things manually until one of them gets stuck in the console, in which case we might learn where it gets stuck.
Or maybe the server is cursed
To answer your question, yes