i heard bolt12 fixes this
hmm it's picture only isn't it.
we need to integrate the gallery
sick!
nostr:note1s8s2p8uh5l8hktz5jq00dgmtq3jclvma495wgz5hv22fha3x0arsskyfr8
I'm willing to bet that the camera looks better than many phones with a 1-in sensor due to all the processing
new phone 
i want embedded egui
i've had enough. of the monero propaganda
it's a shitcoin, it's privacy dysphoria. i'm sorry
i love you. i love you! if you're a friend, and you're hurt by this, know that i love you!
but i really don't think that those ring signatures are good for you. i don't!
i've had enough. of the solana propaganda
it's a shitcoin, it's decentralization dysphoria. i'm sorry
i love you. i love you! if you're a friend, and you're hurt by this, know that i love you!
but i really don't think that buying $CUM is good for you. i don't!
In-Person nostr voting machines, who's building this?
i caved 
I feel like in a lot of cases though that could lead to websites shipping their own UI frameworks (egui, imgui, nuklear), which is not ideal.
I think the advantage here is that it picks the default browser native framework automatically, and then you could probably give it some kind of GPU access to.
That's probably the toughest part
The advantage that I see of this method though, is that the project in question is already an abstraction over Swift UI, gtk3, and whatever Windows has going on so you could make an abstraction over egui using the same technique and then load it over the wire with nostr events
and then after you do that, you only have to ship one version of your product. the client library just adapts that abstraction.
lots of ideas here, many ways to explore it.
curious to see what you come up with though
