Work as an ActivityPub Relay #10

New issue

Open

opened 2020-05-17 23:10:46 +02:00 by schmittlauch · 0 comments

schmittlauch commented

2020-05-17 23:10:46 +02:00

Owner

relaying post IDs in ActivityPub

many implementations fetch a post that's just referenced by ID
but not all do, it doesn't appear to be an apparent consequence of JSON-LD
- e.g. FunkWhale doesn't do that
better idea: wrap this into a new activity (similar to Announce)
- problem: needs to be supported explicitly by each implementation

actor types/ relays

relay actors announce posts, but these aren't displayed as normal posts due to special bot flag (or similar)
- litepub-relay actors.py

interaction with AP server

have a relay running @ localhost, that represents a single actor for each hashtag
- that announces posts like a normal actor does
- subscribing to @hashtag@relay.localhost to follow #hashtag
relay also gets all outgoing posts, can then lookup the contained hashtags and do the forwarding
randomised batching and exponential backoff retry should still be implemented in the AP server

## relaying post IDs in ActivityPub - many implementations fetch a post that's just referenced by ID - but not all do, it doesn't appear to be an apparent consequence of JSON-LD - e.g. FunkWhale doesn't do that - better idea: wrap this into a new activity (similar to `Announce`) - problem: needs to be supported explicitly by each implementation ## actor types/ relays - relay actors `announce` posts, but these aren't displayed as normal posts due to special bot flag (or similar) - litepub-relay actors.py ## interaction with AP server - have a relay running @ localhost, that represents a single actor for each hashtag - that `announce`s posts like a normal actor does - subscribing to `@hashtag@relay.localhost` to follow #hashtag - relay also gets all outgoing posts, can then lookup the contained hashtags and do the forwarding - randomised batching and exponential backoff retry should still be implemented in the AP server