AT&T responds to iPhone MMS hoopla with a video explaining why they are delayed in letting iPhones do MMS: [link]

What they don't answer for me is, how come OTHER AT&T phones can MMS, but the iPhone can't?

Okay, my prime suspect for the fucked-up fan is indeed the fucked-up fan. It's clearly dying; I can stop it with a pencil and the noise stops and the noise returns as soon as it starts up.

I measured it, and it looks to be 90 mm. Do I have to get a fan with the same dimensions? I figure I do or else the screws won't be in the right place, right? I found one on Newegg for three bucks that looks just like the piece of crap that's in my computer already, so hey.

What they don't answer for me is, how come OTHER AT&T phones can MMS, but the iPhone can't?

I'm 99% certain it's not CAN'T, but MUSTN'T BE ALLOWED TO.

The strain on the data structure for AT&T because of the various iPhones is enormous. MMS would make it melt down. I'm almost certain - but not QUITE (because, after all, I can't know, not being a decision-maker at AT&T) - that this is a totally-artificial excuse.

Number !!!!!

I'm almost certain - but not QUITE (because, after all, I can't know, not being a decision-maker at AT&T) - that this is a totally-artificial excuse.

It is, and you know why? Because every picture I *would* be sending via MMS, I send now via email or ShoZu instead. The pixels are still being transferred over the EXACT SAME NETWORK. The data load excuse is a good one for why 5 bars sometimes means no reception. It is BULLSHIT for MMS.

Do I have to get a fan with the same dimensions? I figure I do or else the screws won't be in the right place, right? I found one on Newegg for three bucks that looks just like the piece of crap that's in my computer already, so hey.

Yes.

The strain on the data structure for AT&T because of the various iPhones is enormous.

yes, that is apparently why there's been such a problem with getting voicemail

I don't suppose anyone's used OpenSSL and its base64 encoding/decoding?

I'm trying to figure out a way to collect customer data, encode it using a public key cypher and save it in a mySQL database. Then I would bring it onto my PC and decode it using my secret passcode. OpenSSL seems like the perfect solution and PHP has built in support.

I've written a small PHP program that takes text input, encodes it using OpenSSL and my public key, Base64 encodes it (so that it can be stored as text) and then writes it to a file. I download the file to my PC and run "openssl enc -d -base64 -in download.txt -out download.bin"

The problem is that download.bin is 0 bytes. And, indeed, if I try to run "openssl rsautl -decrypt -inkey private.pem -in download.bin" I get the message "Error reading input data".

It *does* work if I don't base64 encode/decode. But for data portability, I'm way more comfortable with ascii data.

Yes.

Ordered! Now let's hope I don't fry my motherboard when I install it. Annoyingly, it has a 4-pin Molex cable that can be used to plug into the power supply, but I don't need it; my current one appears to be hooked up only to the motherboard. So it's just going to be an annoying loose cable. What can I use to keep it out of the way of things so it's not flopping around? Can I tape it to the side?

You mean the new one has two cables? One that'll plug into the motherboard and one directly to the power supply? Yeah, just tie it up with a twist tie of something. Taping it to the case won't hurt anything.