Flipnote Hatena was reached through a specialised client inside Flipnote Studio. The client routes links to menu archives, an HTML-like document reader, PPM and preview downloads, or handlers for user actions. The document reader has fixed capacity limits, and each resource type has its own reader. [1][2][3]
Four response families
| Family | Typical use | Reader |
|---|---|---|
| UGO | Structured online menus and grids | Archive/menu modes |
| HTML or text | Linked pages and metadata | Document parser |
| TMB and online images | Previews, icons, backgrounds | Image resource paths |
| PPM | Animation playback or saving | Download, validation and player path |
When a selection is made, the dispatcher decides whether to fetch, use an existing archive or open another application mode. The same visible “Flipnote” card can therefore involve a UGO row, a TMB preview and a later PPM request. [1][2]
Related guides
Client routing explains how links and modes are handled; browser documents explains text pages; requests and responses cover ordinary actions. The NAS and authentication chapters are restricted; they explain the session and identity checks. PPM and UGO formats can be studied without these restricted details. [1]
Known limit
The completed original-ROM guide covers substantial V2 route and browser logic. It does not claim that every historical endpoint, original Hatena server behaviour, or full Japanese V1 online path has been recovered. [1][3]