#Smithereen update. Groups are more-or-less done, as a proof of concept. They should federate in theory, but I haven't tested any of it yet because I'm too lazy to set up a second internet-facing instance and Mastodon isn't very much compatible with what I'm doing here.
That said, there's still a lot of work ahead. Admin/moderator features, public admin list, events, invitations...
You can actually try joining the group by following it from any ActivityPub server: @wow_look_a_group, but it doesn't post anything itself so nothing will show up in your feed. It works by forwarding LD-signed activities of people posting things on the wall. Oh, and I should make /groups/X/wall return a real collection of posts. And then will be the time to write my FEP about publicly-appendable collections.
@felix first thing I tried was to get an actor for a community but this request returned an HTML page. Posts (/post/222) and users (/u/galo) do the same. Am I doing it wrong?
@grishka you have to use `application/activity+json` for the accept header. tbh i'm quite confused about all the different ones, and dont know which ones we should support or not.
@felix Mastodon sends this:
Accept: application/activity+json, application/ld+json; profile="https://www.w3.org/ns/activitystreams", text/html;q=0.1
This also returns HTML. application/activity+json by itself works. Many web frameworks parse the Accept header and allow specifying different handlers for different content types. I only had to specify it twice to cover all possible cases:
@grishka actually I think we support the exact headers defined in the activitypub spec. But not the one you mention, and I dont know if our web framework supports parsing the accept header.
Anyway, here are our docs for federation:
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!