Futr nostr client can now fetch profile metadata and update the UI in place...
https://video.nostr.build/e204add37172dfabde7caf891f8805deff1e04338735a54f50f4ea35ada8f7e8.mp4
Oh, can you add one or two test cases of derived PNS keypairs? I like to make sure to test against those and ensure compatibility.
I see now, I missed the derived PNS keypair. So I know what to fetch, but no other user (relay maybe can?) can make a relationship between this encrypted data and myself.
I like that.
just published NIP-PNS: Private Note Storage. nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn nostr:npub13v47pg9dxjq96an8jfev9znhm0k7ntwtlh9y335paj9kyjsjpznqzzl3l8
was going to use this for backing up openai-style chat sessions for dave, as well as private application settings (NWC, etc). keys can be per-device, or tied to user nsec (although this is more risky if your key is compromised).
It's like giftwraps without the p tag or seal. It only has the wrap and rumor encrypted to your private PNS identity.
The PNS note has no tags on it. the only metadata is the note timestamp, and random but deterministic key.
Let me know what ya'll think!
Do I read this correctly? It's NIP44 encryption over NIP78 app data, nothing more or less?
I make a trip to where electricity is available and continue coding on nostr.
By the way, the wavlake link on your nostr profile isn't working.
It's not for the sats, you can keep 'em. You need to learn good food 😂
Quick update on what has been going on in futr development (a native nostr desktop client):
- solved memory leak in Qt5
- fixed recursive re-rendering bug in Qt5
- enable QML debugger through Haskell binding
- improve event handling and Qt5 signal triggering
These things were a major blockers before next release, unfortunately it took way longer than expected. However within the next 1-2 weeks, the UI Updates will be done and then you'll get a Windows binary as well. Next release comes with tons of new features and Bugfixes.
Side note for other developers: Qt5 Quick is awesome, however there are some things you just can't solve intuitively, this thing will just eat all CPU resources and you don't know why. I never had to benchmark a web frontend, but here you have to verify whether or not it's working efficiently. You just have to know certain things or you get bitten.
QML profiler is running. Now I "only" need to inspect the huge amount of data it generates and find the culprit.
Hacking into Haskell/ Qt Bindings right now in order to enable QML Profiler from Haskell. Going forward...
https://github.com/futrnostr/futr is the source code
1000 USD for anyone who can solve fix a memory leak in a Qt5 app with Haskell backend. I pay in Bitcoin.
I tend to grab tasks that are over my head. Best way to learn.
Before your first contribution, watch the project closely (follow PRs/releases) to really understand it. You'll become very familiar soon! This guide has more great tips for getting started. #OpenSource https://un.curl.dev/start/contributing.html
Best way of getting started is just do it. You ran into a problem and you work on a solution. Once you got it figured out, you send in your pull request and go from there.