Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Users often wish to be able to delete or make something that was once public private.

People also wish to be be able to do a lot of other things, but that doesn't make it right.

What becomes public history must remain immutable. Otherwise you're just going to encourage a state in which those who have the power to will destroy and rewrite the past to their advantage, to control the narrative over the population. The trendy phrase "right to forget" is effectively a "right to rewrite history".

It's interesting that you automatically call those wanting to preserve what could possibly be very important history "malicious scrapers".



>It's interesting that you automatically call those wanting to preserve what could possibly be very important history "malicious scrapers".

I am going off of twitter's view. If you store tweets locally you must listen for when they get deleted and then delete them on your end too. If a scraper is breaking twitter's rules I consider that malicious scraper.

https://developer.twitter.com/en/developer-terms/policy#3.Up...

>If you store Twitter Content offline, you must keep it up to date with the current state of that content on Twitter.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: