Replies (15)

Nice, beyond the data scrapers which show client use I didn't think about displaying the client tag in the note, I'll have to do that in a minute, I'm just trying to add polls atm πŸ˜€ thanks for the help πŸ™
Weird. I'm using nos2x on Brave without a problem. But that shouldn't have anything to do with the log in button. That just triggers a simple action. Perhaps the page didn't load fully. It canbe a bit slow. I'm wondering if it was too busy loading the Discover Content carousel, but even that shouldn't stop the log in button from activating, that should all be rendered and ready to go.
Ahh shit, has it started adding nostr.band back in to the relays? I told it to purge all mentions a while ago, but it seems the model is stuck thinking nostr.band is an active project
No content available is informative. I may have more questions later, if I may? Just off back up the hospital to visit my mate in a minute.
Ah, yeah, I yanked that and run the code locally, it doesn't rely on nostr band to provide the modal any more. I had to make that change way back when because nostr band wasn't responding sny more.
I figured out why this is happening. Plume uses nostr-login, which inserts itself between the page and your signer so it can pass messages along, instead of talking to the signer directly. Sidecar doesn’t support that, so the login button appears to do nothing. The nostr-login library comes from nostr.band, a service that has shut down and is no longer maintained. I’d suggest replacing it with a direct connection to the signer extension through window.nostr, which is how most modern NIP-07 clients work.
↑