Saturday, December 09, 2006

GMail, you are _fail_

Every once in awhile Google does something that pisses me off.

Not as much as Microsoft (Microsoft seems to be doing this kind of shit in /spades/ recently, like they got stock in some kind of "piss off Arron" factory.), but enough to make me rage.

Christ, anyway, I'm trying to send a client an executable file via email, real simple procedure, right? Wrong. Oh, how terribly fucking wrong. "I can't send it because its an executable," Google astutely ponders, "And that means its a virus."

Oooh, fuck you GMail, fuck you so goddamn bad. Now I have to inconvenience THEM, this OTHER PERSON, now I have to give them the login details to my FTP, maybe they don't even _have_ an FTP client and have to download one, all because you motherfuckers have some disgusting hard-on against executable files.

Seriously, what the fuck is wrong with you? You think I can't turn a .py or a .rb file into a virus? You've got fucking integrated _virus scanners_ but you're banning .exe file extensions? _WHAT_ that makes _NO SENSE_ you are a /TECH COMPANY YOU SHOULD KNOW BETTER THAN THAT/.

God. For every 10 smart things Google does, there's always this inexplicably retarded one that's just hiding in the shadows waiting to jump out at you. I would love to _smack_ the sucker-fool who made this decision. Just smack the stupid out of him. because lord knows he needs it and he needs it _bad_.

I'm going to go take out my aggression on Rainbow Six Vegas.

5 comments:

Anonymous said...

This behavior is not specific to GMail.

Easy solution: Zip up the .exe. If this doesn't help, zip up the zip file again. Or protect it with a password.

Or just rename the extension.

Anonymous said...

This behavior is not specific to GMail.

Easy solution: Zip up the .exe. If this doesn't help, zip up the zip file again. Or protect it with a password.

Or just rename the extension.

Bet's On said...

Gmail scans zips.

As for password protection / renaming the zip, I'd hate to put my clients through that kind of hassle. I know from experience that zip passwords get lost and when you tell someone to rename an eye its like "how do I do that?" and... tch.

Hopefully I'll find a better digital distribution system in the near future...

Anonymous said...

Are you seriously suggesting that having clients rename the file is more of a hassle than having them install an FTP client and connect to your server to download it?

You don't need to zip the thing. Just replace the .exe extension with something else like filename.changethistoexe and it goes through without a bother.

It is an annoying, and arbitrary restriction, but it's not hard to get around.

Bet's On said...

Yes, yes I am.

Because to you or me, its 'renaming the file.'

To them, its having to enable viewable file extensions, 'rename' the file, launch the file, disable file extensions again -- (the only people who leave it enabled that I know, personally, are the technocentric-types).

In other words a pointless hassle I'd like to avoid.

Anyway, I found out that p/w-protected zipping wasn't the answer at all when GMail cock-blocked the attachment because it detected a binary executable header inside the attached zip-file.

I found another way to securely shoot files to clients using one of those web-enabled file transfer services, so its not much of an issue anymore.