- Press "V" or press the + button to show the large JPEG. You can't view the PNG version if there's a JPEG. (PNGs are for editing and archival; I can't think of any reason to want to load them instead of JPEGs when *viewing* images--all it'll do is choke the browser.)
- Vote with `, 1, 2 and 3.
- Press "F" to jump to the find box.
- When viewing the large version, a navigator appears in the top corner to make navigating easy. It disappears in fullscreen to get out of the way, but it'll appear if you hover over it.
- Edit a post by pressing "E". You can edit with the keyboard quickly; for example, type "E" "S" <enter> to quickly change a post to Safe, or press "E" "pool:123" to add the post to pool #123. Pressing escape while in the edit box will close it again.
- Most editing works in place: flag, delete, undelete, unhold, etc. Not everything is there yet (can't destroy a post, no link to history, etc).
- When on post/show, press "B" to jump directly to the browser on that post.
- If you use Chrome, try "Tools -> Add application shortcuts"; it'll work like a native application.
- If you have a rotating LCD stand, try switching it to portrait. I may increase the vertical resolution of sample images a bit so this works better.

- The browser works on iPhone and Android. On iPhones, use "add to home screen", to get the Safari interface out of the way. The UI is a bit goofy on Android: you may need to turn the phone to landscape and back to get it to go fullscreen. (Android's browser just isn't very good at full-screen web apps, which is surprising given that Google is built on web apps. They really need to improve on this.)
- You can vote on posts on a touchscreen. When in fullscreen, touch the bottom-left corner of the screen and voting stars will pop up. Drag to the vote you want. You need to log in to vote, and you can't do that from post/browse right now, so just log in normally once before using it.

- Open the editor and click "Frames" to edit image frames; drag in the image to create and modify them, and then click Save. Changes may take a couple minutes to show up.
- This takes advantage of the full image resolution by cropping each box from the original PNG. Instead of an image with four frames being squished into a single sample image, each one gets its own.
- It's useful for separating pages with multiple illustrations, and for cropping out borders, without creating lots of duplicate posts.

- Every browser I've tried is suboptimal when scaling large images. The closest to having solid performance is Opera, but it's still not smooth when dragging around. Chrome is slow to the point of being broken when rendering the thumbnails over a large image. So, some Canvas tricks are played behind the scenes to speed things up. This should be mostly transparent.
- All WebKit browsers, including Chrome, tend to leak memory. I'm pretty sure this is a browser bug. I've mitigated it as much as I can; it seems bearable.
- Images are preloaded if it notices that you're viewing images in order, which makes viewing images much smoother. It only does this if you're viewing images one after another; if you skip around it'll stop.
- When you first run a search, it loads 100 posts; this doesn't put much load on the server, and makes searches quick. If you view enough of those posts (around 75% currently), it'll rerun the search in the background and load 1000.
- It doesn't put much load on the server. All page rendering is done client-side; if you view 50 posts from a search, it only has to make a single API call to the server.
- Chrome and Opera have nice, clean fullscreen modes. FF3.6 doesn't (you'll get an ugly white menu strip at the top), but that seems to be fixed in FF4.
- We'll probably drop an ad into the thumbnail bar, so it'll be visible but not intrusive.