New iOS interface (iPad) 🙃 
Hey, I made a new pull request that has more CMake support for the secp256k1 lib, do you have time to merge it? Thanks (Sent from Nostur for Mac, neat desktop client) . https://github.com/damus-io/nostrdb/pull/2
Spent all day trying to build an iOS app with errors of “Xcode couldn't find any iOS App Development provisioning profiles”. Do you guys at Damus headquarters have any luck with certificates for XCode? https://stackoverflow.com/questions/48584288/code-signing-no-account-for-team-message-when-signing-for-different-developer/76833424#76833424
On the competition chapter, my app now builds on iOS. Hopefully AppleStore coming soon . A screenshot on iPhone
iOS build 🤗 
chatgpt has been helping me build nostrdb. It knows a lot about databases, C, and LMDB, so it can give me advice specific to the problem I’m trying to solve:
https://chat.openai.com/share/1e57a2ba-c596-466b-8517-2b137ae7fb7e
Impressive 👀
Check out the demo of my project https://damus.io/note1haxrq5a96264jnurqxv64w9d3zq6npg6gx7fhwwz8msa5u03jc0qvfqkjf
DoraHacks demo workshop of ‘nostr_client_relay’ was published. We demo the C++ API with Microsoft Visual Studio, the client web interface and the native desktop
clients. Thank you for YakiHonne for hosting the workshop. Link to GoogleDrive below (Round 2, Session 1) https://dorahacks.io/hackathon/hack-nostr-on/workshops-&-demo-live
Hey, I created one more pull request 🫡 https://github.com/damus-io/nostrdb/pull/2
Also bug report for Damius i can only see 70% in height of the video. On ipad. On snort on web video is fine
That “delay in the UI” remark caught my attention. If the delay was because you Were doing a DB query that could be because you were doing a synchronous call. in UI we have to do asynchronous calls or use another thread for things that take a long time . Maybe an issue in Nostr is that it takes a long time to query many different relays . A solution maybe to have a local cache and show that first and then update 🫡
It’s really cool that I get to do my browser for the #nostr protocol. The world is your 🦪
I also applied for a OpenSats grant. If they sponsor my project, maybe one day I can work on a place like this https://pedro-vicente.net/nostr/nostr.html
This just seems like the perfect work environment 😐 Not a real work environment, is it, just some nice landscape you found on the Internets? 🧐
That doesn't justify making the protocol a much more complicated thing for everybody. WebSockets are simple, simpler than HTTP and REST, to be fully honest. If you don't like them that means you're just not used to them. You can use a Nostr library that abstracts that for you.
If you want a curl-like experience on the CLI, use https://github.com/fiatjaf/nak
Yes, that was kind of what my point was “if it ain't broke, don't fix it”. As #nostr devs, we shouldn’t have to deal with the underlying transport, we just use libraries that abstract that from us. I believe most languages have a WebSockets library. In my case, when I started with Nostr, it took me a week to find a good C++ library that I was happy with, but now I just use it and don’t care what happens under the hood. And because there was no Nostr C++ API, I made one. Check it out https://pedro-vicente.net/nostr/nostr.html
If you need an API to publish or receive events over WebSockets from the command line, you can use this one (there is also a prototype HTTP client and server that sends/receives #nostr events) https://github.com/pedro-vicente/nostr_client_relay
Hmm 🧐 But nostr is over websockets, mixing HTTP into the mix seems a bit out of whack? nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6
I’m working on exactly that, download OpenGraph data from a URL to generate link previews for my JSON clients. It’s about 90% done, it can download a HTML page and traverse the HTML to get the OG tags https://github.com/pedro-vicente/url_parse_open_graph