Nsec login definitely doesn't make much sense, aside from "bunkers are high friction for now so Damus users should just paste nsec". This will improve as bunkers improve, I will share a significant step forward in this area next week.
Local nsec signup makes total sense - let users start asap but then let them export nsec to a bunker. Nostr-login widget has this option built-in, only works with nsec.app for now but will be proposed as NIP upgrade when we are confident it's good enough.
It looks like the only post with Alexandria hashtag is a reply. We don't pull replies - only root posts. Also it's not fetching from nostr.band - it's using your outbox relays. If you remove the hashtag filter some notes are showing up.
"Homepage hashtags" is when you only want a specific hashtag posts appear on homepage (but other posts still pulled in and discoverable through menu or from homepage posts).
I can see your "another Alexandria" post on the homepage now. There might be some delay with server-side rendering of new posts. Local renderer living in the service worker should catch them faster, after the worker starts from the first page load.
Navigation is completely detached from hashtags - we just pre-populate it based on your hashtags, but you can include anything there, including external links.
Point particular post to "sub-page" (some custom url) is coming soon.
I'm sorry for the confusion, but it seems like you're doing it wrong @.
To decide what's included on the site you use "Content filters" - you should specify your hashtags there. Only posts with those hashtags will be pulled into the site. All of them will be included on the homepage.
But some people want to be even more selective even more with their homepage, i.e. "posts with #bitcoin and #nostr should be somewhere on my site, but homepage should only show #nostr". Then you go to "Homepage settings" and choose #nostr there - posts with #bitcoin will still be visible on the site, and you can i.e. add /tag/bitcoin to navigation to direct people there.
Does this make sense?
The issue on our end is fixed - comments on long-form posts published from context menu ("quote" etc) weren't visible - didn't have 'a' tag. But we've also discovered that other apps are having the same bug - Amethyst shows their comments, but we don't (and shouldn't). We've reported to Nostur and Nos about the issue.
Can you please tell me more about your issue? At which stage it stops working? Any errors shown? Maybe make some screenshots or a recording please? Thanks!
Can you please tell me more about your issue? At which stage it stops working? Any errors shown? Maybe make some screenshots or a recording please? Thanks!
Looks like you only have 2 relays in your list - "wss://nostr.chrysalisrecords.com/" and "wss://nostr.indiemusic.com/" and both aren't responding. Please try adding more relays, i.e. wss://nos.lol or wss://relay.damus.io
> A DID of this form can be resolved to the corresponding DID document by querying a server at https://plc.directory/, which is currently operated by Bluesky Social PBC
That's not "how often people open apps and read from relays". It's "how many people have this relay in their relay list with a 'read' marker" - meaning, how many people will use this relay to read events from it, as opposed to 'write' relays - those they will use to broadcast their events.
Server should provide two api endpoints, one accepts npub and should send the one time code as dm. The other one accepts the code and should either set a cookie, or return some payload identifying the session. Nostr-login will pass that payload with onAuth event so you could use it to make future api calls. Codes should be bound to npub and expire
We could just add a block height based on timestamp but that can be faked (timestamp), would be cool if we attached opentimestamps to published articles and then it would be a real thing - an actual provable time when it was published... Let me think on this.
Forget AI agents! Every pet will have an npub and a website!
nostr:nevent1qvzqqqqqqypzq0l6cwnvsk0242xdmkevwqp2dcgtx0h7hyksykc5att03gkk2ejhqqsx564vu60awrrvqfhee7cp2hk3y3mg2xa6053gxddvrhfrwuq6d9c3aljy4
Yes you'd have to wait for us to support it. Not sure what you mean about facilitating, when we implement it you'll be able to include classified listings on your site and have DM support right there.
Npub.pro doesn't support classified listings atm, but as I'm looking into it that shouldn't be too hard to add. Checkout etc are harder, but we could start by just showing the listing properly.
Hi there's no such tool at this point. If you'd like to help us build it, you can find a good wordpress exporting plugin, export the public data you need and give us the exported file. Then we'll see if we can build an importer tool. Thanks!
Oddbean new post about login | logout
Notes by brugeman | export
The issue on our end is fixed - comments on long-form posts published from context menu ("quote" etc) weren't visible - didn't have 'a' tag. But we've also discovered that other apps are having the same bug - Amethyst shows their comments, but we don't (and shouldn't). We've reported to Nostur and Nos about the issue.