>-Original Message-
>From: twitter-development-talk@googlegroups.com
[mailto:twitter-development->t...@googlegroups.com] On Behalf Of Chris
McIntosh
>Sent: Wednesday, June 10, 2009 5:36 PM
>To: twitter-development-talk@googlegroups.com
>Subject: [twitter-dev] Re: Wha
That could be a tricky slope think about times like elections where people
could get a littl nuts with that button.
- Original Message -
From: "Dewald Pretorius"
To: "Twitter Development Talk"
Sent: Wednesday, June 10, 2009 2:37 PM
Subject: [twitter-dev] Whacking The Spammers
>
> T
Interesting concept. That would mean you'd have to add a additional
element to each message that would update the spam content by ID.
Here's the problem.
If you get enough people together, you can flame/spam messages and
make the messages go away.
Lets say you hard code a number like '100' repo
Tweets will only show up in your timeline if you are following the account
in which case they are probably not a spam account.
On Wed, Jun 10, 2009 at 15:05, Dewald Pretorius wrote:
> Plus, to block you have to specifically visit the user's profile to
> find the block link. With tweet spam repor
We use blocks, DMs sent to @spam (d spam @sketchy_user), and @replies to at
spam (@spam @sketchy_user) to help learn about spam accounts. All
of these are used as signal in the fight against way-ward users.
Thanks,
Doug
On Wed, Jun 10, 2009 at 1:05 PM, Dewald Pretorius wrote:
>
> The bock take
The bock takes care of the account level. It does not take care of the
individual tweet level.
And with block you don't have the aggregation of reported spam tweets
that automatically results in an account suspension.
Plus, to block you have to specifically visit the user's profile to
find the b
How is that different than block, other than terminology?
Jesse
On Wed, Jun 10, 2009 at 1:37 PM, Dewald Pretorius wrote:
>
> Twitter already has a few million Dels, namely us, the users.
>
> All they need to do is to add a report spam button to the tweet, much
> like the favorite button.
>
> X
