thetwitcleaner.com Report : Visit Site

Technical data of the thetwitcleaner.com

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host thetwitcleaner.com. Currently, hosted in United Kingdom and its service provider is Bytemark Computer Consulting Ltd .

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called Apache containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

-- -- home twitter home faq blog media about help out! support twit cleaner! help me take a well deserved holiday contribute (and wow, thank you. so much) key posts stopping dm spam simple tips to minimise the dm spam you receive. how to be a good twitter citizen improve your presence & interaction, minimise your chance of appearing on twit cleaner reports. twitter business success (the right way) a brilliant ebook (pdf) by rick bakas . rick really gets twitter, si user feedback @teddarling : your app has saved me at least 100 hours of my time. that's worth a lot more than what you charged me. @neoblog : you guys kick more ass than a 3 legged man in an ass kicking contest! @heathrbabes : detailed feedback here & chart here see more feedback .. archives march 2013 january 2013 october 2012 september 2012 may 2012 february 2012 may 2011 march 2011 december 2010 may 2010 april 2010 march 2010 february 2010 january 2010 december 2009 november 2009 twitter? it’s not fun anymore posted by si dawson on 10/03/13 in thankyou this week i worked 62 hours straight. actually, that’s a lie, i worked 65 hours straight , with 3 hours of naps. twitter has stopped being fun. i started twit cleaner in 2009 . given that i haven’t managed to develop a livable income out of it in that time (barring donations from you many wonderful, generous people), it’s pretty obvious i’m not in it for the money. it’s been my primary occupation over that time, and absorbed several thousand hours of coding, designing, building, testing and supporting it. everything on twit cleaner (bar some low level server decisions), i’ve personally done. i wanted to make twitter a better place for everyone. i love to code. i love helping people. that’s it. unfortunately, the new api is so crippling that twit cleaner is unable to continue. if i can’t even maintain the base service, i certainly can’t (won’t) roll out any new functionality i had planned, all of which sits on top of twitter’s apis. so, here’s some things i had in the pipeline that won’t see the light of day: filtered follow back – like auto-follow, but filtered through the (user customisable) twit cleaner reports , so if they would appear on (your choice of) report sections, you won’t follow them; only if they’re awesome. i’ve had this running on my personal account for a year or so, it’s just needed some ui whipped up around it. oh, and a billing system. dm guard – deleting the myriad of dm spam we all receive. making direct messages useful again. additionally, catching and quarantining all the phishing attacks twitter suffers, and feeding those back en masse to twitter, so they can break the links and quickly quell any new attacks that arise, before they spread. this is already partly running on my twit cleaner account. spam hunter – a neat game (a core chunk of the back end code already written) to make it fun (and super efficient) to hunt spammers on twitter. thus, the masses pool their efforts to remove spam from twitter (since of course, all this would be collated and automatically fed back to twitter’s spam team). i reckon, combined? we could make twitter spam history (or so expensive as not to be worth it for the spammers). i’ve tracked, identified and reported hundreds of thousands of spammers off twitter.. just while testing this code – not even using it in force. at the risk of sounding immodest, twit cleaner was a stupidly robust system (optimising systems is something i’m really good at). most of the downtime i did experience was because i was constantly tweaking and improving things, while working at the outer limit of my skills in some pretty arcane technical areas. i could happily leave the system running for weeks at a time while i worked on other code. i’d do tech support, but not really touch the engine. it would gracefully handle the plethora of random errors emanating from twitter’s complex environment; interpret, adjust and retry. nothing would be lost. not much would slow. it was an engineering marvel built, as it were, atop a fail-whaling ship. and yet the v1.1 twitter api “upgrade” hit like 20 ice bergs. every single twitter related part of my system started screaming. yes, some bits i’d made bad choices or coded less-than-perfectly, but when you fix 15 major problem sites, and there’s still more, many of which i genuinely have no idea how i can correct, adjust for or code around? that’s dark. and when you factor in how smoothly everything ran before this upgrade? it’s not fun. now, to be really clear. i don’t begrudge the decisions twitter has made with these changes. they’re running a system with a couple of hundred million users . mine has a couple of hundred thousand. at that many orders of magnitude difference, things change. a lot. with thirty years of tech experience , i marvel that twitter works at all – let alone as quickly and (relatively) painlessly as it does. all that said, i’d hoped that dropping the maximum user size down would help things, but quite literally, every part of my system is still complaining (despite a ton of work by me). i’m running out of api calls (how much twitter will let me do, per 15 minute block) everywhere. everywhere. the twitter api documentation says i should check that. oh, wait, i’ve run out of api calls to check how many api calls i have left . wtf? seriously? and so on. multiply that by 60+ hours in 3 days and you start to see why i’m walking away from the dead horse. i suspect i won’t be alone . running twit cleaner has been one of the most amazing experiences in my life. i’ve met so many incredible people . i’ve helped, in a small-but-significant way so many to have a better experience on twitter. i deeply regret that i can’t continue to help improve your lives. it’s not feeding starving children in africa… but you know, it wasn’t nothing. and wow, you people are amazing. thank you, from the bottom of my heart. thank you also to both matt and katy in the spam team at twitter. it was an extreme pleasure and an honour helping them kick all those bad guys in the ass. through all this i’ve learned so, so much. perhaps the key thing? never play football when someone else owns the field . so obvious in hindsight . perhaps if i’d known that in oct 2009, when i started all this, i might have taken a very different path. but i would have missed so, so much. and i’m incredibly grateful for it all. from here? i have no idea. i’ll see what the universe brings. a holiday would be nice. in the mean time, of course, i’ll keep learning how to love more and keep posting weird crap on my personal twitter account, @sidawson . take care out there. si [related: some of the feedback twit cleaner has received over the last four years] 374 comments epilogue posted by si dawson on 29/03/13 in administration in the two weeks since i announced the shutdown of twit cleaner, the following has happened: i’ve personally responded to: somewhere between 3-4000 twitter messages (i figure, if people cared enough to comment, they deserved a response) 200-ish blog comments 50+ emails a stack of meetings and proposals of various seriousness/ridiculousness ( “you should write angry birds , but on a zipline ! it’d be easy! we’ll make millions!” ) on top of that, i had offers from two different “competitors” (of sorts), to buy, variously – the domain, the traffic, the email list (ie, all your email addresses), and the twitter account. one offered a trivial amount, in exchange for wanting me to spam you all, three times a day for three months. uhh. yeah, really. needless to say, i told them (politely) to bite the wax tadpole. possibly replacement services unfortunately, despite looking, i haven’t found any other services that with good conscience i can point you to as a reasonable replacement. there are a dozen services that do the basics – who’s not following you back , who’s left twitter (although be warned here – twitter gives false information; a lot of these services tell you way more people ha

URL analysis for thetwitcleaner.com

http://thetwitcleaner.com/blog/blog/cutting-back-on-dm-spam
http://thetwitcleaner.com/blog/2010/12
http://thetwitcleaner.com/blog/privacy.php
http://thetwitcleaner.com/blog/help_out
http://thetwitcleaner.com/blog/twitter-api-v1-1-sorry-and-goodbye-large-users
http://thetwitcleaner.com/blog/quickbites
http://thetwitcleaner.com/blog/category/admin
http://thetwitcleaner.com/blog/epilogue#comments
http://thetwitcleaner.com/blog/2012/09
http://thetwitcleaner.com/blog/media
http://thetwitcleaner.com/blog/category/thankyou
http://thetwitcleaner.com/blog/2012/10
http://thetwitcleaner.com/blog/goodbye
http://thetwitcleaner.com/blog/2011/03
http://thetwitcleaner.com/blog/2011/05
google.co.uk

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Domain Name: THETWITCLEANER.COM
Registry Domain ID: 1573845294_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.enom.com
Registrar URL: http://www.enom.com
Updated Date: 2016-10-14T00:30:12Z
Creation Date: 2009-10-29T00:01:07Z
Registry Expiry Date: 2017-10-29T00:01:07Z
Registrar: eNom, Inc.
Registrar IANA ID: 48
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: A.NS.BYTEMARK.CO.UK
Name Server: B.NS.BYTEMARK.CO.UK
Name Server: C.NS.BYTEMARK.CO.UK
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2017-09-08T07:52:54Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.

  REGISTRAR eNom, Inc.

SERVERS

  SERVER com.whois-servers.net

  ARGS domain =thetwitcleaner.com

  PORT 43

  TYPE domain

DOMAIN

  NAME thetwitcleaner.com

  CHANGED 2016-10-14

  CREATED 2009-10-29

STATUS
clientTransferProhibited https://icann.org/epp#clientTransferProhibited

NSERVER

  A.NS.BYTEMARK.CO.UK 80.68.80.26

  B.NS.BYTEMARK.CO.UK 85.17.170.78

  C.NS.BYTEMARK.CO.UK 80.68.80.27

  REGISTERED yes

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .