Comments for onelittlewindow

Comment on An Introduction to NoScript by kim

kim — Tue, 07 Sep 2010 09:35:02 +0000

Nice short concise writeup. Cheers!

Comment on Synchronicity? by Corrina Reamy

Corrina Reamy — Mon, 30 Aug 2010 22:23:17 +0000

Fed up with getting low numbers of useless visitors to your website? Well i want to tell you about a brand new underground tactic that makes me personally $900 daily on 100% AUTOPILOT. I really could be here all day and going into detail but why dont you merely check their site out? There is really a great video that explains everything. So if your seriously interested in producing quick cash this is the website for you. Auto Traffic Avalanche

Comment on Refresh DC Presentation by celebrity fuck you

celebrity fuck you — Tue, 24 Aug 2010 18:42:07 +0000

Sign: zdbrw Hello!!! pmvqf and 9982tzubuscdba and 1897 : I love your site. Love design!!! I just came across your blog and wanted to say that Ive really enjoyed browsing your blog posts.

Comment on Nmap for Conficker by martin

martin — Mon, 29 Mar 2010 08:16:13 +0000

Can you help with the new smb-check-vulns.nse script? It seems that it has changed a bit and they are now writing the results to a table before outputing.. I tried adding the code you suggested in various places but keep getting errors.. below is the excerpt from version 5.21.
— Check for Conficker
status, result = check_conficker(host)
local hosttodump = host.ip
if(status == false) then
local msg = CONFICKER_ERROR_HELP[result] or “UNKNOWN; got error ” .. result
table.insert(response, get_response(“Conficker”, msg, nil, 1)) — Only set verbosity for this, since it might be an error or it might be UNKNOWN
else
if(result == CLEAN) then
table.insert(response, get_response(“Conficker”, “Likely CLEAN”, nil, 1))
elseif(result == INFECTED) then
table.insert(response, get_response(“Conficker”, “Likely INFECTED”, “by Conficker.C or lower”, 0))
elseif(result == INFECTED2) then
table.insert(response, get_response(“Conficker”, “Likely INFECTED”, “by Conficker.D or higher”, 0))
else
table.insert(response, get_response(“Conficker”, “UNKNOWN”, result, 0, 1))
end
end

Comment on Account Collision on Twitter? by Doug Wilson

Doug Wilson — Thu, 23 Apr 2009 20:27:48 +0000

Well, “data inconsistencies” definitely could be the cause of the problem. Honestly, the issues that I’ve seen are a little more severe than what they’ve outlined. Ah well, hopefully this will clear it up, and they (internally) are more aware of what’s going on than they’ve indicated.

Comment on Account Collision on Twitter? by Jeremy

Jeremy — Thu, 23 Apr 2009 20:23:01 +0000

I agree with you Doug, that this is a big issue. I’ve just found out that Twitter has posted a status update on their website, which seems to be concerning this issue, although its a little vague:

http://status.twitter.com/post/99180872/tracking-down-data-inconsistencies

Comment on Account Collision on Twitter? by Doug Wilson

Doug Wilson — Thu, 23 Apr 2009 20:09:57 +0000

I think that it is being corrected over time. I have never actually gotten in touch with Twitter support on the issue — I researched it until late last night, and then this morning, it was “fixed.”

Whether this is their application catching up with itself, or if they are manually fixing something that is getting out of control is unknown. My concern is that having account collisions across a service is kind of a big deal — you really can’t trust a service if your risking regularly having other people’s information show up as your own, or get locked out of your account due to wires being crossed.

Obviously, Twitter is a free service, but like Gmail, its has unrealistic expectations put on it due to the vast scope and impact that its service has. I’ll be curious to see if they make a public statement about the issue, or if it’s just chalked up as another technical problem that twitter has so often.

Comment on Account Collision on Twitter? by RT: @Fenng: http://onelittlewi… « ?????

RT: @Fenng: http://onelittlewi… « ????? — Thu, 23 Apr 2009 18:03:24 +0000

[...] @Fenng: http://onelittlewindow.org/blog/?p=228 – new accounts on twitter are being taken over by [...]

Comment on Account Collision on Twitter? by Jeremy

Jeremy — Thu, 23 Apr 2009 17:37:28 +0000

Doug, thanks for the answer. I’ve noticed other people with the same issue are getting back control over their accounts. And so did you. Did this happen by itself, or was it a manual correction by Twitter?

I’m just wondering. If there somehow is a “lag” during which the problems are solved automatically, all I have to do is wait I guess.

Comment on Account Collision on Twitter? by Doug Wilson

Doug Wilson — Thu, 23 Apr 2009 17:20:23 +0000

Unfortunately, I don’t think there’s really anything you can do about this. I don’t know enough about the actual architecture of Twitter (though @translucent_eye posted an article I need to go back and read now about the back end and how they are trying to improve it), but it smells to me like something is getting out of synch, thus allowing accounts to overlap, and they are then somehow restoring consistency. This could a database issue, or it could be something in their distributed architecture where updates are not propagating properly. I’m worried that some of my recently created accounts are now getting locked out again . . .