#fedify

9 posts · Last used 5d

Back to Timeline
IFTAS @iftas@mastodon.iftas.org · 5d ago
@z9mb1@hackers.pub #Fedify co-maintainer Jiwon up next doing an excellent job on first public speaking! Introducing Feder: a Rust framework for building ActivityPub applications.
11
1
12
julian @julian@activitypub.space · Jul 29, 2026

Reflecting on the existence of httpsig.org

<p><a href="http://httpsig.org/" rel="nofollow ugc">httpsig.org</a> is a site with one sole purpose, to advocate for the adoption of <a href="https://www.rfc-editor.org/rfc/rfc9421.html" rel="nofollow ugc">RFC 9421 HTTP Signatures</a>. It has a "Libraries" tab that does exactly what it advertises, it lists a bunch of libraries for you to use so you don't have to roll your own.</p> <p>If you want to integrate AP today, but you don't want to roll your own everything, where do you go? Who do you ask?</p> <p>All I know is:</p> <ul> <li><a href="https://fedify.dev/" rel="nofollow ugc">Fedify</a> → Typescript (thanks <a href="https://hollo.social/@hongminhee">@<bdi>hongminhee@hollo.social</bdi></a>!)</li> <li><a href="https://github.com/go-ap/fedbox" rel="nofollow ugc">FedBOX</a> → Go (thanks <a href="https://metalhead.club/@mariusor">@<bdi>mariusor@metalhead.club</bdi></a>!)[...]</li></ul> Hover or focus to reveal Sensitive
httpsig.org is a site with one sole purpose, to advocate for the adoption of RFC 9421 HTTP Signatures. It has a "Libraries" tab that does exactly what it advertises, it lists a bunch of libraries for you to use so you don't have to roll your own. If you want to integrate AP today, but you don't want to roll your own everything, where do you go? Who do you ask? All I know is: Fedify → Typescript (thanks @hongminhee@hollo.social!) FedBOX → Go (thanks @mariusor@metalhead.club!)[...] Do we even have a list sorted by language? This would be huge. What other AP frameworks do you know of? Granted, I didn't do a lot of thinking and deep diving before I listed those two examples, but even then, that's 1 more example than is listed on https://activitypub.rocks so I think I might be on to something here from a developer advocacy point of view. If I were looking to integrate AP, one of the first conclusions I'd come to is that the protocol itself is fairly complex and a library or framework might help. I don't think there is a list that plainly lists supported libraries by language.
0
6
0
Julian Fietkau @julian@fietkau.social · Jul 09, 2026
Boosted by fedicat @fedicat@pc.cafe
Having some nice ActivityPub design/implementation conversations with @hongminhee@hollo.social in the @fedify@hackers.pub Matrix chat at #fedify:matrix.org And if it sometimes boils down to an exchange of 😮‍💨 and 😞, then maybe that's what we need that day, and 💪 can be for tomorrow.
5
0
3
洪 民憙 (Hong Minhee) :nonbinary: @hongminhee@hollo.social · Jun 25, 2026
Boosted by fedicat @fedicat@pc.cafe
Starting on FEP-ef61 (Portable Objects) in @fedify@hollo.social. It's a @sovtechfund@mastodon.social milestone due September 30, and the scope is… substantial. Not a lot of runway. Wish me luck. #Fedify #FEPef61 #PortableObjects #ActivityPub #fedidev
33
5
17
Fedify: ActivityPub server framework @fedify@hollo.social · Jun 17, 2026
Boosted by fedicat @fedicat@pc.cafe
DrFed is our sister project, built alongside #Fedify to tackle the debugging side of #ActivityPub development. It just received @nlnet@social.nlnet.nl funding and now has its own account here: @drfed@hackers.pub. #DrFed #fedidev #fediverse #NLnet RE: https://hackers.pub/@drfed/019ed3c9-7e8c-782f-a512-5fbc75a4610b
Quoting
DrFed @drfed@hackers.pub
Some of you have already heard of us as #Fedify Studio. We now have a proper name: DrFed, short for “Doctor Fed.” We've also just received funding from @nlnet@social.nlnet.nl, through the NGI0 Commons Fund. #DrFed is a web app for debugging #ActivityPub interoperability failures. When two implementations don't federate, the slow part is usually figuring out where the exchange broke: signing, JSON-LD processing, WebFinger, or something less obvious. DrFed's first job is to show where it failed. We're the team behind @fedify@hollo.social: @2chanhaeng@hackers.pub, @gaebalgom@hackers.pub, @hongminhee@hollo.social, and @z9mb1@hackers.pub. We'll post updates when there's something to try. #fedidev #fediverse
Open quoted post
0
0
5
DrFed @drfed@hackers.pub · Jun 17, 2026
Boosted by fedicat @fedicat@pc.cafe
Some of you have already heard of us as #Fedify Studio. We now have a proper name: DrFed, short for “Doctor Fed.” We've also just received funding from @nlnet@social.nlnet.nl, through the NGI0 Commons Fund. #DrFed is a web app for debugging #ActivityPub interoperability failures. When two implementations don't federate, the slow part is usually figuring out where the exchange broke: signing, JSON-LD processing, WebFinger, or something less obvious. DrFed's first job is to show where it failed. We're the team behind @fedify@hollo.social: @2chanhaeng@hackers.pub, @gaebalgom@hackers.pub, @hongminhee@hollo.social, and @z9mb1@hackers.pub. We'll post updates when there's something to try. #fedidev #fediverse
0
0
1
Fedify: ActivityPub server framework @fedify@hollo.social · Jun 06, 2026
Boosted by fedicat @fedicat@pc.cafe
There's a Matrix room for #Fedify contributors, open to anyone curious about how development happens. Feel free to drop in or lurk; small questions are fine too. #fedify-contributors:matrix.org
2
0
5
洪 民憙 (Hong Minhee) :nonbinary: @hongminhee@hollo.social · Apr 27, 2026
If you'd like to preview the #tutorial I'm writing on building a small federated image sharing service, similar to @pixelfed@mastodon.social, with @fedify@hollo.social and @nuxt@m.webtoo.ls, here it is: https://pr-731-0.fedify.pages.dev/tutorial/content-sharing If you'd like to give feedback after reading it, please leave a comment on the following PR: https://github.com/fedify-dev/fedify/pull/731 #Fedify #fedidev #ActivityPub #Nuxt #Pixelfed
32
1
54
洪 民憙 (Hong Minhee) :nonbinary: @hongminhee@hollo.social · Apr 24, 2026
Replying to @hongminhee@hollo.social
Honestly, I don't really care what strategy other #ActivityPub implementations follow to comply with the spec. (I solved it in #Fedify by just using a proper JSON-LD processor.) It's just a bit annoying that I always send valid JSON-LD documents, but whenever I encounter an interoperability bug where the other side can't process them, I'm the one who has to send them a patch to fix it. 😩
11
5
8

You've seen all posts