Google Mail won't permit attachments of files larger than twenty-five megabytes and instead sends those files to Google Drive and then sends a link in the email instead. This is known as the Facebook Style of Vampire Recruiting. No-one wants Google Drive so they make it mandatory for their mail and force it. Peaches.
The way it seems to work is setting the file so only someone who got the email can read it resulted a request going back to me to authorize it. Say what?? The original email already authorized it.
An alternative is to set the file so anyone who knows the URL can read it. This defeats Google's security and it won't compromise the file because the URL is beyond guessable but I don't see it as anymore than another mindless incantation from programmers who hate us.
In the words of my ol' Dad ... it's silly.
Note: that was the absolute worst. Anything 'silly' is not worthy of any further attention.
No need for an extended editorial but don't think my professional experience with computers makes me hate them any less than you. In fact, it probably makes me hate them more because that experience gives one, not just me, more reasons to hate them.
You know, man, I remember Joey Carbino and he was one of the best as he could write assembler code in his head ... but then the mainframe ate him.
(Ed: you mean he lost his mind like in "Real Genius?")
No, I mean it ate him. Some interface opened in the machine and he was never (sob) seen again.
I was the one who had to call his mother to tell her, "I'm so sorry to bring this news but Joey was eaten by the mainframe."
She cried and wailed, "God even denies me an open casket for my boy."
It was heartbreaking and I didn't have any kind of heart to tell her we might be able to find his disassociated self in there somewhere ... but he was the only one (sob) who could write the code.
We would lose one like that every so often, one of the hazards.
Note: Dropbox only permits 200 MB and I need to send over 7 GB so that's not a solution. I know of various big file transfer sites and assumed Google would be relatively easy as well. Yep, that's what I assumed.
The way it seems to work is setting the file so only someone who got the email can read it resulted a request going back to me to authorize it. Say what?? The original email already authorized it.
An alternative is to set the file so anyone who knows the URL can read it. This defeats Google's security and it won't compromise the file because the URL is beyond guessable but I don't see it as anymore than another mindless incantation from programmers who hate us.
In the words of my ol' Dad ... it's silly.
Note: that was the absolute worst. Anything 'silly' is not worthy of any further attention.
No need for an extended editorial but don't think my professional experience with computers makes me hate them any less than you. In fact, it probably makes me hate them more because that experience gives one, not just me, more reasons to hate them.
You know, man, I remember Joey Carbino and he was one of the best as he could write assembler code in his head ... but then the mainframe ate him.
(Ed: you mean he lost his mind like in "Real Genius?")
No, I mean it ate him. Some interface opened in the machine and he was never (sob) seen again.
I was the one who had to call his mother to tell her, "I'm so sorry to bring this news but Joey was eaten by the mainframe."
She cried and wailed, "God even denies me an open casket for my boy."
It was heartbreaking and I didn't have any kind of heart to tell her we might be able to find his disassociated self in there somewhere ... but he was the only one (sob) who could write the code.
We would lose one like that every so often, one of the hazards.
Note: Dropbox only permits 200 MB and I need to send over 7 GB so that's not a solution. I know of various big file transfer sites and assumed Google would be relatively easy as well. Yep, that's what I assumed.
No comments:
Post a Comment