News for hackers. Stuff that matters.
Re:Reconstructing Twitter's Firehose by mhfs on Wednesday February 27, 2019 @08:16PM (#19268293)
I worked with a company in the past that abused the twitter api to an unimaginable level from a single IP address.

That was a few years ago but at the time I’m pretty sure their blacklisting was between inexistent and pathetic.

Re:Reconstructing Twitter's Firehose by dev_dull on Wednesday February 27, 2019 @10:20PM (#19268755)
It’s sad that you think this somehow reflects badly on Twitter. I appreciate a company that will opt to be conservative rather than ban-hammer innocent people on accident just to stop a single idiot.
Re:Reconstructing Twitter's Firehose by mhfs on Wednesday February 27, 2019 @10:40PM (#19268816)
I don’t think it reflects badly on Twitter, it was simply a remark on the state of their blacklisting at the time. I’m sure they could’ve done a lot better if they chose to. Sorry I didn’t expressed myself better.
Re:Reconstructing Twitter's Firehose by jorvi on Thursday February 28, 2019 @01:17AM (#19269348)
> It’s sad that you think this somehow reflects badly on Twitter. I appreciate a company that will opt to be conservative rather than ban-hammer innocent people on accident just to stop a single idiot.

Off-topic but reminds me of ~2004 where we had a particularly pervasive cheater in our dedicated game server and the end decision of the admin was to just ban the entire IP range of said cheaters' ISP. Not particularly conservative - very effective.

Re:Reconstructing Twitter's Firehose by tomglynch on Wednesday February 27, 2019 @08:32PM (#19268338)
Using these keys?
Re:Reconstructing Twitter's Firehose by mhfs on Wednesday February 27, 2019 @08:39PM (#19268369)
No. Different strategy.