Posts Tagged ‘twitter’

Twitter was useful just then

Wednesday, June 10th, 2009

Wow, I finally found a use for Twitter. RubyForge was (is) down once again, and a confirmed I am not the only person experiencing the problem, perhaps saving me a few minutes of tinkering.

I don’t mind this usage pattern; people “tweeting” about disasters, downtime or other anomalous events is useful. It’s the everyday crap and people using the service as a particularly crappy RSS feed that I don’t like.

Anyway, RubyForge is crtical infrastructure in the Ruby world and shouldn’t be going down like this. Hope they make higher availability a priority. Imagine if you were doing an emergency server reinstall right now. Who knows how long you’d have to wait?

UPDATE: It’s been down over 7 hours now, a really serious failure. Thinking about creating my own mirror when it comes back up, wonder what the storage requirement would be?

There are only 17,814 available three letter Twitter names left!

Wednesday, April 8th, 2009

Just when you thought domain squatters could not possibly get any lower – a new service allows you to search and register Twitter names:

Extra Extra!

Time is running out to register a great Twitter name!

With about 10 million people already using Twitter and thousands more signing up every day, the number of great Twitter names is shrinking rapidly.

Don’t delay: Before you know it, all the good names will be taken and gone for good.

Needless to say, the value I place on a “Twitter name” is approximately zero. However, it’s still annoying to see the lengths people will go to to screw up everything for the rest of us. It’s difficult to see any legitimate reason why someone might want to search for names merely by length; if they have a name to “defend”, surely they’d know it already, and the length wouldn’t be an issue. No – this is for domain squatting scum only, now graduating to the hilarious, worthless hype of Twitter.

If I were Twitter, I’d cancel every single account coming from that site. In fact, I’d block their entire IP range to keep them from even finding these precious gems.

Contemptible. Anyway, everyone knows the best 3-letter Twitter name was taken .

Twitter phishing using TinyURL

Tuesday, January 6th, 2009

In April, 2008 I posted about how TinyURL is a very bad idea. One of my reasons for it being a bad idea:

If you don’t give the proper URL, I can’t tell:

  • Whether it’s a link to some likely spam/other hostile site

The phishing scam seen on Twitter is exactly this – sending people obfuscated URLs then hoping they don’t notice the actual domain when they open them. Working, too.

More Github failures

Sunday, August 24th, 2008

Output from my trusty svn_up script, which also pulls git:

git detected in arkx
executing: git pull
github.com[0: 65.74.177.129]: errno=Connection refused
fatal: unable to connect a socket (Connection refused)
!!! command ‘git pull’ failed in arkx, retry manually?
 
git detected in couchrest
executing: git pull
github.com[0: 65.74.177.129]: errno=Connection refused
fatal: unable to connect a socket (Connection refused)
!!! command ‘git pull’ failed in couchrest, retry manually?
 
git detected in globalite
executing: git pull
github.com[0: 65.74.177.129]: errno=Connection refused
fatal: unable to connect a socket (Connection refused)
!!! command ‘git pull’ failed in globalite, retry manually?
 
git detected in masquerade
executing: git pull
github.com[0: 65.74.177.129]: errno=Connection refused
fatal: unable to connect a socket (Connection refused)
!!! command ‘git pull’ failed in masquerade, retry manually?
 
git detected in rack
executing: git pull
github.com[0: 65.74.177.129]: errno=Connection refused
fatal: unable to connect a socket (Connection refused)
!!! command ‘git pull’ failed in rack, retry manually?
 
git detected in relaxdb
executing: git pull
github.com[0: 65.74.177.129]: errno=Connection refused
fatal: unable to connect a socket (Connection refused)
!!! command ‘git pull’ failed in relaxdb, retry manually?
 
git detected in rest-client
executing: git pull
github.com[0: 65.74.177.129]: errno=Connection refused
fatal: unable to connect a socket (Connection refused)
!!! command ‘git pull’ failed in rest-client, retry manually?
 
git detected in thin
executing: git pull
github.com[0: 65.74.177.129]: errno=Connection refused
fatal: unable to connect a socket (Connection refused)
!!! command ‘git pull’ failed in thin, retry manually?

Does anyone else think that it is not really acceptable for a large number of important source repositories to just go down at the drop of a hat?

UPDATE: from github.wordpress.com:

github 7:46 pm on August 23, 2008 | 0 | # |
We’ve taken the site down for approximately 3 hours while we’re upgrading our servers.

THREE HOURS??!!!

Github becoming more unreliable

Sunday, August 3rd, 2008

Github down again

Gee, I guess centralising source control around a single website might have some downsides after all.