That's real cool!
You can reach me on fedi @[email protected], matrix @prefetcher:tchncs.de or XMPP [email protected] :)
Honestly the name just kinda randomly crossed my mind as I had just bought a toki pona book back then. I thought it fit and I adopted the name for my project :)
Glad people like it too!
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 :)
Toki - A C# Fediverse server.
A C# Fediverse server. Contribute to purifetchi/Toki development by creating an account on GitHub.
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 :)
Hi, thank you so much!!
For learning ActivityPub I've used a ton of resources actually, but the ones that were the most helpful to me were:
- https://tinysubversions.com/notes/reading-activitypub/ (reading the specs)
- https://socialhub.activitypub.rocks/t/guide-for-new-activitypub-implementers/479 (general activitypub knowledge)
- https://seb.jambor.dev/posts/understanding-activitypub/ (understanding the protocol flow and quirks of software)
- https://iceshrimp.dev/iceshrimp/iceshrimp.net (code examples from a real project)
- https://blog.joinmastodon.org/2018/06/how-to-implement-a-basic-activitypub-server/ (implementing a very basic activity sending flow and HTTP signatures)
additionally
- https://docs.joinmastodon.org/ (the mastoapi implementation)
- https://oauth.net/2/ (oauth2 spec for mastoapi)
and a ton of code reading of other AP projects :)
Toki - A C# Fediverse server.
A C# Fediverse server. Contribute to purifetchi/Toki development by creating an account on GitHub.
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 :)