An excellent suggestion. Dabr’s users primarily browse on a mobile. So the back button is often hidden in a menu. Lack of JavaScript support in many phones means I can’t use .go(-1).

I suppose I could make the “newer” button call the same URL as the previous page – and the home page if none existed – but that means that the user journey could be
50-60, 60-70, then 95-105. Missing out all those tweets inbetween. Meaning you have to go to the newest and work back rather than sequentially through.