@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 learned a lot from this experiment tho