Attempt to directly proxy or redirect video and audio content

[jon-betts]

Currently we block certain sites which have high video content, but not others. A better solution would be to see if we can either:

• Detect media content by mime-type
• Issue a redirect to the source

Or

• Maintain a list of domains and intercept them in wombat.js on the client side, so they are never attemped to be proxied in the first place

The first is good, as it works without any manual intervention to build up a list of domains. The second is good because it doesn't require many any connection to the upstream service.

It's likely that we will see cross domain issues with this.

[mkdir-washington-edu]

@jon-betts Do you think it's worth differentiating via.hypothes.is and viahtml.hypothes.is (if I have that right)? Only one of those is likely to be abused for video content, and it seems like there's maybe different solutions for the different Vias?

(bringing this up due to a recent Support ticket)

[mattdricker]

This is the user @mkdir-washington-edu mentions: https://app.hubspot.com/contacts/6291320/ticket/1301456914

Adding to the support board for possible triage or discussion.