"how to not regret c2s"
https://w.on-t.work/activitypub/c2s

my opinions about how activitypub c2s ought to be implemented, probably with way too much snark for anyone to take it seriously. wrote pretty much all of it at like 1 am so expect the writing to not be great. will prolly regret it tomorrow but eh. whatever

#activityPub #fediDevs

MastoBlaster is now available in public testing on TestFlight.

It is a lightweight, privacy-first Fediverse client for iOS, built around a simple idea: fast, small, predictable behavior, and first-class support for snac.

What makes it different:

• snac-first by design, not "compatible by accident"
• Works with all Mastodon API compatible software, including Mastodon, snac, GoToSocial, Akkoma, and others
• EXIF stripping on upload (HDR and orientation preserved)
• Optional on-device alt text generation via Apple Intelligence for your uploads and for images in your timeline
• Markdown posting for snac
• Granular notifications, grouping, multi-account
• Blocking and moderation tools
• Very small footprint, very low RAM usage

Alt text generation happens entirely on device via Apple APIs on supported hardware. Nothing is sent to external services.

It is built around my own workflow and priorities. It may not be for everyone, and that is perfectly fine.

Important note:
MastoBlaster will always be free for BSD Cafe users, illumos Cafe users, and for anyone connecting to a snac instance, including self-hosted ones.

The app is already usable, but this is still a test phase. I am looking for feedback, bug reports, and real-world usage insights.

TestFlight link:
https://testflight.apple.com/join/Pkxa5R1k

Stay tuned.

#MastoBlaster #iOS #Apple #Fediverse #Mastodon #snac #GoToSocial #Akkoma #ActivityPub

Hi #fediverse and #ActivityPub developers!

I'm currently working on interoperability testing for #Hollo and #Fedify, and I need a #Bonfire account to test federation with their implementation.

Since there aren't many open public Bonfire instances available, I was wondering if any Bonfire instance admins out there would be willing to grant me a test account? It would be a huge help for improving interop! Let me know if you can help. Thanks!

#fedidev #BonfireNetworks

Hi #fediverse and #ActivityPub developers!

I'm currently working on interoperability testing for #Hollo and #Fedify, and I need a #Bonfire account to test federation with their implementation.

Since there aren't many open public Bonfire instances available, I was wondering if any Bonfire instance admins out there would be willing to grant me a test account? It would be a huge help for improving interop! Let me know if you can help. Thanks!

#fedidev #BonfireNetworks

Fedify 2.0.0 is here!

This is the biggest release in Fedify's history. Here are the highlights:

• Modular architecture — The monolithic @fedify/fedify package has been broken up into focused, independent packages: @fedify/vocab, @fedify/vocab-runtime, @fedify/vocab-tools, @fedify/webfinger, and more. Smaller bundles, cleaner imports, and the ability to extend ActivityPub with custom vocabulary types.
• Real-time debug dashboard — The new @fedify/debugger package gives you a live dashboard at /__debug__/ showing all your federation traffic: traces, activity details, signature verification, and correlated logs. Just wrap your Federation object and you're done.
• ActivityPub relay support — First-class relay support via @fedify/relay and the fedify relay CLI command. Supports both Mastodon-style and LitePub-style relay protocols (FEP-ae0c).
• Ordered message delivery — The new orderingKey option solves the “zombie post” problem where a Delete arrives before its Create. Activities sharing the same key are guaranteed to be delivered in FIFO order.
• Permanent failure handling — setOutboxPermanentFailureHandler() lets you react when a remote inbox returns 404 or 410, so you can clean up unreachable followers instead of retrying forever.

Other changes include content negotiation at the middleware level, @fedify/lint for shared linting rules, @fedify/create for quick project scaffolding, CLI config files, native Node.js/Bun CLI support, and many bug fixes.

This release includes significant contributions from Korea's OSSCA participants. Huge thanks to everyone involved!

This is a major release with breaking changes—please check the migration guide before upgrading.

Full release notes: https://github.com/fedify-dev/fedify/discussions/580

#Fedify #ActivityPub #fediverse #fedidev #TypeScript

Fedify 2.0.0 is here!

This is the biggest release in Fedify's history. Here are the highlights:

• Modular architecture — The monolithic @fedify/fedify package has been broken up into focused, independent packages: @fedify/vocab, @fedify/vocab-runtime, @fedify/vocab-tools, @fedify/webfinger, and more. Smaller bundles, cleaner imports, and the ability to extend ActivityPub with custom vocabulary types.
• Real-time debug dashboard — The new @fedify/debugger package gives you a live dashboard at /__debug__/ showing all your federation traffic: traces, activity details, signature verification, and correlated logs. Just wrap your Federation object and you're done.
• ActivityPub relay support — First-class relay support via @fedify/relay and the fedify relay CLI command. Supports both Mastodon-style and LitePub-style relay protocols (FEP-ae0c).
• Ordered message delivery — The new orderingKey option solves the “zombie post” problem where a Delete arrives before its Create. Activities sharing the same key are guaranteed to be delivered in FIFO order.
• Permanent failure handling — setOutboxPermanentFailureHandler() lets you react when a remote inbox returns 404 or 410, so you can clean up unreachable followers instead of retrying forever.

Other changes include content negotiation at the middleware level, @fedify/lint for shared linting rules, @fedify/create for quick project scaffolding, CLI config files, native Node.js/Bun CLI support, and many bug fixes.

This release includes significant contributions from Korea's OSSCA participants. Huge thanks to everyone involved!

This is a major release with breaking changes—please check the migration guide before upgrading.

Full release notes: https://github.com/fedify-dev/fedify/discussions/580

#Fedify #ActivityPub #fediverse #fedidev #TypeScript

Fataler Fehler bim Aktivieren von #ActivityPub in meiner neuen #Wordpress-Installation. 🤯

✅ Fehlermeldung grob ausgeschnitten und nach #Copilot kopiert
✅ Grobe Ursachenbeschreibung erhalten
✅ Nach Behebungsmöglichkeiten gefragt
✅ In Reihenfolge ausprobiert, dritte Option funktioniert
✅ ActivityPub ist aktiv

Ja, der Slop kann auch hilfreich sein. 🙃

#SolvedWithAI

Fataler Fehler bim Aktivieren von #ActivityPub in meiner neuen #Wordpress-Installation. 🤯

✅ Fehlermeldung grob ausgeschnitten und nach #Copilot kopiert
✅ Grobe Ursachenbeschreibung erhalten
✅ Nach Behebungsmöglichkeiten gefragt
✅ In Reihenfolge ausprobiert, dritte Option funktioniert
✅ ActivityPub ist aktiv

Ja, der Slop kann auch hilfreich sein. 🙃

#SolvedWithAI

Is there any good activitypub/fediverse blogging software out there? Most of what I find is ultra minimalistic. Was looking for something a bit more.

#ActivityPub #Fediverse

RE: https://mastodon.social/@drupalcon/116103906415187116

“Open Web”

it is not lost on me that the VC-backed #Drupal leadership jumped on the #AIslop bandwagon with this REDUNDANT DrupalCMS conceit; but nary a peep about what would make sense for the project: turn Drupal into an #ActivityPub framework for building different #fediverse webapps.

Drupal isn't the open-source mess Wordpress became; but it’s been a thing to watch how the capitalists set the priorities.

#BackdropCMS should do what Drupal won't: become a framework for AP webapps.

Mastodon has announced plans to make its app more approachable for newcomers, and developed new features for creators. Here's @Sarahp's story for @Techcrunch. Find the full blogpost by @renchap and @imanijoy at the second link.

https://flip.it/TKKQZS
https://flip.it/RQRRnp

#ActivityPub #Mastodon #OpenSocial #Technology #Tech

What does a Discord replacement look like, and how might the open social web play a part? @laurenshof looks at what needs to happen — different apps built on the same protocols, active collaboration to make sure it all fits together — and how that's already fundamental to the Atmosphere and fediverse.

https://flip.it/QdL.FX

#ActivityPub #Mastodon #ATProtocol #Bluesky #Blacksky #Discord #Technology #Tech

"how to not regret c2s"
https://w.on-t.work/activitypub/c2s

my opinions about how activitypub c2s ought to be implemented, probably with way too much snark for anyone to take it seriously. wrote pretty much all of it at like 1 am so expect the writing to not be great. will prolly regret it tomorrow but eh. whatever

#activityPub #fediDevs

What does a Discord replacement look like, and how might the open social web play a part? @laurenshof looks at what needs to happen — different apps built on the same protocols, active collaboration to make sure it all fits together — and how that's already fundamental to the Atmosphere and fediverse.

https://flip.it/QdL.FX

#ActivityPub #Mastodon #ATProtocol #Bluesky #Blacksky #Discord #Technology #Tech

Mastodon has announced plans to make its app more approachable for newcomers, and developed new features for creators. Here's @Sarahp's story for @Techcrunch. Find the full blogpost by @renchap and @imanijoy at the second link.

https://flip.it/TKKQZS
https://flip.it/RQRRnp

#ActivityPub #Mastodon #OpenSocial #Technology #Tech

Btw, this is a good opportunity to once more thank @nlnet for their years-long hard work and support of the social web, and the fediverse in particular. I counted 86 fine social web R&D projects who have received @NGIZero and other @ngi support from the #EU over the past couple of years.

At the bottom of the article I mention the urgent #FOSDEM talk and call-to-action by @michiel and also the 2019 keynote given by @darius at the #ActivityPub Conference in Prague on "How to play and win our own game" independent of #BigTech and corporate hypercapitalist shenanigans.

@ben

Btw, this is a good opportunity to once more thank @nlnet for their years-long hard work and support of the social web, and the fediverse in particular. I counted 86 fine social web R&D projects who have received @NGIZero and other @ngi support from the #EU over the past couple of years.

At the bottom of the article I mention the urgent #FOSDEM talk and call-to-action by @michiel and also the 2019 keynote given by @darius at the #ActivityPub Conference in Prague on "How to play and win our own game" independent of #BigTech and corporate hypercapitalist shenanigans.

@ben

@ben wrote a good article "Growing the open social web" for FediForum.

It poses this *essential* question: Why do we want to grow the open social web and for whom?

While the question is crucial when considering the future of social networking and the role of online technologies in society, it is not a question that is being addressed in any significant way. Our social web and fediverse "just happens", emerging from this chaotic cauldron of mostly technical discussions about which features to put in apps, how to connect one app to the next, and which social web technology or app is better than others.

Ben makes an appeal for creating good protocols, where the real value is, but only if we can share ownership of them. I 100% agree with the points in the article.

But how do we get there? What is this ownership? How do we achieve it, and subsequently retain it? I wrote down some some thoughts in a blog post.

https://coding.social/blog/shared-ownership/

#SX #SocialCoding #SocialWeb #fediverse #ActivityPub