employment laws

employment laws help

Twitter Site Issue

twitterstatus:

Update: This issue has been resolved.

Users may be experiencing an issue with our service; our engineers are currently working on this issue.

Twitter Status: Correcting follower and following counts

For some time, the follower and following counts we display have been incorrect for some folks. We’re soon to push a change that will address this issue. This means that the count you see in your sidebar should match what you see on your follower and following pages.

However, a consequence of…

Working on site outage

twitterstatus:

We are working to recovery from an unplanned downtime and will update more as we learn the cause of this outage.

Update (11:28p): Twitter’s DNS records were temporarily compromised but have now been fixed. We are looking into the underlying cause and will update with more information soon.

Site is down

twitterstatus:

We are determining the cause and will provide an update shortly.

Update: we are defending against a denial-of-service attack.

Twitter Status: Reason #4132 for Changing Your Password

As part of our ongoing efforts to monitor our user base for odd activity, we noticed a sudden surge in followers for a couple accounts in the last five days. Given the circumstances surrounding this, we felt it was best to push out a password reset to accounts that were following these suspicious…

Twitter Status: Follow bug discovered, remedied.

We identified and resolved a bug that permitted a user to “force” other users to follow them. We’re now working to rollback all abuse of the bug that took place. Follower/following numbers are currently at 0; we’re aware and this too should shortly be resolved.

Update (10:18 AM PST): Of…

XSS attack identified and patched.

twitterstatus:

We’ve identified and are patching a XSS attack; as always, please message @safety if you have info regarding such an exploit.

We expect the patch to be fully rolled out shortly and will update again when it is.

Update (6:50 PDT, 13:50 UTC): The exploit is fully patched.

Twitter Status: Ongoing denial-of-service attack

We are defending against a denial-of-service attack, and will update status again shortly.

Update: the site is back up, but we are continuing to defend against and recover from this attack.

Update (9:46a): As we recover, users will experience some longer load times and slowness. This includes…

parislemon: Dear HBO

parislemon:

First and foremost, I love your content. You’ve produced several of my favorite shows over the years, and the hits keep on coming. I’d love to watch Game of Thrones now, but I can’t. You see, the only way to get your service is to be a cable subscriber, and several months ago I cut the cord.

"Greater Choice"

parislemon:

Late last night, I linked to a blog post Google put up and jotted down some initial thoughts. Given the response (thousands of views, 100+ notes, etc.), I thought it was only fair that I elaborate a bit.

Google’s post is entitled “Greater choice for wireless access point owners”. It outlines new opt-out functionality for Google’s location database. I ripped into the post — as did several others — not so much because of the feature itself, but because the post is misguided and disingenuous. In my view, it is probably the worst post Google has ever put on their blog. And that’s saying something. 

First of all, this is a post that should not have been written — at least not in the way that it was. Google is building their location database using WiFi hotspots, likely including yours if you broadcast your SSID (your router’s name). Apple does the same thing. So does Skyhook (which is suing Google for ditching their location database to build their own). So do others. It’s a good idea. And it makes locations services much better.

Read More