Re:My experience being blocked by Google Safe Browsing
by input_sh on Sunday April 02, 2023 @07:10AM
(#35409314)
> It’s mostly for me and friends I know personally – nothing like the bigger, public ones.
I'd agree with you if it had thousands of users, but not when the user count is 8. If you have 8 users on your SMTP server, damn easy to know with certainty if any of them did anything that might be considered malicious.
Re:My experience being blocked by Google Safe Browsing
by asmor on Sunday April 02, 2023 @07:19AM
(#35409365)
Mastodon, perhaps unwisely, replicates all media it encounters.
Re:My experience being blocked by Google Safe Browsing
by input_sh on Sunday April 02, 2023 @07:37AM
(#35409497)
Again, it's eight users, one of which has full control over the database plus an approximate timestamp when something went wrong.
Super easy to check every outbound click, every post published, every post received... Everything.
Re:My experience being blocked by Google Safe Browsing
by asmor on Sunday April 02, 2023 @12:00PM
(#35411953)
I run a single user instance, and I definitely can't review every post received?
Re:My experience being blocked by Google Safe Browsing
by literalAardvark on Sunday April 02, 2023 @07:25AM
(#35409416)
Well that's... terrifying.
Re:My experience being blocked by Google Safe Browsing
by asmor on Sunday April 02, 2023 @07:29AM
(#35409450)
In reality, it barely makes a difference if you want to avoid hotlinking (and that has other bad privacy privacy implications, now all your users load bad content).
Law enforcement makes no difference between proxying, caching and storing indefinitely. At least not during all the steps that precede your hardware being seized.
Mastodon is often used to distribute illegal content. If you self host you need to be ready to deal with this stuff. Like with self hosted SMTP server.
Not saying it is good or bad, just reality!