v0.0.5 — threads stop re-fetching themselves

Early pre-release for testing on Android.

Coming from v0.0.3 or earlier, or from the very first v0.0.4 upload? Those were signed
with a debug key, so Android will refuse to install over them — uninstall first.
Coming from the signed v0.0.4, this updates normally.

Which file

File	Size	For
textlog-0.0.5-arm64-v8a.apk	18 MB	Virtually every phone from the last decade — take this one
textlog-0.0.5-armeabi-v7a.apk	15 MB	Older 32-bit devices
textlog-0.0.5.apk	48 MB	Universal; runs on anything, if you would rather not choose

Threads stop re-fetching themselves

This one is about being a good guest. textlog allows 120 API requests a minute, and a nested
thread costs one request per branching node — so browsing a few threads could rate-limit you,
and every trip back into a thread paid the full price again.

Reply pages are now kept for the whole session. Measured against a real five-level thread:

	before	now
Opening it the first time	10 requests	10 requests
Opening it again	10 requests	0
Following "+ N more replies" into a branch already loaded	1–2 requests	0

Freshness is tracked per node rather than per thread, so a pull-to-refresh refetches only
what has actually gone stale instead of the whole tree. If something has aged out, you get
the cached version straight away and the update arrives behind you — on a micro-blog, a
thread that was quiet five minutes ago is almost certainly still quiet.

Also fixed: the same replies page could be requested twice while a screen was being built.

For iPhone owners

There are still no iOS downloads — Apple wants a paid developer account to hand anyone an
installable build, and this project is AGPL, which has historically been incompatible with
the App Store. The README now has step-by-step instructions for building it onto your own
phone with a free Apple ID, if you have a Mac.

Unofficial client. textlog is by stagas.