Author of Tamers of Entropy / Krotitelia Entropie: a lunarpunk / cypherpunk novel about where we are and where we are going. tamersofentropy.net Learn about Bitcoin for your lifestyle, enjoying volatility and thriving in uncertainty. My goal is tech + hacking => liberty and life satisfaction. Good vibes / tech: github.com/jooray - author of Emanator (Nostr multi-account client and scheduler), Lievik (marketing channel automation), Nostrautica (event app with attendee matching) and a lot more! Find my books and courses, such as Cryptocurrencies: Hack your way to a better life. Books, Courses (EN, ES): hackyourself.io/shop/ Books, Courses (SK): juraj.bednar.io/shop/ I teach how to handle volatility, what to do when you want to enjoy the value of your Bitcoin, how Lightning network works, cypherpunk tech and more, hacking applied to many areas of life, etc. Podcasts 🎙️: Option Plus (EN) - optionplus.io/ Reči o živote, vesmíre a vôbec (SK): juraj.bednar.io/reci-o-zivot… Ako vyhackovať otcovstvo (SK): otcovia.com/ I usually hangout on Nostr: [email protected]

Localhost Recording Studio 0.5.0 — the app now tells you what it is doing, and the catalogue tells you which takes you liked. Against 0.4.9: - The song page answers. Open a take while it is being made and you get the phase — LISTENING, SCORING, RECORDING, MIXING, MASTERING, FILING — the time left, and a rule under the words that fills as the job moves. The ring of the disc carries the same progress. Before this, the phase lived only in the studio and a song page said nothing at all about the job that was running. - Hearts. Mark a keeper from its page or with a long press; the index shows a filled heart next to every take you liked, so a batch of variations can be scanned for the good ones. - NEW. A finished take nobody has heard yet is marked NEW in the list. The mark goes when you play the mix or like the take. - The hole in the disc is a play/pause button. It used to seek only on the ring, and did nothing on the song page. While a take is still mixing, it plays the preview. - Covers remember their score. The score written down from a recording is kept, keyed by the recording's own bytes, so covering the same file again skips the listening and goes straight to the song — in a later session too, or after the first take was deleted. SCORE and MELODY stay apart. jooray.github.io/studio-loca… Android on Zapstore, Mac and Android builds on GitHub: github.com/jooray/studio-loc… And check this nice hallucinated song playing in the interface :)

Turns out AI is taking jobs of entrepreneurs in "creative" domains. And we thought robots would be all logic and physical power. And they're hallucinating pictures, videos, codes, photos and songs.

Tomorrow is a very special event that we organize, to celebrate, we have new version for you! Emanator 1.4.1 for Android and the web Interactions moved into the bottom bar. A reply is a daily errand; the calendar is a plan you look at now and then. The phone bar is now Dashboard, Posts, Interactions, Messages, More. Calendar moved behind More — it keeps its own entry on a tablet's rail, and the bar stays put while the calendar is open. You can mention people while replying. Type @ in the Interactions reply box and you get the composer's suggestions: your own accounts first, then people your accounts follow. The pick becomes a real Nostr mention, so the person is notified. Same in the app and on the web. Copy a note, share it as text. Every post page has "Copy text" under the note. Settings → Sharing adds a button per network, off by default: - X opens x.com's compose window with the note already written. - Facebook and LinkedIn cannot take a post's text from a link: their share endpoints only accept a URL, and a note is not a link. On the web the button copies the note and opens their composer to paste. In the Android app the note goes into their app through the system share, and without the app it falls back to copy and open. Retry actually republishes. A failed post that was never signed asks your signer again instead of answering "Cannot retry publishing.". A note that was signed but no relay accepted, and whose signature is older than 15 minutes, is signed again dated now — sending the old event would only bury it — and its reposts are rebuilt with their delays after the new time. A note some relay did accept is resent unchanged, so a retry cannot make a duplicate. Retried replies are dated now instead of the day they failed, and replies can no longer be rescheduled (that path built a plain note and dropped the reply tags). A reply says what it answers. The post page shows "In reply to: view the note", on the web and in the app, so a failed reply is not mistaken for a standalone note. Behind the scenes: imported legacy DMs are stored as history rather than as messages you just sent, and one malformed event no longer aborts the import. Get it: - Website: emanator.cypherpunk.today/ - Zapstore: zapstore.dev/apps/today.cyph… - GitHub release / Obtainium: github.com/jooray/nostr-eman… - Direct APK: emanator.cypherpunk.today/an… - Web app: emanator.cypherpunk.today (already updated, nothing to install)

Emanator 1.4.0 is out — Android and web Interactions is now a primary view instead of a menu item. On the phone it takes Calendar's place in the bottom bar (Dashboard · Posts · Interactions · Messages · More); replies are a daily errand, the calendar is something you look at now and then. The bigger change: you can mention people while replying. Type @ in the Interactions reply box and you get the same suggestions the composer has — your own accounts first, then people your accounts follow. The pick becomes a real Nostr mention, so the person is notified. It works in the Android app and in the web app, whose inline reply boxes got the same treatment. Both clients also share a set of retry fixes. A failed post that was never signed now goes back to your signer instead of answering “Cannot retry publishing.”. A note no relay accepted, signed more than 15 minutes ago, is signed again dated now — sending the old event would only bury it — with its reposts rebuilt after the new time and previously failed reposts brought back. A note some relay did take is resent unchanged, so retrying can't duplicate it. Retried replies are dated now rather than the day they failed, and replies can no longer be rescheduled (that path built a plain note and dropped the reply tags). Replies also show what they answer: “In reply to: view the note” on the post page, in both clients. Get it: · Zapstore — zapstore.dev/apps/today.cyph… · GitHub release / Obtainium — github.com/jooray/nostr-eman… · Direct APK — emanator.cypherpunk.today/an… · Web app — emanator.cypherpunk.today The web is already updated — same features, no install.

Another day, another set of patches - @BtcpayServer (because of rtl/nodejs/brotli), NodeJS everywhere, Bind (although I do not run vulnerable configuration). This is fun :) I am token poor until reset, so my daily driver is DeepSeek 4.1 Flash 1017 and it is amazing. I barely feel any difference. And I used to be a professional sysadmin, so I could do it myself, but this is way faster.

I don't understand, do they mean that when I put on a tinfoil hat and those funny glasses, I can see the future? Or what did they mean on May 6th?

Confession: Something that I can't unsee lately and it's probably one of the best indicators of intelligence - does a person immediately see second and third order effects, understands emergence and structure of described phenomena (qualitative analysis)? I don't want to be picky about things I understand, there are many things I am not good at (intellectually), but I think this quite well maps with exceptional intelligence and it's very rare that people understand these things, or even see them as something to understand. And then there's this "feeling" when I am explaining this to someone and they just don't get what I am talking about. Or I meet someone with exceptional intelligence and they see it immediately. It's a two minute IQ test. I don't know at what IQ (roughly, IQ is not perfect) there is this "switch', but I just can't unsee it. And I find myself using this probe a lot lately.

I highly recommend cloudflare's security audit skill: github.com/cloudflare/securi… Run it on all your software. Run it with the free models. Use it even if you used a model to audit something - it will find much more things. Works in all agent harnesses and is model independent.

CashuPayServer v0.5.7-alpha is out — the second release from this October's three independent security audits, and it closes every code-side finding they left open. If you've patched your PHP already, you can also upgrade CashuPayServer. If not, patching PHP is more important, go do that. The most serious one was in the WordPress plugin: showing the seed phrase or downloading the database accepted any password, because the already-open admin session was the only check (but you still needed to be logged in as admin into WordPress). It now asks for your real WordPress password. MiniMax M3.1 found that one, and it is again the model that caught something the earlier scans missed. The rest of the important fixes: - Stranded-funds exports now reserve the money, so the same ecash cannot be handed out twice or spent while the token circulates. - The setup wizard can no longer be re-entered to reset the admin password or keep a previous claimant's server address. - Fiat pricing needs two independent sources to agree, so one bad provider cannot underprice invoices. - An interrupted wallet backup no longer leaves a full copy of the database behind. - Public token submissions are bounded, closing a request that could burn minutes of CPU. - Trusted-proxy settings can no longer name the whole internet. Upgrading takes a couple of minutes and there is nothing to configure: - Standalone: upload the new files over the old ones, keeping your data folder. - WordPress: upload the plugin and choose "Replace current with uploaded". The database updates itself on your first visit. Three audits, three models: DeepSeek 4.1 Flash 1017, Opus 5.5 and MiniMax M3.1 (Space Bunny). They found real issues at every level, including the WordPress one above. What changed? We used the same models for previous audits, but this time we used the cloudflare security audit skill: github.com/cloudflare/securi… Highly recommended, it's good. 👉 Download: github.com/jooray/cashupayse…

PSA: turn off PHP now. Mitigations you find on the internet are not enough. Only patched release fixes the bugs. Exploits already in the wild. Watch php.net and your distribution update channels and only enable PHP after you install patched release. This is not a drill.