Notices by Laurin (laurin@mastodon.online)

@angelo @yala @activitypods
The main issue we are working on is solid oidc support.
You can check out https://mypod.store however the server is not well-maintained and more of a playground, you might suffer down-time.

Another thing: Unlinke other implementations, we don't have a file-based architecture (we use a SPARQL db, also using @nextgraph soon). As a consequence you can't choose the name of the URI when creating resources which other implementations let you do. No "slash-semantic".

@silverpill @linos
I see the point about compatibility with apps that do not follow the spec here.
Why would you say, it is cleaner though, to add a property only, over adding a second type?

For both cases: If I wanted to be thorough, I'd go and add this property to an RDF ontology. I'd expect the ontology to define that type and the property associated with it.
So in the end, it'd be a multi-type along with a definition of the property that is linking to a video, for example.

@steve @helge @fentiger @smallcircles

Why is the client-side signing FEP (https://codeberg.org/fediverse/fep/src/branch/main/fep/ae97/fep-ae97.md) using the jcs and not the rdfc crypto suite (https://www.w3.org/TR/vc-di-eddsa/#eddsa-rdfc-2022)?
This would solve the whole problem I suppose, since it will convert the activity to rdf, to sign.

@silverpill