Which nip46 servers support connecting with nostrconnect: schema? nak doesn't seem to, what about others?
I see next.nostrudel.ninja client has it, any other clients?
@fiatjaf@PABLOF7z@Mike Dilger@greenart7c3
There is Nostr Connect nip (nip46) but then there is a small part of it which is nostrconnect://pubkey... urls. Ideally we'd have a more detailed table with more columns, "server", "client", "bunker:", "nostrconnect:", "create_account" at least come to mind.
Remote signer, but also maybe check thread below. Will be adding that to nostr-login and nsec.app
nostr:nevent1qqstv6cl32tfwgtttz9v2sysfra85l9l35plc4zq25mvuf4a3u0h72qpremhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet59upzqv6kmesm89j8jvww3vs5pv46hqm7pqgvpm63twlf9hszfqzqhz7aqvzqqqqqqy84amuq
Import content from Ghost to Nostr, anyone?
Here is a work-in-progress tool for that: https://npub.pro/import-ghost
You can bring articles from your Ghost site to Nostr and make them accessible for people here to zap/react/comment.
Eventually the tool will let you copy all website settings from Ghost to an npub.pro site. For now - content only.
Ghost is great, but nothing beats adding your cryptographic signature to your article and broadcasting it to an open interoperable network, right?!
P.S. A reminder about a similar tool for Twitter: https://exit.pub
You can login using one-time code - choose Login with DM, enter your npub, get a code a nostr direct message and enter the code. Works perfectly on mobile, no need to set up nsec.app or extension.
When creating a website you choose which hashtags to show - it's not only about navigation, it's about what content is shown on the site.
Main page shows everything you've selected (all hashtags you've chosen) by default, but you can choose specific hashtags for homepage in settings.
Whenever you post something with selected hashtags it appears on the website.
And "long form posts" are posts you can make using habla.news or highlighter.com - they have title, summary, and allow for formatting (links, lists, subtitles etc).
Let me know if you have any more questions or feedback, thank!
You choose hashtags and posts with those hashtags will be on the site. We also add several of them into navigation when site is created. All those hashtags appear on homepage by default, but you then choose which of them will be on homepage in a separate setting in admin panel, and you can also change what appears in navigation. Does it make sense? Thanks
Yes edits support is a great idea. Manual post selection is coming a bit later too. Reposts and replies will be supported too.
Thanks, please let me know if you ever need any help!
Yes we don't store your content, it's stored on relays, so you should publish to multiple relays and also make local backups of your notes so you could rebroadcast them if need arises. Not sure about backup services, I think I saw something but can't find it.
Nostr sites aren't just personal homepages!
nostr:nevent1qqsrq7y59uflauz6jrgs3lelwy8n9ryh052g0hd9a5hx5ecu7kvluuspzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtczyqyw4hjsmaga5jjz7hwqgh34kdceqtsx665q2g2mas7h9hrg0n9sgqcyqqqqqqgehhkck
Try watching the intro video below, this shouldn't be too hard. After the site is created with one author, go to Settings and add more contributors.
nostr:nevent1qqsq6g0tytafts9pysutk56ah9jguy65kytqx9mg6g2hnh2a2525pvcsxxw9v
More customizations for your homepages!
nostr:nevent1qqsfqnlr2v54e48whxjx6544m6va7q720ngf43f3nan46aycj4jh0tqpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtczyqyw4hjsmaga5jjz7hwqgh34kdceqtsx665q2g2mas7h9hrg0n9sgqcyqqqqqqgsehkw5
More customizations for your homepages!
nostr:nevent1qqsfqnlr2v54e48whxjx6544m6va7q720ngf43f3nan46aycj4jh0tqpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtczyqyw4hjsmaga5jjz7hwqgh34kdceqtsx665q2g2mas7h9hrg0n9sgqcyqqqqqqgsehkw5
Finally internal links work properly on the nostr sites, so you can quote your posts and keep readers on your site.
nostr:nevent1qqsg3qg2ehccg45uzshq0vfrjkdxqeu7rrqxg67jlfpex89r8kzfvdgpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtczyqyw4hjsmaga5jjz7hwqgh34kdceqtsx665q2g2mas7h9hrg0n9sgqcyqqqqqqgv90qet
This graph is a bit misleading for this point, because if some relay it mentioned in someone's relay list it doesn't mean that relay is important. I.e. current.fyi relay is dead but still around top 5 here just by inertia.
Also how did you evaluate relays? By how much events they cover?
So is this the way to get safe shared access to keys?! I have not thought it through or tried myself yet but looks super promising!
nostr:nevent1qqsx95hu5y6awpx4zyjfzfmqr4nd64r743klata9lm93jx047z7vk3gpz4mhxue69uhkummnw3ezummcw3ezuer9wchsygpnzm3d3rlercggn36lamwd3w4zyk9523268v2k4ash6lk8ndzlu5psgqqqqqqs9z3c9d
I see, this makes sense as a prototype but I think it deserves a separate ui - temp keys could be "connect with temporary key" and new flow as "connect with extension" or something like that.
Yes it's all very confusing, we already have a dozen ways to login on nostr and no good terminology or conventions. Instead of temp keys we could say "Connect" and "Connect as username-from-extension" if it's present.
Could you please elaborate on your second point. You can already delete app perms without deleting the app connections to trigger the popup on any further action. And maybe you are right, we should inform the user that if they login to nsec.app on some device then their main key will be downloaded and stored here. We could also include an option to auto-logout (delete key from device) after a while.
That could work too but nsec.app was specifically created to have a pure web based solution without an extension, so we don't have that on the roadmap atm
I understand, but our primary use case for nsec.app is to onboard people on the web (on nostr sites) into a web-based key storage, without asking for extension install, so we're focusing on that part. If someone adds nip46 to extension I'm totally fine with that, it's just not our focus.
Hi, nsec.app and bunker-urls have nothing to do with browser extensions. Every time you log in to an app, the app generates a temporary nsec/npub which is used to connect to your keys inside nsec.app (and that temporary npub you see in connection requests). Each time a connection is established the new key is generated by an app, and you have to approve it in nsec.app. Limited shared access is impossible atm - you'd need to basically give your friends full access to nsec.app so that they themselves would be able to approve the connection requests without your help. I have limited shared access feature outlined on the roadmap, but it's actually quite hard to implement and you're only a second person to ask for it, so I guess it will take a while before we start working on it.
Can you please tell me more about what your expectation was with browser extensions + nsec.app? Did you mean nsec stored in extension would somehow be "allowed" in nsec.app and then something good could happen? Thanks.
I have not tried using nsecbunker to share access, but from my understanding what you want is:
- add npubs that are allowed to control the main key
- set permissions for each such npub - is they can accept connections, confirm certain kinds, etc
- then if one of those users are trying to log into an app, they would confirm the connection/signing themselves (but within limits that you've specified)
- all this without your friends getting access to your main nsec, which is stored safely on one of your devices
Is that roughly it?
Do you confirm using popups, or do you keep nsec.app tab open? Popups should show the app's domain name, not just npub, you wouldn't have to edit the name manually.
Oh that's an interesting idea of using extension key as app key... need to think it through.
Meanwhile, if they're gonna use just one app, they could try to log in as your main key on their device, you would confirm on main device, add needed permissions (manually or on request) and then they'd just keep using it? If they'd need to re-login you'd have to confirm again, but once the session is created they should be able to use it just fine?
It's just a way for you to mark this session as "I shared it with this npub". If you gave someone access by confirming a login on their device and then mark a session using this option, then you'd be able to filter the activity and connections on the key's screen - you'll be able to select "yourself" or "that npub you shared with". This is some beginnings of shared access, just for reporting.
Maybe we should add an option to specify a black/whitelist of hashtags you'd want to see appearing on your site? Then you'd choose some good list and then the garbage wouldn't annoy anyone.
Another cool site here!
nostr:nevent1qqs920uc7g3wy2sglkgcuh72u4wma4y2tjvruanz6sfrygvusndnvqgppemhxue69uhkummn9ekx7mp0qgsy8w40ps5wdna3jkchacyrux0t8f90m7k9fkdkhtchqfcw6xf7xnqrqsqqqqqpmj0488
Thanks! This post has hashtags mentioned in the content, but not in event's "t" tags, which are used by npub.pro to fetch the content. Looking through the plugin code, I guess it was supposed to offer you to select which hashtags to include in the post, did it? Could you please try again and include one of hashtags you've specified on your npub.pro site (#travel, #photography etc)? Maybe include a screenshot if you did that already? Thank you!
Yes add any hashtag out of ones you've specified for npub.pro site.
I'm not sure how that plugin formats the post, I'm not the one who built it. I agree that adding an image would be a good idea!
The post contains a link to your wordpress blog, Damus just shows the preview of that link. Npub.pro shows the preview too if you open the post, but it can't take a photo from the preview link and use it as the photo of a post, it needs a direct link to the photo inside the post itself.
Notes by brugeman | export