smallcircles (@smallcircles@social.coop)
The delightful #ActivityPub development list has been renamed. Now the 3 fedi-related lists are:
- delightful-fediverse-experience
- delightful-fediverse-clients
- delightful-fediverse-development
The #fediverse development list has largely been stripped of non-developer resources, which moved to fediverse experience.
The fediverse development list should now be reorganized to be most useful to the dev crowds who wanna join the fedi adventure.
Resources missing? File an issue or PR.
Show Original Post
louischance (@louischance@piaille.fr)
A cool thing I discovered yesterday with the #activitypub plugin for #wordpress: you can change the blog username without losing your followers nor your post history.
For my blog I initially chose @blog@ikacode.com, but later realized that only the first part of the handle would show in posts ("blog").
I changed it to "ikacode", to have @ikacode.
After 2 minutes I searched the new handle in Mastodon, and opened the profile.
Everything was there.
The former handle then disappeared.
NOTE: Previous references to the initial profile in posts (like in this one) don't link to the new one but it's fine.
Thanks @pfefferle and all the contributors for this great plugin!
Show Original Post
node (@node@nokoto.org)
Content warning:<p> <p>For some reason I was sending an invalid value with the <code>alg</code> property, and, uhhh, Matthew, you really should have paid attention to Section 3.3 under each algorithm where it states the possible acceptable values:</p><ul><li><code>rsa-pss-sha512</code></li><li><code>rsa-v1_5-sha256</code> </li><li><code>hmac-sha256</code></li><li><code>ecdsa-p256-sha256</code></li><li><code>ecdsa-p384-sha384</code></li><li><code>ed25519</code></li></ul><p>I only have support for <code>rsa-v1_5-sha256</code> (incoming or outgoing) at the moment (as does Mastodon), but finally I have my first successful signed RFC 9421 POST requests to both a Mastodon instance and Wordpress ActivityPub Plugin instance. Those plugins are handling the covered components that I chose to use...</p></p>
For some reason I was sending an invalid value with the alg property, and, uhhh, Matthew, you really should have paid attention to Section 3.3 under each algorithm where it states the possible acceptable values:
rsa-pss-sha512rsa-v1_5-sha256hmac-sha256ecdsa-p256-sha256ecdsa-p384-sha384ed25519
I only have support for rsa-v1_5-sha256 (incoming or outgoing) at the moment (as does Mastodon), but finally I have my first successful signed RFC 9421 POST requests to both a Mastodon instance and Wordpress ActivityPub Plugin instance. Those plugins are handling the covered components that I chose to use fine.
Show Original Post
mariusor (@mariusor@metalhead.club)
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.
Show Original Post
louischance (@louischance@piaille.fr)
@oldrup @oldrup.dk I did the same mistake and named my blog @blog before noticing the handle wouldn't show. Since I have some followers, I don't want to change it anymore now, but I'll remember for next time I install the #activitypub plugin!
I also wondered about what happens when you publish a test post and delete it afterwards. It looks like it remains visible on the #Fediverse.
Show Original Post
oldrup (@oldrup@mastodon.green)
@oldrup.dk - Test posts are federated right away. That is fine, but something to keep in mind if there are already followers. Especially as it is not obvious to me, if it is possible to delete already federated posts.
- Using identical tags in WordPress and in the instance bio, makes the tags (on mastodon) link to the tag archive on the website. Handy.
If you follow @oldrup.dk, with have some patience, it's very helpful to me. Feedback welcome.
Show Original Post
x (@x@alis.me)
A short(ish) guide to , applicable to basically any website (including static ones . . . sort of).
I admit I got most of the way through this for alisfranklin.com, before scrapping it and going with a more straightforward crossposting script (with the ability to implement something along these lines for importing comments). Mostly because as soon as you start getting into anything involving following, receiving interactions, etc., you start having to mess around with digital signing and a bunch of other stuff I couldn’t be arsed with. Might I go back and have another crack at it at some point? Maybe! But . . . not for now.
Show Original Post
smallcircles (@smallcircles@social.coop)
There's Babylonian confusion of speech in all #ActivityPub related discussions that occur across the #fediverse. We have the #SocialWeb protocol specification itself, then the reality-on-the-wire where gaps and optional technology choices are implemented. And where protocol decay and post-facto #interoperability (follow-the-Mastodon) murky the waters. Leading to misunderstandings, wrong expectations, etc.
An example is in how we talk on Nomadic Identity:
https://socialhub.activitypub.rocks/t/nomadic-identity-for-the-fediverse/2101/96?u=aschrijver
Show Original Post
smallcircles (@smallcircles@social.coop)
In the 2nd topic above I describe the conceptual architecture as:
> "a distributed network of addressible actors for the exchange of social activities”
There is a full domain model there, and this conceptual architecture conveys the full promise and potential for #ActivityPub based social networking. All the various gears and mechanics that make the protocol tick have a place in it.
It is a bit of a meta-model, as it is not directly basis for impl in code, but input for specs.
Show Original Post
smallcircles (@smallcircles@social.coop)
As an example, a recent related topic by @lax on #SocialHub mentions clearer layering of the protocol stack..
https://socialhub.activitypub.rocks/t/layered-activitypub/5449
In another recent topic on #ActivityPub C2S I mention a need to discern between conceptual architecture and implementation. "Server" and "client" aren't part of the conceptual architecture, and likely need a different place in the domain model on that basis. They are different kind of abstractions than e.g. an "actor".
Show Original Post
2025 (@2025@www.filmvanalledag.nl)
Nieuwe bruggen
Sinds de dood van Twitter, wilde ik schrijven, maar ondertussen is best de vraag of je niet beter kan schrijven ‘Sinds de transformatie van Twitter naar X’, want het platform Twitter is toch wel blijven bestaan, weliswaar onder een andere naam. Alle politici zitten daar nog, alle sportploegen zitten daar nog, het netwerkeffect is toch te sterk. De totale ineenstorting is niet […]
https://www.filmvanalledag.nl/2025/08/10/nieuwe-bruggen/
Show Original Post
smallcircles (@smallcircles@social.coop)
Yes there are many ways to slice leading to entirely different models. In terms of categories I discern:
- Business domains (e.g. Microblogging, Content management).
- Application domains (e.g. ForgeFed, Mastodon).
Above I refer more to a meta-model, but expressed as a business domain it'd be something like "Protocol development".
Protocol layers, transports, extension points, wire formats, conceptual architecture, etc. So we can talk about #ActivityPub in ubiquitous language.
Show Original Post