4 ms·
The other reason, btw, is because I don't want to be responsible for taking "destructive" action. If a user misunderstands a feature and doesn't know why they d
by mattkruse 5y ago
The other reason, btw, is because I don't want to be responsible for taking "destructive" action. If a user misunderstands a feature and doesn't know why they don't see their friend in their newsfeed anymore, I don't want to be responsible for that. I will never unlike, never unfriend, never unfollow, etc. I won't even trigger positive actions automatically. This is the kind of thing Facebook really cracks down on, and because it's very fragile, a change in their API could cause the wrong behavior from a browser extension. It's not worth it.
- cratermoon 5y ago> If a user misunderstands a feature and doesn't know why they don't see their friend in their newsfeed anymore, I don't want to be responsible for that. Oh that's a gem. It's so rare in the field to see developers thinking in terms of "what if my code does something the user doesn't expect?" and putting into practice the principle of least surprise. So much software seems to want to blame the user for doing it wrong, it's good to see a different approach.