El Presidento Ben on Nostr: ⚡ TWENTY ONE Companion · v1.12.1 v1.12.1 — a repair release. Nothing new on ...
⚡ TWENTY ONE Companion · v1.12.1
v1.12.1 — a repair release. Nothing new on screen, one crash gone.
The app could die right after an update, while it was still open. A background job starting Laravel a second time — the one that checks for new messages, or the one that runs queued work — tore down the running engine instead of attaching to it. It never happened on a cold start, only in that window, which is why it looked random rather than reproducible.
Background work now waits for the first boot after an update to finish before it touches anything, instead of racing it.
And the rule that only portal links under /app/ open in the app, while everything else stays in your browser, is no longer a local patch on top of NativePHP — it is part of NativePHP now. Same behaviour, one less thing that can silently fall away on the next update. The build refuses to produce an APK whose manifest disagrees.
Still no Play Store, still no Google Services — your phone talks to the relay itself.
━━━━━━━━━━━━━━━━━━
📥 Get it / update:
⚡ Zapstore (recommended) →
https://zapstore.dev📦 Obtainium (auto-updates) →
https://apps.obtainium.imranr.dev/redirect.html?r=obtainium://add/https://github.com/HolgerHatGarKeineNode/twenty-one-companion🐙 GitHub (APK + signature) →
https://github.com/HolgerHatGarKeineNode/twenty-one-companion/releases/latest🛠️ Source, MIT →
https://github.com/HolgerHatGarKeineNode/twenty-one-companion#bitcoin #nostr #einundzwanzig #android
Published at
2026-09-11 17:20:29 UTCEvent JSON
{
"id": "8b4ec715af24d8f93a5bfbd59a8d49a5df24ff2574b395fb8c12a8cb366e5ca0",
"pubkey": "0adf67475ccc5ca456fd3022e46f5d526eb0af6284bf85494c0dd7847f3e5033",
"created_at": 1789147229,
"kind": 1,
"tags": [
[
"client",
"TWENTY ONE Companion"
],
[
"t",
"bitcoin"
],
[
"t",
"nostr"
],
[
"t",
"einundzwanzig"
],
[
"t",
"android"
]
],
"content": "⚡ TWENTY ONE Companion · v1.12.1\n\nv1.12.1 — a repair release. Nothing new on screen, one crash gone.\n\nThe app could die right after an update, while it was still open. A background job starting Laravel a second time — the one that checks for new messages, or the one that runs queued work — tore down the running engine instead of attaching to it. It never happened on a cold start, only in that window, which is why it looked random rather than reproducible.\n\nBackground work now waits for the first boot after an update to finish before it touches anything, instead of racing it.\n\nAnd the rule that only portal links under /app/ open in the app, while everything else stays in your browser, is no longer a local patch on top of NativePHP — it is part of NativePHP now. Same behaviour, one less thing that can silently fall away on the next update. The build refuses to produce an APK whose manifest disagrees.\n\nStill no Play Store, still no Google Services — your phone talks to the relay itself.\n\n━━━━━━━━━━━━━━━━━━\n📥 Get it / update:\n\n⚡ Zapstore (recommended) → https://zapstore.dev\n📦 Obtainium (auto-updates) → https://apps.obtainium.imranr.dev/redirect.html?r=obtainium://add/https://github.com/HolgerHatGarKeineNode/twenty-one-companion\n🐙 GitHub (APK + signature) → https://github.com/HolgerHatGarKeineNode/twenty-one-companion/releases/latest\n🛠️ Source, MIT → https://github.com/HolgerHatGarKeineNode/twenty-one-companion\n\n#bitcoin #nostr #einundzwanzig #android",
"sig": "4a837c53bde6bf60a7ed6424f437d1e74e6e4a8fe3a3f9634f239f9c9a6e0adb35fcbe34673b131805bc83b128f18c88de9605608f9d85bcb5d862e1770c18fb"
}