Elliott C. Back: Internet & Technology

Today in The Verge’s How-to: Build a killer gaming PC for under $1,000 they suggest putting together the following components:

I feel that it does a few things wrong, emphasizing an nVidia graphics card that trails ATI’s mid-range offering, lacks significant RAM, and splurges on unneeded components like a DVD drive and spinning-disk hard drive. If I were to build an off the shelf gaming PC with the ample budget of $1000, using the same tricks (no peripherals, no OS, no LCD/LED monitor) as The Verge, here is what I’d buy:

The motherboard/CPU are virtually identical here and they are great picks–I also don’t care much about which case to use. However, I think this build is significantly stronger in the graphics/memory/drive arenas, and benefits from a cheaper 500W power supply. When you buy the ATI 6950 over the suggested nVidia 560 Ti, you get:

• Twice as much graphics RAM (2GB vs 1GB)
• 30 – 50W loaded less power consumption
• Similar performance

8 GB of RAM is OK, but when you have a 64 bit OS that can handle it all, why not put 16 GB into the system for $30 more? It’s a cheap easy win. And last, and possibly more controversially, I don’t see the need for an optical drive–everything is downloadable these days. I’d also rather have twice the SSD space than a slow spinning drive to load applications off.

Readers, what do you think? I’m sure my ATI preference will upset you…

For whatever reason, Gmail keeps blocking my account alert emails from Chase. In my spam folder, guess which are really spam, and which are legit?

When I move them to my inbox and/or mark them as spam, I get warned that “Warning: This message may not be from whom it claims to be. Beware of following any links in it or of providing the sender with any personal information.”

How do I get Google to believe that my emails from Chase are real? I keep marking them as not spam, but that doesn’t help! Ridiculous that Gmail is hurting Chase Bank’s ability to conduct business and manage their fraud/risk. I highly suspect that account fraud alerts would get thrown into the same bucket…

Update 1:

The message headers seem to indicate a failure between Cornell and Google’s servers on SPF (Sender Policy Framework):

Delivered-To: XXXX@gmail.com
Received: by 10.231.53.18 with SMTP id k18cs6777ibg;
Sat, 24 Sep 2011 05:13:22 -0700 (PDT)
Received: by 10.52.93.112 with SMTP id ct16mr4101007vdb.423.1316866401115;
Sat, 24 Sep 2011 05:13:21 -0700 (PDT)
Return-Path: <Chase@alerts.chase.com>
Received: from limestone3.mail.cornell.edu (limestone3.mail.cornell.edu. [128.253.83.163])
by mx.google.com with ESMTP id bz6si11946296vdc.126.2011.09.24.05.13.20;
Sat, 24 Sep 2011 05:13:21 -0700 (PDT)
Received-SPF: fail (google.com: domain of Chase@alerts.chase.com does not designate 128.253.83.163 as permitted sender) client-ip=128.253.83.163;
Authentication-Results: mx.google.com; spf=hardfail (google.com: domain of Chase@alerts.chase.com does not designate 128.253.83.163 as permitted sender) smtp.mail=Chase@alerts.chase.com; dkim=hardfail header.i=@alerts.Chase.com
X-CornellRouted: This message has been Routed already.
…

Update 2: A helpful Googler/blog reader said this:

It appears to be a problem specifically with Cornell. It’s a known issue when Cornell is forwarding e-mails to GMail. The Cornell IT admins [are fixing] their exchange server. In the meantime you can fix this with either:

- have Chase send info direct to @gmail.com
- create a filter to “never mark as spam” for that address.

My solution is to change my old rules to email directly to gmail rather than forward through Cornell’s servers.

An interesting bit of German scenery from Google Maps, if you go forward one step, you go suddenly from a summer view:

To a Stark-cold winter one:

This serendipitous discovery (more discussion at Reddit) brought delight.