I'd just like to mention that using the [Update] buttons, in catalog, overboard and thread, will speed up your update as compared to pressing F5 or the refresh button. This is because the browser has to revalidate the cache when you refresh manually, and that's why those [Update] buttons are there in the first place.
Always use the [Update] buttons rather than Ctrl+R or F5.
You're not accounting for the inherent delay caused by having to take my hands off of the keyboard to click a button. Refreshing the page is infinitely faster. Is auto-updating at intervals possible without js?
>>1089 >Is auto-updating at intervals possible without js?
Short answer: use a browser plugin. Long answer: Yes, but it's impractical because it wouldn't take into account whether you're tying something into the post box: it could refresh just as you were about to make a post, and then you would lose your post.
>>1088 on the overboard:
>ctrl+R takes 15 seconds
>[Update] takes 3 seconds
hey you're right
if only the browserdev niggers added a keyboard shortcut for doing this
>>1092 I don't think I would be capable of detecting whether someone was using an auto-refresh plugin, short of measuring their refresh times which would be incredibly unreliable at best because I don't have their IP address. Maybe if javashit was enabled it would be a security risk.
>>1094 Use F6+Enter instead. Or Ctrl+L+Enter. Caveat: it doesn't work when you have #anchor targeted in the URL box.
>tfw search on shitoverflow and pajeets recommend using javascript just to reload the page
AAAAAAAAAAAAAAAAAAAAAAAAA
I'd just like to mention that using the [Update] buttons, in catalog, overboard and thread, will speed up your update as compared to pressing F5 or the refresh button. This is because the browser has to revalidate the cache when you refresh manually, and that's why those [Update] buttons are there in the first place.
Always use the [Update] buttons rather than Ctrl+R or F5.