I’m getting a few reports that some bird.makeup accounts have forwarded messages that don’t appear anymore on their Twitter page in the last day or so. I don’t have much to go on right now to investigate this, but have anyone seen suspicious posts?
You were offered guest_accounts to handle the scraping internally by Zedeus, what you’re doing is a dick move scraping public instances for the data. Furthermore you apparently prevent access to people from poa.st but feel its ok to scrape their Nitter instance for data.
I haven’t seen anything personally on the hundreds of bird.makeup accounts that I follow, but keeping it accurate is very high on the priorities of this project. If it’s a vulnerability or a bug I want to fix it
@Salastil@vincent Yeah, especially given how easy it is to run your own Nitter instance instead of chewing up capacity on public ones hosted by other people.
@Salastil@vincent Yeah, but apparently Zedeus has automated handing those out.
(Also I am using https://github.com/iv-org/smart-ipv6-rotator being able to get around Google and Twitter as an example next time someone tells me that we're actually ready for IPv6 and it will be fine.)
@p@Salastil@vincent this burden is heavy but we alone shall bare it pete. no sweat, your twitter linx r safe (I don't even think you use our nitter)
the whole point of all of this was to nudge him into doing the right thing and implementing API like nitter or at be consistent and not scrape our service when he blocks us. instead, he took the hard coded values and moved it to his in-database config adding an additional "lowtrust" boolean. not implementing checks that the posts are even from the right account, not using the Twitter API like we are. still scraping nitter instances. just now he's instead hiding it.
I don't even use my own Nitter instance any more, I tossed it away.
> the whole point of all of this was to nudge him into doing the right thing and implementing API like nitter or at be consistent and not scrape our service when he blocks us. instead, he took the hard coded values and moved it to his in-database config adding an additional "lowtrust" boolean.
May i suggest in the future being kind to the people who provide you with services rather than mass blocking them on sight?
If you find poa.st unsavory, thats fine, but it seems a bit "poor me" to not expect this to happen. Personally i try not to use other peoples services before asking them whether i can or not.
I don't approve of the massive amount of abuse you're getting however, but i think this is a good opportunity for everyone to re-evaluate what tech they use, whether they trust it, and whether they are giving something back to the people who actually host the tech