cloud fodder

{ "id": "0a8b964fa4d000efe22bd9791c477603858e06af2c3d1fc04ecbb3b288ab88ef", "pubkey": "7cc328a08ddb2afdf9f9be77beff4c83489ff979721827d628a542f32a247c0e", "created_at": 1773509714, "kind": 0, "tags": [ [ "alt", "User profile for cloud fodder" ], [ "name", "cloud fodder" ], [ "display_name", "cloud fodder" ], [ "picture", "https://rogue.earth/.well-known/th3administrator1.jpg" ], [ "banner", "https://i.nostr.build/iRxVglmf9W1FXauf.jpg" ], [ "about", "captain of a sailing vessel\n\nbuilding relay.tools\n\nelectron microscopic time preference capable\n\nsimplex DM me for all your remotely operated underwater vehicle needs: https://simplex.chat/contact#/?v=1-4\u0026smp=smp%3A%2F%2FSkIkI6EPd2D63F4xFKfHk7I1UGZVNn6k1QWZ5rcyr6w%3D%40smp9.simplex.im%2FP0rE9zB_W1ljpc_Jsaz6K-tbRm2mHqsP%23%2F%3Fv%3D1-2%26dh%3DMCowBQYDK2VuAyEAvVLbWdTbqwpdPLLtKG22WDXJUiS1EMVTByd5NuwikWU%253D%26srv%3Djssqzccmrcws6bhmn77vgmhfjmhwlyr3u7puw4erkyoosywgl67slqqd.onion" ], [ "nip05", "[email protected]" ], [ "lud16", "[email protected]" ] ], "content": "{\"name\":\"cloud fodder\",\"about\":\"captain of a sailing vessel\\n\\nbuilding relay.tools\\n\\nelectron microscopic time preference capable\\n\\nsimplex DM me for all your remotely operated underwater vehicle needs: https://simplex.chat/contact#/?v=1-4\u0026smp=smp%3A%2F%2FSkIkI6EPd2D63F4xFKfHk7I1UGZVNn6k1QWZ5rcyr6w%3D%40smp9.simplex.im%2FP0rE9zB_W1ljpc_Jsaz6K-tbRm2mHqsP%23%2F%3Fv%3D1-2%26dh%3DMCowBQYDK2VuAyEAvVLbWdTbqwpdPLLtKG22WDXJUiS1EMVTByd5NuwikWU%253D%26srv%3Djssqzccmrcws6bhmn77vgmhfjmhwlyr3u7puw4erkyoosywgl67slqqd.onion\",\"picture\":\"https://rogue.earth/.well-known/th3administrator1.jpg\",\"nip05\":\"[email protected]\",\"banner\":\"https://i.nostr.build/iRxVglmf9W1FXauf.jpg\",\"displayName\":\"cloud fodder\",\"display_name\":\"cloud fodder\",\"lud16\":\"[email protected]\",\"username\":\"cloudfodder\"}", "sig": "a172f378b95519e2d9a0c0380c04eaf134674559936d480558a2a9a195556104033de39fd340f541c08921cfe07f7e4296cb8f619aa0a64c76e61888c75daede" }

Last Notes

2026-08-02 16:14:07 UTC

The commit that disabled RNG had a simple commit message: "runs"
Wow. Good1.
#nevent1q…ekt5

2026-08-02 07:41:40 UTC

- reply

you can tell if there is entropy available yes, but you have a really hard (impossible?) time checking afterward

2026-08-02 07:29:16 UTC

just to be 100% clear..
#nevent1q…algj

2026-08-02 07:28:37 UTC

- reply

and also, the lesson isn't "shoulda rolled dice"
ffs

2026-08-02 07:25:22 UTC

- reply

Well, I hope to hear your next podcast denouncing these (alleged) **** that (allegedly) ***** .. we all get fooled, but we cannot allow the lessons to be swept under a rug of (alleged) cover up..
so i don't wanna see, just some pivot to shilling jade, or etc.
this just will not (allegedly) stand.

2026-08-02 07:19:20 UTC

- reply

thanks, wg stalled

2026-08-02 06:25:18 UTC

- reply

oh you did, lemme add you to the list @npub1jlr…ynqn
don fuk w me rn, you called your wife to beg for seed
and you're fucking lucky she could read 12 words in time for you to rescue your funds from these piece of shit patsies. they killin bitcoin self-custody with their inside job allegedly bullshit, and your gonna tell me to knock off the witch hunt?
nah bro, i don't think i'll knock off this time.

2026-08-02 05:06:29 UTC

The bullet
#nevent1q…fnv8

2026-08-02 04:57:11 UTC

Take account. You prob never would see me this pissed off

2026-08-02 04:55:18 UTC

What's it gonna take

2026-08-02 04:54:33 UTC

I feel bad, because we let the plebs down.. We let, yet another scam motherfucker and all their fucking piece of shit advertisement eclipse actual knowledge.
Bitcoin cycle 2026
FUCK

2026-08-02 04:51:31 UTC

- reply

All their bullshit don't work without a couple random #$

2026-08-02 04:50:16 UTC

On X
This would get burried. Use it or loose it what are we even here for. 🕵❤
Tag or just add a comment. With EVERYONE you ever saw shill coldcard.
I'll start @npub1qny…95gx
@npub1myg…sn5p
...

2026-08-02 04:30:19 UTC

- reply

Its a
Fucking
Disgracd

2026-08-02 04:26:35 UTC

Boosted
Welcome to the final show
#nevent1q…74sf

2026-08-02 04:24:57 UTC

- reply

Ya naw man, you can't tell from a string if it was RNG or not. This is the root of the problems.
Math people will fight all day long about this and we just learned. Idiot larping pieces of shit, who rode on the coat tails of gpl-v3 and then did this..they can't be trust.
Open source for reals, or bust.

2026-08-02 04:18:40 UTC

Damn that's cray
#nevent1q…jh45

2026-08-02 04:17:31 UTC

- reply

If you used linux, you're good
If you didn't, just stop your cryin its a sign of the times
Gotta get away from here
😭🌶😭🌶

2026-08-02 04:04:06 UTC

- reply

Harry styles

2026-08-02 04:02:50 UTC

- reply

These grifter motherfuckers

2026-08-02 03:59:40 UTC

you can't prop the door on your way to the sky
you look, pretty good down here
but you aint' really good.
#nevent1q…n76d

2026-08-02 03:43:48 UTC

- reply

Everything will be alright, we can meet
Again somewherr

2026-08-02 03:40:20 UTC

- reply

Jus stop your cryin its a sign of the times

2026-08-02 03:38:13 UTC

Hope your wearing yourbess
Clothes.
Welcome to the final show

2026-08-02 03:33:52 UTC

- reply

Never did jack shit

2026-08-02 03:18:41 UTC

- reply

ya, this is what I see, nothin'
cause whatever that was, somebullshit dog. but I'm happy for u, or sorry that happen 😗
http://newlay.relay.tools/4defab5552616525e2b0d401f0baaee37fccf1377bb8f2856fa80ebaa897d09c.png

2026-08-02 03:06:14 UTC

- reply

no, it would be used in all aspects of anything that needs to negotiate cryptographic stuff.. including doing, pretty much anything

2026-08-02 03:03:58 UTC

- reply

tails or somethin

2026-08-02 02:57:22 UTC

yah, I said it.. its true imho
#nevent1q…0x4z

2026-08-02 02:55:55 UTC

- reply

you can't trust any of it's features because it used shit RNG to bootstrap all of it IMO

2026-08-02 02:53:19 UTC

- reply

I mean, the 50,000 lurking DAU seems to think its more alive than anything 😂 hold on lemme shill that to the suits

2026-08-02 02:46:04 UTC

- reply

I know dude

2026-08-02 02:43:00 UTC

scriptz as far as eye can see
#nevent1q…zv5p

2026-08-02 02:42:09 UTC

- reply

its clear that regardless of any supposed updates to the code..
trust is broken.
I wouldn't trust those fuckers with dice Rollin scripts even after auditing with fable5

2026-08-02 02:32:51 UTC

you wanted to be your own bank or not? its OK if you don't. tbh, some would call it hard
https://image.nostr.build/8ca570643cb2c614282cd3f12043017bd5edf8433717aa2649e78da8da5d7153.png
#nevent1q…hfpu

2026-08-02 02:25:40 UTC

- reply

multi pass?
https://image.nostr.build/0e63a83a8c6e607bc9f2ec31e4e435fa4bc6a7f1e1e6e2ca84e43cb639abe238.png

2026-08-02 02:14:44 UTC

so silly that my OG relay nostr21.com regularly and sustainably gets >50,0000 simultaneous connections.. from mostly unique IPs. there's hardly anyone on here.. 😂😂😂😂
fuk, whatever

2026-08-01 23:18:34 UTC

- reply

With multisig, yes.

2026-08-01 23:15:36 UTC

clock's ticking @npub1qny…95gx
#nevent1q…28mu

2026-08-01 23:15:00 UTC

- reply

O M G

2026-08-01 23:13:25 UTC

- reply

scammer don't care.

2026-08-01 22:59:20 UTC

- reply

I will accept your screenshots, and nothing less. You DOXed yourself just to get them, and provided X with your pumped up viewership of their scam ridden advertisement machine. I couldn't stomach that probably, but, maybe I would'of. In the past.

2026-08-01 22:54:40 UTC

Marked safe from X. I was going to go on there and talk shit, but they wanted me to install the mobile app and I said no. If you post links to twitter, I'm just gonna judge you harshly now. I hope your influencoor points are gonna do some good in the world, but we all know they won't.
Fuck the fuckers. Y'all scam artists now by association.

2026-08-01 22:51:22 UTC

- reply

This is kinda why I don't like seed plates. Any good hygiene means moving to new wallets frequently.. So they're kinda useless. Multisig better, geographic distributed and able to be destroyed.

2026-08-01 22:48:52 UTC

- reply

Tldr, time to get out the pitchforks

2026-08-01 22:46:02 UTC

- reply

I can barely read this I am so disgusted.

2026-08-01 22:38:12 UTC

- reply

Yeah, it's not just that either, it's that hardware RNG, while vastly superior to ZERO RNG, is still, created by a manufacturer who could fake it, and cause non-entropy for their own whim.. That's why, linux RNG drivers in the kernel derive entropy from that PLUS many other sources and combine it all into one. And that's I guess why they sold these shitty dice along with the device, but they knew a majority would never use it.. Nor should they have had to. Or maybe they should have had to.. But if that was the case, WHY WAS THE UI ENCOURAGING ZERO ENTROPY?! FFS. yeah.
brutal.

2026-08-01 22:24:40 UTC

Linux RNG drivers power the entire cryptographic internet (SSL, PGP, verified as best as open source humankind can do, because moneys are at stake). Coldcard dice roll scripts, power nothing of value that hasn't already been stole. That's how you know.

2026-08-01 22:09:13 UTC

- reply

linux RNG has been powering all kinds of stuff for decades, move the mouse a few centimeters, BOOM. yeah I know, I hope im not jinx'ing myself but.. the problem with stm32 and etc, their boot is soo predictable.. Any linux with a screen, mouse keyboard, possible bluetooth .. whatever.. is far superior of an entropy source with less chances to fuckup, than un-audited dice-roll drivers..
But what me know, im just a linux caveman that has actually dealt with low RNG in the past just to boot a server..

2026-08-01 22:06:39 UTC

- reply

If you're an influencor and ever sold this shit to the plebs, i expect an apology like this one .. very soon. Or you're on my fucking list of shitbags.

2026-08-01 21:57:41 UTC

- reply

I seen it before, he will escape unscathed, CFTC will shut them down and take their cut, and cousin jimbob will hook him up in 10 years with the loot.

2026-08-01 21:55:43 UTC

- reply

Like, the Linux entropy is pretty good.. Can't believe its 2026 and everyone is like inputting dice rolls into some script kiddy script on some stm32 piece of shit..Fucking wild.

2026-08-01 21:09:42 UTC

Linux has spent the last decade+ obsessing about RNG which is basically a mathmaticians nightmares. The kernel, gathers RNG from a hardware chip and from any other sources it can and combines them all with many eyes watching and improving its drivers over the years. Has blocking and non-blocking calls that have been scrutinized and even Python itself patched to use it (as of v3.6)
So I guess what I'm saying is personally, I'd trust an airgapped Linux over fumbling around with dice that someones silly device code written (when? a year ago?) has to interpret and use properly(still an unknown and verified by far less people), anyday..

2026-08-01 20:59:28 UTC

- reply

Oh shit, I read that wrong, sorry dog. Good eye 👀

2026-08-01 20:58:00 UTC

- reply

A bank just outsources their security to 1)FDIC and 2) 3rd parties. They literally don't want or need the liability. Someone else will take care of them if they get owned and they can just sue or get compensated.

2026-08-01 20:54:29 UTC

- reply

Eg. What I mean is, this is some miner on vacation somewhere and doesn't know yet and he's still mining to his coldcard.

2026-08-01 20:52:44 UTC

- reply

Probably yeah, there isn't some mailing list or alert going out, many many people still probably have no idea this compromise has happened.

2026-08-01 20:50:06 UTC

- reply

Embedded devices, micropython would make the code easier audit, test, understand and use. It's just a wrapper for C. Language doesn't matter, development practices do. Wanting different code won't help if your mainline accepts some scam code on it's critical path and scurrry off with 1000 btc .. 😭

2026-08-01 20:43:02 UTC

- reply

Whew

2026-08-01 20:30:55 UTC

Anyway, yeah I'm still in a bit of shock watching everyone get ripped off like this.

2026-08-01 20:28:19 UTC

If anyone tries to gasslight you like this "bro you should a known to roll dice". Tell em to gfy. These companies that make products if they can't generate RNG then what the hell you paying them for. If this was the case there would be NO generate seed option WITHOUT dice, but there was.
Fuckin lame ass gaslight motherfuckers IMO. And I don't even use coldcard, but in solidarity I will say, yes you got scammed and yes you should be mad. And yes, by a public figure/company, that yes should be held accountable for his companies extreme negligence. As well as anyone promoted their products or funded them. Accountability doesn't usually happen though. There really is no govmnt CFTC or anyone that will help you. But the least we can do is not listen to their bald faced gasslighting lies.
#nevent1q…eq9z

2026-08-01 20:11:43 UTC

- reply

I think its just nostr pretty quiet.. And still a lot of people using damus/primal which are hit and miss at delivering events/reading a feed. (Hint: they only use those two relays).

2026-07-31 17:32:10 UTC

- reply

disagree, their job was to generate seeds. why else would you have a hardware wallet that's airgapped?

2026-07-31 15:13:36 UTC

- reply

Sure, I asked Fable5 to audit and look for flaws in the dice generation system working from the latest commit of coldcard firmware from today @ commit f32e05792515a676fe8a9e4b83950d477ded9333 (committed one hour ago).
It did find a problem worth mentioning for sure, that even using dice with the old MK3 firmware is NOT GOOD ENOUGH depending on what you did when generating. I look to others to confirm, what fable is saying here. But it sounds like you were able to skip rolling the correct amount of rolls if you used "Add dice into the mix".
Fable5:
Verdict: the dice-assisted paths are safe — they never touch the RNG that was weak
I traced every dice entry point in the firmware and each one derives its output purely from the user's keypresses via SHA256. The patched RNG bug could not have contaminated seeds made through the pure dice flows, even on vulnerable firmware.
The four dice paths, audited
1. New master seed from dice (shared/seed.py:471, core at add_dice_rolls, seed.py:380): starts from sha256(b'') and does md.update(ch) for each keypress '1'–'6'; the final seed is md.digest() (seed.py:467). No RNG input anywhere in the path. Runs with enforce=True: a hard, non-overridable minimum of 50 rolls (12 words, ~129 bits) or 99 rolls (24 words, ~256 bits), plus a sanity check rejecting any die face above 30% frequency.
2. Ephemeral seed from dice (seed.py:586): identical derivation, pure dice. Difference: enforce is off, so a user can accept fewer than the threshold rolls after an explicit "only N bits of entropy" warning and confirmation. That's a documented UX tradeoff, not a flaw, but worth stating to the community: the ephemeral path lets you shoot yourself in the foot if you dismiss the warning.
3. Paper wallet from dice (shared/paper.py:191): private key = SHA256(rolls), enforce=True with the full 99-roll/256-bit requirement, then correctly range-checked against the secp256k1 curve order and zero (paper.py:198) before use. The key is passed into ngu.secp256k1.keypair(have_key), so no RNG-generated key is involved.
4. "Add dice into the mix" (seed.py:677): the only dice path that touches RNG output — new seed = SHA256(TRNG seed ‖ rolls). Mixing extra entropy into a hash can only strengthen the result, and post-patch the base is the hardware TRNG. The one caveat: a Mk3 user who used this path while running vulnerable firmware had a weak base seed, and no roll minimum is enforced here — those seeds inherit the RNG weakness and should be rotated, same as any plain TRNG-generated seed from that window.
Why users can independently verify this
Two properties make the pure dice paths trustless rather than trust-the-audit:
- The hash shown on screen during rolling is the same md object that becomes the seed (seed.py:411 vs seed.py:467), so the display can't diverge from what gets committed.
- docs/rolls.py (and rolls12.py for 12 words) reproduces the exact algorithm — SHA256 of the ASCII roll digits → BIP39 — on an offline computer with only Python's stdlib. I checked its BIP39 checksum math; it's correct. The test suite also pins the device behavior against CPython's hashlib with known-answer assertions (testing/test_ux.py:296, testing/test_paper.py:281).
Minor observations, none security-relevant: the random module in seed.py is used only to shuffle word-quiz decoys; the 30% distribution check is a sanity check, not a randomness test (a biased-but-under-30% die passes — inherent to dice entry, and the user is the entropy source); and after 10+ rolls the cancel key intentionally stops working so partially-entered entropy is either completed or explicitly abandoned.
Bottom line for the community: seeds created via "New Seed Words → Dice Roll" or paper-wallet dice were never dependent on the weak RNG and are safe, and anyone can confirm their own seed with rolls.py offline. Seeds generated from the TRNG on Mk3 during the vulnerable window — including TRNG seeds that had dice "mixed in" afterward — should be rotated.

2026-07-31 14:53:51 UTC

- reply

As your only inbox, prob not very good. But as an extra inbox, good. Mostly for people that are using TOR they won't have to use an exit node to send you a message..

2026-07-31 14:33:31 UTC

This RNG path is the first thing you would audit in a hardware wallet, that this wasn't found, by what I would assume would be multiple paid 3rd party auditors.. For this many years. This wreaks of an inside job. Mark kerpaples level status incoming.

2026-07-31 14:26:25 UTC

I asked Fable5 to audit seedsigner's entropy paths. I don't use seedsigner *yet* but I probably will try it out at some point. This did produce one good recommendation in hardening the code to prevent future 'mistakes' in the UI entropy gate, but, other than that, no flaws found. Seems like a decent way to accompany dice rolling or etc.
Fable5:
I'll audit SeedSigner's entropy generation and key derivation paths. Let me start by mapping out where entropy enters the system — dice rolls, coin flips, camera-based entropy, and any use of RNGs — then closely review each path.
The audit is complete. Here's my full report.
Verdict
I found no flaws that could lead to a low-entropy key in normal use. SeedSigner's design deliberately avoids trusting any onboard RNG — every seed-generation path is driven by external entropy (camera image, dice, coin flips), hashed through SHA-256, and fed to a well-reviewed BIP-39 implementation (embit 0.8.0, pinned in requirements.txt). The things I'd normally hunt for in this kind of audit — random module use in key paths, reused/aliased entropy buffers, early-exit paths that accept short input, silent truncation — all check out clean.
What I verified, path by path
Camera image entropy (tools_views.py:120-198): The final entropy is SHA256(chain) where the chain folds in the CPU serial number, time.time(), up to 50 live preview frames, and a final full-resolution photo (at ≥2× screen dimensions). Two things I specifically confirmed:
- Each preview frame is an independent copy — camera.read_video_stream(as_image=True) does frame.astype('uint8') + Image.fromarray(...) (camera.py:52), so the 50 frames aren't 50 references to one reused buffer.
- The weak inputs (serial number, wall time) are only ever added to the hash chain; hashing extra low-entropy data can't reduce the entropy contributed by the image itself.
Dice rolls (mnemonic_generation.py:64-81): 50 rolls for 12 words (~129 bits, ≥128 ✓) or 99 rolls for 24 words (~256 bits ✓), hashed as an ASCII string via SHA-256 — the iancoleman.io "Base 10" approach. The entry keyboard only offers digits 1–6, backspace is handled correctly, and the screen returns only when exactly return_after_n_chars characters are entered (screen.py:1289). I checked the one early-return path in KeyboardScreen (the save button at screen.py:1237) — it's gated behind show_save_button, which the dice and coin-flip screens never enable, so you cannot submit fewer rolls than required.
Coin flips: Same structure, exactly 128/256 flips enforced, charset limited to "0"/"1". Sound.
Final-word calculation: Contributes only 7 bits (12-word) or 3 bits (24-word) plus checksum — but that's the correct math for this feature, and the UI states it explicitly. The "finalize with zeros" option is a deliberate, labeled choice.
Key derivation (models/seed.py): Straight bip39.mnemonic_to_seed (PBKDF2-HMAC-SHA512, standard) with NFKD normalization. The Electrum variant uses the spec's 2048 rounds. No custom crypto.
PRNG usage: The only uses of Python's non-cryptographic random are the screensaver animation, the backup-quiz decoy words (seed_views.py:1284-1289 — doesn't touch key material; the random.seed() call there is screenshot-generator-only), and the CLI tool's demo mode, which prints "This is a demo seed. Do not use it to store funds!!!". No os.urandom or PRNG anywhere in a key-generation path.
Test coverage: tests/test_mnemonic_generation.py pins fixed vectors cross-checked against iancoleman.io and Coldcard's published dice-roll verification sample, so any regression in the entropy→mnemonic math would fail CI.
Minor findings (none are exploitable in normal use)
1. No length validation in generate_mnemonic_from_dice / generate_mnemonic_from_coin_flips (mnemonic_generation.py:64, 85). Any input that isn't exactly 50 chars silently produces a 24-word mnemonic — e.g. 10 dice rolls would yield a 24-word seed with only ~26 bits of entropy. Today the UI makes this unreachable, but it's a single-layer defense; a future caller or a UI refactor could regress it silently. An assert len(...) in [50, 99] (with an escape hatch for the Coldcard 6-roll verification vector, which currently relies on this leniency) would be cheap defense-in-depth.
2. No degenerate-image check on camera entropy. If the sensor ever returned truly constant frames (fully dead sensor still returning data), the remaining entropy would be roughly just time.time() — guessable. In practice a disconnected camera raises CameraConnectionError, and even a lens-capped sensor produces thermal noise, so this is theoretical — but a cheap "image variance too low, reshoot" warning would close it.
3. Cosmetic off-by-one: bip39.WORDLIST[int(random.random() * 2047)] at seed_views.py:1284-1286 can never pick the last word ("zoo") as a quiz decoy. Should be random.randrange(2048). No security impact.
Practical guidance
The strongest guarantee this codebase offers is verifiability: for dice or coin-flip generation you can independently reproduce the mnemonic from your recorded rolls via tools/mnemonic.py or iancoleman.io/bip39 ("Base 10"/"Binary" mode), which removes the need to trust the device's code at all. If maximum assurance matters to you, dice generation with external verification is the path I'd use; camera entropy is also sound but is inherently harder to audit after the fact.

2026-07-31 05:29:58 UTC

- reply

Woah

2026-07-30 17:53:32 UTC

- reply

who doesn't enjoy a 'lil malware on your pc' 😂
but ya, VLC is goat

2026-07-30 17:48:59 UTC

funny, image search for "newlay" shows.. it's some kind of concrete. 😂 I only picked that name, for internal reasons then just ended up calling it that. It was kinda like, "this is a new relay, newlay".
I welcome name change suggestions, I don't even have an icon yet really..

2026-07-30 17:00:50 UTC

- reply

I forked it to remove non-nostr onboarding flow and I'm also running a buzz (relay) and working on a drop-in replacement for the buzz relay written in kotlin. Come by the dev channel if you're interested.
https://buzz.relay.tools/invite/v2.qHsAp_wm31FiSn07n16yt07in4nvldB2aOXFjJASuKQ

2026-07-30 16:17:35 UTC

- reply

cc @npub1kgh…kuut ^^

2026-07-30 16:17:13 UTC

Newlay v0.3.5 released!
Android Changes:
Supports un-interrupted running in the background.
Supports start on boot.
Other Changes:
FULL BUZZ COMPATIBILITY! Drop-in replacement for a Buzz relay with (mostly) all of the bells and whistles. Git repos, http endpoints, etc. #buzz #buzzfork
https://code.relay.tools/opensauce/newlay/
https://zapstore.dev/apps/tools.relay.newlay.android
https://cloud.blossom.band/88a39fd580eb58de1c26fdaa8a966ae85132de9b77f86bba46686dc1f217684c.png

2026-07-30 15:06:30 UTC

- reply

genius. will start saying this

2026-07-29 21:07:32 UTC

- reply

I think, I use the thinkpad nub, ~< repeat

2026-07-29 21:06:26 UTC

- reply

Jus gonna chill here and be a dock blob

2026-07-29 21:05:40 UTC

- reply

Sooooo jiggly. Damn autocorrect 🎷

2026-07-29 21:04:46 UTC

- reply

solo jiggly

2026-07-29 21:03:48 UTC

- reply

This don't look like any keyboard I ever seen 😘

2026-07-29 20:57:04 UTC

- reply

uh wot mate? 🤔🤓

2026-07-29 20:43:49 UTC

whoops, thought this was my dock.. off'ser
#nevent1q…nn0e

2026-07-29 20:43:07 UTC

- reply

http://newlay.relay.tools/6c5ffe505675cd050881b45e7374a08305927eb557f432b76441aefc0ade13a8.png

2026-07-29 20:42:29 UTC

chu looking at Willis? @npub1ymt…pxnz #memethrowbacks

2026-07-29 20:41:07 UTC

#taco
http://newlay.relay.tools/b4bad021cb6d5b4cc7c3e37900951eb49c3ec859266437a03037b2e5978c3439.jpg

2026-07-29 20:36:25 UTC

- reply

get back to me when it's a faded shirt I can take SRS ✅😂

2026-07-29 20:28:58 UTC

- reply

cheers 🔱

2026-07-29 18:42:46 UTC

- reply

Oo, 64 not bad eh? 😂

2026-07-29 18:28:28 UTC

- reply

I have to scroll for an hour just to see my fav tab: relays

2026-07-29 18:26:59 UTC

- reply

Itz ALOT 😂

2026-07-29 17:44:33 UTC

- reply

Not true, sometimes they convince me to do something that ends up sucks 🌶😂

2026-07-29 16:24:52 UTC

- reply

not even a prod condom lol, more like, .. an un-used condom in the drawer just-in-case.. 😅

2026-07-29 16:22:21 UTC

- reply

we all know you will keep running it 😂 but yeah it's a test for sure, of your conviction'es eyy? ❤

2026-07-29 15:41:39 UTC

- reply

here you go ser
https://buzz.relay.tools/invite/v2.M9jEUgI81tzXkknPtex6gBEROGgEmgNvu-aNIjTjk7Q

2026-07-29 15:39:16 UTC

- reply

True, it could be just some android app/settings need to be set.. It doesn't do the automatic style "would you like to set" stuff yet. But I'm going to look into it also.. Make it do it like citrine does.

2026-07-29 15:36:47 UTC

- reply

I'll send u an invite to my buzz server where I'm working on buzz and other things shortly, so you won't have to install the server yet just to see it. My fork on desktop removes all non-nostr on boarding friction, just have it generate a new nsec for research purposes..

2026-07-29 15:29:38 UTC

- reply

seems like it 🦾

2026-07-29 15:21:42 UTC

More thoughts on buzz from the frontline.
https://image.nostr.build/06496db8172cc3d70918c919f9e7e80e9480729454ed3a2861fe7cfd2c4b5360.png
I've been diving deep into buzz internals, and running a fork of it at https://code.relay.tools/forks/buzz
The idea was to see how close it is to Nostr Native, and the surprising answer is, VERY. I am impressed with how much nostr was used to build this thing.
Buzz is also VERY buggy. In ways that you may not notice, until you have used it for a few days or a week. At some point, I almost grew exhausted of it because of this, I was like, mmmmm, did I just get suckered into yet another dev project going nowhere? But then, I came back and said, THIS IS KINDOF INCREDIBLE. THIS IS NOSTR.
Every day, I check the new commits and when I encounter bugs I check the issues, and watch them being fixed in real-time by agentic workflows that have been setup by block, or I fix them myself. Overall, this experience is cool because I get to see how block thinks development works these days with AI. I think it is working! PRs are being merged, commits are flowing, bugs being squashed in a timely manner, roadmaps fleshing out etc.
Buzz has self-hosted Git repos, issues, PRs, and even Workflows, all BUILT-IN to it's relay service. This is wild, because it means you need no extra service to host these things, you just need a Buzz server and you and your friends, and all of your agents combined, can ride off and code some stuff. This part gets me really excited, because NOTHING else was doing this. And it uses Nostr Native patterns.
So, that's just a 'quick' update for you on the buzz hypetrain. AMA, I'll be releasing some more stuff soon.

2026-07-29 14:47:14 UTC

- reply

Cool, yeah it makes sense, I'll add it for the next release.

2026-07-29 14:28:07 UTC

- reply

Yep! It does. I didn't add wake lock to it. It will sync when it starts up using negentropy tho. Should I make it stay on better, maybe an option to do so? You are the first I've heard trying the android (besides me of course hehe)

2026-07-27 20:03:40 UTC

- reply

Are you Buzzin' yet?