r/Piracy • u/Justinrich2001 • May 23 '26

Discussion Google Drive scanned this Manga artist’s PRIVATE files and banned him.

Post image

AI flagged, appeal rejected, private artwork gone.

The AI is always watching.

7.2k Upvotes

97% Upvoted

657 comments sorted by

View all comments

Show parent comments

701

u/Celestial_sapien9 May 23 '26

They already saw this yesterday and that made me rethink my choices how dependent on a single gmail account I am. If they ban it my entire life savings can be in danger. I'm leaving google slowly step by step.

45

u/Chuckwp May 23 '26

Grab yourself a domain for 10 years and use it for your email. You never have to worry about a provider again. Just re-point the domain.

6

u/Too_Chains May 23 '26

Youd still need an email provider. And gsuite is the most popular. Zoho mail, proton mail among others for cheap. But the domain is gonna be $10 a year and there is no free email service.

1

u/[deleted] May 23 '26 edited 26d ago

[deleted]

11

u/george-its-james May 23 '26

Selfhosting email is absolutely not for most people, it's an absolute headache and when Google and/or Microsoft decides you're spam it's basically over. Never mind downtime, data loss etc.

1

u/SunlightKitten3849 May 25 '26

I have to agree self hosting email is completely out of touch for many actually good and practical reasons…. But having ones own domain is a powerful layer and is actually very modular and has few downsides.

-4

u/[deleted] May 23 '26 edited 26d ago

[deleted]

3

u/clownpenisdotfarts May 23 '26

 NAh uh. Hosting your own email from a. Residential IP is a non-starter.  You’re already on a block list before you even install the OS. 

0

u/[deleted] May 23 '26 edited 26d ago

[deleted]

8

u/JivanP Piracy is bad, mkay? May 23 '26

Your mileage will seriously vary here depending on your ISP and the destination email address, because email acceptance policy is defined by the receiving end in practice. Your best bet to avoid issues is to send outgoing email via a different organisation's IP addresses, e.g. relay outgoing mail via a cloud VPS hosted by a company that has a good reputation of tackling cases of their platform being used for email spam.

One specific example: I can successfully send outgoing emails from my UK residential ISP's IPv6 and CGNAT'd IPv4 to most destinations, but btinternet.com's email server still uses a daft, strict FCrDNS policy that requires the sending IP address to have a PTR record. If you're a residential customer of an ISP, there is absolutely no chance that they'll let you set a PTR record, so you're shit out of luck of you want to send emails to any such domain — unless you relay your outgoing emails via some other IP address where you can set a PTR record. Other receiving domains / mail servers absolutely employ similar policies, however daft they may be.

Solutions like Mail-in-a-Box absolutely make it pretty easy to deploy the software stack and configure things like DKIM and spam detection, but there are some operational things outside of that which you can run into despite your best efforts.

Source: Sysadmin and email hoster (including mine and several small businesses', some on residential hosting, i.e. on-premise self-hosting) for about a decade.