My hot take is that the #ActivityStreams and #ActivityPub specs are fine. Having some more standards for working with groups might be nice but honestly I'm happy with how much folks are able to do already and how many implementations are out there that can work together. This is from a few months of working on a new implementation. Honestly there's been a decent amount of docs spread around the place to go off of.
@mariusor @helge Are you using your library for yourself and your own interests? That's the best way to do open source IMO. Whether a thing is "popular" or not is secondary. As long as it's useful to *someone* it's a win IMO. Unless you want to makey money off of it I guess, but that's a whole other ball game 😅
@mauve there's links in my bio. The main packages for the library are under the https://github.com/go-ap umbrella.
You should do a (video) tutorial on how to start developing with go-ap for the Fediverse. Taking the first steps is currently hard.
I really want someone to do a video tutorial on developing for the Fediverse. But that might be personal bias. A text how to set up and interact with Mastodon would be fine too.
@helge right now I'm focused on making it easier for web publishers to use this stuff and with all our work being in the open for devs to peek at and reuse 🥰
My wip blog post about it: https://github.com/RangerMauve/blog.mauve.moe/pull/1
Tbh these two guides and peeking at my mastodon data got me all I needed. :P
https://paul.kinlan.me/adding-activity-pub-to-your-static-site/
https://blog.joinmastodon.org/2018/06/how-to-implement-a-basic-activitypub-server/
It was honestly trivial compared to some of the stuff out there 😅
That's really not a hot take. It's a pretty chill take.
For me the question is: Can you do something to make the entry of new developers to ActivityPub easier?
I wrote this tutorial and it seems to have helped some people. Creating a better developer experience will hopefully attract new people and thus great ideas.