I also agree.
While I couldn’t care less (it’s their body and bodily autonomy is super important to me), I’d be a little hurt if they didn’t tell me about it.
In that case I’d be more interested in talking to my partner to try and understand why they felt that they couldn’t talk to me about it and needed to keep it a secret.
I had emergency cosmetic surgery after my accident and remember up to the anaesthesia counting down from ten to about four, and then waking up afterwards.
We aren’t defeferated from them. That’s different from hosting that content ourselves though.
I’m not personally against piracy, however hosting that kind of content here ourselves would put our primary reason for creating this space (that of providing a safe social space for trans and LGBTQIA+ people) at risk.
I just wanted to point that out before we get a whole bunch of piracy subs created on our instance that we’d have to remove.
I would point out that piracy is against our ToS, so we wouldn’t tolerate hosting piracy subs ourselves.
I found that the Caddy handler above blocked many third party clients and even Tesseract.
So instead I’m using this CEL expression to return a 444 error on match of the unscoped old-sorted 50 per-page comments past page 99:
@block_comment_spam expression <<CEL {http.request.uri.path} == "/api/v3/comment/list" && {http.request.uri.query.limit} == "50" && {http.request.uri.query.sort} == "Old" && int({http.request.uri.query.page}) > 99 && {http.request.uri.query.post_id} == "" CEL handle @block_comment_spam { respond 444 }