Archive for the ‘computer science’ Category

I’m tired of all the Twitter API applications that force users to enter their Twitter usernames and passwords to log in. Why? Well, because it’s just so insecure! Many people realized this for web applications some time ago, so now, most Twitter web services use OAuth to connect with the Twitter API. But for some [...]


Today, I moved all my junk from one room to another. In celebration of the glories of my new office (more info coming soon on office specs), I decided to do what I’ve been meaning to do for a long time: set up an Ethernet bridge/hub. My room has only one Ethernet port, and as I have multiple networkable [...]


It’s been in the news this whole weekend: on Friday, a man attempted but failed to detonate pentaerythritol tetranitrate, an incendiary powder, on a flight from Amsterdam to Detroit. Thankfully, the panic of the passengers drove them to extinguish the fire before the detonation continued, but the issue still remains: how was this Nigerian man able to get these [...]


 In my last post, I explained what truly went on in the Twitpocalypse, which dealt with tweet IDs passing the limits of the 32-bit signed integer (from -2,147,483,647 to +2,147,483,647), which is the most common datatype in use in computer applications today. Yet, whilst computer science has limits embedded into its structure, Twitter does not [...]


Numerous friends have asked me about this whole Twitpocalypse thing, as they just don’t get it. “What’s this whole deal with signed integers?”, they ask. Well I’m here to clear that up, as I do programming, and in programming, if you don’t know such basics of computer science, you’re doomed. What the predicters of the [...]



Follow

Get every new post delivered to your Inbox.