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

@helge @hrefna What we actually need is a developer-friendly subset of ActivityPub. Fediverse is already running on this protocol, it's just not formalized.

I'm collecting my observations in this document: https://codeberg.org/silverpill/feps/src/branch/main/d85d/fep-d85d.md

APx v0.2.0 has been released together with Mitra v3.6.0

I started to keep a change log: https://codeberg.org/silverpill/mitra/src/branch/main/apx_sdk/CHANGELOG.md. This release includes several breaking changes, and API will remain unstable until 1.0 is released.

@fentiger If I remember correctly, @trwnh was advocating for attributed collections

@trwnh @mikedev @julian If a relevant authority makes a claim about an object, I have no reason to not believe it. The default assumption is full representation, so if object is signed, or embedded within another object of the same origin, I wouldn't fetch it. Unless it is known to be partial - and that can be indicated by a special property, or can be required by some specification (as FEP-400e does).

@elvecio I assume posts are coming from a nomadic Streams account? There are several known interoperability issues: https://codeberg.org/streams/streams/issues/178#issuecomment-2349551

@trwnh @mikedev @julian This object design pattern (partial embeddings) can be used in other situations too. We can use a new property like partial: true do indicate partial representations:

https://socialhub.activitypub.rocks/t/partially-embedded-objects/4450

@mikedev @trwnh @julian

Context helps with identifying the target. When I receive an Add activity, I need to know what collection is being modified. Is it a featured collection, a context, or something else?

One solution is to keep an index of all known collections and search through it every time Add is received.
Another solution would require cooperation from producers, but I think it is a bit cleaner: embed partial representation of a target and use specific type there, like Context, instead of Collection. Then, as a consumer, I can simply check target.type instead of searching for target.id in my collection index.

@fentiger FEP-c7d3 discusses the usage of attributedTo property for indicating ownership of an object (and object is defined as "not an actor and not an activity")

@julian @mikedev Yes, this is a new requirement, but I can't comment on that part yet. The FEP is very much work in progress

@smallcircles @hollo Good idea! I'll add that section to the FEP.

@steve The real problem is that written spec is not keeping up with the living spec.

@feditest if you're testing mitra, you can set federation.ssrf_protection_enabled to false (it was added in version 3.4.0)

@dmitri I think this feature also exists in Hubzilla and @streams

@dmitri @helge @evan It already achieved it, albeit on a small scale.

The very possibility of it is a proof that ActivityPub is a good protocol. Usually, if a major protocol feature wasn't considered at a design stage, it can't be added later in an organic way.

@mischievoustomato It re-downloads files only when it processes remote posts or profiles. You can refresh profiles with fetch-actor command, but currently there's is no such command for posts.

@dmitri @helge I don't think we need a different protocol, though. ActivityPub is extensible

@mischievoustomato Mitra simply reads files from the directory specified in config. If image is not displayed, that means file is not present, or was somehow corrupted. You can verify this using browser developer tools - server responds with 404 if file doesn't exist.

The text shouldn't be distorted when it happens, though. Could you give me a link to that post?

@julian @erlend_sh Thank you, this is the correct link. The URL in my post leads to AP object, I forgot that Discourse doesn't redirect when you view those in the browser. It also doesn't seem to support Update activities

FEP-ef61 update: https://codeberg.org/fediverse/fep/pulls/397

I fixed proof.verficiationMethod values in examples, as well as accompanying text. These values should include fragments that identify a specific key in a DID document, so they are not actually DIDs but DID URLs (a similar change was made in FEP-8b32).
I also added a paragraph on authentication and authorization (with a normative reference to FEP-c7d3), and described WebFinger address reverse discovery in compatibility mode.

#NomadicIdentity #fep_ef61

@hollo This is how hashtags were represented in Create activity:

Curiously, if I fetch the object now, there's a name instead of nameMap, as expected.