Been thinking about fediverse wiki after 
[[Page Title@other-instance.wiki]][[Page@instance-a.wiki]] → [[Page@instance-b.wiki]], sharing edit history up to the fork pointThe fork/merge model feels natural for federated collaboration. Thoughts?
FenTiger @fentiger@zotum.net
did:self identifier, and stores the private key locallyscp or something to copy this JWT to the right place on the serverdid:self is that seems to be possible to add extra metadata, such as a human-readable name, to the ID, by using standard JWT claims - without needing the data to appear in the DID document.RE: https://neuromatch.social/@jonny/115343246885448739
Rumors that the fediverse can't do mobile identity have been greatly exaggerated: #FEP_1580 is now in draft status - https://codeberg.org/fediverse/fep/src/branch/main/fep/1580/fep-1580.md
This is a proposal for how to migrate all your stuff along with you when you move instances.
The gist:
Just using existing ActivityPub mechanisms. There are 6 new terms.
Bonus: lays the next steps to migrate to content addressed URIs, decouple accounts from instances, and merge and split accounts.
It being a draft means that there is a 60 day (or longer) public comment period, and feedback/edits/etc. Are very much welcome.
Issue: https://codeberg.org/fediverse/fep/issues/702
Discussion: https://socialhub.activitypub.rocks/t/fep-1580-move-actor-objects-with-a-migration-collection/8111
TIL: #Mastodon specifically treats actor URIs with the pattern Turns out I misread the code. 😅https://<domain>/actor as instance actors.
Here's a draft FEP to do full account migration with posts and whatever other kinda objects you want to bring with you. It's a trivial expansion of existing ActivityPub/streams systems and supports gradual migration as it's implemented and after an account migration. It should be possible to migrate pretty much everything this way, both private and public objects.
criticism, feedback, revisions, etc. welcome - i don't think this is a "final version" and there are certainly things i overlooked.
https://codeberg.org/sneakers-the-rat/fep/src/branch/move-map/fep/1580/fep-1580.md
https://codeberg.org/fediverse/fep/pulls/692
#MoveAllPosts #FediDev #FEP #FEP_1580 #FullMigration #AccountMigration
in which post migration has been requested for three years. six years? nine years!?
okay i've polished up my FediTag javascript which embeds a feed of Mastodon posts from one account using a particular hashtag on a website or page. you can find it on github https://github.com/Enichan/feditag
#FediDev #Mastodon #OpenSource #JavaScript #WebDevelopment #GitHub
If we were to do a regular online Fediverse meeting —
(Maybe once a month.)
WHAT DAYS OF THE WEEK WOULD YOU BE ABLE TO ATTEND?
A regular (online) meeting for Fediverse developers, for those who care about the Fediverse as a social movement, and for those who care about the success of the Fediverse.
Sunday?
Monday?
Tuesday?
Wednesday?
Thursday?
Friday?
Saturday?
(You can pick more than one day)
PLEASE REPLY WITH YOUR ANSWER.
#ActivityPub #FediDev #FediUX #Fediverse #FediverseUX #SocialWeb
RE: https://mastodon.social/@reiver/115300910507077759
I just did a video-chat with 
@sl007Sebastian Lasse —
(This is the first time we chatted.)
We talked about a number of Fediverse related things.
One of those things was — having a regular (online) meeting.
A regular (online) meeting for Fediverse developers, for those who care about the Fediverse as a social movement, and for those who care about the success of the Fediverse.
I have heard others say this, too, over and over again.
(And, at times, we have had them before.)
Fedi should have been a wiki
A wiki you can post on, what a concept.
But that's basically what it is we just don't have names for posts or concepts.
I actually did implement this, where you could give a post a title and that gives it a namespaced URL, ideally then one would be able to do [[my post]] or [[@jonny/my post]] , (and then quoting a named concept would be {{ @jonny/my post }} ). Idk why we never deployed this.
Thinking about building “#Fedify Studio” (tentative name)—a web-based #ActivityPub debugging & development toolkit, like a supercharged version of ActivityPub.Academy and fedify inbox command. Imagine having a proper UI for testing activities, inspecting actors, debugging federation issues… Would this be useful for other ActivityPub developers out there?
"＠context": [
"https://www.w3.org/ns/activitystreams",
{
"Quotation": "as:Quotation",
"citation": "as:citation",
"quotation": "as:quotation"
},
],
#ActivityPub #ActivityStreams #FediDev #Fediverse #JSONLD #ObjectTypeQuotation #retejo
3/
Apparently the Bookwyrm developer had the exact same idea!
(Which isn't too surprising.)
Here is how it works —
...
#ActivityPub #ActivityStreams #FediDev #Fediverse #ObjectTypeNote #ObjectTypeQuotation #retejo
4/
Apparently, Bookwyrm stores quotations with:
type="Quotation"
And if one Bookwyrm server talks to another Bookwyrm server, then — the ActivityPub / ActivityStreams representation of the quotation will have:
type="Quotation"
...
BUT — if a non-Bookwyrm server talks to a Bookwyrm server, then — the ActivityPub / ActivityStreams representation of the quotation will have:
type="Note"
#ActivityPub #ActivityStreams #FediDev #Fediverse #ObjectTypeNote #ObjectTypeQuotation #retejo
2/
How could you represent a quotation in ActivityPub‽
...
I suppose there are 2 major approaches.
Either use an existing Object Type. Maybe:
type="Note"
Or create a new Object Type:
type="Quotation"
...
Here is the interesting thing though —
#ActivityPub #ActivityStreams #FediDev #Fediverse #ObjectTypeNote #ObjectTypeQuotation #retejo
3/
Apparently the Bookwyrm developer had the exact same idea!
(Which isn't too surprising.)
Here is how it works —
...
#ActivityPub #ActivityStreams #FediDev #Fediverse #ObjectTypeNote #ObjectTypeQuotation #retejo
Quotations & the Fediverse / ActivityPub
1/
One thing I used to do a lot on social-media is — post quotations.
Sometimes I was reading a book. And, I would quote things from the book and post it on social-media.
Or I was reading a scholarly paper, or reading a blog post, or watching a video, or listening to a podcast, etc.
...
I was thinking — how could you represent a quotation in ActivityPub‽
#ActivityPub #ActivityStreams #FediDev #Fediverse #ObjectTypeNote #ObjectTypeQuotation #retejo
![“[And yet another book that made an argument that was in favor of human universals is] Brent Berlin and Paul Kay’s [book] "Basic Color Terms: Their Universality and Evolution" (1969).”
“by the early 1970s two independent lines of psychological research, culminating in studies conducted among preliterate peoples of New Guinea, had shown that there are universal facial expressions of emotions.”
“Berlin and Kay show that although color classification does vary, it also shows remarkable uniformities: particularly in the sequence in which basic color terms are added to the lexicon.”
“Anthropologists and linguists had long known that the way colors are classified varies from language to language. Careful studies conducted by anthropologists after World War II, such as Harold Conklin’s (1955) study of Hanunóo color words, made the point very clearly.”
“The different sets of words for color in various languages …”](https://files.mastodon.social/media_attachments/files/115/213/467/578/403/241/original/7e01ca3ce905134a.png)
2/
How could you represent a quotation in ActivityPub‽
...
I suppose there are 2 major approaches.
Either use an existing Object Type. Maybe:
type="Note"
Or create a new Object Type:
type="Quotation"
...
Here is the interesting thing though —
#ActivityPub #ActivityStreams #FediDev #Fediverse #ObjectTypeNote #ObjectTypeQuotation #retejo
Quotations & the Fediverse / ActivityPub
1/
One thing I used to do a lot on social-media is — post quotations.
Sometimes I was reading a book. And, I would quote things from the book and post it on social-media.
Or I was reading a scholarly paper, or reading a blog post, or watching a video, or listening to a podcast, etc.
...
I was thinking — how could you represent a quotation in ActivityPub‽
#ActivityPub #ActivityStreams #FediDev #Fediverse #ObjectTypeNote #ObjectTypeQuotation #retejo
8/
REMEMBER: this is for power-users, not regular users
How would you get ActivityPub / ActivityStreams into HTML using RDFa‽
Like this:
<div vocab="https://www.w3.org/ns/activitystreams#" typeof="Note">
<p property="name">Hello!</p>
<p>How do you do?</p>
</div>
AGAIN, REMEMBER: this is for power-users, not regular users.
Regular users can just write Markdown or HTML and Retejo will figure this out automatically for you
#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa
9/
A regular users might write Markdown like this:
"""
# Hello!
How do you do?
"""
Or write HTML like this:
"""
<article>
<h1>Hello!</h1>
<p>How do you do?</p>
</article>
"""
#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa
7/
If you are wondering what RDFa is —
You might be more familiar with OpenGraph.
OpenGraph is usually the thing that causes "preview cards" to be showed for links shared on social-media.
OpenGraph is written in RDFa. Which, in practice, is some special HTML elements added to the page.
For example:
<meta property="og:image" content="https://example.com/img/preview.png" />
So what about ActivityPub‽ —
#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa
8/
REMEMBER: this is for power-users, not regular users
How would you get ActivityPub / ActivityStreams into HTML using RDFa‽
Like this:
<div vocab="https://www.w3.org/ns/activitystreams#" typeof="Note">
<p property="name">Hello!</p>
<p>How do you do?</p>
</div>
AGAIN, REMEMBER: this is for power-users, not regular users.
Regular users can just write Markdown or HTML and Retejo will figure this out automatically for you
#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa
6/
Obviously, beginners are NOT going to do this, but — some power-users may want this level of control.
There are different way this could be done, but — one way might be that power-users could use RDFa to explicitly specify what data from the HTML gets into the ActivityPub / ActivityStreams data.
Again, beginners and typical users would NOT do this.
But a power-user might want to.
Here is an example —
#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa
7/
If you are wondering what RDFa is —
You might be more familiar with OpenGraph.
OpenGraph is usually the thing that causes "preview cards" to be showed for links shared on social-media.
OpenGraph is written in RDFa. Which, in practice, is some special HTML elements added to the page.
For example:
<meta property="og:image" content="https://example.com/img/preview.png" />
So what about ActivityPub‽ —
#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa
5/
So, what would be a good user-experience (UX) for power-users be — in a system that automatically creates ActivityPub / ActivityStreams data from HTML and Markdown‽
One thought I had is that power-users could explicitly mark what data from their HTML gets into the ActivityPub / ActivityStreams data (if they want to).
I'll explain —
#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa
6/
Obviously, beginners are NOT going to do this, but — some power-users may want this level of control.
There are different way this could be done, but — one way might be that power-users could use RDFa to explicitly specify what data from the HTML gets into the ActivityPub / ActivityStreams data.
Again, beginners and typical users would NOT do this.
But a power-user might want to.
Here is an example —
#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa
4/
I think one mistake some software does is — they create a good experience for beginners, but have a poor experience for power-users.
And keep in mind that — some beginners become power-users later on.
I think it is important to design for power-users, too, in addition to beginners.
...
#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa
5/
So, what would be a good user-experience (UX) for power-users be — in a system that automatically creates ActivityPub / ActivityStreams data from HTML and Markdown‽
One thought I had is that power-users could explicitly mark what data from their HTML gets into the ActivityPub / ActivityStreams data (if they want to).
I'll explain —
#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa
3/
If a typical user is writing in Markdown, and their Markdown file has a level-1 heading right at the beginning, then —
That could go into the ActivityPub "name" field.
And, similar could be done for HTML, too.
...
But what about power users —
#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa
4/
I think one mistake some software does is — they create a good experience for beginners, but have a poor experience for power-users.
And keep in mind that — some beginners become power-users later on.
I think it is important to design for power-users, too, in addition to beginners.
...
#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa
2/
What are "good" ways of automatically creating ActivityPub / ActivityStreams data from HTML and Markdown‽
I think the answer depends on who, for example, is writing HTML, and how they are writing it.
For example, is this a typical user? Is this a power-user? Do they know HTML? And if they do know HTML, how well do they know it? Etc?
I will show you what I mean —
...
#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa
3/
If a typical user is writing in Markdown, and their Markdown file has a level-1 heading right at the beginning, then —
That could go into the ActivityPub "name" field.
And, similar could be done for HTML, too.
...
But what about power users —
#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa
1/
I have spending time thinking of ways you could automatically create ActivityPub / ActivityStreams data from HTML and Markdown
Most people will probably write in plain UTF-8 text, or Markdown, or HTML
How to do you take that and get it onto the Fediverse and Social Web‽
This isn't just a question of how to technically do it — but also a question of user-experience (UX)
I.e., what are "good" ways of doing it‽
...
#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa
2/
What are "good" ways of automatically creating ActivityPub / ActivityStreams data from HTML and Markdown‽
I think the answer depends on who, for example, is writing HTML, and how they are writing it.
For example, is this a typical user? Is this a power-user? Do they know HTML? And if they do know HTML, how well do they know it? Etc?
I will show you what I mean —
...
#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa
1/
I have spending time thinking of ways you could automatically create ActivityPub / ActivityStreams data from HTML and Markdown
Most people will probably write in plain UTF-8 text, or Markdown, or HTML
How to do you take that and get it onto the Fediverse and Social Web‽
This isn't just a question of how to technically do it — but also a question of user-experience (UX)
I.e., what are "good" ways of doing it‽
...
#ActivityPub #ActivityStreams #FediDev #Fediverse #Markdown #retejo #RDFa
Today I discovered an interesting inconsistency in Activity Streams specs while investigating a Fedify issue.
The question: How should we interpret URLs like "icon": "https://example.com/avatar.png"?
JSON-LD context (https://www.w3.org/ns/activitystreams): @type: "@id" → “This is an IRI reference, dereference it to fetch an ActivityStreams object.”
Activity Streams Primer: “assume that a bare string is the href of a Link object, not an id” (no dereferencing)
Result: JSON-LD processor-based implementations try to parse PNG files as JSON and fail.
Turns out w3c/activitystreams#595 already discusses the same issue for href properties. I added a note that icon, image, etc. have the same problem.
Once again reminded of how tricky spec work can be…
#ActivityPub #Fedify #ActivityStreams #fedidev #specifications
We're excited to share an update on #Fedify's development! While we're actively working on Fedify 1.9 in the main branch, we've also begun preparations for Fedify 2.0 in the next branch.
Before you get too excited about revolutionary new features, we want to set clear expectations: Fedify 2.0 will primarily focus on cleaning up technical debt that we couldn't address due to backward compatibility constraints. This means removing deprecated APIs and making breaking changes that will ultimately result in a cleaner, more maintainable codebase. Think of it as a major housekeeping release—necessary work that will make Fedify better in the long run.
Some of the planned improvements include adding readonly modifiers throughout our types and interfaces to better enforce our immutability-by-default principle, implementing our own RFC 6570 URI Template library for symmetric expansion and pattern matching, and various CLI tool migrations to our new Optique framework for better cross-runtime support. While the majority of changes will be about refinement rather than revolution, these updates will strengthen Fedify's foundation and improve interoperability across the #fediverse. You can track all planned changes in detail by checking out the Fedify 2.0 milestone on our GitHub repository.
In #WebFinger, are there any relations that use the template property instead of the href property, excluding the http://ostatus.org/schema/1.0/subscribe relation?
FenTiger @fentiger@zotum.net
The #Fedify monorepo has grown to 16 packages!
We've been working hard to make Fedify more modular and easier to integrate with your favorite tools and platforms. From the core framework to database drivers, from CLI tools to web framework integrations—we've got you covered.
Our packages now include:
Each package is available on JSR and/or npm, making it easy to pick exactly what you need for your ActivityPub implementation.
What integration would you like to see next? Let us know!
Are you a Fediverse developer? Do you work with ActivityPub?
You should follow https://activitypub.space
And here is the awesome thing — you can follow it from your existing Fediverse account!
Follow these activitypub.space channels:
• 
@generalGeneral Discussion
• 
@technical-discussion
• 
@faqFrequently Asked Questions
• 
@random
• 
@meta
(Thank you 
@julian )
We're excited to announce the release of BotKit 0.3.0! This release marks a significant milestone as #BotKit now supports #Node.js alongside #Deno, making it accessible to a wider audience. The minimum required Node.js version is 22.0.0. This dual-runtime support means you can now choose your preferred #JavaScript runtime while building #ActivityPub #bots with the same powerful BotKit APIs.
One of the most requested features has landed: poll support! You can now create interactive polls in your #bot messages, allowing followers to vote on questions with single or multiple-choice options. Polls are represented as ActivityPub Question objects with proper expiration times, and your bot can react to votes through the new onVote event handler. This feature enhances engagement possibilities and brings BotKit to feature parity with major #fediverse platforms like Mastodon and Misskey.
// Create a poll with multiple choices
await session.publish(text`What's your favorite programming language?`, {
class: Question,
poll: {
multiple: true, // Allow multiple selections
options: ["JavaScript", "TypeScript", "Python", "Rust"],
endTime: Temporal.Now.instant().add({ hours: 24 }),
},
});
// Handle votes
bot.onVote = async (session, vote) => {
console.log(`${vote.actor} voted for "${vote.option}"`);
};The web frontend has been enhanced with a new followers page, thanks to the contribution from Hyeonseo Kim (
@gaebalgom개발곰)! The /followers route now displays a paginated list of your bot's followers, and the follower count on the main profile page is now clickable, providing better visibility into your bot's audience. This improvement makes the web interface more complete and user-friendly.
For developers looking for alternative storage backends, we've introduced the SqliteRepository through the new @fedify/botkit-sqlite package. This provides a production-ready SQLite-based storage solution with ACID compliance, write-ahead logging (WAL) for optimal performance, and proper indexing. Additionally, the new @fedify/botkit/repository module offers MemoryCachedRepository for adding an in-memory cache layer on top of any repository implementation, improving read performance for frequently accessed data.
This release also includes an important security update: we've upgraded to #Fedify 1.8.8, ensuring your bots stay secure and compatible with the latest ActivityPub standards. The repository pattern has been expanded with new interfaces and types like RepositoryGetMessagesOptions, RepositoryGetFollowersOptions, and proper support for polls storage through the KvStoreRepositoryPrefixes.polls option, providing more flexibility for custom implementations.
For a sneak preview of my followup to the Fediverse Schema Observatory, there's now a project page on the lab website for the ActivityPub Fuzzer:
https://asml.cyber.harvard.edu/activitypub-fuzzer/
Basically it lets an ActivityPub server developer test compatibility with simulated messages from Fediverse software known to the Observatory (dozens of software projects and hundreds of versions!). The dev can do this entirely in a local dev environment.
The project is still in the works but I'll be releasing the code soon.
super nice.
#fedidev #ActivityPub
What I worked on the past weeks was to analyze the current news corpora of the University of Leipzig in different languages.
Then mixed it with an anonymized fedi corpus and wrote a thing which can
- compress ActivityPub Objects to 20% of its size by a combination of semantic compression where 256 languages can be covered. The rest would be uncompressed in multilanguage Objects (see Evans new Primer Page).
Result is UInt8Array for a database.
What I am working on now is to "preserve hashtags and common knowledge".
One byte is a pointer to Hashtags (where any word has a # at 0) and one byte is a pointer to 3x(256²) wikidata tables. So that we directly get the e.g. Q1055 for Hamburg and can ask the author if the prominent Hamburg is meant …
This was just a first demo for German https://github.com/sebilasse/compressDE which meanwhile improved and soon you can generate your lexica from corpora.
btw This can detect 852 languages https://github.com/redaktor/languages
Less data, better climate …
I just realized that the default specifications for ActivityPub/ActivityStreams do not have a way to perform an update on an object's ID. (ie, moving it from example.com/1 -> example.com/2)
An Update activity does not allow ID updates because it would lose the reference to the original one. (It can be massaged by using an Origin property, but I don't like that).
Another option would be to use a Move activity (which is defined as moving objects between collections), where the Origin property is the object itself instead of a collection. (I like this behaviour better, as it requires less divergence from the spec)
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.
@z9mb1wwj 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.
Improved the setup steps for a new #ONI instance.
Initially it wasn't possible to operate everything without manually editing some json files, but now everything works with vanilla client to server #ActivityPub activities triggered from a CLI helper.
Now I just need to put it all into a document.
Feditext, one of my favorite, consistently solid fediverse apps, (love it for GtS) is looking for iOS devs to swat at a bug or two.
#FediApps #FediDev #iosdev https://mastodon.social/@Feditext/114990933150568200
Web Monetization, Programming
11/
I implemented Simple Payment Setup Protocol (SPSP) (from scratch) in the Go programming-language.
https://github.com/reiver/go-spsp
Base on the specification I found before.
#CrowdBucks #FediDev #Fediverse #Golang #PaymentPointer #PeerTube #WebMonetization
Web Monetization, Programming
12/
I have been looking for (working) Payment-Pointers being used by others.
But, ever time I find one — it doesn't work (mostly because one provides seems to have stopped working).
...
For example, over here:
https://web.archive.org/web/20250222120416/https://pupper-pages.glitch.me/
If I look at the HTML source-code, I see a Payment-Pointer.
But the host in the Payment-Pointer doesn't work.
#CrowdBucks #FediDev #Fediverse #PaymentPointer #PeerTube #WebMonetization
Web Monetization, Programming
10/
I found some updates for the https://paymentpointers.org/ web-site that haven't been deployed:
https://github.com/interledger/paymentpointers.org/pull/57/files
Some of it confirms things I suspected. But, there is also new information in there.
#CrowdBucks #FediDev #Fediverse #PaymentPointer #WebMonetization
Web Monetization, Programming
11/
I implemented Simple Payment Setup Protocol (SPSP) (from scratch) in the Go programming-language.
https://github.com/reiver/go-spsp
Base on the specification I found before.
#CrowdBucks #FediDev #Fediverse #Golang #PaymentPointer #PeerTube #WebMonetization
Web Monetization, Programming
9/
I implemented Payment Pointers (from scratch) in the Go programming-language.
https://github.com/reiver/go-pymtptr
Base on the specification I found before.
#CrowdBucks #FediDev #Fediverse #Golang #PaymentPointer #PeerTube #WebMonetization
Web Monetization, Programming
10/
I found some updates for the https://paymentpointers.org/ web-site that haven't been deployed:
https://github.com/interledger/paymentpointers.org/pull/57/files
Some of it confirms things I suspected. But, there is also new information in there.
#CrowdBucks #FediDev #Fediverse #PaymentPointer #WebMonetization
🔒 Security Update for BotKit Users
We've released #security patch versions BotKit 0.1.2 and 0.2.2 to address CVE-2025-54888, a security #vulnerability discovered in #Fedify. These updates incorporate the latest patched version of Fedify to ensure your bots remain secure.
We strongly recommend all #BotKit users update to the latest patch version immediately. Thank you for keeping the #fediverse safe! 🛡️
All #Fedify users must immediately update to the latest patched versions. A #critical authentication bypass #vulnerability (CVE-2025-54888) has been discovered in Fedify that allows attackers to impersonate any #ActivityPub actor by sending forged activities signed with their own keys.
This vulnerability affects all Fedify instances and enables complete actor impersonation across the federation network. Attackers can send fake posts and messages as any user, create or remove follows as any user, boost and share content as any user, and completely compromise the federation trust model. The vulnerability affects all Fedify instances but does not propagate to other ActivityPub implementations like Mastodon, which properly validate authentication before processing activities.
The following versions contain the #security fix: 1.3.20, 1.4.13, 1.5.5, 1.6.8, 1.7.9, and 1.8.5. Users should update immediately using their package manager with commands such as npm update @fedify/fedify, yarn upgrade @fedify/fedify, pnpm update @fedify/fedify, bun update @fedify/fedify, or deno update @fedify/fedify.
After updating, redeploy your application immediately and monitor recent activities for any suspicious content. Please also inform other Fedify operators about this critical update to ensure the security of the entire federation network.
The safety and security of our community depends on immediate action. Please update now and feel free to leave comments below if you have any questions.
Web Monetization, Programming
9/
I implemented Payment Pointers (from scratch) in the Go programming-language.
https://github.com/reiver/go-pymtptr
Base on the specification I found before.
#CrowdBucks #FediDev #Fediverse #Golang #PaymentPointer #PeerTube #WebMonetization
Web Monetization, Programming
very nice!
#FediDev
considering "from scratch" to be the default ;) I have written today the generator for semantic compression in any language.
What I am working on is a compressor for ActivityPub Objects with Natural Language Maps. It converts anything to a UInt8Array which is only 20-25% of the original.
Basically it loads a news corpus from the Leipzig Uni (not the famous Leipzig HGB Academy Of Visual Arts, from the ordinary University but it's fine ;) Then it generates a definition for the most 256 common languages.
Made a demo for the before (from scratch generated) DE 2 days ago https://github.com/sebilasse/compressDE and it will be combined with the language detection of 852 locales https://github.com/redaktor/languages
Web Monetization, Programming
8/
PeerTube seems to have Payment-Pointers and Web-Monetization built-in already.
#CrowdBucks #FediDev #Fediverse #PaymentPointer #PeerTube #WebMonetization
![Web Monetization payment pointer
Interledger payment pointer for Web Monetization. In the form of $example.org/account.
[_______________________________________________]](https://files.mastodon.social/media_attachments/files/114/983/283/158/844/839/original/cfcc38464b2b98ce.png)
Web Monetization, Programming
9/
I implemented Payment Pointers (from scratch) in the Go programming-language.
https://github.com/reiver/go-pymtptr
Base on the specification I found before.
#CrowdBucks #FediDev #Fediverse #Golang #PaymentPointer #PeerTube #WebMonetization
Web Monetization, Programming
7/
And, a description of the fields in the SPSP JSON seems to be here:
https://interledger.org/developers/rfcs/simple-payment-setup-protocol/#response-body
• destination_account
• shared_secret
• receipts_enabled
.
#CrowdBucks #FediDev #Fediverse #PaymentPointer #SimplePaymentSetupProtocol #SPSP #WebMonetization
Web Monetization, Programming
8/
PeerTube seems to have Payment-Pointers and Web-Monetization built-in already.
#CrowdBucks #FediDev #Fediverse #PaymentPointer #PeerTube #WebMonetization
Is there anything like #foursquare or, let's call it, micro place reviews app based on #activitypub ?
We're thrilled to announce Fedify 1.8.1, a mega release made possible through the incredible efforts of contributors from South Korea's #OSSCA (Open Source Contribution Academy). This release marks a significant milestone in #Fedify's development, bringing major architectural changes, new packages, and numerous enhancements across the board.
Note: Version 1.8.0 was skipped due to a versioning error.
Fedify has been restructured as a #monorepo, consolidating all packages into a single repository with unified versioning. This change streamlines development and ensures all packages are released together with consistent version numbers.
All existing Fedify packages now live under one roof:
This release introduces four new packages to the Fedify ecosystem:
Federation and Context classesA powerful new feature that allows you to create custom collections beyond the standard ActivityPub collections. This enables implementation of domain-specific collections while maintaining federation compatibility.
Contributors: ChanHaeng Lee [#310, #332]
Federatable interface: setCollectionDispatcher() and setOrderedCollectionDispatcher()getCollectionUri() method to the Context interfaceKey–value stores now optionally support CAS operations for atomic updates, enabling optimistic locking and preventing lost updates in concurrent environments.
KvStore.cas() methodMemoryKvStore and DenoKvStoreNew utility functions make working with #fediverse handles more convenient.
Contributors: ChanHaeng Lee [#278]
parseFediverseHandle() — Parse handles into componentsisFediverseHandle() — Validate handle formattoAcctUrl() — Convert handles to URLsFediverseHandle interface for type safetyContributors: Lee ByeongJun [#248, #281], Hyunchae Kim [#51, #315]
LookupWebFingerOptions.maxRedirection option for controlling redirect behaviorAbortSignal for request cancellationDocumentLoaderOptions interfacesignal options to LookupObjectOptions, LookupWebFingerOptions, and DoubleKnockOptionsThe CLI has received significant improvements thanks to our OSSCA contributors:
fedify webfinger CommandContributors: ChanHaeng Lee [#260, #278], KeunHyeong Park [#311, #328]
Look up WebFinger information for any fediverse resource:
@user@server) and URLs--user-agent option for custom User-Agent headers--allow-private-address for local testing--max-redirection to control redirect followingfedify nodeinfo CommandContributors: Hyeonseo Kim [#267, #331, #168, #282, #304]
Replaces the deprecated fedify node command with improved terminal rendering.
fedify lookup CommandContributors: Jiwon Kwon [#169, #348, #261, #321]
-o/--output option to save results to filesfedify inbox CommandContributors: Hasang Cho [#262, #285], Jang Hanarae [#191, #342]
--actor-name and --actor-summary options for customizing temporary actorsfedify init --dry-runContributors: Lee ByeongJun [#263, #298]
Preview project initialization without creating files.
Contributors: Cho Hasang [#257, #341]
Correctly handles color output based on TTY detection and NO_COLOR environment variable.
Contributors: Hyeonseo Kim [#286, #339]
New Elysia integration brings Fedify to Bun-powered applications with a simple plugin interface:
import { Elysia } from "elysia";
import { fedify } from "@fedify/elysia";
const app = new Elysia()
.use(fedify(federation, { /* options */ }))
.listen(3000);Contributors: Jaeyeol Lee [#269, #309]
Enterprise-ready NestJS integration with dependency injection support:
import { FedifyModule } from "@fedify/nestjs";
@Module({
imports: [
FedifyModule.forRoot({
kv: new MemoryKvStore(),
queue: new InProcessMessageQueue(),
origin: "https://example.com",
}),
],
})
export class AppModule {}Contributors: An Subin [#274, #318]
SqliteKvStore implementation compatible across all major JavaScript runtimes:
import { SqliteKvStore } from "@fedify/sqlite";
const kv = new SqliteKvStore("./fedify.db");Contributors: Lee ByeongJun [#197, #283]
Comprehensive testing utilities with mocking support for Fedify applications:
import { MockFederation, MockContext } from "@fedify/testing";
const mockFederation = new MockFederation();
const mockContext = new MockContext();
// Track sent activities with full metadata
// Support custom path registration
// Multiple activity type listenersThis release represents an extraordinary community effort, particularly from the participants of South Korea's OSSCA (Open Source Contribution Academy) (Note: page in Korean). We extend our heartfelt thanks to all contributors:
@2chanhaeng초무) — Custom collections, fediverse handles, WebFinger command
@joonnotnotJoon) — WebFinger redirections, dry-run, testing utilities
@r4bb1t) — AbortSignal support@gaebalgom개발곰) — Elysia integration, nodeinfo command
@kodingwarriorJaeyeol Lee) — NestJS integration
@nyeongAn Nyeong (安寧)) — SQLite driver@z9mb1wwj) — Terminal image display, output options
@crohasang크롸상) — Color output handling, actor customization
@meneleHanal Ae) — Activity object type display
@w8385박근형) — WebFinger redirect options
@ooheundaoed) — Fixed PostgreSQL test race conditions [#346, #350]
@songbirds) — Test stability improvements for Redis and code generation [#344, #347]
@woaol벨) — CLI version management and documentation fixes [#306, #329, #330, #343]Your contributions have made Fedify stronger and more versatile than ever. The OSSCA program's support has been instrumental in achieving this milestone release.
If you're using separate Fedify packages, update all packages to version 1.8.1:
{
"dependencies": {
"@fedify/fedify": "^1.8.1",
"@fedify/cli": "^1.8.1",
"@fedify/express": "^1.8.1"
}
}All packages now share the same version number, simplifying dependency management.
There are no breaking changes in this release. All existing code should continue to work without modifications.
With the monorepo structure in place and new integrations available, we're excited to continue improving Fedify's developer experience and expanding its capabilities. Stay tuned for more updates, and thank you for being part of the Fedify community!
For detailed technical information about all changes, please refer to the full changelog.
Fedify is an open-source project that helps developers build federated server applications powered by ActivityPub. Join us on GitHub or Discord to contribute or get help!