@lan@meetiko.org btw @SolSoCoG@ieji.de I thought that the issue with parsing the two accounts on your instance was due to your server blocking requests from mine (I've been careful about generated traffic, you shouldn't see more than 5-6 requests to your API every couple of hours from the gaza-verified archive scrapers).
But now I see that the requests actually fail at DNS level (often because of timeouts), no matter which DNS I use:
❯ time nslookup ieji.de 208.67.222.222
Server: 208.67.222.222
Address: 208.67.222.222#53
Non-authoritative answer:
Name: ieji.de
Address: 185.237.100.33
Name: ieji.de
Address: 185.237.100.34
Name: ieji.de
Address: 185.237.100.35
;; communications error to 208.67.222.222#53: timed out
;; communications error to 208.67.222.222#53: timed out
;; communications error to 208.67.222.222#53: timed out
;; no servers could be reached
nslookup ieji.de 208.67.222.222 0.01s user 0.01s system 0% cpu 15.046 total
Are you aware DNS resolution issues for your instance?
L
