Loving the honesty of this conversation from nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc and nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft, well worth a listen.
Open Librarian (www.openlibrarian.com) is currently VERY ugly, but at least it is my ideas realised, and I am shipping while learning all the time.
#nostr #devstr #bookstr
Oh wow, this is a real podcast?! I didn’t know they’d started. Sweet!
I added a book to my shelf, but your app isn't publishing nostr notes signed by me. are you just using nostr login and your own database?
I shall some digging apologies for this. Not having any issues when I log in using NIP-07 or with my nsec directly. Were you using nip-07?
I'm using nip-07
an error is happening during event signing:
Yeah it is the clunky way I initially built the app using Python exclusively before having to rewrite to push all the key stuff to the front end. The signed event gets passed back to the backend where it publishers it from there. I didn’t store the relays list in the front end, it is in the session data. It is pretty ugly so working on how to unpick that issue.
When you get a min would you mind testing it out again please and let me know if you are still have trouble with the published events. If you continue to have similar issues can you raise an issue on the GitHub repo please so that we can talk through the steps to replicate the issue.
I’ve added to the backlog to move the event publishing to the front end instead of passing it back to the server as I am currently doing. I do wonder though if the event is pushed from the server (rather than the client) would that shield the IP for the client from the relays do you think?
Really appreciate you taking the time to try it out and find bugs. If you have any other suggestions (or features you want to see) fire them my way and I’ll add them to my backlog of user feedback.
