2026 (@2026@danielandrews.com)
I’m shutting down the post -> WP Plugin shares to Mastodon as @blog -> replies to that post operate as comments workflow. I wrote about this a while back. The short version: I want my WordPress posts to automatically share to Mastodon, and I want replies on Mastodon to show up as comments on my blog. I had recently posted on my site that I’d be trying out this integration as a way to incorporate comments and likes/reposts as well. Today I’m here to tell you, it’s not ready for prime time so I’ll be shutting this down for now and moving back to posting links to all posts from assortednerdery@mastodon.social instead.
The first part worked well. Posts go out automatically under @blog@danielandrews.com. The rest? Kind of a shit show.
A couple things I’d love to see improve:
- I wish you could link it up with you personal account. It posts from its own Mastodon account, not my personal one. Minor, but it bothers me. I’d love a way to interweave auto-posting.
- It was, broadly speaking, pretty unreliable. Posts would publish and then disappear after some time. No idea why. If it annoyed me, I’m sure it annoyed anyone following along.
- The default template is super opinionated, so you basically have to build an override to nuke the entire thing or it won’t bring along custom fields or anything else.
- No spam control. When I did a batch import of old posts recently, the account blasted out a wave of “edited” notifications to anyone following it. I took every precaution I knew of to suppress the RSS feed updates. Didn’t matter. Sorry to anyone who follows @blog@danielandrews.com and watched their timeline get buried.
The thing I keep coming back to, though, is something the tooling doesn’t really support yet: I want my short Mastodon posts to interweave with my longer writing on the site, as their own post type. A kind of unified stream.
I think I might just be describing micro.blog.
https://danielandrews.com/2026/03/20/wp-activitypub-plugin/Show Original Post
richard (@richard@www.main-vision.com)
On the Euphoria of Setting Up Activitypub With Gemini – Irony
Reading Time: 3 minutesI have spent many hours, and got Gemini to hallucinate multiple times, through multiple chats, attempting to get my Eleventy blogging experiment to talk with Activitypub and the Fediverse with limited help.Setting p a webfinger was easy, but getting follows to be accepted, and for posts to show up has been a complex task.
The Gemini Limitation
While putting Gemini through its paces I noticed that Gemini loves to try A, then B, before trying C, and during the entire process it will tell me why the solution works. Ironically, it often doesn’t. We hear so much about vibe coding, but based on my experiences I’d say that vibe coding is deeply ingrained within the scope of plain dumb luck.
One of the problem with AI, that I notice on a task such as this, is that AI tokenises what should be kept as a whole. An eleventy.js file should be kept whole, or if not whole, then as individual functions. By breaking it up in the wrong place, every time you try something and it fails, the AI model grows exponentially in complexity. That’s why I close a chat, take the latest iteration and continue from there.
If I tried this with Euria, LeChat and other LLMs I’d run out of tokens way before I achieved my goal. That’s why I stick with Gemini.
Of Image Paths and Activitypub Experimentation
If you’re setting up an RSS feed for Eleventy, with Gemini’s help, then it’s fantastic, but if you’re dealing with paths to images, file conversion, and stepped processes, such as ingesting the photos to a site specific directory, converting them from jpg to webp, and then serving them, then Gemini will get confused and hours of iteration will take place. That’s why I speak of luck playing a part.
Another term for luck is perseverance.
The Activitypub Marathon
Two or three years ago, when I was experimenting with Activitypub integration with a wordpress blog the process took time, and iterations. I used many different sources to try to resolve why it wasn’t working, and I was using the RTFB model, rather than AI. Read the Fabulous Blog trying to understand if I had made a mistake and if I had done something wrong.
I seem to remember moving the well know webfinger to the site’s route directory and that worked eventually.
Over time the wordpress plugin was improved and now it is optimised, to work within minutes, rather than hours.
What Worked
Setting up Webfinger was simple, and getting Mastodon to see the profile was simple. It is the process of getting a static blog to be seen by Mastodon that is a challenge.
Bridgy Fed
Setting up Bridgy Fed was quite fast, and simple, but I forgot to modify the site’s domain so it’s pointing to the wrong one for now. It was relatively quick and intuitive to setup, so if you’re in a rush take the Brid.gy route. I found that Bluesky prefers it.
Seeing JSON Rather than HTML
One of the stumbling blocks with my attempt to add the static blog to the fediverse is that Eleventy was serving html rather than json. Outbox was serving HTML, so that had to be fixed in the layout, but also via htaccess, and the same was true of the post pages. Now they’re serving the html versions, as well as a fediverse friendly json version. With patience fediverse instances should notice and index the blog, as the five hundred posts are noticed and indexed, and as new posts are shared.
And Finally
Lack of Gemini Support
I’m puzzled by how many iterations it takes with Gemini to get something like Activitypub to work with Eleventy. I’d expect AI to have encyclopedic knowledge on a topic, and help to resolve an issue within seconds or minutes, rather than hours. I’d also expect it to ask for context and encourage identifying the environment, before blundering in, and assuming, rather than verifying first.
Lack of Contextual Memory
The single most exhausting thing about trying to problem solve with Gemini is that it has no contextual memory, and it hallucinates. Both of these lead to negative loops where you get stuck. The easiest way to end such a loop is to open a new chat, but in so doing you need to add the context back in.
The Case for Writing and Using Tutorials is Alive and Well
With a well researched, and written tutorial, by following clear and concise instructions, you can follow a list of steps methodically and achieve what you want with a fraction of the carbon footprint, and in a fraction of the time. Next time I will look for a tutorial.
#activitypub #challenge #experimenting #fatigue #learning
Show Original Post
pub (@pub@btfree.social)
Fireside Fedi 80** **- Delta, AltStore, and Other Ways to Jailbreak Your iOS Experience - Riely Testut - AltStore
Special thank you to @rileytestut@mastodon.social of @altstore@fosstodon.org !
🚀 **Full VOD:** tubefree.org/w/bPVjxbLt8cQtK...
🔎 ** More Episodes:** tubefree.org/a/ozoned/video-channels
FOLLOW to never miss an episode!
#Owncast #Livestream @ozoned@stream.firesidefedi.live
#Peertube #VOD @firesidefedi@tubefree.org
SUBSCRIBE to never miss an episode!
📡 ** #RSS ** tubefree.org/feeds/videos.xml?videoChannelId=5934
🎧 ** #Podcast ** tubefree.org/feeds/podcast/videos.xml?videoChannelId=5934 #FiresideFedi #FiresideChat #Podcast #VideoPodcast #Fediverse #Fedi #ActivityPub #BSKY #DecentralizedSocial #OpenSocialWeb #Community #TechCulture #FutureOfSocial #TechTalk #DevCommunity #CodingFun
Show Original Post
eve (@eve@inkwell.social)
March 20, 2026 8:32 AM
And before someone says “But you’re posting this on #Bluesky”, no I’m actually not. I’m posting from the Fediverse and it’s just broadcasting to Bluesky through #ActivityPubhttps://inkwell.social/eve/march-20-2026-832-am-551731
Show Original Post
riotRhino (@riotRhino@social.coop)
I checked #Bluesky today to see the reactions to the delayed news of receiving crypto VC cash a year ago and liberals learn nothing over there. #Mastodon suffers from a lot of problems but one thing is for sure, people are here because they are passionate about an open web for the people, by the people. I have high hopes for #ActivityPub and the #Fediverse in the long run.
Show Original Post
item (@item@hub.tschlotfeldt.de)
@mthie
Du meinst das GotoSocial mit gleicher API? Es ergibt keinen Sinn, dass das nicht funktioniert.
Dazu muss ich dann doch noch etwas anderes loswerden, weil hier ja ein paar engagierte Leute im Thread mitlesen.
StarterPacks funktionieren nur mit Mastodon-Accounts. Obwohl alle #Fediverse -Systeme (okay, bis auf Diaspora) wie beispielsweise GotoSocial, Friendica und Hubzilla, #ActivityPub sprechen, sind StarterPacks ausschließlich für Mastodon entwickelt worden. Das kann man als Mastodon-Funktion natürlich gerne bauen. Aber der Anspruch des Domainnamens #FediDevs führt dann in die Irre. Das ist keine Fediverse-übergreifende Funktion.
Und diese Vereinnahmung des Fediverse-Begriffs stößt dann natürlich in verschiedensten Fediverse-Ecken auf Verwunderung – mindestens.
@Steffen Voß @WebMontag Kiel @Samuel Brinkmann
Show Original Post
wjmaggos (@wjmaggos@liberal.city)
We were being told to stop criticizing #bluesky and what their VC funding might mean, at the same time that their team knew that they had secretly taken much more than before from the same kinds of sources we were concerned about.
And of course this meant they could build on #ATproto much faster than anyone could with #ActivityPub, because our side refuses to believe we are somehow uniquely immune to the enshittification process that comes with that money.
The #SocialWeb is tired of your BS.
Show Original Post
post (@post@samuellison.com)
My website has been rebuilt from scratch with AI, Node.js, and #ActivityPub, now fully self-hosted on my own machines. What started around photography and hiking has become something more #agnostic — a home for dev logs, coding, experiments, and the broader trail of what I’m making 💻🍄
Show Original Post
jevans (@jevans@climatejustice.social)
@eff @taylorlorenz @404mediaco @system76
Friends in #colorado and any organizations that can help. A misguided bill (HB26-1255) from people who's hearts are in the right place just passed the last committee before going to the state house floor. This bill will essentially criminalize any #fediverse instance with at least one user in Colorado.
This bill does three particularly scary things:
1. Removes the existing 100,000-user lower limit for the definition of "Social Media Platform" in Section 6-1-1601 (4) of the Colorado Revised Statutes. This means that any of the tens of thousands of small #ActivityPub instances that happens to have a single user in Colorado at any time would be subject to this bill and any others that reference Section 6-1-1601 (4) of the Colorado Revised Statutes.
2. Adds a requirement for a staffed 24/7 hotline for each "Social Media Platform" to be available for law enforcement. This would require a minimum of four part-time staff, even for a Mastodon instance with two people on it that is run off of a Raspberry Pi in a bedroom closet in another country by someone in their spare time.
3. Requires notification of law enforcement within 24 hours of a flag of a threatening post. With VPNs, tunnels, Tor, etc., how do I know which law enforcement agency to reach out to? What if I don't keep any location data on my users? How do I decide what is credible and requires notification?
The ACLU has thankfully already voiced opposition.
the bill: https://leg.colorado.gov/bills/HB26-1255
testimony from last night's committee in opposition (starts at 7:12pm): https://sg001-harmony.sliq.net/00327/Harmony/en/PowerBrowser/PowerBrowserV2/20260318/-1/18310
Show Original Post
ktistec (@ktistec@epiktistes.com)
Release v3.3.4 of Ktistec is available.
This release adds Mastodon-compatible client support for publishing posts. Just like the previous release, however, all Mastodon API support is behind a build flag (-Dwith_mastodon_api). It's still experimental, so opt in only if you're happy to work with rough edges.
Beyond that, I focused on cleanup and refactoring throughout the codebase. Here's the full changelog:
Added
- Cursor-based pagination on actor timeline and everything pages.
- Mastodon-compatible API:
/api/v1/statusesendpoint for status posting. - Mastodon-compatible API:
/api/v1/timelines/publicendpoint.
Fixed
- Autosave focus handling. Fixes problems introduced in v3.3.3.
- Prevent blur from creating a draft post when publishing a post.
Changed
- Integrate X-Ray Mode colors into the theming system.
- Improve CI: add
npmaudit, test, and caching. - Use
npm ciin Dockerfile for reproducible builds. - Remove very old compiler bug work-around.
🏋️ Mastodon API support is coming along—more in the next release!
#ktistec #crystallang #activitypub #fediverse
Show Original Post
Profpatsch (@Profpatsch@mastodon.xyz)
So I got this bot that allows multiple people to curate a list of toots that are boosted by it, to create a nice topical account to follow.
Now I only need ideas what to boost haha :)
Show Original Post
homegrown (@homegrown@social.growyourown.services)
As you might have seen over on @FediTips , Wanderer is a trail-sharing platform for the Fediverse somewhat similar to Strava.
Wanderer is free open source software so you can host your own server if you want, and federated so you can communicate with other servers too.
At the moment Wanderer does require some technical knowledge to create your own server, you can find installation instructions at https://wanderer.to/run/installation/quick and source at https://github.com/open-wanderer/wanderer
#Wanderer #SelfHosting #ActivityPub
Show Original Post