Avatar
Kody Low
de8823cdc979bf4c753223edc19a7abc35ecff2959ef50ca9e9d573ac0f83fd0
It's not about you. Cypherpunks Write Code.

wife and I are currently in an argument about what's more painful, getting OC sprayed or childbirth. anyone with experience of either please feel free to chime in.

GENTLEMEN, YOU CAN'T FIGHT IN HERE. THIS IS THE WAR ROOM.

Rewatching Dr. Strangelove and gotta say Gen. Ripper was ahead of his time on calling out fluoride as a commie plot

no it uses openai o1, pretty similar to cursor but a little faster and only works with python/flask/vanillaJS for now

Playing with Replit's new Agent and it's pretty awesome, got some funny results though like here where its subtasking structure got it to describe itself as first person plural

fedi:user:@npub1dalsknffa0p2mznf790vyk6nclkcwnqea5ekrh9jxmpasz5vmzwsckfgp7:m1.8fa.in

got the npub in it just has some decorator stuff

@npub1dalsknffa0p2mznf790vyk6nclkcwnqea5ekrh9jxmpasz5vmzwsckfgp7

feature on the roadmap, going to have exporting the Fedi derived nsec first then byo npub after

he's done like a dozen of them and each time makes the same arguments even when they've been refuted or he's conceded the points previously to other people and is banking that the audience isn't aware. would be helpful to slim shady it and just address each argument he's previously made beforehand in like a written blog post, and ask if there's any new or different arguments he'd like to make for this debate and stick to those.

e.g. in at least 3 debates he's done he makes the argument that Bitcoin isn't scarce because it can be forked. In each debate his opponent clearly demonstrates why he's wrong and he drops it. but then he comes back in the next debate and makes the same argument, knowing he's wrong but hoping it won't get addressed.

Replying to Avatar Kody Low

nostr:npub1nc0ynppqh37rtulr57xjqpzmfjp58xrd4ey8896ehn9j5flg33fszrz5pa's been working on and off on a better indexDB transaction abstraction that'll make doing ecash TXs from a PWA or webapp much more reliable, will also work for cashu since it's just generic KV! https://github.com/elsirion/webkv/blob/master/src/lib.rs

The default indexdb behavior is to commit the transaction as is whenever the event loop hits a network request, so for ecash transactions that might be hitting multiple mints it's probably causing the same issues we used to see in the Fedi PWA. webkv makes indexdb transactions operate the way everyone assumes they should work haha

nostr:npub1nc0ynppqh37rtulr57xjqpzmfjp58xrd4ey8896ehn9j5flg33fszrz5pa's been working on and off on a better indexDB transaction abstraction that'll make doing ecash TXs from a PWA or webapp much more reliable, will also work for cashu since it's just generic KV! https://github.com/elsirion/webkv/blob/master/src/lib.rs

The default indexdb behavior is to commit the transaction as is whenever the event loop hits a network request, so for ecash transactions that might be hitting multiple mints it's probably causing the same issues we used to see in the Fedi PWA. webkv makes indexdb transactions operate the way everyone assumes they should work haha

thanks for the ping, this is getting updated once we have it posted I'll post here.

Fedimint weekly Dev Call starting on the hour!

Onboarding new contributors, farming out issues, pitching nostr:npub1s0veng2gvfwr62acrxhnqexq76sj6ldg3a5t935jy8e6w3shr5vsnwrmq5 cohort attendance, updating PRs and Roadmapping out the 0.5 release. It's a good time, all are welcome (just keep your camera off, like to keep things ricky-recon-secret-squirrely)

https://meet.jit.si/fedimintdevcall

all good, yeah every release we cut the source code will get posted into that org per the new source available license. mirrors an internal repo which has all the github issue tracking and normal internal company stuff with feature branches. every release that gets pushed to stores / public apk that happens then the fedixyz/Fedi will get the same source code pushed.