Notices by silverpill (silverpill@mitra.social)

@mapache Because I keep seeing those "You have been blocked" and "Verify you are human" pages when visiting random Fediverse sites.

Twitter/Microsoft/Meta are less annoying. I think Twitter and Meta actually help the network because they give people many reasons to create an account here.

@gabriel I use Yggdrasil sometimes, it's a nice tool for connecting devices which can't communicate directly for some reason.

I like how it's faster than Tor, but of course that comes at the price of anonymity.

Never tried Reticulum. It came after Yggdrasil/CJDNS and I ignored it because it seemed like an attempt to reinvent the same thing.

@julian Hopefully nothing, the object is ignored. It may also crash :)

We use a different kind of identifier to keep portable objects compatible with ef61-unaware implementations:

which works like a regular HTTPS URL, but ef61-aware implementations treat it as equivalent to ap://did:example:abcd/object

@mariusor

@mapache Cloudflare.

@sendpaws I always wanted to add more admin controls to mitra-fe. Guess it is time to finally do that.

In your opinion, which admin/mod tool is the most important?

@japananon @coin I went to check rekt.news, they never disappoint

https://rekt.news/hashrate-heist-or-hype

@mariusor Move is used for migrating actors from one ID to another: FEP-7628. It can be used for migrating objects too, but I don't think it's practical.

FEP-ef61 solves the problem by making identifiers portable.

@japananon @coin This one is good. In every other article I have seen so far the journalists were lying, saying that it was either an attempted or a successful 51% attack.

@nimda Awesome, thank you for testing.

@andre Made a new release including this change

https://codeberg.org/silverpill/mitra/src/tag/apx-v0.16.0/apx_sdk/CHANGELOG.md

#APx v0.16.0

https://crates.io/crates/apx_sdk/0.16.0

- Added method for creating RFC-9421 signatures (previously only verification was implemented).
- Support for wasm32-unknown-unknown compilation target in apx_core.

@gabriel For me, the peak doom was 3-5 years ago. Everything seemed to be under control, several prominent people had been arrested or suicided. But things went better than expected: the globalism is receding, AI is dumber and less centralized than it could have been, etc.

I think we're in a good timeline, and this is a great opportunity.

@julian Was there a meeting? Could you provide a short summary?

I am particularly interested in cross posting.

@gabriel Have you seen the comment? https://github.com/TryGhost/ActivityPub/issues/1178#issuecomment-3174496501

@kopper This sounds similar to actor tokens from FEP-db0e

@liaizon @anewsocial Keys and DIDs can be linked too: https://codeberg.org/fediverse/fep/src/branch/main/fep/c390/fep-c390.md

@dimkr I think servers can fetch Activity.actor, either by checking gateways specified in ?gateways parameter, or right away if actor ID is in compatible form.

verificationMethod is supposed to be linked to the DID.

@dimkr This is an open question. One option is to avoid using canonical portable IDs and only use compatible ones. Another option is to add a special property to objects that contains recommended gateways.

Existing implementations always use compatible IDs so we didn't think much about this problem.

@dimkr I still don't support ?gateways, this feature might even be removed from the spec in the future.

But ap://did🔑x is equal to https://social.example/.well-known/apgateway/did🔑x. I store canonical (ap://) IDs in the database to make comparisons and lookups easier.

If you need to test anything @nomad is a portable actor

@bengo @feld My implementation of FEP-ef61 only supports did:key. It doesn't perform DID resolution, which will be implemented later.

The first supported DID method after did:key will probably be did:web, and after that we can add others with less effort. did:dht looks interesting, but the repository is not very active, the last commit was 10 months ago. Also the link to Rust implementation is dead.