My hot take is that the and 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.

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.

@helge @mauve

Sometimes I wonder, man. I've been working on building a library with a decent API for ActivityPub in Go for about 4 years and there's barely any developer interest. Sometimes I feel like I'm just pouring all that work into /dev/null. :(

Follow

@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 😅

Sign in to participate in the conversation
Mauvestodon

Escape ship from centralized social media run by Mauve.