For people working on ActivityPub implementations I just wrapped up a nice chat with the folks of https://homebrewserver.club in Amsterdam (@manetta @rra and others). It was all via document editing and you can read the whole thing starting at line 188 in this document
It's a bit disorganized and I think they are going to digest it into a blog post or similar but for now this may be helpful to people who are puzzling their way through ActivityPub implementation!
It's weird that the Mastodon server and the web-based ActivityPub reader that it comes standard with are the same code base and the same project with the same name. It makes it hard to communicate certain concepts like how in theory you could have an account on Mastodon dot social and follow literally only pleroma users
I want ActivityPub (and the likes) to evolve to a point where I can have something like @aaronpk has on his personal site as https://aaronparecki.com/aaronpk
Darius Kazemi
https://social.tinysubversions.com/@darius
•
Aug 9
@aaronpk oh awesome. Can you share the code with me? I am writing my own extremely stripped down server that is meant for bots *only*, so it lets you create new accounts, make/delete posts, and it accepts follow requests, and that's basically it! (also allows the creation of new accounts via API because bots) Anyway, another dirt-simple reference implementation would be a huge help since there are not good "here is what ActivityPub messages should look like" resources I can find
Darius Kazemi
https://social.tinysubversions.com/@darius
•
Jul 31
One fun thing I just learned is that ActivityPub has almost no implementations, certainly no barebones modules I can tell except maybe https://github.com/Arkanosis/microstatus ? except I can't even tell if that is a module or a full-fledged server or both or what
I am a professional software developer and this shit is so byzantine, no wonder the indie web is having such a rough time
XRay, the library that I use to parse URLs to show comments, now supports parsing direct Microformats JSON, ActivityStreams 2.0, as well as finding a rel=alternate link and parsing data from that instead!
This means I now get great results when parsing Mastodon or other ActivityPub links, and this is also the first step in what I hope will result in fixing the Microformats situation for WordPress, since a WordPress plugin will be able to generate Microformats JSON and advertise that in a rel=alternate link.
Next up is updating Aperture to take advantage of these new features!
Just wanted to chime in here again to say that my implementation now also includes a rel=alternate link to the ActivityStreams JSON representation of the page.
e.g.
https://aaronparecki.com/2018/07/12/10/indieauth
<link rel="alternate" type="application/activity+json"
href="https://aaronparecki.com/2018/07/12/10/indieauth.as2" />
That brings this up to at least 3 implementations that support it, making it a good candidate to incorporate into the spec.
Reposting @aaronpk's interface they implemented for #ActivityPub mentions in #p3k (https://indieweb.org/p3k) for better visibility and inspiration. Bridging the #indieweb and #fediverse is so exciting. Lets hope this trend continues infinity!
nightpool
https://github.com/nightpool
•
Jul 11
It probably wouldn't be super hard to write a nginx module to enable content negotiation, if there was an interest in it
On Wed, Jul 11, 2018 at 7:11 PM Aaron Parecki notifications@github.com wrote:
This would allow a static site to serve ActivityPub objects as well as human-readable HTML. Currently it's not possible to do this, since static sites can't do content negotiation of course.
— You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/w3c/activitypub/issues/310#issuecomment-404338732, or mute the thread https://github.com/notifications/unsubscribe-auth/AAORV8zh504acM1VU-qjYTFjpKw1xwpDks5uFoYjgaJpZM4UdtrM .
