... card, from Swift or from Dart. The fix is push to start: the app saves the push to start token, and the backend raises the card itself. Two traps inside that one: a Date in the activity attributes never decoded from the push payload (send plain seconds), and the app is suspended the moment the intent returns, so the intent has to wait for the started card's own push token before answering, or the "ready" push has nowhere ...

... exact octoscope version wrote it, with the same data layout, for the same token looking at the same account, and only while it's under a week old. Anything else is ignored like a first run, because a zero decoded from a renamed field looks exactly like a real count. Upgrade: brew upgrade gfazioli/tap/octoscope How do you keep your dev dashboards open: one long-running tab, or quick launches all day? Site: https://gfazioli.github.io/octos... Newsletter: https://octoscope.substack.com Discord ...

... limits on everything. At most a hundred line items. At most twenty taxes on any one item. A length cap on every text field, a byte cap on the logo, and checks that run before anything expensive is decoded. Each limit was chosen by asking how large one field can reasonably be, and each one was sensible on its own. Then we measured a request that respected every single one of them: a hundred items, each carrying twenty taxes ... ... totals, so it got its own cap of sixty characters instead of sharing the two hundred allowed for an item name. And the logo is drawn into a box a few centimetres wide, so a 3000 pixel image was decoded

... where Chinese, Japanese and Korean mail stops looking like a row of . Turns out "just assume UTF-8" isn't a real internationalization strategy. Who knew. Fixed CJK charsets decode properly. GBK, GB18030, Big5, Shift_JIS and EUC-KR subjects and bodies now come through as actual text, not replacement characters ( #53 ). Already-garbled mail repairs itself. Folders that were holding the broken messages get refetched once on the next sync, this time decoded

... realized I don't like reading text linearly. Someone writes a text, and it's encoded by their writing style, knowledge, thinking patterns, and so on. Then I need to read it through, decode it, and understand if it was worth the effort. AI slop summaries don't work for me either. But I'd like a tool that lets me "read on my terms" - explore text in stages that I prefer, as shallow (topic/description/keywords) or as deep ... ... want. Like a progressive JPEG, zooming into details based on my interest level. For example, with typical inbound emails, I'd want them reshaped into a "decoded