What does an ActivityPub client look like when the server does NOT support the `proxyUrl` endpoint?

What does an ActivityPub client look like when the server does NOT support the `proxyUrl` endpoint?

Imagine having to visually parse a URL to guess who a post is from...

#ActivityPub #c2s

to be clear there are more issues than being able to represent an actor alongside a post

but the short version is that not having a proxyUrl endpoint means your client will hit CORS everywhere!

@django is the code available anywhere, I'd like to have a look if possible.

@mariusor hey I haven’t published it yet, I’ll be doing so in the next couple of weeks