https://void.cat/d/Xttkn4VvL7jVQ4C8vojy6Y.webp
when nostrtube?
š¤·āāļøIām not sure
Proving you can post from Neovim to nostr
What do you exactly mean? I think nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn is doing interesting stuff with provided relay info and has implemented some gossip like stuff in coracle.
Or do you mean like turning them on and off / adding and removing?
Iāve seen a lot of issues when interacting with many nostr sites with things like loading, caching etc.. Also there are many ways to interact with relays, should they be front and center on the site/app? should they just be added to a settings page somewhere? Is it better to read from many relays at once or just one at a time?
I just wanted to get some feedback from people who are using nostr sites/apps.
In your opinion which nostr client handles relays the best?
test post from Neovim
Todays nostr stream:
I'll be streaming nostr development content here if anyone is interested:
https://www.twitch.tv/chrisatmachine
https://www.youtube.com/@chrisatmachine/streams
I'm the creator of blogstack.io and notebin.org so I know a little bit about how to get started and can give some advice for developers trying to understand how nostr works.
I'll be working on a nostr development tool for Neovim for the next couple streams: https://github.com/ChristianChiarulli/nostr.nvim
If there are any nostr devs who use Neovim, Iām working on a plugin that will allow you to interact with nostr directly from the editor. Hereās the repo: https://github.com/ChristianChiarulli/nostr.nvim
I should have a working PoC after tonights stream.
I know there are differences of opinion on this, but I'd like to make a case for allowing sign in w/ an nsec in nostr apps; Long form text apps used as a case study, nostr:npub107jk7htfv243u0x5ynn43scq9wrxtaasmrwwa8lfu2ydwag6cx2quqncxg , nostr:npub1ygzj9skr9val9yqxkf67yf9jshtyhvvl0x76jp5er09nsc0p3j6qr260k2 .
I agree that we should educate users and recommend safer ways of authenticating, but I think especially in the near term, allowing for nsec log-in will:
- Enable users who know about extensions but have chosen not to use them to still log in and use these apps
- Allow users who use multiple nostr accounts to switch between them without having to use multiple extensions or multiple extension accounts
- Accommodate mobile users who do not want to get set up with an extension-compatible mobile browser like Kiwi
* I think that better solutions will come in the future, but for now, it seems that many users have chosen for themselves to tolerate the risk for the sake of convenience.
** I wonder what % of the half a million or so users on Nostr are set up with key management through an extension. Even if it's not ideal, I think it's still good to support these users' ability to interact with the full extent of the nostr ecosystem.
Thoughts and comments welcome.
Tags: #ux #design #habla #HablaTeam
I plan to revamp blogstack at some point and will implement a better login flow then. Likely Iāll work these things out in my notebin rewrite.
Getting back into nostr development, what are the best clients/projects these days?
If you want to test out blog/longform content on nostr, checkout https://blogstack.io/