Jim Greer's dashboard

A comment on the idea "Flag as spam button" in Twitter:

I don't really agree with that. If they're overposting, then just don't follow them. But if they're using Twitter exclusively as an outlet for advertising, then they should be flaggable as spammers. – Timothy McNeil, on October 11, 2008 02:38

fireman4 replied on October 07, 2008 02:07 to the idea "Flag as spam button" in Twitter:

Over the past 10 hours, I've blocked over 200 spammers. Manually. It never ends. When does it stop? At what point do you just throw in the towel and say "I like Twitter, but this really sucks?" and then delete your account? Every 10 minutes, a few more spammers start following me and if I don't block them, it increases exponentially. Seriously, WTF?

a7 replied on October 06, 2008 11:12 to the idea "Flag as spam button" in Twitter:

"Rachael329 (Rachael329) is now following your updates on Twitter."
yes sure.

mdy replied on October 01, 2008 01:52 to the idea "Flag as spam button" in Twitter:

We can now also report spammers by sending a Direct Message to Twitter's @spam account.

To do this, you'll first need to follow http://twitter.com/spam. You can then send a direct message to @spam either by:

1. Typing a direct message from the "What are you doing?" box
Ex. d spam @spammy1, @spammy2 are spambots!

2. Sending a direct message from your phone
Ex. d spam @spammy3 is yet another spambot

3. Composing a direct message at http://twitter.com/direct_messages

Mark replied on September 30, 2008 21:53 to the problem "Changes to our backlog are not getting applied" in Pivotal Labs:

Hi Jim,

We are trying to track down this issue, but aren't having any luck recreating the problem. Is your team still experiencing the problem? What browser(s) are you seeing the problem in?

danp replied on September 30, 2008 03:53 to the problem "Changes to our backlog are not getting applied" in Pivotal Labs:

Hi Jim...we have started noticing this over the last few days as well. We're looking into the problem, thanks for letting us know.

Jim Greer started following the problem "Changes to our backlog are not getting applied" in Pivotal Labs.

mdy replied on September 04, 2008 03:45 to the idea "Flag as spam button" in Twitter:

Looks like we can now officially report spammers by sending an @reply to the @spam account on Twitter.

At least, that's what a recent update from Crystal in another thread says.

The recommended syntax seems to be:
@spam @spammerusername OptionalMsg

noman4me replied on September 04, 2008 02:46 to the idea "Flag as spam button" in Twitter:

PLEASE. i have to block about 5 people a day who are following about 2,000 people with no followers, and their only update is "i have a great business opportunity for you!"

annoying.

amicalmant replied on September 03, 2008 14:29 to the idea "Flag as spam button" in Twitter:

A "Report Spam" button or some equivalent is absolutely necessary. In order to be fair a human check is also necessary. Although we could think of an automated public "flagged as spam" notice on suspected home pages once the number of spam reports reaches a certain point, the process of closing an account should always been taken by a responsible human being.

Nimdae replied on August 24, 2008 23:40 to the idea "Flag as spam button" in Twitter:

Flagging posts would be a better idea, as Margaret mentioned. Also, limiting the ability to mark (such as a usage within time period limit) would cut down on trolls.

Jim Greer started following the idea "Flag as spam button" in Twitter.

jaikoo started following the problem "Performance/reliability problems" in Beanstalk.

argyle_soxxx started following the problem "Performance/reliability problems" in Beanstalk.

Jim Greer replied on June 05, 2008 15:05 to the problem "Beanstalk / EngineYard Issues" in Beanstalk:

Ok, Beanstalk and Engineyard have fixed this and our deploy succeeded. Thanks Chris.

Jim Greer replied on June 05, 2008 14:39 to the problem "Beanstalk / EngineYard Issues" in Beanstalk:

Sure

Chris Nagele replied on June 05, 2008 14:28 to the problem "Beanstalk / EngineYard Issues" in Beanstalk:

Jim,
Can you chat?

https://wildbit.campfirenow.com/8c14a

Chris

Jim Greer replied on June 05, 2008 14:22 to the problem "Beanstalk / EngineYard Issues" in Beanstalk:

Same error:

** [err] svn: PROPFIND request failed on '/kongregate/tags/current_release'
** svn: PROPFIND of '/kongregate/tags/current_release': SSL negotiation failed: Connection reset by peer (https://kongregate.svn.beanstalkapp.com)

Chris Nagele replied on June 05, 2008 14:14 to the problem "Beanstalk / EngineYard Issues" in Beanstalk:

Jim, We have opened up some resources on the servers. Can you give it a try again?

Chris

Chris Nagele replied on June 05, 2008 14:02 to the problem "Beanstalk / EngineYard Issues" in Beanstalk:

I see. I'll update you when it is stable. Should be very soon.