helvede.net is one of the many independent Mastodon servers you can use to participate in the fediverse.
Velkommen til Helvede, fediversets hotteste instance! Vi er en queerfeministisk server, der shitposter i den 9. cirkel. Welcome to Hell, We’re a DK-based queerfeminist server. Read our server rules!

Server stats:

169
active users

#activitypub

44 posts37 participants0 posts today
Replied to Robert Kingett

Thanks for indirectly introducing me to #ButtonDown @WeirdWriter. For those who (like me) aren't familiar with it, it's an email newsletter engine, akin to Ghost, who I see are also working on ActivityPub integration. So we'll be able to follow ButtonDown newsletters with our fediverse accounts, and comment on posts;

theverge.com/2024/4/22/2413729

See also;

web.archive.org/web/2025012319

Illustration of the fediverse surrounding the Earth like a constellation.
The Verge · Newsletter platform Ghost adopts ActivityPub to ‘bring back the open web’By Nilay Patel
fediversity.siteMike Macgirvin 🖥️The streams repository (the best fediverse server you never heard of) has been updated to v25.3.15. This is a periodic maintenance release with some minor bug fixes and composer updates. Be advised that the core streams code is PHP 8.4 compatible, however some required composer packages are not...

So if Section 230 gets repealed (ugh), my understanding is:

1. You can post anything you want on your own website and are personally liable for it.

2. If you host comments (syndicated or otherwise) you could be liable for what's said in those.

So the answer might be an #indieweb style interconnected blogosphere (yes, I said blogosphere) and more peer to peer style interfaces for #activitypub etc.

Hey all, the easiest way I can find #Ghost blogs using #ActivityPub is to search for @index and you will get some Friendica results, etc, but for now, that should be a sure way to find almost all the blogs that have enabled this feature so far. I couldn't tell if replies appear as comments, so if you don't want your comments on their blog, don't reply to their fediverse posts. A few told me they can see my comments on their dashboard but I don't know what that means. #FediTips #Fediverse

If you claim to be a leftist and you are trying to convince people to move to #BlueSky rather than the community driven #ActivityPub options (#mastodon / #PixelFed / etc) I cannot take you seriously as a leftist.

A major component of leftist thought is community organizing and defense. It is opposition to centralized power and control. Intentionally helping people move or set up on centralized systems, regardless of what their CEO's claim about them, is directly in opposition to leftist ideals.

Yes some people are sometimes confused by the
#Fediverse options. It's your job to help them find an appropriate community and work through the technical hurdles. The platforms they are moving away from, such as #Twitter, #Facebook & #Instagram were all confusing and overwhelming for people when they first joined. This is no different, it's always a learning curve.

Actually help and protect your communities by helping them not only escape corporate controlled networks but also by helping them find and utilize networks that are community run, moderated and controlled.

I am just back from an awesome #hackathon at the #cloudfest

We had three days to work on Federated (#WordPress) Events, you can find our results on that lovely page: fedivents.blog/

Thanks especially to @linos for his awesome work with the Event Bridge: wordpress.org/plugins/event-br

...and to @heiglandreas for pitching and leading the project!

#ActivityPub #Fediverse

@johnonolan the team came up with the puppies without any knowledge of your newsletter, so this must be really a thing!

AI generated image of a group of people with two dogs. with the headline: Online Federated Community Event.
FediventsFediventsWelcome to the world of the Federated Community Events

🏕️ my adventures in #selfhosting - day 93 ✨

Thanks to the brilliant advice of @CyberSaloperie I have found an easy-to-implement, no sweat solution for my redirect issue. I am about to create a test subdomain with #YunoHost to try it out before I make the real switch (from my current Ghost blog to the new, self-hosted one).

Maybe tomorrow I'll share with you the URL of my self-hosted Ghost blog if you want to try things out? 🙈 I have already imported my existing members, I'm ready to go 🚀

And yes, I'm fully aware the timing of my switch (from a Ghost Pro plan to self-hosted) is odd, considering Ghost Pro accounts are now part of the Fediverse. It's just that I couldn't justify spending so much ($31/month) on a free, non-monetized blog that I am capable of self-hosting. It's 6x the cost of my Debian or Ubuntu VPS.

And I kept getting close to the edge of 1000 members, which would have increased my monthly payments. Now I don't have to stress out about getting new readers. From what I understand #ActivityPub followers count as members for Ghost, so someone who gets a sizable following on their federated Ghost site would have to pay more.

I'm sure many people will love this feature (it's fantastic!) but it's not for me. I already have 3 federated Wordpress blogs and too many ActivityPub profiles as it is 🙃

I'm glad to announce the release of version 2.74 of #snac, the simple, minimalistic #ActivityPub instance server written in C. It includes a lot of web UI translations by lovely people and a bit of minor tweaks and fixes:

Added Spanish (default, Argentina and Uruguay) translation (contributed by gnemmi).

Added Czech translation (contributed by pmjv).

Added Brazilian Portuguese translation (contributed by daltux).

Added Finnish translation (contributed by inz).

Added French translation (contributed by Popolon).

Added Russian translation (contributed by sn4il).

Added Chinese translation (contributed by mistivia).

Added German translation (contributed by zen and Menel).

Added Greek translation (contributed by uhuru).

Added Italian translation (contributed by anzu).

Mastodon API: added support for /api/v1/custom_emojis (contributed by violette).

Improved Undo+Follow logic (contributed by rozenglass).

Reverted (temporarily) the Markdown code that converted text between underscores to italics, because it was causing more problems that what it was worth.

Fixed bug in bookmark CSV import.

Don't indent Twitter-like "threads" (i.e. chains of short posts from the same author that are self-replies).

https://comam.es/what-is-snac

If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/

#snacAnnounces
Summary card of repository grunfink/snac2
Forgejo: Beyond coding. We Forge.snac2A simple, minimalistic ActivityPub instance written in portable C
Continued thread

Coming soon in #Fedify 1.5.0: Smart fan-out for efficient activity delivery!

After getting feedback about our queue design, we're excited to introduce a significant improvement for accounts with large follower counts.

As we discussed in our previous post, Fedify currently creates separate queue messages for each recipient. While this approach offers excellent reliability and individual retry capabilities, it causes performance issues when sending activities to thousands of followers.

Our solution? A new two-stage “fan-out” approach:

  1. When you call Context.sendActivity(), we'll now enqueue just one consolidated message containing your activity payload and recipient list
  2. A background worker then processes this message and re-enqueues individual delivery tasks

The benefits are substantial:

  • Context.sendActivity() returns almost instantly, even for massive follower counts
  • Memory usage is dramatically reduced by avoiding payload duplication
  • UI responsiveness improves since web requests complete quickly
  • The same reliability for individual deliveries is maintained

For developers with specific needs, we're adding a fanout option with three settings:

  • "auto" (default): Uses fanout for large recipient lists, direct delivery for small ones
  • "skip": Bypasses fanout when you need different payload per recipient
  • "force": Always uses fanout even with few recipients
// Example with custom fanout setting
await ctx.sendActivity(
  { identifier: "alice" },
  recipients,
  activity,
  { fanout: "skip" }  // Directly enqueues individual messages
);

This change represents months of performance testing and should make Fedify work beautifully even for extremely popular accounts!

For more details, check out our docs.

What other #performance optimizations would you like to see in future Fedify releases?

Newsletter platform #Ghost, an open source competitor to #Substack, is now connected to the fediverse, also known as the open social web.

Federated apps run on the protocol #ActivityPub, which powers apps like Mastodon, Pixelfed, Threads, Flipboard, and others,
allowing posts published on one app to be seen and engaged with by those on other federated platforms.

Ghost said last year that it was working on an integration with ActivityPub, which would allow its publishers to share their blog posts with the broader open social web.

The company expected the integrations to go live last year. However, Ghost this week announced the launch of its social web beta, which now allows any site running on its Ghost Pro subscription to try out the new ActivityPub integration.

The beta feature is still in active development, the company notes in its help documentation, but is expected to ship in a more finalized state in the Ghost 6.0 release.

When Ghost Pro users connect their blog or newsletter to the fediverse, others across the open social web will be able to follow their account’s handle.

This handle is a combination of “@index,” representing the home page of the publication, followed by the domain name (@yoursite.com).

Ghost says users will soon be able to customize the @index part of their @index@yoursite.com handle.

Users on federated apps will then be able to follow the Ghost publisher’s posts, as well as interact with them by liking, replying, or reposting.

To help Ghost publishers also participate in the fediverse and build their readership,
Ghost also launched a social web reader.

Here, users can browse a “feed” of the short-form content shared across the fediverse, including posts from services like Mastodon and Threads.

In a separate area called the “Inbox,” Ghost users can keep up with long-form content, like articles published on Ghost or WordPress, the popular publishing platform that integrated with the fediverse in 2023.

“Think of the Inbox screen like your email inbox. When you follow other publications on the social web, new articles they publish will show up here,” Ghost’s help page explains.

“Clicking on a post will open an inline reader view, right inside Ghost,
and when you get to the end you’ll be able to like, repost or reply.”

With the integration of these two feeds into Ghost’s admin, Ghost will also now allow its publishers to directly post short-form content to the fediverse, helping them to build their reputation and following on the open social web.

Ghost’s Reader also alerts users of interactions like follows, replies, likes, and reposts in its “Notifications” section.

Plus, users can customize their Profile page to offer a preview of their social web account,
following/followers, and their content, both short and long-form.

Later, the company hopes to more deeply integrate users’ social web profiles with Ghost memberships,
but for now, they operate independently from one another.

Other coming features include tools to block, report, and mute people or add images or media to notes and replies.
techcrunch.com/2025/03/19/subs

TechCrunch · Substack rival Ghost is now connected to the fediverse | TechCrunchNewsletter platform Ghost, an open source competitor to Substack, is now connected to the fediverse, also known as the open social web. Federated apps run
Continued thread

We've been working on adding custom background task support to #Fedify as planned for version 1.5.0. After diving deeper into implementation, we've realized this is a more substantial undertaking than initially anticipated.

The feature would require significant API changes that would be too disruptive for a minor version update. Therefore, we've decided to postpone this feature to Fedify 2.0.0.

This allows us to:

  • Design a more robust and flexible worker architecture
  • Ensure better integration with existing task queue systems
  • Properly document the new APIs without rushing

We believe this decision will result in a more stable and well-designed feature that better serves your needs. However, some smaller improvements from our work that don't require API changes will still be included in Fedify 1.5.0 or subsequent minor updates.

We appreciate your understanding and continued support.

If you have specific use cases or requirements for background task support, please share them in our GitHub issue. Your input will help shape this feature for 2.0.0.

NoteWe've decided to postpone custom background task support to Fedify 2.0.0 instead of 1.5.0 as originally planned. This feature requires significant API changes that would be too disruptive for a...
GitHubSupport custom background tasks in worker · Issue #206 · fedify-dev/fedifyBy dahlia

Patch releases for #Fedify versions 1.0.21, 1.1.18, 1.2.18, 1.3.14, and 1.4.7 are now available. These updates address two important bugs across all supported release lines:

  1. Fixed a WebFinger handler bug that prevented matching acct: URIs with port numbers in the host. Thanks to @revathskumar for reporting and debugging the bug!
  2. Resolved server errors that occurred when invalid URLs were passed to the base-url parameter of followers collections.

We recommend all users upgrade to these latest patch versions for improved stability and federation compatibility.

Released on March 20, 2025.


Fixed a bug of WebFinger handler where it had failed to match acct: URIs with a host having a port number. [#218, #219 by Revath S Kumar]


Fixed a server error thrown...
GitHubRelease Fedify 1.0.21 · fedify-dev/fedifyReleased on March 20, 2025. Fixed a bug of WebFinger handler where it had failed to match acct: URIs with a host having a port number. [#218, #219 by Revath S Kumar] Fixed a server error thrown...