post (@post@badgefed.vocalcat.com)
Hey Fediverse! 👋
We’ve been quiet… but not idle. Forget waiting for long blog posts, time for micro updates.
Today’s news:
We’ve got a few BadgeFed instances live and federating! 🏅
To make it happen, we did a hardcore backend rewrite to support multiple domains on a single machine. For most, it’s a niche cost-saving move, but it might be useful for others too. Under the hood: each domain runs its own SQLite DB, with backups in place.
But this isn’t just about the tech, the fun part is seeing multiple BadgeFed servers talking to each other (!!). Follow them, check the thread, boost it, and watch for more as they come online!
You can read the article "BadgeFed Update: Multiple Instances Online!" by @mapache here as well.
#badgefed #fediverse #openbadges #update #activitypub #sqlite #federationShow Original Post
notes (@notes@not-brain.d.on-t.work)
Please chime in if this sounds like something you'd want to implement
socialhub.activitypub.rocks/t/would-there-be-any-interest-in-a-pre-authorized-fetch-fep/5481
/forcepub
#activityPub #fediDev #fediDevs #mastoDev
Show Original Post
mapache (@mapache@hachyderm.io)
what are the main forum software that are #fediverse enabled? Has someone used reddit-clones (#lemmy) as forums for support?
I am evaluating creating something for #badgefed
Show Original Post
Linux (@Linux@mstdn.ca)
Thankfully, I don’t see this behavior often on the Fediverse — not to say that it doesn’t happen, of course.
I can point out that it certainly happens on Facebook. And on Twitter, it definitely used to happen a lot — which is why they added a time limit.
I do think it’s something worth considering for Mastodon and Misskey.
#Mastodon #Misskey #Fediverse #ActivityPub
Show Original Post
nick (@nick@mastodon.law)
This seems like a good opportunity to remind everyone that threads users can be followed on mastodon/activitypub. And mastodon/activitypub users can be followed on threads. #threads #activitypub
Meta's Threads Surges to 400 Million Users, Rivals Elon Musk's X https://www.webpronews.com/metas-threads-surges-to-400-million-users-rivals-elon-musks-x/
Show Original Post
p (@p@postygram.com)
Raels is my own #tiktok clone using #ostatus and #activitypub protocols. It's about 95% finished.
Show Original Post
notes (@notes@tokler.com)
I don't know if I should really bother with trying to fork Goldfish, Raels is already more mature, and #ActivityPub federation is mostly working now.
Show Original Post
fabiobruna (@fabiobruna@mastodon.social)
Haha! Het werkt! #ghost #activitypub
Show Original Post
post (@post@community.nodebb.org)
Bridge as a service...
Reflecting on justbsocial.eu's recent launch, I wonder whether @anewsocial@mastodon.social is thinking about creating a bridge as a service product to connect existing social networks to the fediverse.
Having them start from scratch is a barrier in many ways!
https://community.nodebb.org/post/105509
Show Original Post
dansup (@dansup@mastodon.social)
Mastodon could really use tombstone placeholders when a reply is deleted so the tree/chain isn't broken or orphaned.
I've implementing this in Loops, and it is a bit tricky federation wise, but it makes the experience much better.
Show Original Post
dansup (@dansup@mastodon.social)
Shoutout to @lain for creating Pleroma - arguably the most technically ambitious fediverse project.
From ActivityPub innovations to sponsoring ElixirConf, they've put their money where their code is.
The fediverse needs more builders, fewer critics.
Show Original Post
fedify (@fedify@hollo.social)
We'd like to recognize the valuable contributions from two developers who participated in Korea's #OSSCA (Open Source Contribution Academy) program. Both contributors identified important gaps in #Fedify's functionality and documentation, providing thoughtful solutions that benefit the broader #ActivityPub ecosystem.
@gaebalgom contributed PR #365, addressing issue #353 regarding NodeInfo parser compatibility, originally reported by @andypiper. The issue arose when Fedify incorrectly rejected #NodeInfo documents from snac instances due to overly strict version string parsing that required semantic versioning compliance. Their solution improves the fallback behavior in the parseSoftware() function to handle non-SemVer version strings by parsing dot-separated numbers and defaulting to zero for missing components. The implementation includes thorough test coverage for various edge cases, including single numbers (3), two-part versions (2.81), and malformed version strings. This fix provides immediate compatibility improvements across the fediverse while maintaining backward compatibility, and will be included in Fedify 1.9. The contribution serves as an interim solution, with a more comprehensive fix planned for Fedify 2.0 (issue #366), where the NodeInfo software.version field will be changed from the SemVer type to a plain string to fully comply with the NodeInfo specification.
@z9mb1 contributed PR #364, resolving issue #337 by adding practical examples for Fedify's custom collection dispatchers feature. Custom collections were introduced in Fedify 1.8 but lacked clear documentation for developers seeking to implement them. Their contribution provides a comprehensive example demonstrating how to set up custom collections for tagged posts, including proper routing patterns, pagination handling, and counter functionality. The example includes mock data structures, shows how to configure collection dispatchers with URL patterns like /users/{userId}/tags/{tag}, and demonstrates the complete request/response cycle using federation.fetch(). This work provides developers with a clear, runnable reference that reduces the complexity of implementing custom collections in ActivityPub applications.
We appreciate these meaningful contributions that help make Fedify more accessible and robust for the entire ActivityPub community.
#opensource #fedidev #fediverse
Show Original Post