Any computer program can be designed to run from a single file if you architect it wrong enough! I wanted to create the simplest possible Fediverse server which can be used as an educational tool to show how ActivityPub / Mastodon works. The design goals were: Upload a single PHP file to the server. No […]
@Edent nice, I was thinking of writing a simple #activitypub server for a single account that would use an #rss xml file as a source. Pretty sure this has already been done anyway.
@Edent in the client I use (Megalodon), it opens correctly. However, I get what you're discribing with some posts from users of other fedi servers. I did not yet make the effort to find out which ones, though.
@Edent Nice work! It looks similar to my own self-study one-file ActivityPub server in Python. I think the structure of the protocols lends itself to implementing single-actor servers as a learning experience.
I know you're saying it's quick & dirty in some ways, but if it's intended as a learning tool for others, do you want feedback on it? There's one bad assumption in there that I think would be better if it was cleaned up.
@Edent Then I'll make it short: The assumption that a server has a shared inbox at /inbox does not generalize, as even the existence of a shared inbox is not mandated by anything.
What you'd need to do is when someone follows, you fetch their actor data and store at minimum their inbox and/or shared inbox.
For sending, I build a set of all shared inboxes that occur more than once, and use the individual inboxes for the rest.
@julian interesting! Thanks.
How difficult do you think that is to implement? I'm wary of making something too complicated - but I'd like to point to a simple solution if possible.
@Edent great stuff; I'd seen the previous Symfony-based iteration on Github, and my first thought was "I bet you can get that down to a simple single file install" 🙂
Add comment