中國(중국)의 開發者(개발자)인 北雁雲依(베이옌윈이) 님(@21018365486)이 Fedify를 利用(이용)하여 自身(자신)의 블로그에 ActivityPub을 붙인 이야기. 利用(이용)해 주셔서 感謝(감사)합니다!
A Chinese developer, @21018365486, wrote about adding ActivityPub to her blog using Fedify. Thank you for using Fedify!
Discussion
These are the people building the Fediverse!
中國(중국)의 開發者(개발자)인 北雁雲依(베이옌윈이) 님(@21018365486)이 Fedify를 利用(이용)하여 自身(자신)의 블로그에 ActivityPub을 붙인 이야기. 利用(이용)해 주셔서 感謝(감사)합니다!
A Chinese developer, @21018365486, wrote about adding ActivityPub to her blog using Fedify. Thank you for using Fedify!
中國(중국)의 開發者(개발자)인 北雁雲依(베이옌윈이) 님(@21018365486)이 Fedify를 利用(이용)하여 自身(자신)의 블로그에 ActivityPub을 붙인 이야기. 利用(이용)해 주셔서 感謝(감사)합니다!
中國(중국)의 開發者(개발자)인 北雁雲依(베이옌윈이) 님(@21018365486)이 Fedify를 利用(이용)하여 自身(자신)의 블로그에 ActivityPub을 붙인 이야기. 利用(이용)해 주셔서 感謝(감사)합니다!
@hongminhee I'm adding Fedify to FEP-ef61 implementation list: https://codeberg.org/fediverse/fep/pulls/937/files
-----
So, what's your verdict, does FEP-ef61 have a future?
@silverpill Thank you for adding it! I think it does. I implemented it in Fedify because I believe the fediverse needs identities that outlive any single server. I hope having it in a framework makes it a little easier for others to adopt. Thanks again for all your patient answers along the way.
This is very bad news. Owncast has relied on this program the past couple of years, and has allowed us to have servers and services we wouldn't normally afford to be able to do otherwise, especially now with Gabe being unemployed.
Any other cloud hosting providers want to step in and help all the open source projects that are going to be in this position?
Additionally, this might be a good time to show your financial support for Owncast.
Fedify 2.4.0 is out.
The main addition is support for FEP-ef61 portable objects. A Fedify server can now host actors whose identity is a DID instead of a domain, serve their signed objects through /.well-known/apgateway/, and verify the portable objects of other servers. I tested it against tootik and Mitra, and wrote up where Fedify's profile differs from the FEP and what it leaves out.
The release also adds application-defined background tasks, the ActivityPub Media Upload extension, per-request inbox reports, 410 Gone for deleted objects, and four new packages (AdonisJS, Netlify, PGlite, and interaction controls).
Some defaults changed, so please read the upgrading section before you update, especially if you federate with software that uses FEP-ef61 compatible identifiers.
Release notes: https://hackers.pub/@fedify/2026/fedify-2-4.
Thanks to everyone who contributed to this cycle, and to @silverpill for patient answers about the FEP.
@hongminhee I'm adding Fedify to FEP-ef61 implementation list: https://codeberg.org/fediverse/fep/pulls/937/files
-----
So, what's your verdict, does FEP-ef61 have a future?
remember the time where there was a boop and a bop and a little beep
Fedify 2.4.0 is out.
The main addition is support for FEP-ef61 portable objects. A Fedify server can now host actors whose identity is a DID instead of a domain, serve their signed objects through /.well-known/apgateway/, and verify the portable objects of other servers. I tested it against tootik and Mitra, and wrote up where Fedify's profile differs from the FEP and what it leaves out.
The release also adds application-defined background tasks, the ActivityPub Media Upload extension, per-request inbox reports, 410 Gone for deleted objects, and four new packages (AdonisJS, Netlify, PGlite, and interaction controls).
Some defaults changed, so please read the upgrading section before you update, especially if you federate with software that uses FEP-ef61 compatible identifiers.
Release notes: https://hackers.pub/@fedify/2026/fedify-2-4.
Thanks to everyone who contributed to this cycle, and to @silverpill for patient answers about the FEP.
Fedify 2.4.0 is out.
The main addition is support for FEP-ef61 portable objects. A Fedify server can now host actors whose identity is a DID instead of a domain, serve their signed objects through /.well-known/apgateway/, and verify the portable objects of other servers. I tested it against tootik and Mitra, and wrote up where Fedify's profile differs from the FEP and what it leaves out.
The release also adds application-defined background tasks, the ActivityPub Media Upload extension, per-request inbox reports, 410 Gone for deleted objects, and four new packages (AdonisJS, Netlify, PGlite, and interaction controls).
Some defaults changed, so please read the upgrading section before you update, especially if you federate with software that uses FEP-ef61 compatible identifiers.
Release notes: https://hackers.pub/@fedify/2026/fedify-2-4.
Thanks to everyone who contributed to this cycle, and to @silverpill for patient answers about the FEP.
Fedify 2.4.0: FEP-ef61 portable objects, background tasks, media uploads, and inbox request reports
Fedify 2.4.0: FEP-ef61 portable objects, background tasks, media uploads, and inbox request reports
@avtpiavva Hi 👋 it sounds similar to this https://codeberg.org/GeopJr/Tuba/issues/1801 if you have any information not found there that could help figure out where the problem lies, please add it to issue!
@avtpiavva Hi! It should be fixed now on flathub! If you are using a source-built package, it won't have the fix yet as it needs more ironing out, but it was pulled on the flatpak early.
We're entering spooky season, and here's a neat Halloween-haunted-house-themed game made with Spritely's Hoot Scheme->WASM toolkit by @bonthron ! https://community.spritely.institute/t/hoot-haunted-house/851
Spritely office hours today Wednesday, September 30th at 2 PM EDT (6 PM UTC)! https://community.spritely.institute/t/next-office-hours-on-9-30/847
Drop by! Say hello! Ask us questions! Tell us what you're building!
These are always fun and the conversations are always great! Hope to see you there!
We gave a really well received talk at QCon London: “Spritely: Infrastructure for the Future of the Internet”, and it's now uploaded publicly! Give it a watch! https://www.infoq.com/presentations/spritely-decentralized-architecture/
We received some feedback about our technical posts, so we will keep this account dedicated to big announcements and updates, and move our technical posts to our Pixelfed Engineering account: @pixeldev
We apologize for any inconvenience!
Wrote and submitted my first FEP!
FEP-070c: Block synchronization across servers
Just wrapping up the implementation in Pixelfed as we speak.
PSA: AI Agents have been observed trying to get commissions for slop "art".
Please report these accounts so they can be suspended and if you are looking for an artist to commission, use a trusted server like mastodon.art with better artist vetting and moderation!