lukechilds
Luke Childs ☂️

https://lu.ke

Cofounder & CTO Umbrel.

Previously BitcoinJS, Browserify.

Public Key

npub1htnhsay5dmq3r72tukdw72pduzfdcja0yylcajuvnc2uklkhxp8qnz3qac

NIP-05 Address

_@lu.ke

NIP-57 Address

alby@lu.ke

Profile Code

nprofile1qqst4emcwj2xasg3l997txh09qk7pykufwhjz0uwewxfu9wt0mtnqnspyfmhxw309a6k6cnjv4kzuarpd9krqvtp8qerztn5wvhxuet58g6rsdpcqyg8wue69uhh2mtzwfjkcw358q6rsen72gr

Publishing to

umbrel.tail01a821.ts.net:4848

umbrel:4848

nos.lol

Author Public Key

npub1htnhsay5dmq3r72tukdw72pduzfdcja0yylcajuvnc2uklkhxp8qnz3qac

Show more details

Last Notes

2024-12-02 07:59:14

- reply

musig leaks nothing about the contract on chain and is more block space efficient.
Using the script path for unilateral exit leaks the fact you were most likely using a Spillman channel to any observers. It’s also much larger.
Maybe simpler backups are more important to people than privacy and block space. And if that’s the case my proposal also works with the script path variant.

2024-12-02 04:01:53

- reply

There are a few different ways to do Spillman channels, the way I propose requires holding onto a presigned transaction for unilateral exit. This is only needed if the mint is uncooperative. This is non deterministic so you need to store it alongside your seed. However unlike lightning if you lose it the mint can’t cheat you out of any money by settling a bad state.
You can make the users unilateral exit path deterministic by implementing it as a timelocked script path instead of a timelocked presigned transaction. Then you only need your seed and nothing else to unilaterally exit.
However I like the presigned tx model better since it results in everything being a musig spend.

2023-08-16 16:24:30

The new LlamaGPT self-hosted Al app on @npub1agh…mhct is uncensored, just saying...
#note1c0y…ss92 https://cdn.nostr.build/i/be01663709561ebc630c562175a23ed5aad3e8c32bae435a06b793e31008f69e.jpg

2023-08-08 06:49:05

- reply

GPT-4 is very capable, the resulting bash scripts work well about 95% of the time. However there are often subtle bugs or edge cases that aren’t handled unless you explicitly tell it to look out for them.
After a few iterations of adding extra details to handle edge cases you can get something very high quality.
Results are much worse on open source LLMs but they’re catching up quickly.

2023-08-07 17:43:22

- reply

Not if you run it on your host but you can also run it in a Docker sandbox so you can just mount in directories that you want it to have access to.

2023-08-07 13:11:29

- reply

You can run it in a sandbox with Docker, also note the disclaimer.
https://void.cat/d/HSFLrikz6MdYqWmRuXVqkD.webp

2023-08-07 13:10:21

- reply

I got you fam

2023-08-07 12:43:44

humanscript is an inferpreter. A script interpreter that infers commands from natural language using AI. There is no predefined syntax, humanscripts just say what they want to happen, and when you execute them, it happens.
https://github.com/lukechilds/humanscript
This is a humanscript called tidy-screenshots. It takes an unorganised directory of screenshots and organises them into directories based on the month the screenshot was taken.
It can be executed like any other script.
https://void.cat/d/Rf3GkVQbCtg6NSfzUndkou.webp
The LLM inferpreted the humanscript into the following bash script at runtime.
https://void.cat/d/Br86EpyZev12HtsxtYka3i.webp
The code is streamed out of the LLM during inferpretation and executed line by line so execution is not blocked waiting for inference to finish. The generated code is cached on first run and will be executed instantly on subsequent runs, bypassing the need for reinferpretation.
https://void.cat/d/CCLBU6ZNWq5bXnioMGkkcB.webp
The humanscript inferpreter supports a wide range of LLM backends. It can be used with cloud hosted LLMs like OpenAI's GTP-3.5 and GPT-4 or locally running open source LLMs like Llama 2.
You can run humanscript in a sandboxed Docker environment with a single command if you want to have a play.
https://github.com/lukechilds/humanscript#install-humanscript

2023-06-24 01:50:49

- reply

It’s actually valid semver during 0.x.x releases. https://semver.org/#spec-item-4
Technically according to spec you can do anything during 0.x.x releases but it’s common convention to push the meanings across one place so:
- 0.5.3 > 0.6.0 = major bump
- 0.5.3 > 0.5.4 = minor bump
- No way to define a patch bump
This is the convention we’ve been following since initial launch of 0.1.0.

2023-05-30 20:51:41

- reply

Yes! Raspberry Pi and custom servers are still supported platforms for Umbrel.

2023-05-30 19:01:27

- reply

haha sorry had my head down pre-launch

2023-05-30 14:49:08

- reply

ty sur

2023-05-30 14:47:35

- reply

It idles around 5W and bursts to about 15W.
Strip our payment processor don’t support Bitcoin out of the box but we’re working on adding Bitcoin as a second payment method!

2023-04-24 06:12:58

- reply

It was a really great episode my man, thoroughly enjoyed it!

2023-02-28 19:05:29

- reply

Thanks for the tip but I’m using https://carrd.co which doesn’t support proxying. I’ll run a proxy to it on my dedicated server and add in the nostr.json file there.

2023-02-28 19:03:28

- reply

Hmmn yeah I get that but aren’t you doing the opposite here?
HTTP spec already states how 301/307 should be handled. NIP-05 rules are saying do a lookup how HTTP says but don’t follow the redirect how HTTP says.
So if an app is requesting some HTTP resource and a NIP-05 JSON file it has to follow two different sets of rules to resolve both those resources instead of just following the HTTP spec.

2023-02-27 23:50:10

- reply

Awww man that sucks, that redirect massively simplifies my server setup. Thanks for the heads up though.
#[3] what is the security issue with redirects? Couldn’t anything bad done by a redirect also be done by a proxy?

2023-02-20 13:19:03

- reply

This is the way

2023-02-20 13:16:16

- reply

I heard it from the nostr board of directors.

2023-02-20 12:59:46

- reply

Congrats on the demotion!

2023-02-20 12:58:38

- reply

I zapped this note but it doesn't appear to have generated the zap note.
#[2]

2023-02-18 01:13:34

- reply

This is ridiculously cool

2023-02-18 00:50:54

- reply

Yeah you can add the LNDhub endpoint in Zeus or BlueWallet.

2023-02-17 19:58:35

- reply

Great policy, here’s one in

2023-02-17 19:43:43

- reply

#[2] is absolutely killing it

2023-02-17 19:34:07

- reply

Beautiful 😍

2023-02-17 19:25:50

- reply

Right back at you ⚡️

2023-02-17 19:24:28

- reply

I can’t zap you so have a 🤙

2023-02-17 19:21:13

- reply

The free market always delivers

2023-02-17 19:20:05

- reply

Have a zap for your pain

2023-02-17 19:19:40

- reply

Oh I can’t, you’ve gotta add a lightning address to your profile first.

2023-02-17 19:19:03

- reply

Here’s your zap you cheeky devil

2023-02-17 19:17:10

- reply

Here’s a beefy zap for your kickass work on nostream and answering all my annoying questions

2023-02-17 19:15:42

- reply

Good point, have a zap

2023-02-17 19:15:00

- reply

My bad, please accept this zap for spilling the beans

2023-02-17 19:13:06

- reply

Please accept this zap as an apology

2023-02-17 19:09:46

How are you guys fighting the uncontrollable urge to excessively zap yourself into poverty?

2023-02-06 13:52:29

Get it while it's hot folks!
#[0]

2023-02-06 13:49:47

Get it while it’s hot folks!
note1a7yyenq9xkrmz9v6f5t6rwmggwl8hlkt7kd5r8p0y629v7rxjgrqmarxh5

2023-02-03 15:08:15

- reply

You need to remove the second entry, the first one is your correct pubkey.

2023-02-03 15:06:21

- reply

https://hodl.camp/.well-known/nostr.json
You have two pubkeys for the same name in the JSON. Keys are unique in JSON so they will overwrite each other. Different JSON parsers could parse the differently and end up with a different pubkey.

2023-02-01 18:13:29

- reply

Pubsub but cooler

2023-02-01 12:42:31

New relay, who dis?
https://nostr.lu.ke

2023-01-26 02:05:36

- reply

Such a badass logo

2023-01-19 15:19:30

Reverse Shell as a Service - https://reverse-shell.sh
https://github.com/lukechilds/reverse-shell
https://camo.githubusercontent.com/9ffdee4663ef22d343ebc88325a3f504e585669679942758485b215b1d7caa09/68747470733a2f2f692e696d6775722e636f6d2f71716a687841772e676966

2023-01-18 14:03:42

Doge Seed: Dank mnemonic seed phrases.
https://dogeseed.com

2023-01-17 14:48:27

- reply

Been busy with some IRL stuff but will get back on that soon!

2023-01-08 21:21:57

- reply

Yusssss it would be great

2023-01-08 15:58:03

- reply

Nice thing with CDN style caching is it takes a huge traffic load off the relay. So the relay kinda becomes the single source of truth and just has to serve the real-time traffic and new queries. All historic data fetches get offloaded to the CDN.

2023-01-08 15:55:28

- reply

Ohhh I’m with you, you mean the current server side query perf has a lot
of headroom left for improvement.
Yeah totally agree, and I assume clients too.

2023-01-08 15:33:57

- reply

You’re referring to client side caching right? So clients can’t share a global cache like they could with CDN layer caching?

2023-01-08 15:10:55

- reply

Might be nice to expose as much of the protocol over HTTP as possible. Seems like the possibility of CDN layer caching would be a major win for relay scalability.

2023-01-07 20:54:32

#[0] lol free NIP-05 from GitHub Pages. Genius.

2023-01-07 18:41:38

- reply

There are browser extensions like getalby.com that will sign for web clients without exposing your private key to them

2023-01-07 17:06:19

- reply

Yes. It’s the same as if you leak your secret key in Bitcoin or PGP. They are unusable if the secret key is no longer secret.

2023-01-07 14:58:50

- reply

Oh really, I was not aware of that.
What do you think to extending window.nostr to explicitly handle this?
I Nostr based web auth would need some sort of standardisation, even if only to agree on a challenge message format so software can clearly explain to users what they are signing.
Thoughts?

2023-01-07 14:33:36

Nostr as a super simple DID layer.
Interested in anyone’s thoughts.
https://github.com/nostr-protocol/nips/issues/154

2023-01-06 22:56:50

These notifications give me tingles
https://i.imgur.com/hSZusM0.jpg

2023-01-06 13:09:52

- reply

Patience young grasshopper

2023-01-05 23:42:57

- reply

Can we leave the cj beef on Twitter and focus on productive discussion on nostr? Asking for a friend

2023-01-05 17:44:22

- reply

I would say it makes more sense to focus on private relays at this point but totally up to you what approach you wanna take.

2023-01-05 15:11:26

- reply

This is the way

2023-01-05 15:10:53

- reply

Do they not already support it with Orbot?
Honestly not super bullish on Tor for realtime stuff, but feel free to annoy away haha.

2023-01-05 15:07:04

- reply

Wooop awesome. Feel free to reach out if I can be of any help.

2023-01-05 14:20:25

- reply

#[4] are you interested in publishing nostream to the Umbrel App Store?
A requirement is a webui but you can get around it by shipping a gotty container alongside it that just dumps the stdout logs to a web page. You can see an example of this in the Snowflake app, feel free to pinch the code from here if you’re interested: https://github.com/getumbrel/umbrel-apps/blob/master/snowflake/docker-compose.yml
Could be cool use case to run a local instance of nostream on Umbrel, connect over Tailscale in a client and get all your notes and broadcasts backed up locally.

2023-01-05 13:12:03

- reply

In nostr land he’s purplematt

2023-01-05 13:08:53

- reply

Haha yes been waiting to show this bad boy off

2023-01-05 13:08:27

- reply

Thanks my man

2023-01-05 12:38:45

- reply

Haha sick. And double check against https://bitcoin.lu.ke for good luck.

2023-01-05 12:12:59

- reply

“Lemme quickly check a mempool” just doesn’t have the same ring to it

2023-01-05 09:39:18

Testing ecash over nostr, this payment is redeemable by anyone:
https://legend.lnbits.com/cashu/wallet?mint_id=GsAL2UKczDnkS5SWW65GZE&recv_token=W3siaWQiOiJLRDZBSlZFNDdTNXMiLCJhbW91bnQiOjEsIkMiOiIwMzQ1YjFkMzQ1MzBiYmVkZjkyNjM4YjdhMDJmNDU2ZTk5NzZjNWJjZDVlNTNlMjhlN2JhNmJiNWRjMzZmMzFlYzQiLCJzZWNyZXQiOiJlYlRXeC9xYThzT2tTSEtCNzVFTDhZUGVGN09nUWU5Y0hyTVBiUnd2cTFrPSJ9XQ==

2023-01-05 08:59:12

- reply

Hmmn was trying to quote tweet but not sure that worked. The text was from Gigi:
https://twitter.com/search?q=%22verifying%20my%20account%20on%20nostr%22&f=live&pf=1
This uses the nostr.directory verification message, but the &pf=1 limits the twitter search to only people you follow.
https://nostr-resources.com/#finding-others

2023-01-05 08:56:49

- reply

Here you go Tuur:
note1epxfqk5y24zqwcnjtkfq9u7gjh4vep7qeprsadlmahcnsegsyz8se463r5

2023-01-05 01:27:14

- reply

Thanks bro you too 🥹

2023-01-05 01:24:10

#[0] am I dumb or is there no way in Damus to see who 🤙’d my notes?

2023-01-05 01:21:37

2023-01-05 00:59:49

#[0] Verifying My Public Key: "lukechilds"

2022-12-25 18:20:31