Make your life easier, created issue #1744 on github for the FAQ update.

@nik said: Mobile view - this needs major rework and a dedicated mobile theme. Right now it's practically unusable to type as the keyboard is taking up 95% of the composer box. The voting buttons are too small and things basically don't look right for anything but browsing. Other buttons to attach pics are equally too small. Needs mobile specific features like 'take a pic'. The composer in mobile view is a serious issue, it's barely usable in the current form. Just a pair of lines show up, depending on the screen size. Isn't there a way to fill the screen with the text area without resizing it when popping out the keyboard? Geotagging is also very cool and innovative. I see a lot of uses for it, think about combining it with an event plugin.

@a_5mith said: I have a photographic memory. I read it, honest. Yep, I read it too. It was 3 days ago. If only we had a search that actually...

Seems to happen more often after a restart, after the first 404s it will eventually start pulling posts properly then at some point the connection will go stale and it'll 404 again. It's pretty consistent for me. About to try it out on the latest pull. Nothing in the logs/dev mode. Just 404s in the console.

@zenkamal @a_5mith This sounds like it's due the new way we store post bookmarks. Basically: Before, we stored the pid (e.g. 2341) Now, we store the post index (e.g. 5) The bookmark only updates if the current post # is > than the bookmarked post # Unfortunately, 5 will never be greater than 2341, so the bookmark never goes away. The old bookmark is basically trying to load the 2341th post in the topic, which doesn't exist. You can clear the bookmark by clicking the "x" at the top right of the notification alert, then that topic should be fixed.

@nik This was the board I tested it on. I'm not sure if @julian can shed some light on this as something isn't right with your experience and I'm not sure what would cause these things to happen. It's not your build of NodeBB, it's not one browser or the other as it happens on both Desktop & Mobile, the only thing left is your internet connection, but I don't know whether xhr-polling or websocket issues would cause it.