nostr:npub1qz2usdlga5msmejstskxx9234uyvzyy98dgeq4wseheanqw6ttps9gm8hf Any chance you could add krux?
nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr 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 😅 .
The wording seems something Trump would say 🤣
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.
Some #GNU #linux programs are really trash, inconsistent UX, most notably example GNUpg with his fururistic chatbot-like experience that try to "understand what command you mean" failing everytime.
Another peak bad linux UX is the damned wireless wpa connection that require to use 5 different utilities inconsistent with each other just to connect to the damned wifi jesus and imagine to change resolv.conf file and set it to read-only just to make the dns-proxy stick and avoid network-manager rewritr the file every 2 minutes.
How many utilities are needed on openbsd? Just one, ifconfig. How pages is long a fucking config that set an automatic connection at startup with correct wpa resolution? 2 consistent and simple lines of config.
Hey nostr:nprofile1qqsw3znfr6vdnxrujezjrhlkqqjlvpcqx79ys7gcph9mkjjsy7zsgygpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz8thwden5te0dehhxarj9ekh2arfdeuhwctvd3jhgtnrdakj7qgkwaehxw309ajkgetw9ehx7um5wghxcctwvshspg7dju I think I'm near to join your "hate linux club", I'm still on a gentoo machine compiling gcc because I fall for the "linux is the common standard" narrative and I have solarpanel so can compile free basically.
I think that if you want to stay on "normal" linux, the best way is to run Fedora Workstation, at least it has the (imho) best sane defaults (security wise with uefi support, selinux and so on, btrfs and snapshots, etc ...) and only touch connestions using nmcli (network manager)
Given the tokens are "saved" as nostr events on relays, what information is an external observer able to get by looking at a nostr profile? Just a bunch of tokens unable to be "decrypted"? Amount? Mints used? What is the level privacy of this thing?
Sorry for the probably stupid question, but I am not that technical on this stuff.
I don't fully uderstand the part on the middle of the scheme with those nostr relays, does that mean that each traffic/packet coming from the proxy is "encapsulated" into nostr events that are then read by NWS exit nodes?
So basically we have HTTPS traffic into nostr events and then back to HTTPS traffic again?
It's normal https based on SSL. Otherwise it wouldn't work with anything other than custom software.
So you still need to use certificates and be bound to certificate authorities, unless you use a self signed one and trust it?
So basically this is "only" (I mean it's a lot) an alternative way to reach a web site? And does the website still need to have a public IP or is the NWS component "pulling" the connection from the relay somehow?
Huge milestone: First demo of Nostr Web Services (NWS) bringing TCP to Nostr. With NWS, you can host any existing web application on Nostr without having to use DNS or even announce your public IP to the world, simply by sharing your service's npub (or nprofile).
Try it out the demo yourself. Here is a Cashu test mint running with NWS. Let's use curl to retrieve the mint's information. The request travels from your computer to the public NWS entry relay, then through nostr to the service's NWS exit relay. At the other end is a Cashu mint with HTTPS encryption.
```
curl -s -x socks5h://relay.8333.space:8882 https://nprofile1qqs8a8nk09fhrxylcd42haz8ev4cprhnk5egntvs0whafvaaxpk8plgpzemhxue69uhhyetvv9ujuwpnxvejuumsv93k2g6k9kr/v1/info --insecure | jq
```
I can't stress this enough: THE MINT RUNS BEHIND HTTPS!
The NWS entry relay can't read your traffic. It's encrypted. We can host public entry relays that can be used by anyone.
This means we can plug the entire internet to it 🌐.
Let's plug it into Cashu for now. Nutshell wallet supports socks5 proxies (that's how it uses Tor). By setting the public entry relay as the proxy, the wallet can now connect to a mint's npub/nprofile and communicate with it via NWS.
This is going to be so freaking cool. And it's going to be a lot more useful than just for Cashu. There are still bugs and issues that need to be ironed out but the code is coming out soon. Watch this space.
So basically the HTTPS encryption is based not on certificates but on nostr keys? Therefore the relay cannot see the content of the connection?
Ops, didn't finished the post:
..., creates the amber application and then you are ready to go (without needing to first copy the string from the phone app to the site you are trying to login)
Yeah I think you can make the login process with a bunker managed by amber so that you don't need to previously create an application in amber.
The flow would be really cool if you could somehow login by typing your nostr username and then amber sees the bunker request from the set relays
With this process, what info is an external "attacker" able to get from looking at the relays where the tokens are being posted?
Only who is receiving those ecash? Other info about the "payment"?
Thank you, this is awesome.
Now we only need proper private DMs and this thing is gonna be fire!!!
Is the wallet creating a sort of hidden seed like other cashu wallets (so you are dependent on using the Highligther app), or is it only relying on your nostr pubkey? Were is the difference here? Apart from the "ecash token on relays" part.
Might be a stupid question, but I am still learning these kind of stuff.
Yeah I guess you can basically treat each zap (ecash token) as a nostr event propagated on some relays
Yeah too much coffee for my understanding, try once a day maximum, and never after the afternoon, it messes with your sleep.
Then again, anyone is built different, but still...
I'll say LN payments to nostr posts? I mean it is a nice first thing to experience.
On an unrelated note: is there a nostr "bot" that notify the user everytime a new message/conversation has been written on a "root" post?
