@Claire one more question.... did something change recently in the way you serve instance actors? I'm getting a lot of GoToSocial saying instances are unauthorized, because I can't dereference the instance actor....
For example, I can federate with ondergrond, because the instance actor is dereferencable: ondergrond.org/actor (3.3.2), but I can't federate with, say, writing.exchange, where the actor doesn't seem to be dereferencable: writing.exchange/actor
Just to clarify, GoToSocial has the equivalent of mastodon's secure mode always being 'on': if it can't validate a signature coming in, it won't accept the activity
fuchsiaaaaaaaaaaaaaaaaa
@dumpsterqueer @Claire the big 3.4.6 change was something with the JSON-LD, maybe that's messing with things?
@meena @f0x @Claire it would make sense based on the symptoms i'm seeing though: the fact that this instance can still communicate with instances it was already federated with, even if those instances are running newer versions (without a dereferenceable instance actor) can be explained by the fact that gts.superseriousbusiness.org already has the actor keys cached in the db, so it doesn't need to look them up, whereas a new instance does (and hence fails)
@dumpsterqueer @f0x @Claire what if the key changes?
or is that not defined in the spec?
@f0x @dumpsterqueer @Claire *mumbles something about backwards compatibility*