They closed shop after DHH's scathing criticism.
enough is enough!
61–70 of 113 posts
They closed shop after DHH's scathing criticism.
enough is enough!
Earlier quoted context omitted.
Wow. So twitter censors disparaging comments about companies? Wow.
More likely that terms that are continuously mentioned in huge numbers (and therefore don't count as "trending") are omitted.
(It's possible there are scale-related reasons that make this infeasible, though.)
War was Beginning.
Internet: What happen?
MarkZ: Somebody set up us the bomb.
FB: We get signal
MarkZ: What?!
FB: Main screen turn on.
MarkZ: It's you!!
DDH: How are you gentlemen !!
DDH: All your Information are belong to us.
DDH: You are on the way to destruction.
I've been using the Application Boundaries Enforcer feature of no-script in Firefox to block facebook content when I'm not visiting a facebook site directly.
Site .facebook.com .fbcdn.net
Accept from .facebook.com .fbcdn.net
Deny
This is motivated by privacy concerns of Facebook's ability to track which partner sites I visit.=====www.facebook.com
new-host-3:dpu2 robertbuffone$ dig -trace www.facebook.com ;; Warning, ignoring invalid type race
; > DiG 9.6.0-APPLE-P2 > -trace www.facebook.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER;; QUESTION SECTION: ;www.facebook.com. IN A
;; ANSWER SECTION: www.facebook.com. 0 IN CNAME sorry.ak.facebook.com.edgesuite.net. sorry.ak.facebook.com.edgesuite.net. 0 IN CNAME a1030.g.akamai.net. a1030.g.akamai.net. 4 IN A 63.84.59.59 a1030.g.akamai.net. 4 IN A 63.84.59.10
;; Query time: 10 msec ;; SERVER: 198.6.1.142#53(198.6.1.142) ;; WHEN: Thu Sep 23 16:57:29 2010 ;; MSG SIZE rcvd: 144
========facebook.com
new-host-3:dpu2 robertbuffone$ dig -trace facebook.com ;; Warning, ignoring invalid type race
; > DiG 9.6.0-APPLE-P2 > -trace facebook.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER;; QUESTION SECTION: ;facebook.com. IN A
;; ANSWER SECTION: facebook.com. 352 IN A 69.63.181.12 facebook.com. 352 IN A 69.63.189.16 facebook.com. 352 IN A 69.63.189.11
;; Query time: 13 msec ;; SERVER: 198.6.1.142#53(198.6.1.142) ;; WHEN: Thu Sep 23 16:57:44 2010 ;; MSG SIZE rcvd: 78
www.facebook.com uses an invalid security certificate.
The certificate is only valid for the following names:
a248.e.akamai.net , *.akamaihd.net
This is the biggest problem with the SSL PKI. It is partially responsible for the lackluster deployment of SSL. We need to switch to a TOFU model supplemented by a more nimble version of the current PKI for first connect acceptance.You would not believe how often I run into problems just trying to use SSL on major sites. If you can't trust a large organizations like facebook and akamai to mess up SSL support during problems, you simply will never get it deployed well on all the rest of the sites.
SSL is simply a poor user experience. Twitter's SSL site often goes down more often than the main site too. SSL users get a second class experience and that is the most damming thing I can think of for a technology where deployment is so critical.
As an aside I notice that 'Facebook' is not a trending topic on Twitter. Seems the term must be blacklisted in some way along with all the swears and other undesirable terms. Which seems a bit underhand by Twitter. Edit: I notice that 'Facebook isnt working' has appeared now. I've blogged about this issue here: http://blog.dansingerman.com/post/1174729229/twitter-mostly-... (if anyone cares)