Notices by silverpill (silverpill@mitra.social), page 5

@possibledog @summertime Everything that is possible in ATProto is also possible in ActivityPub. In fact, ActivityPub is a much more capable protocol. Developers even could use DIDs (real ones, not did:plc) for data portability: https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md

@laurin @linos
isVirtualLocation is self explanatory. [Place, VirtualLocation] is not - is it "Place and VirtualLocation", "Place or VirtualLocation", something else?

More importantly, no one in Fediverse uses multi-typing, we use properties to extend standard objects. Introduction of multi-typing creates a lot of work for everyone.

@mario Thank you!

@mro Is it related to me trying to follow Seppo actor?

I just received a Create(Note) where Note doesn't have attributedTo property (but is has actor property, which should be used only on activities afaik).

@mochi Unfortunately, handle is tied to a domain name. If primary gateway is dead, actor should update its gateways array, and thus obtain a new handle.

Actor ID ('ap' URL) is a permanent identifier that doesn't depend on a specific gateway.

@mcc @julian @MrCheeze

@mro @julian Could you elaborate? Where should I use anyURI?

@julian I think servers should synchronize data between themselves, but the other approach where clients write to multiple servers (as they do in Nostr) is also fine

@mcc @MrCheeze

@julian @mcc @MrCheeze

>Mitra exists as a practical implementation compatible with Mastodon, and it implements...

The main specification is FEP-ef61, which describes how decentralized ("nomadic") identity works. FEP-c390 is an older idea and it doesn't provide full data portability. FEP-ae97 is about combining FEP-ef61 with ActivityPub Client-to-server API.

>I just don't fully understand what that gets us.

You can clone your account to multiple servers, and those multiple accounts would work as one! And more: peer to peer, local-first applications.
Mitra's implementation is actually incomplete, I recommend also checking out Streams, which supports FEP-ef61 and non-ActivityPub nomadic identity (Nomad protocol; this is where the "nomadic identity" comes from).

@scott Nomadic identity over AP needs to mature first. Once the specs stabilize, I think more projects will be interested in implementing it.

We also need to write explainers and guides for developers. I can tell from discussions with other developers that FEP-ef61 is difficult to understand

@Hyolobrika @anemone Because this is what people want.
New centralized social networks can't compete with Twitter and other incumbents. They can offer slightly better moderation and slightly better UI, but this is not enough. The network size is far more important.

Decentralization, on the other hand, is a strong competitive advantage. Everyone wants more control and more choice, so startups have to promise that. Of course, the easiest way is "fake until you make it" aka "progressive decentralization". Every VC-funded web3 social startup did that, with predictable outcomes. Eventually people learned to avoid them, so the marketing strategy has changed and now we're in the era of "web3 but without blockchain". Same scams under a different name.

@helge

I'm not sure if follower (client) should connect directly to the media server. When client GETs new content, media is already cached on the follower's server (according to the diagram).

@raphael @thisismissem @by_caballero @ruud @shlee

@julian @trwnh @evan @jenniferplusplus @mikedev @scott @erincandescent @trwnh What if we use context for activities and thread for posts?

@scott OK, maybe this has already been fixed in later versions

(cc @mario just in case)

@darius There seems to be an overlap between this and https://funfedi.dev/support_tables/

Perhaps you can contribute to that project? It seems to be privacy-respecting because samples are generated locally

@scott Does authorship.studio run an outdated version of Hubzilla? I checked NodeInfo and it displays 9.0 while the most recent is 9.4.3

I'd like to report a bug - In Update(Question) activity the Question.published is formatted as 2024-10-11 06:10:46, which is not a valid xsd:dateTime, as far as I know.

@knt It is worth noting that accept rules only make sense if one wants an allowlist. For example:

An empty ruleset is equivalent to accept *

@helge Thank you, this is an important work. CanIUse.com but for Fediverse

@feld @frogzone @jeffcliff @p The way of Mastodon

@feld @frogzone @jeffcliff @p Projects that implement FEP-8b32 are already using Ed25519 keys (most notable of them is probably Hubzilla).

Some other developers are also considering Ed25519, either for embedded (FEP-8b32) or HTTP signatures (RFC 9421).

>Mastodon

Mastodon too: https://github.com/mastodon/fediverse_auxiliary_service_provider_specifications/pull/27/files#diff-2caefb0fa42bedec7feb2490de59da44151d6e5e98fbab4640495535229b079cR65

@p @frogzone @jeffcliff @feld Thank you, this is a useful feedback. I'll adjust the FEP