Yes, but...
I understand the RSS and Atom specs well enough that I've created programs with RSS/Atom feeds. But the ActivityPub spec scares the willies out of me. Too many moving parts.
Yes, but...
I understand the RSS and Atom specs well enough that I've created programs with RSS/Atom feeds. But the ActivityPub spec scares the willies out of me. Too many moving parts.
@bobjonkman you should read my blog post.
https://socialwebfoundation.org/2026/09/04/static-activitypub-publishing/
@judell @bobjonkman @samruby definitely @davew is on the Fediverse!
@bobjonkman @evan Relevant: http://scripting.com/davenet/2001/04/04/aBusyDevelopersGuideToSoap.html.
Back in the day both Dave Winer (no Fediverse handle?) and Sam Ruby ( @samruby) showed ways to do The Simplest Possible Thing with SOAP.
I just finished reading your post (after posting my previous reply) and it confirms my thought that ActivityPub, even a static implementation, has too many moving parts. I'll follow some of the links in your post (later, I've been rate-limited) to see if I can wrap my head around it. I've never been able to wrap my head around anything Ruby, tho.
The ActivityPoll #FEP has a very unfortunate name, clashing and overloading with the existing concept of a #Poll on the fediverse. The mechanism it documents is generally called #Polling.
@bobjonkman I think it's possible to tighten up the file structure even further, by using embedded objects with fragment identifiers. That said, I think it's a big step forward for publishers. I was able to make a plugin for Jekyll pretty quickly.
@smallcircles @bobjonkman I think "very unfortunate" is an exaggeration.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.