Well, once they fix the whole "each instance copies the media from other instances automatically" thing. I'd love to self-host a vanity instance if I didn't have to either worry about CSAM or just nuke the entire pict-rs facility via script.
...actually I wonder if that's an option on kbin. Even if the Mastodon interoperability is a bit wonky right now I like the platform working with both services on ActivityPub (thus why I'm here).
Making it mandatory and something you can't opt out of is not acceptable. "Work as a knockoff as a CDN" shouldn't be a requirement of running a vanity instance. That's a barrier to entry without much benefit.
Well, once they fix the whole "each instance copies the media from other instances automatically" thing. I'd love to self-host a vanity instance if I didn't have to either worry about CSAM or just nuke the entire pict-rs facility via script.
...actually I wonder if that's an option on kbin. Even if the Mastodon interoperability is a bit wonky right now I like the platform working with both services on ActivityPub (thus why I'm here).
Fix?.... Look at the Lemmy code base.
This is a feature not a bug.
Making it mandatory and something you can't opt out of is not acceptable. "Work as a knockoff as a CDN" shouldn't be a requirement of running a vanity instance. That's a barrier to entry without much benefit.
Just run an allow-list?..
From what I understand, that's difficult to do, and even if done it prevents the inline loading of images from those other instances at all.
Hopefully it'll be academic before long anyway. The CSAM attack lit a fire under the devs and changing this is now one of their highest priorities.