Nate's Blog

Thought I would take some time and post some of my ideas of what Apple is going to say on the 27th.

First the MacBook Pro.  The low and mid range models (13-15in) will get a speed bump with the C2D.  With the low end getting a 2.53GHz CPU while the mid range gets 2.8-3.2GHz.  But I think the 17in MacBook Pro will get a Core i5.  I don't think it will be at 2.66GHz, but more like 2.33GHz.  On the GPU side, I can see Apple moving onto a ATI 4650 on the 15in and a 4850 on the 17in unless they want to keep the 9400m with a Nvidia GPU for better battery life.

 

As for the tablet, its all still rumors.  I have no idea if Apple will make one, I don't see why not, a lot of people would buy them including me.  But if it runs the iPhone OS then I don't know.  I would like OS X running on it so I could install Windows 7 on it also.  I think it will come with built in 3G for AT&T and Verizon.  And you would be able to buy them at the those stores with a 2yr contract for about 200-300$ with full price at 800$.

 

I can see a iPhone OS update to 4.0.  I think the 4.0 update will come with a different home screen or a better one.  Hoping for a message like area on the lock screen that is more detailed.  Apple could show the new iPhone but I think that will wait till June.

 

I can also see a MacBook Air update also with a faster CPU and 4GB of RAM on the high end Air.

 

Thats all for now.

I was just doing a random speedtest on my iPhone and got this.

Not bad AT&T.

 

I was also posted on the front page of DSLReports! 
 http://www.dslreports.com/shownews/Hints-Of-72-Mbps-ATT-3G-In-Kansas-City-106060

Wow, look at this, AT&T has started to block img.4chan.org which so happens to host /b/.

Here is a traceroute to the "www"

C:\Documents and Settings\Admin>tracert 4chan.org

Tracing route to 4chan.org [207.126.64.166]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Faen.ta.deg [192.168.1.1]

2 1 ms <1 ms <1 ms modem [192.168.0.1]

3 8 ms 9 ms 9 ms ppp-70-255-145-254.dsl.ksc2mo.swbell.net [70.255

.145.254]

4 9 ms 10 ms 9 ms 67.64.49.1

5 9 ms 8 ms 9 ms bb1-tg3-0.ksc2mo.sbcglobal.net [151.164.40.85]

6 23 ms 23 ms 23 ms ex3-p9-0.eqchil.sbcglobal.net [151.164.189.81]

7 23 ms 23 ms 23 ms te7-2.ccr02.ord03.atlas.cogentco.com [154.54.11.

237]

8 23 ms 23 ms 23 ms 154.54.29.17

9 36 ms 35 ms 35 ms te4-2.mpd01.mci01.atlas.cogentco.com [154.54.6.1

58]

10 35 ms 35 ms 35 ms te4-7.mpd01.dfw01.atlas.cogentco.com [154.54.25.

205]

11 35 ms 34 ms 34 ms te8-3.mpd01.dfw03.atlas.cogentco.com [66.28.4.17

4]

12 34 ms 34 ms 35 ms 38.104.35.234

13 37 ms 36 ms 36 ms unknown.xeex.net [216.152.253.26]

14 * * * Request timed out.

15 36 ms 36 ms 82 ms 207.126.64.166

Trace complete.

 

And here is "img.4chan.org"

C:\Documents and Settings\Admin>tracert img.4chan.org

Tracing route to img.4chan.org [207.126.64.181]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Faen.ta.deg [192.168.1.1]

2 1 ms <1 ms <1 ms modem [192.168.0.1]

3 9 ms 9 ms 8 ms ppp-70-255-145-254.dsl.ksc2mo.swbell.net [70.255

.145.254]

4 9 ms 17 ms 9 ms dist1-vlan60.ksc2mo.sbcglobal.net [151.164.29.13

0]

5 * * * Request timed out.

6 * * * Request timed out.

7 * * * Request timed out.

8 * * * Request timed out.

9 * * * Request timed out.

10 * * * Request timed out.

11 * * ^C

 

Blocked right at the router level before it leaves town. But the funny thing is, it is NOT blocked on AT&T's Tier 1 network.  Im able to reach the site fine.

C:\Documents and Settings\nmarolt>tracert img.4chan.org

Tracing route to img.4chan.org [207.126.64.182]

over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 216.63.14.74

2 <1 ms <1 ms <1 ms 216.63.14.105

3 1 ms 1 ms 1 ms 12.88.17.157

4 * * * Request timed out.

5 * * * Request timed out.

6 15 ms 15 ms 15 ms ggr3.dlstx.ip.att.net [12.122.139.17]

7 * 15 ms 15 ms cr2-pos-0-3-3-3.dallas.savvis.net [208.172.139.2

25]

8 15 ms 15 ms 15 ms dpr1-ge-4-0-0.dallasequinix.savvis.net [204.70.1

96.30]

9 15 ms 15 ms 15 ms er1-te-2-1.dallasequinix.savvis.net [204.70.204.

145]

10 15 ms 15 ms 15 ms 208.175.175.22

11 15 ms 15 ms * unknown.xeex.net [216.152.253.26]

12 * * * Request timed out.

13 325 ms 316 ms 251 ms 207.126.64.182

Trace complete.