Post AjUgeea2WiRyZvr73Y by mikedev@fediversity.site
 (DIR) More posts by mikedev@fediversity.site
 (DIR) Post #Aj7fuNkgIwvNOlOLwm by silverpill@mitra.social
       2024-06-20T15:18:29.583070Z
       
       4 likes, 2 repeats
       
       Welcome @nomad, the first ever FEP-ef61 + FEP-ae97 actor.It doesn't have S2S inbox yet, but it has C2S outbox and was created from a client. The client controls the identity key, can send signed messages to local users, and receive messages from them. I published the code here: https://codeberg.org/silverpill/fep-ae97-clientFEP-ae97 clients are not difficult to build, and I invite everyone to do so. C2S protocol is identical to S2S protocol, except you send activities to a local outbox instead of a remote inbox, and you pull activities from local inbox instead of listening for them online. The development version of Mitra already has necessary endpoints. FEP-ae97 spec needs to be updated though, I will do that soon.#fep_ef61
       
 (DIR) Post #Aj9UDNqlLzwK4SRzF2 by silverpill@mitra.social
       2024-06-21T12:16:44.769935Z
       
       0 likes, 0 repeats
       
       @nomad It was discovered that mention of @nomad caused many servers to reject the whole message, because the Mention tag contained a raw 'ap' URL and not a compatible HTTP URL. Mastodon, Pleroma, probably many others too. This has been fixed
       
 (DIR) Post #AjUgeea2WiRyZvr73Y by mikedev@fediversity.site
       2024-06-21T21:01:33Z
       
       0 likes, 0 repeats
       
       FWIW that was received here and and ap urls are allow-listed generally, but it's too late now to see what the HTML-Purifier did with the original link. It has its own allow-list which hasn't been modified. Will need to create a unit test for that as I suspect it might have been filtered or otherwise mangled in transit. Then there are a few places in the codebase where we might actually rewrite/resolve those, but based on your experience it appears there's no hurry to do so.
       
 (DIR) Post #AjUgefhWMO1q3QMbM8 by silverpill@mitra.social
       2024-07-01T17:45:21.739673Z
       
       1 likes, 0 repeats
       
       @mikedev FEP-ef61 'ap' URLs are not valid URIs according to RFC-3986, because in URIs ":" is used as a delimiter between host and port components. However, many other characters are allowed. For example, this is a valid URI:ap://did;key;z6MkvUie7gDQugJmyDQQPhMCCBfKJo7aGvzQYF2BqvFvdwx6/objects/123Apparently did;key;z6MkvUie7gDQugJmyDQQPhMCCBfKJo7aGvzQYF2BqvFvdwx6 is a valid host.DIDs can be also percent-encoded.I don't think we need to change anything now, but this is something to be aware of (and something FEP-ef61 implementers might demand in the future)