total hypocrite (![[info]](http://l-stat.livejournal.com/img/userinfo.gif){kind=small} totalhypocrite) wrote,@ 2006-04-23 00:23:00 |
|
10 millionth reason to hate LiveJournal.
If you're looking at an entry on LiveJournal, and click the next entry button, it doesn't always show you the next entry.
If the next entry is set to private, friends only, or "all friends but adam" protected, you get a wonderful "Error You are not authorized to view this protected entry." page instead.
This is bad for a number of reasons:
1. It's not really an error at all, it's just asshole permissions working as intended.
2. It lets me, the user know that there are entries in existence that I can't read. This is the sort of bug that's important to pay attention in social software. I don't want to know that you're writing things marked as private or "all friends but adam," my blood pressure is high enough as it is.
3. The "error" page doesn't have forward and back arrows, so you can't continue to browse the entries, it's just a deadend.
4. This situation is wholly preventable on the server side since the next and previous buttons hit a server side script to direct to the next entry (it's not as though it's a static link on the page.) It should just smartly figure out the next *viewable* entry for the user, rather than doing something braindead like take the next sequential entry regardless of viewability.
How much did SixApart pay for this again?
And yes, as always, I'm talking about you.
If you're looking at an entry on LiveJournal, and click the next entry button, it doesn't always show you the next entry.
If the next entry is set to private, friends only, or "all friends but adam" protected, you get a wonderful "Error You are not authorized to view this protected entry." page instead.
This is bad for a number of reasons:
1. It's not really an error at all, it's just asshole permissions working as intended.
2. It lets me, the user know that there are entries in existence that I can't read. This is the sort of bug that's important to pay attention in social software. I don't want to know that you're writing things marked as private or "all friends but adam," my blood pressure is high enough as it is.
3. The "error" page doesn't have forward and back arrows, so you can't continue to browse the entries, it's just a deadend.
4. This situation is wholly preventable on the server side since the next and previous buttons hit a server side script to direct to the next entry (it's not as though it's a static link on the page.) It should just smartly figure out the next *viewable* entry for the user, rather than doing something braindead like take the next sequential entry regardless of viewability.
How much did SixApart pay for this again?
And yes, as always, I'm talking about you.
