huh, does the whole webfinger forwarding from your personal website to your mastodon instance thing no longer work, or is it taking a long time to propagate, or... third option
none of my masto servers can do @many@viscountexx.buzz and resolve it to @viscountexx fsr
lemme try from gotosocial?
nope
okay
why that is weird is that i can use https://viscountexx.buzz/.well-known/webfinger?resource=acct:@many@viscountexx.buzz and get the json file returned correctly
that should be all i need?
@MindmeshLink hm wonder if its because its doing a 301 redirect to the file first
sadiq@demonreach ~/dev> curl "https://viscountexx.buzz/.well-known/webfinger?resource=acct:@many@viscountexx.buzz" -I
HTTP/2 301
age: 0
cache-control: public,max-age=0,must-revalidate
cache-status: "Netlify Edge"; fwd=miss
content-type: text/plain; charset=utf-8
date: Sat, 13 Jul 2024 23:12:00 GMT
location: /.well-known/acct%3A%40many%40viscountexx.buzz?resource=acct:@many@viscountexx.buzz
@MindmeshLink like I'm thinking that particular code path doesn't know what to do with a 301 response instead of the JSON and doesn't follow the 301 redirect
@aescling @packetcat also true