You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, Friendica allows setting different actor names for the server actor, thus making it impossible for instances with a "wrong" server actor name to connect to Activity-Relay (using LitePub relay style).
I cannot find any documentation or speficication on ActivityPub relays, is it really necessary that actors be named relay?
The text was updated successfully, but these errors were encountered:
The current implementation requires the following server actor to have an id ending in
/relay
:Activity-Relay/api/resolver.go
Lines 185 to 188 in 7f942e7
However, Friendica allows setting different actor names for the server actor, thus making it impossible for instances with a "wrong" server actor name to connect to Activity-Relay (using LitePub relay style).
I cannot find any documentation or speficication on ActivityPub relays, is it really necessary that actors be named
relay
?The text was updated successfully, but these errors were encountered: