silverpill

Developer of ActivityPub-based micro-blogging and content subscription platform Mitra. I help maintain the FEP repository and write my own FEPs too. Currently working on ActivityPub Next.

Public Key

npub1df0nthpgzfmvxrzj0cfypmmt45l0y770j260auqhm3l45hp3uhkqx27gmw

NIP-05 Address

silverpill@mitra-social.mostr.pub

Profile Code

nprofile1qqsx5he4ms5pyakrp3f8uyjqaa4660hj008e9d877qtacl66tsc7tmqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsde92a5

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub1df0nthpgzfmvxrzj0cfypmmt45l0y770j260auqhm3l45hp3uhkqx27gmw

Show more details

Last Notes

2026-04-01 18:59:31 UTC

How Nomadic ActivityPub (FEP-ef61) compares to other protocols?
I made a table:
https://codeberg.org/ap-next/ap-next/src/branch/main/nomadpub.md#protocol-comparison

2026-03-30 16:46:45 UTC

- reply

@nprofile…qhdx Is there a blocklist? I've never seen FediBuzz announcing my posts, although I did see it announcing posts from other Mitra instances.

2026-03-30 16:40:52 UTC

- reply

@nprofile…m7tc Welcome back

2026-03-29 17:18:42 UTC

Announcing Mitra Mini v0.1.0
Mitra Mini is an ActivityPub client that implements nomadic identity. It has become stable enough that I decided to cut the first release.
The basic features have been implemented: posts, reposts, likes. For more information, check the project's readme:
https://codeberg.org/silverpill/minimitra
It all started nearly four years ago with a vague idea that linking cryptographic keys to #ActivityPub actors could unlock decentralized identity in Fediverse. Eventually, the solution was discovered, and implemented by several projects, but these implementations were servers, not clients. Now there is finally a client, and the design has been proven to work well.
#NomadicIdentity

2026-03-26 22:19:31 UTC

- reply

@nprofile…h0ux @nprofile…cjkf I would simply ignore an obviously vibe coded project with no history.
Fedibook doesn't has a license, so it is not qualified for inclusion either way.

2026-03-26 21:45:43 UTC

- reply

@nprofile…h0ux I am already facing this problem in @nprofile…cjkf.
I think vibe-coded projects will be de-prioritized because most of them are not newsworthy and immediately abandoned by their authors. A project will be featured only if it survives and gets some traction.

2026-03-26 21:21:39 UTC

- reply

@nprofile…ptyr ActivityPub relays can help with that
https://joinfediverse.wiki/Relays

2026-03-26 21:17:17 UTC

- reply

@nprofile…svam You can say it at https://codeberg.org/silverpill/mitra
Some fedi developers took an aggressive stance, but I don't care that much. If a bug report is legitimate, then it shouldn't matter what tool was used by the reporter.

2026-03-25 21:31:20 UTC

- reply

@nprofile…2y8k @nprofile…c7yq @nprofile…s2sp
What hasn’t been considered is the ability of multiple people to speak with “one voice” yet.
Imageboards?
There was one that federated using ActivityPub: https://github.com/FChannel0/FChannel-Server

2026-03-25 21:19:12 UTC

- reply

@nprofile…c7yq Fediverse is not like email because ActivityPub has many different message types. What kind of client API developers use is irrelevant.

2026-03-23 21:54:14 UTC

Mitra 5.0
Like previous major releases, this one contains several changes that may require operator's attention.
It also introduces a stability guarantee for REST API. From now on, breaking changes in API will only happen in major releases.
RE: https://mitra.social/objects/019d1c79-6704-c2e2-0787-cc2cb36a816c
#nevent1q…fgny

2026-03-21 20:04:12 UTC

- reply

@nprofile…ut88 +1 for formalizing the existing practice in a FEP.
PropertyValue is covered in FEP-fb2a, but it proposes an alternative representation which implementers must support:
https://codeberg.org/fediverse/fep/src/branch/main/fep/fb2a/fep-fb2a.md

2026-03-20 13:40:17 UTC

- reply

@nprofile…dcn3 @nprofile…s2sp No, but I think you can use it to set up a darknet shop

2026-03-19 16:52:03 UTC

Mitra 4.20.0 will add context property to replies. Among other things, this should help Pleroma re-construct threads when some posts are not available.
cc @nprofile…s2sp
RE: https://mitra.social/objects/019d06ec-3768-06df-99b6-61bb71a86d45
#nevent1q…2666

2026-03-19 16:44:36 UTC

- reply

@nprofile…ut88
It's the question of why so many open source tools get built by startup teams in the first place.
Not that many. Their developers are the loudest, but in most cases a not-for-sale alternative exists, and often that alternative is of higher quality.
My dependency tree is almost corpo- and startup-free (the biggest problem is probably TypeScript).

2026-03-10 14:13:04 UTC

- reply

@nprofile…vkpw @nprofile…x4d0
This request returns an HTML page instead of ActivityPub object:
curl -H 'Accept: application/ld+json; profile="https://www.w3.org/ns/activitystreams"' https://blog.fabiomanganiello.com/article/Madblog-federated-blogging-from-markdown

2026-03-10 13:57:29 UTC

Large-scale online deanonymization with LLMs
https://arxiv.org/abs/2602.16800
It's over, anons.

2026-03-09 21:22:56 UTC

- reply

@nprofile…s2sp HTTP signature bypass is serious, but I can't figure out what it going in this PR. Looks like a bunch of unrelated changes

2026-03-09 21:03:26 UTC

- reply

@nprofile…z7ps I usually add "on your own hardware"

2026-03-09 21:01:39 UTC

https://www.openwall.com/lists/oss-security/2026/03/09/7
Misskey and Sharkey, ActivityPub-based social network services (similar to Mastodon), have released updates to patch vulnerabilities Sharkey maintainers describe as "extremely severe".
Details have not been not published yet but "missing permission checks" and "authentication bypass" sound like vulnerabilities that could be prevented by following recommendations from FEP-fe34: Origin-based security model.

2026-03-09 20:04:03 UTC

- reply

@nprofile…ekds
I have a couple of comments regarding the spec https://codeberg.org/portafed/portafed/src/branch/main/portafed-spec/spec.md
It contains a comparison with FEP-ef61, but it is not quite correct:
- FEP-ef61 identity is not actor-rooted. The closest equivalent of FEP-ef61 identity in normal ActivityPub is a server with a domain name. A single FEP-ef61 authority can manage multiple actor documents.
- FEP-ef61 does not lack a migration flow. Strictly speaking, it doesn't need one, because data is not attached to a server and can be continuously synchronized between multiple servers. But a more familiar migration flow is also possible via outbox export-import.
@nprofile…e40t

2026-03-09 12:39:53 UTC

- reply

@nprofile…dqzr
https://example.viii.fi/posts/69aeb347-03d0-dc44-83c8-9c7c488ff6e0.json
It is served by an instance of your bot? The value of inReplyTo in this document is an empty string, which is not a valid URI.

2026-03-08 22:02:03 UTC

- reply

@nprofile…9fxy
There have also been rumblings of implementing Zot/Nomad’s nomadic identities, although that effort seems to have stalled out. Finally, some platforms like Streams/Hubzilla (Nomad & Zot respectively) offer limited user account ownership, bridging internally to ActivityPub. However, if a server went down, the user would retain their Nomad/Zot following while losing their ActivityPub followers/following.
It didn't stall. Streams and its successor Forte support ActivityPub-native nomadic identities.
There are other implementers too: https://codeberg.org/ap-next/ap-next/src/branch/main/nomadpub.md
cc @nprofile…2lch

2026-03-08 21:18:01 UTC

FEP-ef61 update: https://codeberg.org/fediverse/fep/pulls/773
Gateways can now remove integrity proofs from collections when they generate collection views. This enables filtering and pagination and is compatible with client-side signing (FEP-ae97).
#fep_ef61

2026-03-08 18:49:55 UTC

- reply

@nprofile…yr0l Hi, do you known anyone working on ActivityPub-Farcaster bridge?

2026-03-08 18:41:34 UTC

- reply

@nprofile…8scz Cool. Did you implement AP from scratch or used some library/framework?

2026-03-07 19:20:15 UTC

- reply

@nprofile…3mlc
The Mastodon API is open source, but it is not an open standard. It is designed, maintained, and changed by one project, without input from the rest of the ecosystem.
Not without. The design of this API is shaped by the needs Mastodon users. Sometimes PRs are submitted by developers of 3rd party clients and by developers of other servers. Independent implementers of Mastodon API often extend it, and copy each other's extensions, there is even a discussion about Mastodon API Enhancement Proposals (similar to FEPs).
So I think that by now it is very much an open standard.
ActivityPub API may have W3C's stamp or approval, but that doesn't mean anything if nobody uses it.
P.S. Does you blog not federate anymore?

2026-03-07 17:53:54 UTC

- reply

@nprofile…tc7m The site was built by @nprofile…k5jq, I also contribute to this project from time to time.
Yes, authors are responsible for maintaining implementation lists, but FEP process is meant to be collaborative and others can add missing implementations by opening a PR.

2026-03-07 17:38:06 UTC

- reply

FEP-0151 is now FINAL, with 5 implementations: https://codeberg.org/fediverse/fep/pulls/760

2026-03-07 17:06:11 UTC

FEP website now displays the number of implementations for each implementable proposal:
https://fediverse.codeberg.page/fep/final/
These numbers are based on the information that authors provide in the "Implementations" section of a proposal.
By default, proposals are informational, so authors need to opt in by adding type: implementation to the metadata block.
#fep #fedidev

2026-03-07 00:39:28 UTC

- reply

@nprofile…s2sp
>Rational solutions to the LLM problem
I think your proposed solution doesn't scale. Small projects could treat all contributions the same, but popular projects will be overwhelmed by slop.
Making LLMs socially unacceptable is a rational solution, and might even be the only real solution because it works at scale.

2026-03-06 19:35:43 UTC

- reply

@nprofile…rxpq Paying for it with monero

2026-03-06 19:29:46 UTC

minimitra now uses #PGlite instead of postgres:
https://pglite.dev
It's a portable database, so the installation process will not require any sysadmin skills. You just need to install the rust compiler and npm (the latter is required for pglite, I plan to remove this dependency in the future).
I had to reset my database because pg_restore didn't work with pglite, but identity and actor ID have been preserved: @nprofile…z3wv.

2026-03-04 17:58:16 UTC

- reply

@nprofile…th8u
I built this: https://codeberg.org/silverpill/mitra
It is lightweight and is packaged with a web client.

2026-03-04 17:55:03 UTC

- reply

@nprofile…wchz I know two python libraries:
https://codeberg.org/bovine/bovine
https://github.com/fedi-libs/apkit

2026-03-04 14:59:30 UTC

- reply

@nprofile…2y8k Yes, poll-only ActivityPub is possible. There is a FEP about it: https://fediverse.codeberg.page/fep/fep/b06c/

2026-03-04 14:44:37 UTC

- reply

@nprofile…vgdh OK, I'll increase the limit.

2026-03-02 13:52:14 UTC

- reply

@nprofile…tsag Hosted copies of an object may diverge, but the latest version of it is always available on the client side, because servers can't sign objects (unless server and client are a single application).
How those annotations work? I think instance actor could propose a change, which the author may later accept (and publish an Update activity, for example).

2026-03-02 13:30:26 UTC

- reply

@nprofile…6wm2 The server needs to know mentioned users by the time the post is published. Someday I will figure out how to make it work. Meanwhile, you can verify your mentions using the preview feature

2026-02-28 19:12:01 UTC

- reply

@nprofile…6wm2 Hey, nice to see you online again.
What is this bot? Looks interesting

2026-02-28 16:20:06 UTC

- reply

@nprofile…2gus
Changed it to Create: https://codeberg.org/fediverse/fep/pulls/770
@nprofile…u8dh @nprofile…d8rs @nprofile…53ta

2026-02-28 15:46:48 UTC

- reply

@nprofile…2y8k I believe most implementations do that. My server re-fetches a key only if the cached key is 1 day old, for example.

2026-02-28 15:25:00 UTC

- reply

@nprofile…2gus Publishing process doesn't change much. A generic server should deliver activities to actors specified in to and cc fields. It should keep track of collections, such as followers collection, and "expand" them before delivery. This part is not different from the regular ActivityPub.
I think ID assignment should also work the same. In the FEP I proposed Add activity without object as a special activity for creating collections, but now I see that it will not work if IDs are minted by a server (no FEP-ae97).
Perhaps it should be a Create, after all, as @nprofile…u8dh described in an adjacent comment. I was hesitant to use Create because this is a problem for FEP-ae97 clients (not a big one though).
@nprofile…d8rs @nprofile…u8dh

2026-02-27 22:17:47 UTC

- reply

@nprofile…u8dh @nprofile…davq @nprofile…d8rs No, my goal is to interoperate with many Fediverse servers, not just Mastodon. I agree that a generic server is supposed to support any activity, this is exactly what I was arguing about for the last two days, and this is what my FEP is about.

2026-02-27 22:02:28 UTC

- reply

@nprofile…2gus Let's assume that my client is a music player. It publishes a Listen activity where object is an Audio. This activity should increase playCount on the Audio object.
One way to support this on the server side is to teach it about Listen, Audio and how to update playCount. This is how most existing servers are built.
But a server described in my FEP would work differently:
- It doesn't know anything about Listen, Audio or playCount.
- Upon receiving Listen, it will recognize it as an activity, and embedded Audio as an object.
- Since this is not a CRUD operation, it will not check permissions.
- If Listen activity has a result property, the server will process that activity as well.
- If result is an Update activity, the server will recognize it as a CRUD operation and will check permissions: Update.actor and Audio.attributedTo must be the same.
- The server will save both activities, Listen and Update.
- Then it will deliver them to intended recipients (to and cc).
Effects are client's responsibility now, it must provide an Update activity if it wants to update playCount. There are other requirements too, for example all objects should have an attributedTo property, which is needed for permission checks.
But in this setup a single server can work with any kind of client.
@nprofile…d8rs @nprofile…u8dh

2026-02-27 20:55:54 UTC

- reply

@nprofile…s2sp @nprofile…xsag @nprofile…t3h7 @nprofile…y6jc @nprofile…tsag I think you're right about FEPs and cooperation. The optimal strategy is cooperate by default and defect only when the other side defects.
With quotes we were almost successful. The initial version of Mastodon's consent-respecting quotes was based on FEP-e232, but later they decided to introduce a new property.
Now there's FEP-521a (public keys), which they expressed interest in implementing.
Even with Mastodon, it's worth trying.
>Groups
I think Lemmy's implementation is not bad. There is also Conversation Containers from Hubzillaverse, and a possibility of convergence, see this thread https://lemmy.ml/post/43519233

2026-02-27 20:30:46 UTC

- reply

@nprofile…davq Nevermind, side effects wouldn't be a problem. However, it still doesn't seem to be compatible with ActivityPub... Because Announce activity is not defined in C2S context :)
https://www.w3.org/TR/activitypub/#client-to-server-interactions
@nprofile…834j @nprofile…d8rs

2026-02-27 18:43:48 UTC

- reply

@nprofile…davq Placing activities in the target inbox is not always enough, sometimes there are side effects.
In my FEP I discuss how we can deal with that.
There is more to it, see my response to @nprofile…834j:
https://mitra.social/objects/019ca012-a698-5c2a-a6fa-a547373294cc
@nprofile…d8rs

2026-02-27 18:28:47 UTC

- reply

@nprofile…davq
what Vocata did
This project is often brought up as an example of a generic server, but it never reached production stage. The last commit was in 2023.
It is one thing to have an idea and build a prototype, and a completely different thing to build an application that is secure and interoperates with the rest of the network.

2026-02-27 18:17:50 UTC

- reply

@nprofile…2y8k Yes, the signature contains key ID, from which you can obtain actor ID and perform origin / ownership checks.

2026-02-27 18:12:45 UTC

- reply

@nprofile…davq
What happens when you send a "Offer" message to an actor on Mastodon?
The behavior of Offer activity is not described in ActivityPub, so Mastodon is not required to support it. Curiously, ActivityPub mentions Offer when it talks about the side effects of Accept:
The side effect of receiving this in an inbox is determined by the type of the object received, and it is possible to accept types not described in this document (for example, an Offer).
...This statement is not compatible with the idea of a generic server.
Can I create a group actor on Mastodon?
I don't know. But it can create Service actors, I guess it can be easily patched to allow creation of Group actors too.
Can I use this actor to boost other actor's posts and have it visible on a Lemmy client?
I think FEP-1b12 Announce is not compatible with ActivityPub. It has different side effects, doesn't update shares collection.
How can a Mastodon client ask the server to get a collection of all images with an specific tag?
Maybe something like /api/v1/timelines/tag/{tag}?only_media=true ?
@nprofile…d8rs

2026-02-27 17:36:21 UTC

- reply

@nprofile…ut88 Better developer tooling is the only correct answer to rising complexity. Getting 200 different servers to smoothly interoperate is impossible, but we can do that with 10 libraries.

2026-02-27 17:24:43 UTC

- reply

@nprofile…2y8k I don't know Alloy, but I tried to analyze how authorization should be done in ActivityPub. The result is this document:
https://fediverse.codeberg.page/fep/fep/fe34/

2026-02-27 17:08:22 UTC

- reply

@nprofile…834j It looks simple on the surface, but in reality it is much more complicated than a non-generic server. In addition to activity transfer, generic server needs to maintain collections. First of all, a followers collection, which is often used as a delivery target. Then likes, shares etc. It needs to enforce permissions, to prevent actors on the same server from deleting each other posts.
This is doable if you only care about activities defined in ActivityPub. But then you want to introduce context collection. And then 50 other extensions. How to do that without special-casing every one of them?
This is where duck typing (FEP-2277) and unified security model (FEP-fe34) become really handy. No matter what the client sends, you can figure out what it is (an object, an actor, or a collection), and enforce permissions.

2026-02-27 17:05:08 UTC

- reply

@nprofile…d8rs Mastodon supports all standard activities and has a wide variety of clients. I don't find softwares with similar capabilities impressive, although I respect your work (the only ActivityPub server-client project that is not a vaporware).
I doubt that language choice makes much difference, and Rust is not a dynamically typed language anyway. The difficulty you might be facing is likely due to JSON-LD.
The thanks was for your input with regards to collection management.

2026-02-27 13:32:08 UTC

Recently, there was a discussion about generic #ActivityPub servers. Several people claimed that they were working on one, but it turned out that their "generic" servers only support activities defined in the ActivityPub specification. Such a server shouldn't be called generic. It is not difficult to build, neither it is an interesting concept because competing protocols (e.g. Nostr) already offer much more.
I've been writing a #FEP that describes how to build a real generic server. It is not finished yet, but I feel like now is a good time to publish it:
FEP-fc48: Generic ActivityPub server
This kind of server:
- Can process any object type, and can process non-standard activities like EmojiReact.
- Compatible with FEP-ae97 clients.
- Does not require JSON-LD.
I attempted to implement it when I was researching security properties of FEP-ae97 API: https://codeberg.org/silverpill/fep-ae97-server. Back then I didn't know what to do with side effects, but now I think that we can simply force clients to specify them.
Special thanks to @nprofile…d8rs and @nprofile…u8dh for their input.
#C2S

2026-02-27 13:32:08 UTC

2026-02-27 11:11:13 UTC

- reply

@nprofile…ut88 It is a good plan!
FEP-ef61 is still DRAFT and includes a warning that the URI scheme may change to ap+ef61.
Right, all of this is very unstable and may change in the future. In order to be more confident with the spec, I want to build:
- A fully featured FEP-ae97 client (WIP: https://codeberg.org/silverpill/minimitra)
- A generic FEP-ae97 server (this is only an idea: https://codeberg.org/silverpill/feps/src/branch/main/fc48/fep-fc48.md).
Gateway forwarding trust. When forwarding inbox/outbox activities to other gateways, which servers should be trusted and how should that trust be established? FEP-ef61 says unsecured collections may only be accepted from servers in the actor's gateways array, but the details of how a gateway authenticates itself to another gateway are not fully specified.
Could you clarify what you mean by authenticating itself to another gateway?
When an application (client or server) fetches a portable collection from a server that is listed in actor's gateways array, it may skip proof verification. This applies to collections like inbox or outbox.
If a portable collection is fetched from some other server, the proof is required.

2026-02-27 10:33:29 UTC

- reply

@nprofile…c7yq
Yeah, those backlinks.
What backlinks?

2026-02-27 10:17:54 UTC

- reply

1. I don't care much about the "official" version of AP. It is outdated and increasingly irrelevant, most of the real development happens elsewhere.
2. Interledger is a part of Ripple/XRP cryptocurrency project, which is a scammy crypto company.
Please don't spread FUD. Especially when it's so obviously counterproductive. Seems like maybe you need to touch grass a bit more often
Oh my. Counterproductive to what? All you do here is talking about things you know nothing about and trying to insult me. You're pathetic.

2026-02-26 10:15:06 UTC

- reply

@nprofile…ut88 It's a good idea. However, I'd like to note that w3id.org/fep/ permalinks are not canonical, they were proposed in FEP-888d but have never become "official".

2026-02-24 21:04:29 UTC

- reply

@nprofile…20nh How much it is tied to Mastodon? Is it possible to use Fediway with other servers?

2026-02-24 19:38:50 UTC

- reply

@nprofile…ks9l I am pretty sure that nice things are within reach.
Fediverse-ActivityPub already significantly diverges from W3C-ActivityPub. I think eventually they will become completely different protocols, that just requires a bit of coordination among devs.

2026-02-24 19:04:24 UTC

- reply

@nprofile…53ta If by "sufficiently improve" you mean throwing it away and replacing with a better protocol, then yes it's possible.

2026-02-24 18:05:43 UTC

I enabled compatible IDs in minimitra, so @nprofile…z3wv actor should now be reachable from most fedi servers. Follow/unfollow may also work, but only if your activity IDs are resolvable.

2026-02-22 20:07:50 UTC

- reply

@nprofile…z7ps If you're talking about digital technology, today we have more freedom than 10-20 years ago. But an average internet user has no freedom at all, for them internet is like TV.

2026-02-22 19:47:11 UTC

- reply

@nprofile…qhdx Opened an issue: https://github.com/astro/buzzrelay/issues/136

2026-02-22 18:59:38 UTC

- reply

@nprofile…77cu Information about implementations is also present in FEPs, but it is similarly incomplete.

2026-02-21 19:13:05 UTC

- reply

@nprofile…d8rs I would use next if collection is already fetched, but in my case the client needs to start from a position where it stopped during the previous sync session.
This is for inbox synchronization.

2026-02-21 19:06:34 UTC

- reply

@nprofile…d8rs Thanks.
I think this could be mentioned in the FEP.

2026-02-21 18:58:36 UTC

@nprofile…d8rs What convention do you use to iterate through an ordered collection? Suppose I need to get items starting with <object-id>.
I don't see an operator for this in FEP-6606: ActivityPub client to server collections addressing conventions

2026-02-21 18:34:20 UTC

- reply

@nprofile…ek9w
@nprofile…4y4n do you have any plans regarding FEP-0837?

2026-02-21 18:32:03 UTC

- reply

@nprofile…ek9w I am still the only implementer.
flohmarkt devs expressed interest but haven't implemented it yet: https://codeberg.org/flohmarkt/flohmarkt/issues/5#issuecomment-9659876

2026-02-20 18:09:57 UTC

- reply

@nprofile…de6s
>but the governance infrastructure for consent, a way to distinguish deliberate community choices from defaults, is not discussed at all
Let's discuss ActivityPub relays.

2026-02-19 16:50:19 UTC

- reply

And here is a post on the same subject from @nprofile…l5yp
https://w.on-t.work/activitypub/c2s

2026-02-19 16:39:59 UTC

It might be not possible to create a generic #ActivityPub server, but nevertheless this is an interesting thought experiment that helps simplify the protocol and figure out the best way to extend it.
I've been thinking about generic servers for quite some time (because this complements my work on nomadic clients), here are my notes:
https://codeberg.org/silverpill/feps/src/branch/main/fc48/fep-fc48.md
@nprofile…ks9l
RE: https://mastodon.social/users/eyeinthesky/statuses/116095929503245071
#nevent1q…3k4a

2026-02-19 14:49:21 UTC

- reply

@nprofile…834j @nprofile…8qd7 @nprofile…ks9l @nprofile…d8rs @nprofile…c7yq
Yes, they are building blocks, together with Create, Update and Delete. Everything else can be constructed from them.

2026-02-19 13:53:57 UTC

- reply

@nprofile…ks9l I think Add / Remove should be used for extended collections. Like, Announce etc look like legacy / tech debt to me.

2026-02-19 13:02:44 UTC

- reply

@nprofile…9q3v I think @nprofile…qcew is on Hubzilla, perhaps Mastodon doesn't like it.
>atproto
It's true that funding and centralized architecture makes development easier, but these are not the only things that matter. You also need a culture where people are rewarded for building cool stuff and solving problems.
>Mastodon moves slowly for new big features but everytime I try another software I notice the lack of simple stuff
This is simply because Mastodon has more people working on it. Sooner or later other micro-blogging software will catch up if developers don't burn out.

2026-02-19 12:16:30 UTC

- reply

suggested language re: "correctness"
This is much better, thanks. I also changed "incorrect / false" to "intentionally skewed" (as @nprofile…s2sp suggested in another thread).
suggested expanded reasoning re: software.name and software.version
Added that too, and mentioned a valid reason for checking software version: security vulnerabilities.
PR: https://codeberg.org/fediverse/fep/pulls/761

2026-02-18 23:47:00 UTC

- reply

Yeah that's pretty much what I meant.

2026-02-18 23:45:34 UTC

- reply

Often fanfare is the only thing that is being shipped

2026-02-17 21:02:02 UTC

- reply

what defines "correct" here?
Inflated or randomized stats, for example. I don't like "incorrect" here, but haven't found a better word yet.
also, is a SHOULD NOT here sufficient?
No, I think data aggregators like fediverse.observer are useful services, and there is no good reason to disrupt their operation by poisoning data.
these requirements read as redundant, and also the 2nd requirement is more restrictive than the 1st which is weird
I think these should be separate requirements.
The first one is about any NodeInfo parameters, including metadata. There is a FEP about advertising capabilities using metadata (FEP-9fde), I want to discourage this practice, but this method is already used in the wild, hence a SHOULD.
On the other hand, I can't think of any good reason to rely on software. This is a discriminatory practice, because as a developer you can easily add a feature flag to your NodeInfo metadata, but you can't change software to e.g. mastodon.

2026-02-11 18:47:36 UTC

- reply

If you don't understand the message, maybe it is not for you.
These organizations are the participants of the AP working group.

2026-02-09 22:35:40 UTC

- reply

@nprofile…p3lz minimitra is similar to mitra but it's a client, not server.

2026-02-09 21:05:31 UTC

- reply

@nprofile…qum9 Thanks. Do you think we can use it in fedi somehow?

2026-02-09 20:54:37 UTC

- reply

@nprofile…t47j @nprofile…uteg Classic DNS-based identities and cryptographic identities can coexist in Fediverse. Bridges are not necessary.
Cryptographic identities can also come in different flavors thanks to DIDs. If you want to use a keypair like they do in Nostr, choose did:key. If you want to delegate key management to a 3rd party, use did:web. If you want something in the middle, there is did:webvh.

2026-02-09 20:44:21 UTC

First post on public network created using minimitra:
https://mitra.social/.well-known/apgateway/did:key:z6MkumzpDj1cYZD2GrBbVT86xL6CfPuyqWZAEXMfSqN9j3hf/objects/019c4419-e9d4-7262-bfaf-520a43ba549b
All identifiers are ap URIs, so only FEP-ef61 implementers can load this post and interact with it.
#minimitra

2026-02-08 23:41:47 UTC

- reply

@nprofile…t0x0 Thank you. Gitlab is slow, buggy, and they somehow manage to make it worse with every update.

2026-02-07 21:37:50 UTC

- reply

@nprofile…tsag @nprofile…s2sp @nprofile…ut88 @nprofile…e40t JSON-LD: not even once

2026-02-07 21:31:27 UTC

- reply

@nprofile…qum9 @nprofile…ut88 @nprofile…e40t Linked data is good for scientific applications, but this is not what we're building here.

2026-02-07 21:29:56 UTC

- reply

@nprofile…qum9 @nprofile…ut88 @nprofile…e40t The trap is real, I barely avoided it myself. I read SocialHub a lot when I was learning about ActivityPub and got an impression that JSON-LD is super important so it was on my to-do list for a long time. Fortunately, I got distracted by other tasks.

2026-02-07 21:03:53 UTC

- reply

@nprofile…e40t @nprofile…ut88 I have no idea, it is literally useless. JSON-LD is a form of gatekeeping.

2026-02-07 20:56:07 UTC

- reply

@nprofile…d8rs @nprofile…ut88 The @context is not supposed to be required in the first place, but here we are adding it to every activity and wasting bandwidth because Mastodon developers didn't read the spec.

2026-02-05 19:22:51 UTC

- reply

@nprofile…faqy Just in case square avatars are actually important: in version 4.17.0 you can customize their roundness using the --avatar-border-radius CSS variable.

2026-02-05 13:42:10 UTC

- reply

@nprofile…ks9l Our everything accounts will be even better because Bluesky users don't really own their did:plc

2026-02-04 20:39:22 UTC

- reply

@nprofile…qhdx I didn't. I can open an issue with a detailed report if that would help.

2026-02-04 20:37:20 UTC

- reply

Wow, this time W3C did a really good job

2026-02-02 19:56:31 UTC

- reply

@nprofile…qhdx I announced a tagged post to a hashtag actor, the response was 202. Not sure how to verify, though. Does FediBuzz distribute posts back to the originating instance?

2026-02-02 16:48:25 UTC

- reply

@nprofile…qhdx Apparently I am still affected by https://github.com/astro/buzzrelay/issues/132, can't follow a hashtag. I will try to send the Announce activity manually (without a follow relationship), though this will require a bit of work.