Avatar
finch ☦️
e5177ebf513530c2d0924083b64b7eadd7fb85efcc3e4dfb55c73a924c901ca7
Let us fall down and worship Christ, our King and our God ☦️

It says in Gossip number of leading zeroes?

The OP on the github issue keeps fudding it because he has no idea how it works

I think it's perfectly fine to build but it's just not something I'm going to contribute financially to the development of.

I stated fully self-custodial in mine because I just know that if LNDHub is supported everyone will go to using GetAlby custodial wallet and linking it to Amethyst.

I’m convinced the only place this makes sense is the laundry room (don’t need to turn off light when you carry out a load of laundry)

Users will always gravitate towards the path of least resistance. They take the easy route 99 times out of 100.

We have a unique opportunity here to make self-custodial wallets more convenient than custodial wallets for users of Nostr.

By integrating self-custodial wallets into Nostr clients with something like Breez SDK before custodial solution are in place, we make the easiest way of zapping also non-custodial.

Let’s git ‘r done!

#[0]

Thing I really like about the Monero devs is that the actually improve the software instead of gatekeep like Bitcoin core devs

So you don’t think they will either lol

Replying to Avatar Seth For Privacy

I've overhauled and updated my "Privacy First Steps" guide, including adding a section on email aliasing services ✍️

https://sethforprivacy.com/posts/privacy-first-steps/

If you haven't read through it before, this post is how I would approach the journey towards personal privacy (even down to the order!) if I could do it all over again. I think this is one of my most actionable and helpful pieces of content, so I'm glad to be able to share it with Nostr for the first time!

Would love to hear any feedback you all have, or if you'd do things differently!

With an email aliasing service, don't you expose your emails through the aliasing provider?

Let's say I use protonmail without an aliasing service. In theory the only party that is able to read my emails is me and the person I'm sending emails to (as well as their email provider assuming they don't use encryption).

Is there a way to mask or encrypt the emails being routed through the alias provider?

Sad. Stack wallet devs did it in a month and a half And they wrote their own BIP47 dart library to accomplish it!

What about end of year? I don't think they'll have it by then either.

Friendly wager? I say they won't have sending to BIP47 payment code merged in the main repo until after conference day.

A sat saved is a sat earned

Very much looking forward to this!

Will the client be iOS only or both iOS and Android?