These kind of tools do a lot of damage to twitter ecosystem.

On Mar 4, 3:02 pm, Alan Hamlyn <alanhamlyn...@gmail.com> wrote:
> Hi Dewald,
>
> In fact you partly answered it yourself.
>
> Random login CAPTCHA's when logging in to twitter, or the occasional
> one if flagged based on users tweets to have once to fill one in to
> send a tweet.
>
> Algorithms, especially to to detect accounts that send 98%-100% links
> in tweets.
>
> Legal account, which I'm sure they are already doing.
>
> Algorithms like pascal mentioned, to pick up on likely spam behaviour.
>
> Improving the report spam feature on twitters website, and actively
> encourage other users to report spam.
>
> Stop the twitter accounts of the twitter spam software from being able
> to run, i.e @tweettankone and their variant accounts which are site
> hacking sites.
>
> Education to users, that twitter should be used for engagement not to
> spam links and churn followers.
>
> Change up the site code fields that send tweets, or reliant data to
> have 1000's of variants, so if the site changes too much, or something
> the site hackers rely on, the information will change too frequently.
>
> Those are a few of my ideas.
>
> Alan :)
>
> On Feb 24, 9:38 pm, Dewald Pretorius <dpr...@gmail.com> wrote:
>
>
>
>
>
>
>
> > Apart from implementing reCAPTCHA on tweet submission, follow, and
> > unfollow, I can't see what Twitter can do to prevent that kind of
> > abuse (can you imagine the revolt by bona fide users?). How else do
> > you determine that it is an actual human and not a piece of automated
> > software behind the browser on the user's desktop or laptop? The only
> > other option is legally, and that depends on the country of residence
> > of the owners of the software. At this point in time, it appears that
> > anyone who is able to and have the inclination to write desktop
> > software that bypasses the API might have carte blanche to do so.
>
> > On Feb 24, 7:00 am,AlanHamlyn<alanhamlyn...@gmail.com> wrote:
>
> > > Spam applications like Tweetadder, TheTweetTank and many others like
> > > it are currently hacking the website to get round oauth and basic auth
> > > restrictions - what is Twitter doing to level the playing field for
> > > serious developers who use oauth and follow Twitter guidelines?
>
> > > Many thanks in advance,
>
> > >AlanHamlyn
> > > MarketMeSuite

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Reply via email to