What’s it like having all the peripheral dongle things going over usb 3? Seemed like a headache for some things I take for granted to just work these days
Try these: https://matrix.to/#/%23general:matrix.cashu.space
https://matrix.to/#/#dev:matrix.cashu.space
matrix homeserver: matrix.cash.space
or send me your matrix username and I'll invite you dierctly
I am getting the “does not exist” error as well, I am nyonson:matrix.org if I can be added
I avoided hm for as long as I could too. It still feels very heavy, but has iron’d out a few quirks like this.
Yea, I am running Wayland too and had to add some settings in home manager for my cursor. Only issue I still have with gossip is the scrolling feels very different than my other apps. But hard to track down why.
Tried to capture a history of the proposals for it cause curious why it seems to have stalled: https://blog.yonson.dev/log/2025-01-vol1/
Could see it having some tricky UI issues though for something like chat use cases.
Doesn't sound 'trivial' to me! Cool to have that history...
Here's what I see in the output:
```
2025-01-17T23:39:07.382256Z WARN /build/cargo-vendor-dir/winit-0.29.15/src/platform_impl/linux/wayland/window/state.rs:708: Failed to set cursor to Default
```
...replace that last word 'Default' with 'Text' and multiply it a dozen times or so, and that's what I keep seeing.
I didn't install from source (I don't know how to do that on NixOS [yet]), just pointed to the package on https://search.nixos.com (v0.12.0).
A separate issue is that for some reason I cannot get SDL2 to install and be recognized--but that's NixOS-specific, not an issue with gossip.
I'm using gossip now so it's usable, and I like it quite a bit--just a few minor annoyance is all. Thank you for writing it!
Are you using the unstable channel? SDL2 stuff was cleared up for me with this tweak to the package: https://github.com/NixOS/nixpkgs/commit/db6be866d53a65f0081792b05cb37c2a21e5ef89
Trying to recap the history of nostr proposals for onion routing to preserve network metadata privacy: https://blog.yonson.dev/log/2025-01-vol1/
Are there any current onion routing proposals using NIP-17? CC nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft and nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z I believe I saw some rumbling from you guys in some deep comment threads.
Not sure I follow on the two receiving addresses. Wouldn’t we want two envelopes so it’s hard for outsiders to trace the path of the message?
A built in nostr solution (ie a bunch of republishers) may lower the bar for more user usage. Also maybe better privacy if a republisher is popular? Versus just offloading trust to a proxy.
nostr:npub1h0uj825jgcr9lzxyp37ehasuenq070707pj63je07n8mkcsg3u0qnsrwx8 any thoughts on this simple onion routing proposal for nostr as an extra privacy layer? Feel like it could be useful for low bandwidth, but extra sensitive messages. Or is something like this already baked in? https://github.com/nostr-protocol/nips/issues/411
Maybe nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s knows? Any chance you think this would have a good enough value/cost for nostr?
Has there been any consideration for #nostr relays to support some sort of compact filters like BIP157/158 style in order to preserve user privacy? Allow reading from a relay without disclosing exactly which events they are interested in.
Very cool. Curious if this could be used as a payjoin v2 async communication channel, but would need to be able to have the read side too
Nice, good enough for me!
Seeing someone else wonder about this is pushing me to give up on the capitalized version