What is the biggest reason that makes you hesitate to adopt #Fedify?

Huge shoutout to @2chanhaeng for implementing custom collection dispatchers in #Fedify through the Korean #OSSCA program!

This incredible contribution adds support for creating arbitrary collections beyond the built-in ones (e.g., outbox, inbox, following, followers). Now developers can expose custom collections like user bookmarks, post categories, or any grouped content through the #ActivityPub protocol:

federation
  .setCollectionDispatcher(
    "bookmarks",
    Article,
    "/users/{identifier}/bookmarks",
    async (ctx, values, cursor) => {
      const { posts, nextCursor } = await getBookmarkedPosts(values.identifier, cursor);
      return { items: posts, nextCursor };
    }
  )
  .setCounter(async (ctx, values) =>
    getBookmarkCount(values.identifier)
  );

The implementation is technically excellent with full #TypeScript support, both Collection and OrderedCollection types, cursor-based pagination, authorization predicates, and zero breaking changes. @2chanhaeng delivered not just code but a complete feature with 313 lines of comprehensive documentation, practical examples, and thorough test coverage.

This opens up countless possibilities for ActivityPub applications built with Fedify. From user-specific collections to complex categorization systems, developers now have the flexibility to create any type of custom collection while maintaining full ActivityPub compliance.

Thank you @2chanhaeng for this outstanding contribution and to the OSSCA program for fostering such excellent open source collaboration!

• Issue: https://github.com/fedify-dev/fedify/issues/310
• Pull request: https://github.com/fedify-dev/fedify/pull/332

Huge shoutouts to two amazing contributors from Korea's #OSSCA program who just made #Fedify even better!

First, @z9mb1 delivered PR #321, adding a handy -o/--output option to fedify lookup. Now you can save lookup results directly to files instead of just printing to terminal—a nice quality-of-life improvement for analysis and scripting workflows.

But the real showstopper is @joonnot's incredible PR #283, which introduces the brand new @fedify/testing package! This massive contribution (2,014 lines across 20 files) brings MockFederation and MockContext classes that completely transform how we test federated applications. No more complex setups or actual network requests—just clean, straightforward unit testing with activity tracking, inbox simulation, and queue-aware testing capabilities.

These contributions solve real pain points and showcase the amazing talent emerging from the OSSCA program. Both features will be available in the upcoming Fedify 1.8 release. The future of federated software development just got a lot brighter!

@radhitya

Your could talk about it here, if you use the hash-tags #ActivityPub and #FediDev — then other Fediverse developers will see it.

https://pan.rent has been down for the last ~36 hours. Probably, this happened because of an error during an upgrade to Mastodon Glitch 4.4.0. We are back now, running version 4.5.0-alpha ().

Thanks to @victorvandort for dealing with this.

Even though Pan is a tiny volunteer-run instance, so many hours of downtime should never be happening. We are discussing about how to avoid such long outages in the future.

Huge shoutout to two amazing contributors from Korea's #OSSCA program who've made excellent contributions to #Fedify!

@gaebalgom tackled a tricky terminal compatibility issue in PR #282, fixing the fedify node command's favicon display on terminal emulators without truecolor support (#168). His solution elegantly detects terminal capabilities and falls back to 256-color mode when needed—ensuring a great experience across different environments.

@joonnot enhanced Fedify's #WebFinger functionality in PR #281 by adding a configurable maxRedirection option to the lookupWebFinger() function (#248). He transformed a hardcoded limitation into a flexible, user-customizable parameter while maintaining perfect backward compatibility.

Both delivered thoughtful, well-implemented solutions that showcase the quality of contributions coming from the OSSCA program. Welcome to the Fedify community!

Big thanks to @2chanhaeng for his first contribution to #Fedify! He implemented the new fedify webfinger command in PR #278, which allows isolated #WebFinger lookups for testing configurations. This addresses the need for developers to test WebFinger functionality without performing comprehensive object retrieval.

The contribution includes:

• A new fedify webfinger <handle> command that accepts @user@domain format handles or URIs
• Clean JSON output of WebFinger JRD results
• Proper error handling for invalid handles and lookup failures
• Complete #CLI integration with help text and usage examples

This was originally filed as issue #260 and marked as a good first issue—perfect for newcomers to learn the codebase structure while contributing meaningful functionality. The PR has been merged and will be included in the upcoming Fedify 1.8.0 release.

We appreciate all first-time contributors who help make Fedify better for the entire #fediverse community. Welcome aboard, ChanHaeng!

From tomorrow morning, the Newsmast app will be down!

As we move to our new app, the current Newsmast app will go down for a period of maintenance.

In this time, you may see Newmast Channels also go down or be less responsive as we migrate them to a new server.

We can't wait to show you the new look Newsmast! Thanks so much for your patience.

A little known way in which Fedi can be browsed looks like this and is not web-based at all!
imho this a much cleaner interface with the fewest possible distractions.
The screenshot is of a recent post by @FediTips@social.growyourown.services , opened in a #geminiprotocol browser like @lagrange@skyjake.fi via a #tootik instance such as gemini://hd.206267.xyz/ (the 'flagship' instance by tootik's author @dimkr@hd.206267.xyz)

Thank you for this , @jk@skyjake.fi and @dimkr@hd.206267.xyz ! it's a much saner Fedi because of you.

#FediDev people may be interested, too

The #lesserKnownFedi is diverse and interesting to explore