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

@helge @giacelvecio The fix required changes to this file: https://github.com/friendica/friendica/blob/develop/src/Util/JsonLD.php

I also found this in its dependency list https://git.friendi.ca/friendica/php-json-ld

@giacelvecio This is the problem I had with them: https://github.com/friendica/friendica/issues/12815

Looks like their JSON-LD parser is very picky

New version of Friendica is out, and it includes a fix for federating with Mitra

https://forum.friendi.ca/objects/39bbe52a-9613b739-9b7018b2d7b1488f

@liaizon @davew Sounds good. But I don't know what enclosure is, did he mean inline audio/video?

>Enclosures. This makes it possible to use social media for podcasting. Why not? The two seem to go well together.

@raphael No, it is still in research phase. I will start working on implementation in the beginning of the next year.

I think something similar already exists in Streams where ActivityPub is used alongside with Nomad protocol.

@dimkr Did the loss of table actually happen? :)

I loaded posts from your outbox and there were many new ones. Re-followed, let's see if it fixes the issue.

@raphael Here's one possibility: https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md

When object IDs are not linked to a particular server, both identity and data become portable

@dave @agates My code relies on types from http crate so it should be compatible with reqwest.

I want to publish my AP toolbox on crates.io at some point, but it is not ready for that yet. Feel free to copy-paste the parts you need

@alex Sure. If they won't unblock me that is what I'm going to do

@alex Yeah, and now I'm getting 429's from their server. The other instance (public.mitra.social) federates normally.

@Hyolobrika @Moon You can use decentralized cryptocurrency without revealing your legal identity. Even if transactions are public, you can maintain anonymity.

CBDCs, on the other hand, are not anonymous (they might provide some degree of privacy for plebs, but for a regulator everything must be transparent). Add to this cash bans, and you'll get a pretty dystopian picture.

@mikedev I think repeating the top-level context is an option that VC workgroup is currently discussing, but it's not the only one.

I decided to use the jcs-eddsa-2022 name for now, because the definition of eddsa-jcs-2022 may change in the coming months

@Hyolobrika As far as programming goes I don't expect any fundamental differences. An engineer writes some code, then it is executed by nodes of a network in a verifiable way.

Permissioned may mean both things. In CBDC context it makes sense to strictly control who can run the nodes, and also who can create programs too (I expect banks will be allowed to create programs, but not ordinary people)

>Also, do you have evidence for that?

No, I didn't actually read any CBDC design documents. That's just my understanding of the goals and capabilities of those who create these systems.

@helge @mikedev My understanding is that context injection makes sense only for JSON documents (and JSON processors). It means inserting @context key with a certain value into a document:

https://www.w3.org/TR/vc-data-integrity/#context-injection

@Hyolobrika I don't think it will be very different. CBDC networks will be permissioned: only selected parties can deploy contacts and adjust spending conditions.

Without strong privacy by default Bitcoin and Ethereum are losing fungibility and may end up in a similar state. CBDCs with extra steps.

cc @helge @mikedev

I posted about this on SocialHub too but email notifications about watched topics doesn't seem to be working there, at least for me

Important information for FEP-8b32 and FEP-c390 implementers:
https://github.com/w3c/vc-data-integrity/issues/231

It was reported that context injection is a necessary step for eddsa-jcs-2022 cryptosuite. It is necessary even if secured object is nested inside an object with @context property (as in FEP-c390).

This means FEP-c390 feature file is wrong, because I assumed that context injection is not needed. What's worse, it is not even clear how context injection must be done in this case (should we inject a string, or an array?).

In cases where top-level object is being signed, the context injection is not needed, so existing FEP-8b32 implementations are probably correct.

@kik @helge @team type: Note is the new <div>

@team @helge @kik In Fediverse, Like is a class of things, rather than a specific thing. On some platforms it means "like", on others it's "favorite", and then some use it as "upvote". I think repo "stars" belong to that class too.

The common language makes interoperability easier.

If at some point in the future you will need to distinguish between various kinds of Like you can always add some new property.

@Hyolobrika @alex The mentions are only present in HTML content of the post, but not in its ActivityPub representation.

Sometimes this also happens when you edit a post with a quote. The link in content remains, but quoteUrl attribute seems to be absent from ActivityPub object.