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

@dave Yes, I'll make a bugfix release soon.

@dave I fixed signature validation (on mitra.social), and my follow request was processed correctly. Thank you!

@dave Made another attempt.

>missing field "name"

Maybe it is because some items in attachment array don't have this field?

@dave Thanks! I un-followed and sent another follow request at 2024-01-17T17:49:35

Undo -> 200
Follow -> 520

@dave I'm testing it now, but I get error code: 520 in response to my Follow activity.

@dave Should I make an exception for id query parameter? This is not difficult, and as far as I know, using query parameters in actor IDs is perfectly valid according to AP spec - just not common.

@dave Sorry, I think I was wrong about the instance actor. Mitra discovers actor by analyzing the keyId parameter in Signature HTTP header. If the value of this parameter contained URL with a query such as ?id=920666, it was removed, so only https://ap.podcastindex.org/podcasts remained.

I explained that in a subsequent reply:

https://mitra.social/objects/018d1433-67e4-028f-79b8-7ced5a7bad0c

The address of public.mitra.social instance actor is http://public.mitra.social/actor

@dave

Mitra tries to guess actor ID from key ID without making additional requests. Most of the time removing the fragment is enough, but some implementations use query parameter instead of fragment to identify the key, so these are removed too.

I think I can simply add exception for id query parameter if you prefer this URL structure.

@dave

>but missing the url parameters to identify it.

Do you use query parameters? They are stripped

@dave On Mitra side I see incoming Accept activity, but the server can't retrieve the public key:

This is probably your instance actor. I tried to send a request manually, it still returns 400 Bad Request

@devnull Yes, this is known as "instance actor". You can read about it in FEP-2677

@alex @dave @errhead

Here's how I would represent LUD-16 with FEP-0ea0 (and hypothetical lud16: URI scheme):

@errhead @dave @alex

FEP-0ea0 also supports payment URIs like BIP21.

Perhaps someone already proposed an URI scheme for LUD-16 addresses? Similar to mailto: for email addresses and acct: for webfinger addresses.

@dave @alex Is it possible to encode necessary information in URI?

Re-purposing PropertyValue is a nice hack, but I think a better solution is needed. I wonder if FEP-0ae0 is applicable: https://codeberg.org/fediverse/fep/src/branch/main/fep/0ea0/fep-0ea0.md

@lutindiscret Tor and I2P are great tools. Wouldn't recommend anything else

@alex I think public instances don't make much sense because they will be abused and immediately added to all fediblock lists. Private bridge instances, on the other hand, can be used to repair inter-instance connections without attracting unnecessary attention. That's why I made it allowlist based

@alex Yes, for personal usage. For example, it allowed me to unblock myself from threads

@dsfgs @gabriel Some fediverse servers can be configured to work on Tor and I2P. Check the list of Tor instances on FediList: http://demo.fedilist.com/instance?q=&ip=&software=&registrations=&onion=only

Activity Connect bridge can be used to connect them to clearnet instances, even those which are not configured for Tor.

@iwojima @mint You might be interested in this.

Activity Connect, my little side-project, has reached usable state:

https://codeberg.org/silverpill/activity-connect

- Follow, unfollow, create and delete posts - basic activities are supported. Translation is not perfect but can be improved in the future.
- Allowlist-based bridging
- Tor and I2P are supported
- Media URLs are not translated
- Compiled to a single binary, uses SQLite database, configured with environment variables