Elektrine
Log in Register

#fedidev

58 posts · Last used 14h

Back to Timeline
Profpatsch
Beady Belle Fanchannel
@Profpatsch@mastodon.xyz · 1d ago
So we are going to have the Email-Problem sooner or later. Sending Spam is for free and infinitely scalable. In order to combat this, we need to add friction to posting. The most obvious solution here is to add transaction cost in addition to moderation. “you can only send me a message if you pay me 1ct” for example. In systems like Twitter this was a hidden cost layer that active background moderation fixed, which is why Musk’s X is overrun by spam. #fedidev
2
0
2
Boosted by fedicat @fedicat@pc.cafe
fedify
Fedify: ActivityPub server framework
@fedify@hollo.social · 2d ago
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
Boosted by fedicat @fedicat@pc.cafe
drfed
DrFed
@drfed@hackers.pub · 2d ago
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
Boosted by fedicat @fedicat@pc.cafe
silverpill
silverpill
@silverpill@mitra.social · Jun 04, 2026
FEP-f228: Backfilling conversations has been updated: https://codeberg.org/fediverse/fep/pulls/853 I added tootik and Lemmy to the implementation list and did a little cleanup. This FEP feels complete, so I am requesting final comments. Full text: https://fediverse.codeberg.page/fep/fep/f228/ #fep_f228 #fep #fedidev
0
0
1
Boosted by fedicat @fedicat@pc.cafe
lauti
LAUTI
@lauti@bonfire.cafe · Jun 05, 2026
The next step in our #activitypub implementation is ready! This brings a simple instance actor object along with #webfinger support for it and a #nodeinfo endpoint. We highly appreciate reviews from any #fedidev 🙏 codeberg.org/Klasse-Methode/... We are really greatfull for @nlnet@social.nlnet.nl to fund this work and for @linos@graz.social for being such a great mentor!
0
0
1
Boosted by fedicat @fedicat@pc.cafe
julian
julian
@julian@community.nodebb.org · Jun 01, 2026

Feature Highlight for v4.12.0 — Activity Intents

<p>A new feature silently dropped in v4.12.0. NodeBB now supports Activity Intents!</p> <h3>Huh? What's an Activity Intent?</h3> <p>It is <a href="https://w3id.org/fep/3b86" rel="nofollow ugc">a proposal</a> by <a href="https://mastodon.social/@benpate">@<bdi>benpate@mastodon.social</bdi></a> that aims to "extend the capabilities of an ActivityPub server beyond a user's outbox, and enable direct interactions with content on the wider social web."</p> <p>In other words, it allows you to more seamlessly use your fediverse account on other sites without having to register a new account just to contribute.</p> <p>In even simpler words, it means you can go to other forums and interact with content without needing to register a new account.</p> <p>It directly tackles one of the fediverse "hard problems" I talked about last year — <strong>account fragmentation</strong>. You won't need additional accounts just to use other sites, your identity stays whole :sunglasses:</p> <p>Let's learn more about how that works![...]</p> Hover or focus to reveal Sensitive
A new feature silently dropped in v4.12.0. NodeBB now supports Activity Intents! Huh? What's an Activity Intent? It is a proposal by @benpate@mastodon.social that aims to "extend the capabilities of an ActivityPub server beyond a user's outbox, and enable direct interactions with content on the wider social web." In other words, it allows you to more seamlessly use your fediverse account on other sites without having to register a new account just to contribute. In even simpler words, it means you can go to other forums and interact with content without needing to register a new account. It directly tackles one of the fediverse "hard problems" I talked about last year — account fragmentation. You won't need additional accounts just to use other sites, your identity stays whole :sunglasses: Let's learn more about how that works![...] Account Fragmentation in a Nutshell Right now, when you browse to a different site, you usually have to create a new account to interact with it. For example, if you check out someone's Pixelfed profile, you're not able to comment or like their pictures without an account there. This has always been how the internet worked, and before the advent of single sign-on, which lets you log in with a different account (but still creates a new account on that site), that was just how it was. Essentially, there was no way to interact with content using your main identity. The workarounds were numerous... copying URLs, searching for the account on your instance, etc. All of which were fairly friction-heavy, so the next best thing was just to create a local account and fragment your identity. Activity Intents intends (ha!) to address this by allowing servers to advertise support for different types of social actions. How It Works You browse to another site and want to carry out an action, such as liking the post, or writing a reply. That site asks you to enter an Open Social Web handle (or log in, if you have a local account), and you enter it. It then queries your server to see what Intents it supports (e.g. "Like", "Create") If there's a match, it sends you back to your server, where you can complete the action. That's about it! There are additional details about designing the actual flow, and how to "remember" each visitor's social web handle, but the basics are as listed above. What it looks like in NodeBB We've integrated support for four intents: Like/Dislike → These map to upvote and downvote respectively Create → These would be topic creations and replies Follow → self-explanatory Object → Load an ActivityPub resource in NodeBB We integrated two-way support which means that if you land on a NodeBB and your fediverse account supports Activity Intents, then you can simply hit like, reply, or follow from NodeBB, and be sent back to your home server, all without the hassle of copying and pasting links into a search bar. Integrating Activity Intents was a high-impact way to tackle the problem of account fragmentation. Users of NodeBB (whose forums have updated to v4.12.0) should not have to feel pressure to create local accounts elsewhere if the site they end up on supports Activity Intents as well.
0
0
1
silverpill
silverpill
@silverpill@mitra.social · May 20, 2026

Fix Linked-Data Signature bypass through JSON-LD graph restructuring features

JSON-LD adds nothing to Fediverse except bugs and security vulnerabilities.

Of course, there is an alternative to Linked Data signatures that doesn’t require Linked Data, much simpler and more secure:

FEP-8b32: Object Integrity Proofs

#activityPub #fedidev

0
0
1
julian
Julian Fietkau
@julian@fietkau.social · Apr 06, 2026
RE: https://mastodon.social/@bagder/116359048796181736 Could be potentially nice for fediverse server testing, as more implementations make the jump to final RFC 9421 HTTP signatures. On the flip side, ever more complex curl invocations (here: Accept header plus signature fields plus key file, presumably) suggest use of more specialized CLI tools, such as provided by @fedify@hollo.social, or at least scripts/aliases. Speaking of RFC 9421, which notable fediverse implementations can't handle it yet? Anyone keeping track? #ActivityPub #FediDev #RFC9421
Quoting
daniel:// stenberg:// @bagder@mastodon.social

RFC 9421 HTTP Message Signatures support in maybe?

https://github.com/curl/curl/pull/21239

Open quoted post
4
11
9
Boosted by fedicat @fedicat@pc.cafe
hongminhee
洪 民憙 (Hong Minhee) :nonbinary:
@hongminhee@hollo.social · May 14, 2026
A friend of mine, @siliconsjang@siliconbeest.sjang.dev, released SiliconBeest v1.0.0 today. It's a #fediverse server built on #Cloudflare Workers, D1, R2, and Queues, using Fedify. I like the starting point: after watching fediverse servers go down together during Cloudflare outages, they thought, why not just run on Cloudflare directly? They're aiming for something cheap enough that a small instance can stay on Cloudflare's free plan, and a somewhat bigger one can fit in the $5/month tier. It's still early; a lot is missing, and Mastodon/Misskey API compatibility is more of a long-term goal. I'm glad to see Fedify put to use for something like this. Worth checking out. The source code is on GitHub under AGPL 3.0. #ActivityPub #fedidev RE: https://hackers.pub/@siliconsjang/2026/siliconbeest-v1.0.0
12
4
8
Profpatsch
Beady Belle Fanchannel
@Profpatsch@mastodon.xyz · May 07, 2026
#Hashtags don’t scale #fedidev
0
13
4
Profpatsch
Beady Belle Fanchannel
@Profpatsch@mastodon.xyz · May 06, 2026
The new #FediForum videos are up :) https://spectra.video/c/fediforum_demos/videos
4
0
10
reiver
@reiver ⊼ (Charles) :batman:
@reiver@mastodon.social · May 04, 2026
🌐 FediCon 2026 is coming up — and Early Bird (discounted) tickets are still available! We want FediCon to be open and accessible, which is why there is also an affordable (Reduced fare) ticket option for those who want it. Come be part of the conversations shaping the Fediverse and the future of the Social Web. 📅 August 6–9, 2026 📍 UBC campus, Vancouver, BC, Canada 🎟️ Get your FOSSY ticket here: https://2026.fossy.ca/attend/tickets/ #FediCon #FediCon2026 #FOSSY #FOSSY2026 #FediDev #Fediverse
2
0
11
reiver
@reiver ⊼ (Charles) :batman:
@reiver@mastodon.social · May 03, 2026
There is a comparison that can be made between ActivityPub and Event-Sourcing. 1/ With Event-Sourcing, your source-of-truth is an append-only series of events. Ex: USER_REGISTERED, EMAIL_ADDRESS_VERIFIED, PASSWORD_CHANGED, etc. In ActivityPub, this is similar to the inbox, outbox, etc being an append-only series of Activity. Ex: Create, Like, Undo, etc. ... #ActivityPub #ActivityStreams #EventSourcing #FediDev
4
3
7
In reply to
reiver
@reiver ⊼ (Charles) :batman:
@reiver@mastodon.social · May 03, 2026
There is a comparison that can be made between ActivityPub and Event-Sourcing. 2/ With Event-Sourcing, you can "project" the events to get another (often more peformant) view of the data in the events. Without having to incur the cost of having to read all the events to figure out the final state. ... #ActivityPub #ActivityStreams #EventSourcing #FediDev
1
1
4
In reply to
reiver
@reiver ⊼ (Charles) :batman:
@reiver@mastodon.social · May 03, 2026
There is a comparison that can be made between ActivityPub and Event-Sourcing. 3/ With ActivityPub, Activities are often applied to an object. That object gets assigned an ID in the form of a URL. (And, by URL I mean URL, URI, IRI, etc.) One doesn't have to read through all the Activities in an inbox, outbox, etc to get the final state of an object. One can just get the JSON-LD document from the object's ID URL to get the final state. #ActivityPub #ActivityStreams #EventSourcing #FediDev
1
2
4
reiver
@reiver ⊼ (Charles) :batman:
@reiver@mastodon.social · May 03, 2026
It seems as if the uploadMedia ActivityPub extension does not provide a way to resume an upload that didn't previously compete. https://www.w3.org/wiki/SocialCG/ActivityPub/MediaUpload If, for example, you are working with large files (such as video files) this would matter. Because if you uploaded 1GB, and the upload stopped, you would want to resume at where it stopped, and not have to upload from the beginning again. This would be important for ActivityPub C2S adoption. #ActivityPub #ActivityStreams #FediDev
4
9
7
In reply to
reiver
@reiver ⊼ (Charles) :batman:
@reiver@mastodon.social · May 03, 2026
I can think of different ways to support resumable uploads with ActivityPub, but — just to see what others are doing — PeerTube seems to have resumable uploads already. PeerTube seems to use this protocol for it: https://github.com/kukhariev/node-uploadx/blob/master/proto.md I like that it uses Content-Range in the protocol. I would have done the similar. #ActivityPub #ActivityStreams #FediDev
4
1
4
In reply to
reiver
@reiver ⊼ (Charles) :batman:
@reiver@mastodon.social · May 03, 2026
Just thinking out loud — If we wanted to support resumable uploads in C2S API, then — we probably need some URL to upload the file chunks to. … When a user POST to their own outbox, the HTTP "201 Created" response will have a "Location" header that provides a URL. Maybe that could be used as the upload URL. Or, maybe the JSON-LD document at that URL might contain a URL under the "object" field that could be used as the upload URL. Other options too #ActivityPub #ActivityStreams #FediDev
3
1
4
Profpatsch
Beady Belle Fanchannel
@Profpatsch@mastodon.xyz · May 03, 2026
your daily dose of json+ld, #fedidev
5
15
6
reiver
@reiver ⊼ (Charles) :batman:
@reiver@mastodon.social · May 01, 2026
What do you think about JSON-LD language maps for "preferredUsername"? I.e., preferredUsernameMap. "preferredUsernameMap": { "en": "hello", "fa": "درود", "ko": "안녕하세요 " } #FediDev #JSONLD
6
3
6