⚡ Dee Kay ⚡

Amethyst contributor... LCe owner.

We are a small photography business based in Scotland. Early adopters of all things fine.

New project launched, get all your presents... Clutches, earrings, cushions or custom upcycled fashion from old loved items!!

Lightning/btc accepted and preferred (10% discount)

https://houseofeff.com/shop

Public Key

npub1e2yuky03caw4ke3zy68lg0fz3r4gkt94hx4fjmlelacyljgyk79svn3eef

NIP-05 Address

houseofeff.com

Profile Code

nprofile1qqsv4zwtz8cuwh2mvc3zdrl5853g365t9j6mn25edlul7uz0eyzt0zcpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dshvqmt2

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub1e2yuky03caw4ke3zy68lg0fz3r4gkt94hx4fjmlelacyljgyk79svn3eef

Show more details

Published at

2026-09-02T14:59:27Z

Kind type

0 Metadata

Event JSON

{ "id": "928f23a975c0b5a35f30c2732ba6e26ca875b4e67913e80d571ad416df9cdeeb", "pubkey": "ca89cb11f1c75d5b6622268ff43d2288ea8b2cb5b9aa996ff9ff704fc904b78b", "created_at": 1788361167, "kind": 0, "tags": [ [ "alt", "User profile for ⚡ Dee Kay ⚡" ], [ "name", "⚡ Dee Kay ⚡" ], [ "display_name", "⚡ Dee Kay ⚡" ], [ "picture", "https://i.nostr.build/CYa5jCPPy5WfL82g.jpg" ], [ "banner", "https://fertschnigfotography.com/wp-content/uploads/2023/05/banner.gif" ], [ "website", "https://houseofeff.com" ], [ "about", "Amethyst contributor... LCe owner. \n\nWe are a small photography business based in Scotland. Early adopters of all things fine.\n\nNew project launched, get all your presents... Clutches, earrings, cushions or custom upcycled fashion from old loved items!! \n\nLightning/btc accepted and preferred (10% discount) \n\nhttps://houseofeff.com/shop" ], [ "nip05", "_@houseofeff.com" ], [ "lud16", "deekay@zap.houseofeff.com" ], [ "client", "Amethyst" ] ], "content": "{\"name\":\"⚡ Dee Kay ⚡\",\"username\":\"deekay\",\"display_name\":\"⚡ Dee Kay ⚡\",\"displayName\":\"⚡ Dee Kay ⚡🇸🇪🇬🇧🇨🇿🇧🇷🇦🇹\",\"picture\":\"https://i.nostr.build/CYa5jCPPy5WfL82g.jpg\",\"banner\":\"https://fertschnigfotography.com/wp-content/uploads/2023/05/banner.gif\",\"website\":\"https://houseofeff.com\",\"about\":\"Amethyst contributor... LCe owner. \\n\\nWe are a small photography business based in Scotland. Early adopters of all things fine.\\n\\nNew project launched, get all your presents... Clutches, earrings, cushions or custom upcycled fashion from old loved items!! \\n\\nLightning/btc accepted and preferred (10% discount) \\n\\nhttps://houseofeff.com/shop\",\"nip05\":\"_@houseofeff.com\",\"lud16\":\"deekay@zap.houseofeff.com\"}", "sig": "d070c2fb0fe57b2af292d3be301ae4123913cf9dceae1ffbde18e153618c29a3e7cf2109ba25363428ebb16f8dca9165bc6b152feb37e107ad56807db6b121f9" }

Last Notes

2026-09-13 08:18:09 UTC

- reply

Audio book. Whole different experience. Dark room, night, closed eyes, your bed.

2026-09-13 07:31:58 UTC

- reply

This. 😭

2026-09-12 06:15:29 UTC

- reply

Double click the zap icon...

2026-09-10 14:44:03 UTC

- reply

Try it and let me know! Receive only is the secure default....

2026-09-10 06:29:01 UTC

Now added running outside umbrel as well...
Everything you need is on main now: a plain Docker Compose template under deploy/ and a step-by-step procedure in DEPLOYING.md, section "Running outside Umbrel". It runs the published 0.1.20 images against an LND on the same host, either in Docker beside it or on the host itself, and nothing is built locally. Version 0.1.21 will add better admin password management.
#nevent1q…k27t

2026-09-09 10:20:32 UTC

- reply

the nostr primitives currently come from my own fork of go-nostr with a few protocol enhancements, since upstream is archived. The future plan is to own the protocol and depend only on the secp256k1 curve library.

2026-09-09 10:18:04 UTC

- reply

Relays are transport, not trust. The app mints its own nostr key on first run and it never leaves the box; NWC responses are NIP-44 (or NIP-04 for older wallets) encrypted to the pairing key, so a relay only ever carries signed, encrypted payloads it cannot read or forge.

2026-09-09 09:29:59 UTC

I've built something: self custody zap and nwc wallet for #umbrel owners running their own #lightning node.
Focus on security and no external dependencies.
Looking for beta testers!
#nevent1q…3qam

2026-09-07 09:50:01 UTC

- reply

Reminds me of mtgox drain?

2026-09-03 16:47:36 UTC

- reply

Turning on spending or raising the hard cap requires an operator round trip via file system.. The app cannot turn on spending or raise limits from within app.

2026-09-03 16:35:46 UTC

- reply

Both...
Per-pairing budget: applies to one wallet app. Enforced by the server. Soft.
Wallet ceiling: applies across all apps on the instance. Enforced by the server. Soft.
Guard caps: apply to every app on the instance. Enforced inside the node's RPC path by a separate container the server cannot influence. Hard.

2026-09-03 14:12:43 UTC

- reply

No escape hatch:
An update has been posted
An exhaustive list of affected models: Mythos/Fable 5.1, Mythos/Fable 5, Opus 5, Opus 4.8, Opus 4.6.
Haiku ftw!

2026-09-03 13:54:56 UTC

Run your own zap receiver and NWC sender. Nostr-native, self-custodied, no third-party LNURL service in the loop.
https://cdn.nostrcheck.me/7926fd36f8687dc87fdfdd8d839f749918f3c4dcb011699aa03d8668c101722c.jpeg
⚡ BrollyZapper now has its own Umbrel Community App Store for easy installing
BrollyZapper: a self-hosted LNURL-pay / zap receiver and NWC sender can now be installed on any Umbrel node straight from a community app store.
Store: https://github.com/davotoula/brollyzapper-umbrel-store
To add it: Umbrel → App Store → ⋯ → Community App Stores → paste the repo URL.
Optimised for Amethyst: full transaction history rendering via NWC-05 and NWC-06.
Protocol coverage: NIP-01 underneath it all, NIP-57 (zaps), NIP-47 (wallet connect), NIP-04 + NIP-44 (encryption), NIP-19 (bech32 keys), NIP-42 (relay auth), plus LUD-06 and LUD-16 on the LNURL side.
Verified end-to-end: fresh anonymous shallow clone over HTTPS (the same way umbreld fetches it) matches the built store exactly. Two containers under the hood: a spend-capped guard holding the only LND macaroon, and a server that never touches your node's admin credentials.
#nostr #lightning #umbrel #selfhosted

2026-09-02 15:59:15 UTC

- reply

A close without a crash report can also be android shutting it to recover system memory.
Have your tried starting amethyst right after a phone restart and see if it behaves better?
Do you have a lot of system apps running in background?

2026-08-31 12:57:06 UTC

This fixes @nprofile…595x transactions history in #amethyst 🕺
https://github.com/vitorpamplona/amethyst/pull/4022

2026-08-30 16:36:26 UTC

- reply

I raised a wallet bug for you: https://github.com/PrimalHQ/primal-server/issues/19

2026-08-30 16:34:55 UTC

- reply

Just keep swimming

2026-08-30 04:35:23 UTC

- reply

Doesn't Graphene os come with a Google play sandbox? It doesn't support Play Integrity (so doesn't support many bank apps, Google pay etc)

2026-08-30 04:16:12 UTC

- reply

What are you trying to do?
Samsung has some protected area where second independent version of a play store app can be installed.
Google pixel calls it private space, also allows installing second independent version of an app. I'm using it to run a secondary Claude account from mobile...

2026-08-29 19:00:52 UTC

- reply

Verdade

2026-08-29 18:59:59 UTC

- reply

This is great insight. I still don't get it why a tiny payment needs a longer route. Liquidity is always a cost and massive payments are difficult to find a route for.

2026-08-29 18:34:16 UTC

"One thing to flag, unrelated to the feature: that zap paid 2,016 msat in fees on a 5,000 msat payment — 40%. Not a fault, just what routing a 5-sat payment costs; the 28-sat one cost 16 msat."
Now you know 😂
#zap #lightning

2026-08-29 08:23:52 UTC

- reply

Brilliant!

2026-08-28 22:57:20 UTC

- reply

New feature! You can customise your menu (and bottom bar) to only the features you use!
No need to create a simpler client ♥️♥️

2026-08-28 15:26:58 UTC

- reply

Workaround for #primal implemented until they fix their double encoding bug.

2026-08-27 19:04:23 UTC

- reply

This is really really imersive!

2026-08-27 17:36:13 UTC

- reply

What stack did you build you own wallet with?

2026-08-27 16:31:29 UTC

- reply

I see! You are using Web client? Good catch, I was using primal Android app. Aye, cord is a pain on Web

2026-08-27 08:55:30 UTC

- reply

Why not LND?

2026-08-26 19:35:01 UTC

- reply

I tried zapping from primal internal wallet (to myself). It worked

2026-08-26 14:48:22 UTC

Delivery from #berlin
https://blossom.primal.net/ea6610a8ca3bf85f3d6869da39cf817de55df0623309cd61a44874af13969c7b.jpg

2026-08-26 07:23:58 UTC

- reply

This one used to be goat but has been abandoned... I still use it.
https://play.google.com/store/apps/details?id=com.sonelli.juicessh

2026-08-26 07:21:57 UTC

- reply

I like this one https://play.google.com/store/apps/details?id=com.termoneplus

2026-08-24 15:48:27 UTC

- reply

That works since muted words also parse profile

2026-08-24 15:13:00 UTC

- reply

#amethyst, add to muted words: imad in gaza

2026-08-24 14:43:59 UTC

- reply

Having lived in London for a long time, and seeing these crooks operate freely on busy streets, targeting mothers with prams and the elderly... This gives me great pleasure seeing...

2026-08-24 06:41:56 UTC

- reply

Fyi
https://blossom.primal.net/6a7a7e6ba65ad4ee2a02521c8674a3d3b6fd6e07f006c8ca4d11d1ea0f016fd1.jpg

2026-08-22 05:56:59 UTC

- reply

How is it different from bitchat?

2026-08-21 17:31:49 UTC

- reply

Different...
https://nostr.download/0767d62142e7c364bcf57e73351111bab393b60c9ea8d9f4a0327b31c9d7b348.jpg

2026-08-21 15:38:58 UTC

- reply

Getting a lot of these:
https://nostr.download/ff92a8a5b6d81a8d007053ee2d0f54b10c964d4063feca0bc479bc28ed5e1b8d.jpg
When it works it's lovely. There is beauty in simplicity!
Deep linking works on android #amethyst (when the note is in cache)

2026-08-21 07:16:55 UTC

Thoroughly enjoyed the math in the beginning... The Claude solution approach starts at 57m40s.
https://www.youtube.com/watch?v=C-ECTnM7tUY&t=57m40s
#ai #math #Claude

2026-08-20 17:23:18 UTC

- reply

This time it will work... 🤞

2026-08-20 16:19:57 UTC

- reply

How have you kept your 100k long positions alive!

2026-08-19 09:09:19 UTC

- reply

The ONLY way not to lose users' private data is by not having it in the first place...

2026-08-18 06:14:03 UTC

- reply

Do you have a big backlog? Epics, stories, epics place holders?
I've started using Beads and the graph workflow is fantastic for staying on track...
https://beads.gascity.com/getting-started/quickstart

2026-08-18 06:10:58 UTC

- reply

Just watch out for leaking session urls. I find Claude is very keen adding session urls to commits...

2026-08-14 13:05:07 UTC

- reply

True. Use muted words in security settings

2026-08-14 12:54:25 UTC

- reply

Report and block... Then it's hidden for rest of your followers (on #amethyst)

2026-08-13 06:56:31 UTC

- reply

"650 different ideas for solving the problem, coordinating across 60 subagents and spending 31 million output tokens in total"
$1,500 ish...

2026-08-11 19:27:08 UTC

Translations. Plurals conventions in different languages. Not fun.
Did you know that in Czech 2-4 has a different ending than 5 and more?
Did you know that in Portuguese million is plural for more than one but singular for parts of a million (eg 1.5 million). But I think we ignore that in #amethyst...

2026-08-11 13:18:03 UTC

- reply

Fair, I phrased it badly — I wasn't asking why the share isn't in the channel, that's chicken-and-egg and gift wrap is the only option. I was asking about the consequence: since shares only ever go point-to-point, no member can see the roster. Anyone can grant the root to anyone, permanently, and the rest of the team gets no signal.
The performance scaling is there but how does the trust scale? I can see it working for a tight team of 5...but a loose team of 50?

2026-08-11 05:40:12 UTC

- reply

Is this meant for a tight team of knwon members since key-shares go direct to the newcomer and never touch the channel?

2026-08-10 19:16:22 UTC

- reply

September 1st could get messy

2026-08-10 12:04:45 UTC

- reply

Ffs

2026-08-10 12:03:53 UTC

I know that a sesison can spin up sub agents with fresh context.. But I still prefer independent terminals for extra separation.
This used to require copying requests and feedbacks between terminals.. Until now..
Claude sessions can now talk to each other. So you don't have to copy paste between them, they just chat directly.
It's crazy seeing the conversations back and forward in real time 😂
One session project manager talking to 2 different implementers.. Each implementer talking to their own reviewer.
Over engineered? Perhaps. Fun? Definitely!
#Claude #ai

2026-08-09 11:02:01 UTC

Bored on #nostr? Check the Global conversations... much better signal than the global feed itself...
#amethyst

2026-08-09 06:47:48 UTC

- reply

https://nostr.download/54fbae836ff03cf7d01922ef72f48840a4088bac5b314250b85ea306b6ea8561.jpg

2026-08-08 18:00:56 UTC

- reply

If I share i zap 😂

2026-08-08 08:21:58 UTC

- reply

Oh no, latex formatting kicked in.
I think your instructions state to delete *.macaroons
An extra s

2026-08-08 08:07:13 UTC

- reply

Careful with this one — the root key isn't derived from the wallet seed. Per lnd/macaroons/README.md, it's "32 bytes of pseudo-random data" generated when none exists, stored in macaroons.db and encrypted with your wallet passphrase. The passphrase protects the key, it doesn't derive it.
LND also doesn't regenerate macaroons on restart — it only bakes the defaults when they're missing (lnd#7566). On my box the macaroon files were still dated Dec 2021 after 4½ years of restarts, an LND upgrade and an OS migration.
This matters because "restart regenerates them" implies a plain restart rotates your credentials. It doesn't — you'd walk away thinking you were safe while a stolen admin macaroon is still valid. Deleting macaroons.db is what forces a new random root key, and that's the whole point of the procedure. The old files are invalidated, but by deleting the db, not by restarting.
On BTCPay: with stock Umbrel wiring (macaroonfilepath=...), it re-reads the new file on restart — no re-linking needed. Mine reconnected with zero auth errors. You'd only need to re-link if you pasted the macaroon as hex, or you're connecting a remote BTCPay over Tor/LNC.

2026-08-08 07:56:44 UTC

- reply

As written you delete macaroons.db and leave all 8 macaroon files in place. LND then generates a fresh root key but will not regenerate those files — it only bakes the defaults when they're absent (see lnd discussion #7566). You end up with 8 macaroons signed by a dead key: every app fails auth, and nothing regenerates until you go back and delete them properly. Fix:
rm -f "$M"/*.macaroon "$M"/macaroons.db "$M"/macaroons.db.last-compacted

2026-08-08 06:23:07 UTC

- reply

Btcpay Server is next.

2026-08-08 06:01:34 UTC

- reply

Website down.. Dns issue?

2026-08-07 08:26:20 UTC

- reply

What do you predict about the looming bip110 storm?

2026-08-07 06:40:57 UTC

- reply

Last time I checked (2 years ago?) primal Web didn't verify nip05, it just showed all as verified 🤔

2026-08-07 05:50:18 UTC

- reply

EU will soon mandate cameras in all new cars. Not a joke..

2026-08-07 05:37:44 UTC

- reply

Odd.. That one is missing from my catalogue. Was it controversial? 😂😂

2026-08-06 08:15:45 UTC

- reply

Which episode?

2026-08-06 07:50:38 UTC

- reply

He ded.

2026-08-05 15:04:27 UTC

- reply

GM and bitcoin? 😂
Seriously, muted words match on user profiles as well and probably lightning address / nip05.
So alby or Damus will mute a lot of people!

2026-08-04 06:22:47 UTC

- reply

Update? Gotta save those memes! 🙏

2026-08-02 08:32:35 UTC

- reply

Do you have a spare computer? The m2 is probably completely fine.. Just needs adapter to connect to another computer? Drag and drop the data you need 😂

2026-08-02 08:05:15 UTC

- reply

Location: the black rectangular module directly to the right of the two RAM sticks (center of the board), wrapped in a black protective/thermal film with a sticker on it. That's the M.2 slot with the SSD in it. The film peels off — it's just a heat spreader/insulator, not glue.

2026-08-02 08:04:33 UTC

- reply

The ssd is a standard m2 stick 👍
To remove it:
Disconnect the battery connector first (always, before touching anything).
Remove the single Phillips screw at the far end of the M.2 stick.
The drive pops up at ~20° — pull it out of the slot.

2026-08-02 07:16:49 UTC

- reply

I see, so not a problem with ssd but with laptop. Ouch.
Have you opened the laptop? Maybe you can connect an ssd adapter to the ssd from external device?
What laptop is it exactly?

2026-08-02 06:27:55 UTC

- reply

Integrated you mean glued in? Otherwise take out ssd and connect via dock to another computer.
Option two: there are dedicated disk repair os that you boot from USB and can attempt to repair.

2026-08-02 06:24:47 UTC

- reply

Would cursor have downgraded the model due to "security related work"?

2026-07-31 08:16:44 UTC

- reply

Mk3 won't be fixed 😱

2026-07-31 07:57:41 UTC

- reply

Did you just post their seed? 😂😂

2026-07-30 15:42:31 UTC

- reply

Not really, failed htlcs incurred no costs.
You can be more aggressive in deleting but then you start deleting p&l data.
I also turned on aggressive graph pruning. It will remove from graph already on one empty edge rather than two.
This might remove genuine paths with flaky nodes but they will pop back again when active.
For a routing node with many nodes this was a fair optimisation for me IMHO.

2026-07-30 08:37:17 UTC

Running a routing node? Don't forget to delete failed payments regularly:
lncli deletepayments --all --failed_htlcs_only
Or if in docker:
docker exec lightning_lnd_1 lncli deletepayments --all --failed_htlcs_only
My channel.db compacted from 4.43 GB to 1.54 GB.
Full recovery went from 20 minutes to 60 seconds.
#umbrel #lightning

2026-07-29 19:41:49 UTC

- reply

Rock of Cashel 👍

2026-07-29 17:22:30 UTC

Good bot.
https://blossom.primal.net/2ba10eec51e0db943a33b3787b31180b0043098b0d1cbda2dba2700bd7534c27.jpg
#umbrel #lightning

2026-07-29 15:57:17 UTC

- reply

Damn

2026-07-29 12:42:07 UTC

- reply

Isn't it always? 😂😂

2026-07-29 10:56:46 UTC

- reply

No, Google play version is always a bit behind. Github is always the newest.

2026-07-29 09:45:49 UTC

- reply

Apple iPhone Version is not ready yet. Only android and desktop.

2026-07-29 08:40:32 UTC

- reply

Exactly... Different from Chronos which is just regular time...

2026-07-29 08:37:08 UTC

- reply

Github, Obtanium, zapstore or Google play. I recommend Obtanium and github url:
https://github.com/vitorpamplona/amethyst

2026-07-28 21:26:55 UTC

- reply

https://blossom.primal.net/f9b67bfd73af8ef9f6d2bdb19b056629cb5adb9833489ec7f388c7e6c326e7a6.jpg

2026-07-28 20:14:16 UTC

- reply

https://npub1e2yuky03caw4ke3zy68lg0fz3r4gkt94hx4fjmlelacyljgyk79svn3eef.blossom.band/4ec800a17c0f1797d71abfa541c8acaf9f8f59f7a72d025276107f3dffcf205a.jpg

2026-07-28 14:31:51 UTC

- reply

New item in the menu? Indian salad?

2026-07-28 08:30:12 UTC

- reply

App event doesn't render in #amethyst. From my clonker to your clonker:
1. Use naddr, not nevent, for a kind-32267 event. This is the big one. Kind 32267 is parameterized-replaceable, so naddr is the correct NIP-19 form — and per NIP-19 an naddr must carry the d identifier, author (TLV 2) and kind (TLV 3), whereas for nevent all three are optional and were omitted here. That means naddr gives every client a query relays actually answer ({"kinds":[32267],"authors":[…],"#d":["eu.imwald.android"]}), instead of an ids query many relays won't serve for replaceable events.
2. The current link will break permanently on the next release. An nevent pins one version. When they publish the next 32267 for eu.imwald.android, relays replace the old one and 7b47134a… becomes unresolvable everywhere — the announcement's embed dies for good. An older version (9acb338a…, from ~4 days earlier) is still floating around on some relays, which shows this is already in motion. naddr always resolves to the latest version, so the announcement keeps working and even picks up the new version automatically.

2026-07-27 10:47:58 UTC

- reply

Google play version has built in notifications. They have been recently enhanced to stay always on.
Fdroid version doesn't have any built in notifications so would need pokey.
Pokey might have additional notification features that #amethyst doesn't have.

2026-07-25 12:25:24 UTC

- reply

It's the best. Zero sugars, sweeteners, artifical flavours/colours.

2026-07-24 13:17:34 UTC

- reply

Stop rubbing it in! 😂😂

2026-07-24 10:29:06 UTC

- reply

10 million tokens later 😱😱😱

2026-07-24 10:25:08 UTC

- reply

Synchroncity.. I was watching people boarding a zadar flight yesterday morning and I was jelaous!

2026-07-23 19:32:19 UTC

Your DMs now warn you when the sender has been reported by people you follow.
https://nostr.download/824dbd16a78a9b7696886d9ea9682d8241a29c67d0cc3eb2e180a21af8539043.jpg https://nostr.download/45111eecd0e8d6a8b8453e13ba893e3569663025d1d885b8c5a58372ed9f7b10.jpg https://nostr.download/6ccc8c91d62392e5a726625091e2e6fd36a048ba2b3da67b1643b7adb4c42c20.jpg
It flags the account before you open the message, shows how many of your follows reported it and why, and names them.
Web of trust moderation finally doing something useful in your inbox.
#amethyst

2026-07-23 06:28:45 UTC

- reply

https://nostr.download/a8b2faf3782618cc0b248b45f2c9b84cfd0826fe4dd182dadd98c04c46c84e4f.jpg