Emelia Smith

@snarfed there's the important note on DIDs though: > Authority as DID: in normalized form, and no duplicate hex-encoding. For example, if the DID is already hex-encoded, don't re-encode the...

I'm assuming the WHATWG URL parser is correct: ``` > URL.canParse('at://did:plc:ia76kvnndjutgedggx2ibrem/app.bsky.feed.post/3lyxjjs27jkqg') false > URL.canParse('at://did%253plc%253ia76kvnndjutgedggx2ibrem/app.bsky.feed.post/3lyxjjs27jkqg') true ```

Also: ``` unreserved = ALPHA / DIGIT / "-" / "." / "_" / "~" pct-encoded = "%" HEXDIG HEXDIG sub-delims = "!" / "$" / "&" / "'" /...

> (I assume the WHATWG URL parser checks URL conformance, not URI, but no matter.) _URL, URI, [puh-TAH-toh, puh-TAY-toh](https://usdictionary.com/idioms/potato-potato/)_.

@snarfed I'd probably go with parsing the `at://` URIs, and then formatting them according to the URI spec. It's not a fantastic workaround, but it'll at least give you valid...

@snarfed @silverpill so I guess until then we should just encode them for maximum compatibility?

> ThisIsMissEm has flagged this in the CG T&S task force as needing more detail: https://github.com/swicg/activitypub-trust-and-safety/issues/23 That is for user-to-user blocking, not for server's blocking an entire domain. For doing...

> Servers SHOULD NOT deliver Block Activities to their object. This is specifically why that T&S taskforce issue exists. You may deliver the block activity to the object's moderation actor...

@snarfed you could have actors on bridgyfed's PDS that are just storing a list synced from somewhere, so like these actors' PDSes would contain a `app.bsky.actor.profile` record and `app.bsky.graph.list` named...

But that still wouldn't help you with allowing people on bluesky to block entire domains on the fediverse. For that you'd need to use an Settings UI in bridgyfed itself,...