tee8z

Does anyone know of a good open source example on how to implement nostr login, with extensions or with having the user create their own keys in the browser ( having the key creation offloaded to rust wasm)?

2024-08-15 20:29:29

Always satisfying getting a side project to “working”, but then the real beast of deploying shows up to ruin the fun

2024-08-08 21:38:40

- reply

The best kind of applications are the ones you make for yourself

2024-07-04 16:31:41

Youth brings change and energy, if you find a problem to solve young nothing wrong with going all in
https://m.primal.net/JICP.jpg

2024-07-01 11:52:50

Highly recommend making a trip to New Hampshire white mountains if you ever get the chance, they are quite the sight and an incredible place to backpack, picture from my most recent trek there
https://m.primal.net/JEUt.jpg

2024-05-30 20:00:15

“Split a commit, make your code reviews life easier, it can’t be that hard…” absolutely rugged myself, thankfully “git reset —hard” exists and learned to push it remotely before trying to get fancy with git a long time ago

2024-05-30 17:42:32

- reply

Ecash growing on you?

2024-04-11 15:32:02

Headed to BBB, ready to share some sweet lightning simulations
https://m.primal.net/HtnV.png

2024-03-25 01:18:26

Incase anyone wants to see a chain of force closures automatically happen due to inflight htlcs and a peer going offline for too long, got a Doppler simulation for you 👀: https://github.com/tee8z/doppler/blob/master/doppler_files/force_close/README.md

2024-02-27 22:31:53

Is it nap time yet?
https://m.primal.net/Hfjt.jpg

2024-02-21 16:41:30

- reply

pic of actual post:
https://m.primal.net/HeIN.jpg

2024-02-21 16:40:18

huge: https://x.com/gkrizek/status/1760331184905519576?s=46

2024-02-19 20:25:29

- reply

This is awesome! well done sir

2024-02-10 01:08:06

After listening to the lastest @npub10ut…xdlq just want to state it's not trivial to do accounting on lightning nodes. There are edge cases that get hairy around on-chain and lightning fees, can be done but typically requires an external service/added plugin to keep track of your lightning node's historical data and plugging in information from on-chain to get a full picture. The node software itself tries to limit the amount of state it keeps so that it can operater better and stay leaner. This is a bigger problem for larger nodes that have had a ton of state go across them. Just my 2sats

2024-02-02 13:56:37

Not sure if someone has already done this, but something that would be nice to have is a plug & play library to setup a "public chat room" thats application specific (so not the global feed) on nostr that could be use in applications. Think like the stream of messages that happen in a gaming lobby or gambling site, not having to re-invent the wheel whenever someone wants to make it possible for their users to communicate with each other would be a real win.

2024-01-20 15:54:36

- reply

awesome, if you guys open source it I would love to help out where possible

2024-01-20 15:16:39

Realizing multi-party bets are still a hard thing to pull off in a non-custiodal way in bitcoin, especially at scale.
One could do a DLC, but then you have a large amount of data has to be communicted between each participant before the transaction is broadcasted. Not to mention the fees would make small bets (think less than a dollar) not a viable possibility. The amount of data grows nearly exponentially as the number of participants grows, there are some cool math tricks there to try to shink the amount of data needed for determining the payout path, but this doesn't seem like it would work for say a 1000 person competition style bet.
One could go the hodl invoice route of having each participant pay invoices for all possible payout routes then have a central node where all the payments go through funnel where the payments go at bet completetion. The node would cancel the payout routes that lost and allow the winning ones to pass through. But this brings in a lot of issues with lightning state and if you're bet is a long window of time there's a high likelihood of things going sideways (think force closures along payout routes).
It seems there might be hope here to do this in a less custiodal way via fedimint? The prediction market module seems interesting, but not sure how it handles orcale type data, ie an attestation about the outcome of whatever is being predicted/bet on.
Going to keep thinking on this, if anyone has ideas around this I'm all ears.

2024-01-18 17:05:19

So who’s going to be the baller that holds a key to a fedimint with the prediction market module enabled?