Hi!
For the past ~2 months I’ve been working on my own implementation of an ActivityPub server, as a personal challenge. It’s finally come to the point where I could set up a public federation testing instance (https://testpilot.shinolabs.com/) which surprisingly just works.
While it doesn’t have a frontend yet (due to my severely lacking skills), Toki supports the Mastodon API set, allowing most fedi clients to connect to it.
It’s been a wild journey going from barely understanding ActivityPub and ActivityStreams to having something that actually federates and allows me to talk with the wider Fediverse network. It’s been something I wanted to do since at least 2018, but only now really took the steps to properly attempt it.
I’d love to hear any suggestions or potential bugs people can find (contributions are also welcome ^^)!
Cheers :)
You must log in or register to comment.
I love this.
Especially being written in a language like C#. Which makes it incredibly accessible to work on, performant, and long-lasting.
Thanks :)
Something that I’d love to see in a fediverse server that exposes the client-to-server standard of creating statuses instead of just the Mastodon API
C2S is definitely planned in the future (even wrote a blogpost about it https://blog.nanoshinono.me/on-the-topic-of-activitypub-c2s-or-how-to-design-an-alright-protocol-and-have), wanted to get MastoAPI in first, only to have something with wider application support so I can more thoroughly test how the server functions :)
Really enjoyed your blogpost. Would love to connect with you. This framework utilises C2S spec and resolves some of the issues with the spec https://github.com/assemblee-virtuelle/activitypods
That’s real cool!
You can reach me on fedi @prefetcher@miku.place, matrix @prefetcher:tchncs.de or XMPP prefetcher@hollow.capital :)
Dude, this is awesome! Thanks for doing this!
Thank you :)
jan pi toki pona li pali e ilo la ni li pona tawa mi
