What is the best platform or tool to properly search and setup all your relays (inbox, outbox, dm, search, etc...)? Is there a standard or best principles to follow?
ciori
_@ciori.net
npub1hupm...nnm6
@Yuki Kishimoto Hi, I was trying the nostr rust crate to test the nostr connect feature where a web app is generating a qrcode with the "nostrconnect://..." url for Amber to scan and sign. So in this case I am creating the NostrConnectURI object by providing the local public key of the app (not the remote signer) and the usual relays. This goes all well as I am able to then use the Client object, the problem is that when I refresh the web page all the internal state, meaning the Client object, get lost (I am using dioxus as web framework if it can help). The thing is that during the initial "login" phase I save every important value as a String by leveraging the integration with the browser localstorage, so I am fairly certain that the Client object can be recreated, but I don't understand how. I have looked at the examples on the github repo and tried different options but I am unable to properly recreate/parse the NostrConnectURI and then the Nip46Signer. What should be the correct way to do it if I initially "logged in" with a "Direct connection initiated by the client"?
@fiatjaf @hzrd149 Thinking about some alternative home feed: I have to say I find "duplicated" content from people I follow too much often, what I mean is that when someone is resharing other people posts I see both the original post and the reshare it confuses me because I see multiple time the same content. I think it could be an interesting idea to have the option (not a DVM, just an option for the feed that I can decide to enable permanently) to display reshares from people I follow only when they reference a note from a person I don't follow, so that I can avoid duplicated content and feed is less bloated.
What would you say? Could this be useful?
Ehi @Yuki Kishimoto I see you are working on the Rust Nostr library, I was playing around with it mostly for NIP46 and NIP65 stuff following the example codes on the repo and I was wondering: if I want to publish an event using the outbox model what do I need to do? Is there a method or option on the Client object to automatically publish the event on the outbox relays of the user or do I need to make sure to "client.add_relay(...)" for every outbox relay (taken from "Kind::RelayList" events) prior to sending the event?
Ehi @Derek Ross , is it possible to configure the well-known content on nostrplebs.com with the nip46 key to advertise relays used for remote signing with apps like Amber? I am talking about this login flow: 
GitHub
nips/46.md at master ยท nostr-protocol/nips
Nostr Implementation Possibilities. Contribute to nostr-protocol/nips development by creating an account on GitHub.
@JeffG @greenart7c3 @hzrd149 After watching some Nostr Dev videos about NDK I was wondering: are there some nostr clients that uses the outbox model and the "Nostr Connect" login option (the one with the bunker url talking with Amber, like in nostrudel) that are done with NDK? Does NDK support this type of auhtentication?
Some thoughts about Fedimint and Fedi given the recent launch event:
I like the idea behind distributed eCash at least in principle, BUT I still have some doubts on the practical side of things:
- As I understand, Fedimint is distributed only at the cashu level as the federation still requires a SINGLE lightning gateway to function properly. While it is obviously a nice thing to have, I wonder whether this will really make a difference in practice: if we think federations as communities or companies, they might be "distributed" technically, but are still a "single" attackable entity, so what's the difference here from a simpler cashu mint?
- When Fedi open source code? You have money and chat together and expect us to trust a closed source app? I hope the code will be available soon (and with reproducible builds)
So in the end, what I want to say is that unless we get federations composed of different entities that have little to do with each other, like a sort of good "cartel" (so that multiple guardians will actually make sense), fedimint "is only" useful to increase (how much? You still rely on a single LN gateway) the technical difficulty to attack a federation (guardians on geographically distributed nodes, on different cloud provider or datacenter, with different implementations, etc...).
I might have been to harsh here, but this is just my first thought about this, anyway I still like the general fedimint idea.
@npub1qz2u...m8hf Any chance you could add krux?
@hzrd149 Would you say grouping "reposts" of a note from multiple users into a single visible note (with the icons/avatars of all the people that reposted it) could be an interesting feature in nostrudel?
For me it happens sometimes that I see a repost of a note I already saw and think "oh ok I've reached the bottom of all the new posts for today", but then I keep scrolling and I actually see something new, so basically that repost was a new one from a different user.
So sometimes the feed is a bit confusing for me in this sense, maybe there could be a way to group these kind of similar events where the actual content is the same (reposted note) and therefore it feels like it's "duplicated".
Might be a stupid thing, but I have this feeling this could actually be interesting ๐
.
Following the nostr feed during the conference got me thinking: it would be nice to have a DVM that summarize/collects the most relevant messages that were posted during a specific event, so that people can catch up with what happened even after few days have passed.
Ehi @DETERMINISTIC OPTIMISM ๐ I really like when you go into low level and security stuff on your Bitcoin.Review podcast, so I was wondering (maybe a little bit off topic) in the linux desktop world, are you a Wayland or X11 guy? Do you have some knowledge about those two options? And if so, is Wayland really necessary and useful to confine and separate windows, or the surface attacks could be so that when you have a "faulty/malicious" app it doesn't really make a difference?