The current spec doesn’t have that. Thats what I suggested
Who would buy
Oh nice! Glad nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s removed them. 🙏
A few others have too, but I still see some clients where they don't, for example on noStrudel it'll show as red checkmark.
Never had them
I think that with a little push, y'all can help get my Bisq 2 NixOS package over the finish line so that it gets merged prior to the NixOS November stable release.
Especially considering that it's easy to do :)
First, run: nix run github:emmanuelrosa/nixpkgs/bisq2#bisq2
That will grab the package from my PR, build it, and run it.
If you have a HiDPI display, then use this instead:
nix shell github:emmanuelrosa/nixpkgs/bisq2#bisq2
bisq2-hidpi
Then, go ahead a play with Bisq 2 for a bit to see that it works. Note: QR code scanning is unavailable at this time.
Finally, go to the PR at https://github.com/NixOS/nixpkgs/pull/347160 and add a comment stating that you tested the package, and then explain the results: Did it work or not?
The package code has already been reviewed and I addressed all of the concerns. What's needed is to have users report that it works; Those who merge code in Nixpkgs don't usually know how to confirm whether a package works or not since they don't use the software themselves.
Let's make this happen, y'all.
#nixos #bisq
will test
i feel like my life just 10x’d ❤️ (brought on the world’s best assistant nostr:npub1s8dcec2r32yemn036tpqwp6wlj9whkcsymhu5lp3qhvfdyqmtvtq2vjalq)
finally!
03f3c108ccd536b8526841f0a5c58212bb9e6584a1eb493080e7c1cc34f82dad71@ln.damus.io:9735
probably won't work until node is back up
then we would be ignoring a very loud signal. written feedback is all we have because we don’t have analytics.
yes! once its up again
Never gets old nostr:note1d6t76ny3mulp6u37tug88utffgszda54xv4gjnhvspfl4gxwn8msxxn7h3
builders buildin nostr:note1dzmyasjemhqpjlshqmxlcemwmtq92umg67zq9sh54rkq2jw3geaqyg6l7x
Definitely icky, but users have needs 🥲
This is my main concern about edits on nostr, do people see the same concern or am I being overly cautious? Lots of ux issues. We would have to include metadata in the reply to even know which note is actually being replied to. This is pretty important in the example below. Many clients who don’t implement it may find replies confusing. I dunno… 
seems like you are taking my post too seriously bro
Apparently it gets corrupted even in raid setups according to people i’ve talked to here… i suspect there is a bug but core devs don’t think so
the people on nostr are some of the smartest and coolest i’ve ever got to know. who cares if it doesn’t take over the world. It’s done more than i could ever ask for.
at this point if a girl says they want something i assume its a psyop. be yourself
ma’am im trying to lock in
q u a n t u m a i b l o c k c h a i ns
point to hardware even though raid doesn’t handle it? what do you mean
apparently my bitcoind leveldb corrupted *yet again* so I have to redownload the entire blockchain from scratch. ffs. leveldb is terrible.
