I can't promise a base level of activity there, but at some point someone's gotta be the one to get it to that critical mass. I suspect using a community almost as a journal and soliciting comments is probably the best way to start things out, but obviously you're free to try what you like :-).

That last one is a HUUUUGE nope.

There's a reason the sunrise is orange, after all. #GM :-)

So far it's the most impressive I've seen, but I am still looking for a wallet that more difrectly takes user input miniscript to play withso I can try to focus more on learning it and less time learning how wallets otherwise work. Securing against wrench attacks should be priority number one if we're telling everyone to take self custody.

It may be worth checking out Nostr Communities, which many clients support, which function a bit more like a reddit replacement. Also, long form. Satellite.earth may be one of the better clients for exploring some of these features, though certainly others can access them too.

At the end of the day, it's still a relatively small userbase. What sort of dev conversations were you looking for? I can't say I'd be sad to see people getting into the weeds of miniscript personally, though for me, preferably starting from somewhere out on the fairway for a relatively uninitiated pleb.

Probably used a client that mangled or just flat out wiped it. It's happened to most of us I suspect at some point. This site can be a useful tool in managing profile back ups in case it happens again: https://metadata.nostr.com/

In the US some states have laws that make certain services unaccessible that are otherwise widely available. I know in MA for instance I can't use ZBD, but have no trouble with it once I cross every state line except the one into NY, which also doesn't allow it.

Not sure if you're in the states as you didn't indicate this.

Exodus gets into the shitcoin world pretty heavily, which is never something you want to see in a Bitcoin wallet. Means you have a bigger attack surface, with no real gain for it, and meanwhile it's going to throw nonsense about scam tokens at you every time you open it up.

Also, Exodus is closed source, Sparrow is open. Furthermore, sparrow has a wide variety of features relating to Bitcoin, including offline mode, tor support, and a much better array of hardware signing devices support, while Exodus only supports Ledger and Trezor, arguably two of the worst options out there, due to their initialization process relying on their particular software, and an Internet connection.

I'm sure we could dig for even more issues, but I'd hope this is enough reason to leave Exodus for the shitcoiners.

Exodus supports shitcoins. Sparrow doesn't.

Pretty easy win for Sparrow on that count alone.

One people don't bring up much yet though that is worth looking at is Liana, especially if you're interested in bequeathment arrangements and other more involved multisig.

I used to use a good few but now I only really use 5 or so with any regularity. Fountain, Zap.stream, Primal, Amethyst, and Coracle. 0xChat I guess does throw notifications at me that I open from time to time too.

Looking forward to cross platform Damus soon though.

That explains why I couldn't zap Lyn last night. Gonna have to try again.

They sold her clothes to buy more sats.

#GM frens. Always nice to wake up to a new #ATH. Now, for it to go back down because I don't have enough #Bitcoin.

Guess the question here becomes, with or without airhorns? Cuz if you listen to enough nostr:nprofile1qyg8wumn8ghj7mn09eehgu3wvdez7qgewaehxw309aex2mrp0yh8xmn0wf6zuum0vd5kzmp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgawaehxw309ahx7um5wghxy6t5vdhkjmn9wgh8xmmrd9skctcpz4mhxue69uhhyetvv9ujumn0wd68ytnzvuhsz9thwden5te0dehhxarj9ehhsarj9ejx2a30qyg8wumn8ghj7mn0wd68ytnddakj7qgwwaehxw309ahx7uewd3hkctcqyps2tjcydfsvcpptv5z855hfqygcuzedqafj0uktuc8m55n46dcex09q5ck I'm pretty sure you'll get all the points eventually. I don't promise order though.

Sounds like your next step is to look into using miniscript to create time locks to protect against wrench attacks. "I'd be happy to give you my sats, Mr Robber. If you're okay with waiting until next Tuesday, they'll be available for transfer."

Very cutting edge stuff, but you could effectively at least roll it manually using something like Liana wallet at this point. Though you'll end up looking like Popeye if you stamp out a new wallet every time your time lock expires. Might be better to look into making it lock and unlock on a rolling basis within the same wallet...

The concern is that a quantum computer could potentially be able to derive a private key from a public key. Which, if you expose your public key (as with old bitcoin P2PK wallets), would present an issue. If you're following best practices with regards to treating your xpub and other public keys as, well, not public, there's not really much there.

And in any case it's concerns for future decades, about hypothetical technology that may not ever actually exist.

To put it succinctly anyway. It's not something that is suddenly an issue; it was being talked about on the Bitcoin Talk forums back in 2012.

Seems as reasonable a DVM to concoct as any. There's already a One-Per-Follow DVM; sounds like you'd just be making it a 5-per-follow.

Specifically, to make it a lot faster, look at the diff between the old code and the new code. And these days, not being code fluent doesn't need to be too big an issue -- copy/paste it into ChatGPT and ask for a summary of what it's doing. Without the full source it's still going to be abstract but it should make it apparent enough whether or not it's doing something nefarious.

Makes me wonder about having multiple clients running simultaneously. It sounds like the new event should push out to all of them, but depending on what screen you're on on the client at that time it seems like there could be some unexpected behavior.

Relay management does seem to be the number one source of weird behavior in Nostr.

Look on the bright side; they're cultivating the art of trustlessness!

But, in the interest of friendliness, #GM to you too :-)