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

@wjmaggos Another protocol is not necessary. ActivityPub already supports groups, only E2EE is missing, but that will change soon

@grishka This post seems to be from threads.net. Have you implemented FEP-e232?

@laxla I'm currently working on this data portability proposal: https://codeberg.org/silverpill/feps/src/branch/main/ef61/fep-ef61.md

The proposed mechanism is designed to work within today's Fediverse, but at the same time it is future-proof and should work fine in P2P setting.

FEP-ef61 update, as promised: https://codeberg.org/fediverse/fep/pulls/304

Introducing ap:// URLs

#fep_ef61

@benpate @trwnh A conflict may arise if other developers will start using same IRIs for something different. So I think FEP namespace is preferable, but you can indicate in the proposal that you want to switch to w3.org/ns/activitystreams namespace later.

@julian @mauve @snarfed.org Content negotiation is a standard procedure described in the ActivityPub spec. Supporting other discovery methods might be a good idea (and a good topic for a FEP), but I don't recommend relying on them exclusively.

@benpate There is a fep namespace at https://w3id.org, perhaps you can use it:

It is described in FEP-888d (by @trwnh)

Changes in my FEP-ef61 implementation: the resolver endpoint was replaced with gateway, and did:ap URLs were replaced with ap:// URLs

https://mitra.social/.well-known/apgateway/did:key:z6MkjtdL1hhAtJDRTti4JZtjGVkMiqbrQWhLQjK8wV4neCvS/actor

Also found a way to use existing URL library to parse ap:// URLs. A massive FEP-ef61 update is coming.

#fep_ef61

@benpate According to RFC 8288 section 3.3, "registered" relation types can not contain a colon:

"Unregistered" relation types should be URIs (though you can argue that intent:Follow is a URN).

@tfardet No, the FEP only describes how a link between posts should be represented. Notification can be created with a Mention tag.

Friendica supports FEP-e232: https://github.com/friendica/friendica/pull/14032

Meanwhile, Mastodon: https://oisaur.com/users/renchap/statuses/112299860209222424

@julian @evan @evan Normally you send a GET request where Accept header contains the AP media type. The server checks the value of Accept header and returns either HTML page or AP object (or redirects to AP object)
I've heard about <link> tag but I don't know if any applications actually support it

@trwnh If I understand correctly, target.id points to the context collection, and therefore context.attributedTo and target.attributedTo are the same actor.

@mikedev could you confirm?

@trwnh Conversations in streams now have attributedTo property (example: https://fediversity.site/conversation/7342c8d7-6ac2-4128-8168-6cbd0dc9a37c). Does it make streams a complete FEP-7888 implementation?

My instance has been un-blocked by threads.net
Thanks @zuck

@laxla I'm trying to understand how this can work with existing ActivityPub group implementations. Usually there is a Group actor, and group members send activities such as Join, Leave or Create to its inbox, and then Group actor distributes these activities to other group members. So it seems that ordering should not be a problem at all, because the Group actor can ensure that membership events are ordered.

@laxla Sounds good.

There was a discussion recently between MLS co-author and DeltaChat people about message ordering: https://chaos.social/users/delta/statuses/112280986699031775
I assume for ActivityPub this requirement means that every encrypted conversation must have an owner (an actor). What do you think?

@gabriel @Hyolobrika In the talk they mention Mastodon servers too. But even if it only applies to large services... People should stop trying to "fix" them, this is not going to work. Eventually these services will be made obsolete by competitors who use better technology. We're working on it.

@Hyolobrika @gabriel So for example, if I'm providing a service for free, and you are using this service, and if I will ban you for whatever reason, you're going to sue me? Sounds like a stupidest idea ever.

@laxla Will the containing object have properties such as attributedTo and content, or only the bare minimum (which I assume are id, type and encryptedData)?