Your Home Feed is the inbox of an ActivityPub actor — in particular YOUR ActivityPub actor.
There could be an actor for each hash-tag, too.
You could even do Del.icio.us like things — and have actors for intersections of hash-tags, too.
These hash-tag actors' inboxes would need to be readable by anyone.
...
This could be a more ActivityPub like API alternative to Mastodon's "GET /API/v1/tags/{name}" API.
#ActivityPub #FediDev #FediDevs #Fediverse #HashTag #HashTags
FEP drafting: Am I using “side effects” here the same way as other ActivityPub developers? I've seen the term used a bunch in casual conversation, but my personal understanding of it is kinda fuzzy.
there is currently a #Piefed Hackathon going on if anyone is interested in partaking. There are groups working on spanish, german, french and japanese translations, and a bunch of other things.
https://tarte.nuage-libre.fr/c/fediverse/p/221411/hackathon-this-week-7-8-febuary #fediverse #fedidev #activitypub
I have deeply mixed feelings about #ActivityPub's adoption of JSON-LD, as someone who's spent way too long dealing with it while building #Fedify.
Part of me wishes it had never happened. A lot of developers jump into ActivityPub development without really understanding JSON-LD, and honestly, can you blame them? The result is a growing number of implementations producing technically invalid JSON-LD. It works, sort of, because everyone's just pattern-matching against what Mastodon does, but it's not correct. And even developers who do take the time to understand JSON-LD often end up hardcoding their documents anyway, because proper JSON-LD processor libraries simply don't exist for many languages. No safety net, no validation, just vibes and hoping you got the @context right. Naturally, mistakes creep in.
But then the other part of me thinks: well, we're stuck with JSON-LD now. There's no going back. So wouldn't it be nice if people actually used it properly? Process the documents, normalize them, do the compaction and expansion dance the way the spec intended. That's what Fedify does.
Here's the part that really gets to me, though. Because Fedify actually processes JSON-LD correctly, it's more likely to break when talking to implementations that produce malformed documents. From the end user's perspective, Fedify looks like the fragile one. “Why can't I follow this person?” Well, because their server is emitting garbage JSON-LD that happens to work with implementations that just treat it as a regular JSON blob. Every time I get one of these bug reports, I feel a certain injustice. Like being the only person in the group project who actually read the assignment.
To be fair, there are real practical reasons why most people don't bother with proper JSON-LD processing. Implementing a full processor is genuinely a lot of work. It leans on the entire Linked Data stack, which is bigger than most people expect going in. And the performance cost isn't trivial either. Fedify uses some tricks to keep things fast, and I'll be honest, that code isn't my proudest work.
Anyway, none of this is going anywhere. Just me grumbling into the void. If you're building an ActivityPub implementation, maybe consider using a JSON-LD processor if one's available for your language. And if you're not going to, at least test your output against implementations that do.
2/
RE: https://mastodon.social/@reiver/115945290105913697
The resolving of a Fediverse ID to one or more cryptographic public-keys could happen via the activity-file for the user.
A JSON-LD namespace (separate from ActivityPub) could put the cryptographic public-keys into the activity-file.
But, I think we would need more information than what the 2 current methods for including cryptographic public-keys currently support.
#ActivityPub #Cryptography #FediDev #FediDevs #Fediverse #JSONLD
1/
RE: https://mastodon.social/@reiver/115945290105913697
Right now, Fediverse IDs resolve to HTTPS URLs.
For example, the Fediverse ID:
＠reiver＠mastodon.social
Resolves to HTTPS URL:
https;//mastodon·social/users/reiver
...
If we wanted cryptographic public-keys to serve as a basis of Identity on the Fediverse, then —
We would (similarly) also need a Fediverse ID to resolve to one or more cryptographic public-keys
...
#ActivityPub #Cryptography #FediDev #FediDevs #Fediverse #JSONLD
I dream of being able to store my online social presence, identity, and history just as — an (organized) set of static files.
A set that I control.
And, I can (if I want to) host myself. (I.e., I am the "source of truth" / "origin" for my files.)
RE: https://mastodon.social/@reiver/116018261922778583
#ActivityPub #FediDev #FediDevs #FediUX #Fediverse #FediverseUX
3/
If you cannot get (most) regular people to write JSON-LD, JSON, or even HTML —
But, you might be able to get them (regular people) to write something similar to Markdown and INI —
Then, are there ways you could (explicitly or implicitly) encode JSON-LD type information, such as ActivityPub, into a Markdown-like or INI-like file — in a way where they (regular people) would likely include it?
I suspect — probably yes.
#ActivityPub #FediDev #FediDevs #FediUX #Fediverse #FediverseUX
Unfortunately for anyone reading this, I had an idea, although I'm not ready to talk publicly about it.
But I do have a question for #fedidev s out here: Is there a nice way to handle account fragmentation? So having 3 accounts for 3 platforms that need to write-interact with the activitypub stream?
Really new to all of this, sorry if this question is kinda noob-y
RE: https://mastodon.social/@by_caballero/115968453192473247
interesting writeup about federated package management by @andrewnez
#fedidev
@Bonfire: Modular Communication Tools on the Open Social Web
https://fosdem.org/2026/schedule/event/LSUYXG-bonfire_modular_communication_tools_on_the_open_social_web
So… the first day of #FOSDEM 2026 was so inspiring, and it really motivated to build more things for #ActivityPub and the #fediverse! Also it was a lot of fun to meet hundreds of kind and smart people!
On stage now, @django — arguing for widespread adoption of ActivityPub client-server (C2S) protocol.
I agree with him.
At the very least, to make extension of ActivityPub through JSON-LD namespaces possible.
But also to decouple Fediverse client development from Fediverse server development.
And more.
#ActivityPub #FediDev #FediDevs #Fediverse #FOSDEM #FOSDEM2026 #SocialWeb #SocialWebFOSDEM #SocialWebFOSDEM2026
Mentioned by @evan :
(Site doesn't work yet, apparently.)
But also here is the git repo:
https://github.com/social-web-foundation/tags.pub
#FediDev #FediDevs #Fediverse #FOSDEM #FOSDEM2026 #SocialWeb #SocialWebFOSDEM #SocialWebFOSDEM2026 #HashTag #HashTags
Mentioned by @andypiper :
The Mastodon team is planning to release a universal "share" button.
(It wasn't clear to me if this was just for Mastodon servers — or if it would work with non-Mastodon servers, too. It was mentioned briefly from the audience.)
#FediDev #FediDevs #Fediverse #FOSDEM #FOSDEM2026 #SocialWeb #SocialWebFOSDEM #SocialWebFOSDEM2026 #Mastodon
Speaker on stage in the Social Web room at FOSDEM 2026 is arguing for open-source Fediverse projects to do product-development.
Although he is framing it in terms of building for a community.
I agree with him. Although, I think it is true of open-source projects in general.
(For completeness — others have said that, too.)
#FediDev #FediDevs #Fediverse #FOSDEM #FOSDEM2026 #SocialWeb #SocialWebFOSDEM #SocialWebFOSDEM2026
Day 1 of 2 of FOSDEM 2026 in Brussels — I am attending the Social Web track.
https://fosdem.org/2026/schedule/track/social-web/
I arrived a bit late. But, I am here now 🙂
#FediDev #FediDevs #Fediverse #FOSDEM #FOSDEM2026 #SocialWeb #SocialWebFOSDEM #SocialWebFOSDEM2026
First talk today at the Social Web Devroom we have @pfefferle talking about the state of WordPress's fediverse integration
#FOSDEM #ActivityPub #fedidev
By the way, if you're attending #FOSDEM 2026 and are interested in #Fedify, an #ActivityPub server framework, please consider checking out my talk in the Social Web Room tomorrow.
