### Transparency update: Web framework integration progress'n'nWe're sharing a public project board to track our progress on web framework integrations for #Fedify, work commissioned by the Sovereign Tech Fund (@sovtechfund@mastodon.social).
General Discussion
1
Posts
1
Posters
0
Views
-
Transparency update: Web framework integration progress
We're sharing a public project board to track our progress on web framework integrations for #Fedify, work commissioned by the Sovereign Tech Fund (@sovtechfund@mastodon.social). You can follow along at:
https://github.com/orgs/fedify-dev/projects/1
About this work
The Sovereign Tech Fund invested in Fedify to expand its ecosystem through official integrations with popular web frameworks. This investment enables developers to add federation capabilities to their existing applications without changing their technology stack.
Notably, some of these integrations were completed between our initial application submission and the official kickoff of the #STF investment. This demonstrates both our commitment to the project and the community's active development momentum.
Current status
Already completed:
- Next.js integration supporting both App Router and Pages Router (completed before STF kickoff)
- Elysia integration optimized for the Bun ecosystem (completed before STF kickoff)
In progress:
- Fastify integration (PR currently under review)
Upcoming:
- Koa integration
- Comprehensive documentation for all integrations
Why this matters
These integrations make Fedify accessible to developers across different JavaScript ecosystems and runtime environments. Each integration follows established patterns from our Express and h3 integrations, ensuring consistency and ease of adoption.
Investment details
Fedify has been awarded a service agreement by the Sovereign Tech Fund for this work, with a budget of €32,000 and completion target of November 30, 2025. The Sovereign Tech Agency supports the development, improvement, and maintenance of open digital infrastructure through investments like this.
We believe in transparent development and welcome community input and contributions.
#ActivityPub #SovereignTechFund #opensource
-
System shared this topic on
undefined 洪 民憙 (Hong Minhee) shared this topic on
undefined Fedify: ActivityPub server framework shared this topic on
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@konstantin I enabled all the newly-working features with version 2025.2.2 (which means I could have done this eight months ago)
https://codeberg.org/technicat/fedicat/src/branch/main/Sources/Fedicat/Platforms/Sharkey.swift
-
@fedicat thanks!
-
finally 🥳
-
evan Yes, the domain name can be an excellent solution. However I am looking for a solution where a federated platform, e.g. Mastodon, can recognize an account from another federated platform such as NodeBB or Friendica and vice versa. At the moment if I want to reply to a mastodon user, Mastodon asks me what my mastodon account is. If I give it my NodeBB or Friendica account, Mastodon rejects it. I think that the ActivityPub protocol should solve this problem.
-
phi maybe this is a social layer problem rather than a technical problem.
Your issue means a lot in a world where we have amateur hobbyists setting up social network servers and allowing the general public to join. Those hobbyists get overwhelmed or bored after a while, or they do a bad job and your server gets defederated.
In this case, it makes a lot of sense to move from one server to another. But this is not the only way we could organize the Fediverse.
Email isn't like that. You (probably?) don't use an email address from a server you found on a list on joinemail.org. You probably, instead, have an email address from your employer or university, and maybe a personal one from a well-known and reliable cloud service. If you're very clever, you may use your own domain for email, and share it with your household or family.
In those cases, you rarely change email addresses. We have some ad hoc ways to move from one to the other, but they aren't built into the SMTP or IMAP specs. And yet we have a lot of email going around, even after 50 years.
I think we should be putting our efforts into getting Fediverse services from organizations we have a lot of affinity with, like employers or universities or the city you live in or the post office.
Another option is using the extremely portable identity system we already have -- domain names. It should be a lot easier to bring your own domain name to a Fediverse server, and to move your data between servers by backing up and restoring and then repointing your domain name to the new server, like you do for blogs. This is really hard right now.
I think LOLA is doing a good job with online moves, but we should also be encouraging more server developers to support BYOD, and we should encourage Fediverse users to get a domain.
-
@johnefrancis I have a collection of my favourite smarty-pants comments that would fit that description, so yes.
-
@konstantin I don’t know of any current flagship instance but I have a test account on plasmatrsp.com
-
@fedicat is there a "reference" or already updated sharkey instance one can use to test against? I'd like to make sure we support this in TootSDK
Post suggeriti
-
If you own or have access to an embroidery machine, or if you want to learn how the combination of #Inkscape and the #Inkstitch [1] plugin works, I have created a mirror on #codeberg where you can download all my stitching files as SVG and DST.
Uncategorized
2
-
Interview with Igor Ostapenko: Starting FreeBSD Development'nIn this FreeBSD Journal article, Igor Ostapenko shares how he first got involved with FreeBSD, his path into operating system work, and his advice for new contributors.
Uncategorized
1
-
-
