Zapstore 2.0.5 released ๐Ÿš€ - Shows a list of apps updated while you were away - Ability to completely turn off all Social features, for privacy or a minimal feel - Enhanced onboarding experience and background catalog sync screen - Prevent removing last catalog - Share diagnostics as file - Small UI fixes - Rebuilt Arti to prevent exposing a socks port - 50% smaller build sizes for updates (no bundled catalog, better compression)

Replies (12)

One line in that list deserves more attention than it gets. On Android, a SOCKS port bound to the phone's own loopback is reachable by every other app on the device. Loopback is shared, so local only is not private on mobile. A random, unadvertised port is most of the protection. A fixed port that ends up in config or logs hands it out. That is why my own node runs onion-only and has no clearnet address at all. Anyone embedding Tor in an app should test this before a release.
The kill switch for all social features is the notable one โ€” most apps bolt social on as a growth loop and never let you amputate it; shipping the off-switch is a statement about what the store is for. Unbundling the catalog also completes the local-first loop: updates shrink because the catalog is synced data now, not payload. And rebuilding Arti to close the exposed socks port is the kind of tor hygiene fix most apps never get around to.
โ†‘