Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Federating roof-and-bed requests over ActivityPub #20

Open
Houkime opened this issue Dec 13, 2022 · 0 comments
Open

Federating roof-and-bed requests over ActivityPub #20

Houkime opened this issue Dec 13, 2022 · 0 comments

Comments

@Houkime
Copy link

Houkime commented Dec 13, 2022

... which can largely be done via piggybacking on public infrastructure.

Reading requests

Any mastodon server has an api endpoint like this

https://mastodon.social/api/v1/timelines/tag/cats

If there are posts on Fedi (Mastodon or not!) with #cats hashtag, they will be in this feed provided that at least one mastodon.social user was following to the source of this post, or boosted it, or followed someone who boosted.
Polling two or three servers should get one a good percentage of all posts tagged with #cats
For roof-and-bed, we can try using some new tag like #SleepyBikeNeedsRest.
We will poll for this tag in the app or frontend, filter locally for posts that comply with some criteria (like, which include a location which is nearby), and that's it.
Humans can write requests from their Mastodon, Pleroma, Misskey and whatnot by hand and they will be visible to sleepybike users, provided they comply.

Posting requests

If we want posts to be authored by a Solid account and retranslated to the fediverse, we have options:

  • Solid pod software is altered to support ActivityPub. Fediverse-dwellers can subscribe to Solid pods/solid users and see roof-and-bed requests in their timelines.
  • A satellite program subscribes to Solid pod updates via Solid-provided API and constructs Activitypub posts that can be fetched by Fedi. May reside on a different server than the pod.
  • A satellite program directly observes the state of Solid database backend, filters for relevant updates, and constructs ActivityPub posts to be fetched. Needs to reside on the same server with the pod but does not need cooperation from Solid.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant