28
Phi Am I
28a9404d6e6f4f94a77a30bc23cb1a130cc44bc35acf38bcdf3f1348c7c4b16d
Replying to Avatar Seth

🎉 Exciting news from the zap.cooking team 🎉

We are thrilled to announce the launch of the newly redesigned website of https://zap.cooking 🥳

Expanding off the open source concept built by nostr:npub1q7klm2w94hyq3qdm9ffzpahrrq0qcppmjrapzhz0rq6xgq3fdrnqr6atmj, we’ve reimagined this nostr client to provide you with a better culinary experience 👨🏻‍🍳 It was a team effort months in the making, lead by nostr:npub1chakany8dcz93clv4xgcudcvhnfhdyqutprq2yh72daydevv8zasmuhf02 with design support from nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac

In this updated version, we offer a sleek design while enhancing speed, recipe discovery and better tools for community engagement!

Celebrate with us by visiting zap.cooking and explore the fresh look, exciting features and authentic recipes!

Let us know what you think! 👨🏻‍🍳⚡️

The reaction of nostr users when Zuckerberg's first #ActivityPub post bridged through to people's feeds was hilarious. I swear, I could hear the sound of a million nostr users simultaneously hitting the mute button.

Well, Zuckerberg bridged his #Threads platform to the #fediverse which is also bridged to #nostr.

So, anyone that uses a nostr relay* that is also a bridge to #mastodon can follow Zuckerberg and get legal, because he owns the rights, live #sports feeds on #nostr

And yes, that is Zuckerberg's legit, bridged, Threads account..on #nostr.

Open protocols means everyone gets to use it.

* wss://relay.mostr.pub

Replying to Avatar Nichro

Trying to choose a mobile wallet for someone to graduate to from custodial (WoS). I narrowed it down to a few choices based on my use case, wonder if people could give their 2 sats.

Use case:

- Already have and use a hardware wallet

- Use Alby for for nostr management (login, zaps) and pocket change sats

- Do not want to go too deep into channel management, do not want to run and manage a node (yet. that will come with a btc node as planned)

Narrowed choices:

#BlueWallet

Versatile, simple, clean. On-chain & Lightning both. Even multisig. But Lightning requires own node / LndHUB so it would be attached to Alby, which is probably fine. Lots of wallet types possible. Swiss army knife feel.

#Mutiny Wallet

Cross-platform. Can be PWA so usable over web like Alby. Also simple. On-chain and Lightning both. Has minimal channel management, an ideal level probably. Enough to get familiar with it without it becoming a big worry for day-to-day UX. I dig Mutiny's vibe oh! also has Nostr integration, so it's a possible for Alby replacement altogether. If keeping Alby, may be redundant to have Mutiny if it'll serve the same purpose. I'm definitely keeping an eye on Mutiny development, one of the most interesting projects to me atm.

#Phoenix Wallet and #Muun Wallet

These ones felt similar to me, both like almost natural nice light step away from Wallet of Satoshi on the custodial-noncustodial move. Channel management seems minimal like Mutiny. Simple combined-balance display. Phoenix has in-app Tor as an option and possibility to link. Muun has an alternative to the usual seed phrase for backup/recovery, including using email (like Wallet of Satoshi im guessing).

#Zeus

Feels the most advanced in capabilities and target users out of all the bunch. Even if using Quick Start to use the embedded node/LSP, all those possible configurations and settings are sure to trigger curiosity OCD. Possibility to link with Alby LndHUB and use it from there. The UI looks serious and luxurious, I dig it. Am I getting the wrong impression of this wallet? I would see it as the next wallet to "graduate" to when closer or ready to run own node as a big boy. Oh, Nostr friendlist import is always a nice add.

Thanks for coming to my TED talk.

Leaning towards Muun or Phoenix, with Muun slightly edging first because of the email-based recovery. Can be nice to not have to keep and secure yet another seed phrase if the wallet is going to be for pocket change basically.

If anyone feels like sharing their 2 sats, misconceptions I have or suggestions, still appreciated!

#bitcoin #asknostr #lightning

*Cross-posted on https://stacker.news/items/476688

Muun uses submarine swaps so fees can be very expensive. Phoenix is a real non-custodial lightning wallet but their routing fees are half a percent, which is well, I no longer use Phoenix after they jacked their fees up that high.

I use Zeus now.

It might be a bit overwhelming at first to a novice, but it's well worth putting in the effort to learn all it has to offer.

Replying to Avatar william.maggos

nostr:npub1ae09w6hwmzpkys24e6pltm2yujvwhtxwv2e909f0gtvc5mnp0a2qhzr0mm

because relays are intended to be bigger and there to be less of them afaik. I love that it's pretty easy to throw up a server and should get easier. same with moving your account. it's also understandable that someone would start a server if they have their own website and email using their own domain name. that's something I see most companies, orgs, govs and especially journalistic outlets doing (if the fedi wins!)

#Nostr doesn't use accounts though. It uses public key - private key cryptography. Your nostr account isn't on any server, the same way a Bitcoin wallet isn't on any server.

An npub string is a users public key on the nostr network. They also have a corresponding private key that starts with nsec that they use to cryptographically sign new posts.

You've crossed over into...the #Nostr Zone!

Fun Fact: nostr uses have the ability to #zap you Bitcoin rather than a boring old 'like' if you add a lightning address to your nostr profile.

Replying to Avatar mrclownworld

More nuts to grab

cashuAeyJ0b2tlbiI6W3sibWludCI6Imh0dHBzOi8vbWludC5taW5pYml0cy5jYXNoL0JpdGNvaW4iLCJwcm9vZnMiOlt7ImlkIjoiMDA1MDA1NTBmMDQ5NDE0NiIsImFtb3VudCI6Miwic2VjcmV0IjoiaW82ZDhCR1VOTzRCUmlBVjNwcFNMcTZNV1pGa3BCZlkrWEVjY0xUK2twaz0iLCJDIjoiMDI5NWQ1MTViOTI3MzNhMmEwMjNmNzQ2OTMyZDQwY2JiY2Y4ZjVlMmZiZDVlMTMxZmU0OTEyZGYwMzIyYjg1N2IzIn0seyJpZCI6IjAwNTAwNTUwZjA0OTQxNDYiLCJhbW91bnQiOjEsInNlY3JldCI6InRkN3AxajlQU0JmRzR4MEhuWkVjaU9DRXR2cWtNdDVxcmZPcVorUzl3T009IiwiQyI6IjAzNzNmYmNlMzNkM2NiNDA0Mjk0NmIwYzE2OWYwMDNjMDM1ZTA3NDIwNzQ0N2M2MzZlZTg4NWY1MDUwNjU1MGU2MSJ9LHsiaWQiOiIwMDUwMDU1MGYwNDk0MTQ2IiwiYW1vdW50IjoxLCJzZWNyZXQiOiIwUGJDcEt4OVlBTE9ZRTc1cjA2TkFTUUhLdTFNeWF4d2NYWStYU3VqMWFJPSIsIkMiOiIwMmIwYWE2ZmJmZjRiMjBjYWY2ZjIxZTFiOTBkOWMyYmMzZjk1MjIxMWRmZjU0OTAzZjBkZDk0N2U4OWQ5ZGFkMTYifSx7ImlkIjoiMDA1MDA1NTBmMDQ5NDE0NiIsImFtb3VudCI6MSwic2VjcmV0IjoiUm9BbFZYTTlMRHBPRFV1QVVzdGFTQTJscWxwdCtReUJSTlZzTndoejJpVT0iLCJDIjoiMDI1NzVhYmNkOWMyMTQwZGNlNDdkMzExZDQ0MmNlYjgzNzNiYzAzMmI0NDFjN2QxMzgzYTM2MzE2NGU5MTEyOGJkIn0seyJpZCI6IjAwNTAwNTUwZjA0OTQxNDYiLCJhbW91bnQiOjEsInNlY3JldCI6IitwTHVtdkhqb2FreTlpQkZHMS9WQWFnc1VVUlVNaWxxL1FqSnZOWFk3OWc9IiwiQyI6IjAzNzI1YmQ1MDg0ODUwYzNjODAyZjcwYWQ1NWFhMTA1OWNlZmNlOTNkZDE3N2U5MDE2OTY4ZTlhMmFhZjkwOTdmNyJ9LHsiaWQiOiIwMDUwMDU1MGYwNDk0MTQ2IiwiYW1vdW50IjoxLCJzZWNyZXQiOiJGUm1uMEdFRE1nREZXbHhNM21oRVJFdS9pNWs1S3hYdEFlWnFqNktocEVVPSIsIkMiOiIwMmNjMDc2ODliYTYyMmZjYTA2ODgwNmQzZTMxMzI2OWZjOTdhZDFhYWE5Y2RjNjA0MTdjNGRkNDJhNGRkNTcxYzcifSx7ImlkIjoiMDA1MDA1NTBmMDQ5NDE0NiIsImFtb3VudCI6MSwic2VjcmV0IjoiYVR3c2RLZ2pqb2ZDTGk1am1mNFZaTXJwd2NWdU9lZWZQdUV3bGtwSVV2ND0iLCJDIjoiMDIwM2NjNzNhY2YwNDVlMjRhZGEwODE3OTdlMzFiODdhOWQ2Zjk2MjhkOTkzNDViNTczYTdlNmI1MDUxZjg2YzkyIn0seyJpZCI6IjAwNTAwNTUwZjA0OTQxNDYiLCJhbW91bnQiOjEsInNlY3JldCI6IitoMjgrQTVFL004RTdpeGtOZGJSSVNndHNGM1ZpMDBYaEdUVm9PTTVDVDQ9IiwiQyI6IjAyMGFmZmE5NzZjMzNlM2VmZmEzYmE4YjkyMGEzOGVlY2I4OWY0ZTM2YTdlYTM5NDhiYjVmOTI0ZmU0MWY5NDBkZiJ9LHsiaWQiOiIwMDUwMDU1MGYwNDk0MTQ2IiwiYW1vdW50IjoxLCJzZWNyZXQiOiJleHhuN25PVis3Y0p4ck16ajlrbThEUzFFT1ErdXRlNjFnUzZRa1kvNWZZPSIsIkMiOiIwMmNlMmI2NjJkNjg4ZTJmOTZkNTNiNGFiYmUxOTFjN2IzOGY4ZTUyMDc0MTJmNzBmYzEzYjFmOWNmMTI2ODE0ZmQifV19XSwibWVtbyI6IlNlbnQgdmlhIGVOdXRzLiJ9

Ok, I'll try one of theses.

cashuAeyJ0b2tlbiI6W3sibWludCI6Imh0dHBzOi8vbG53YWxsZXQuYXBwL2Nhc2h1L2FwaS92MS85dFpMRVZ5a25ydGFHeGVCakVlY2M0IiwicHJvb2ZzIjpbeyJpZCI6IjAwMjM4MjlmMzViNDQ5MjIiLCJhbW91bnQiOjIsInNlY3JldCI6IjZvdGs0RHJyc29FcDcrM0dUSU5oQktlL1J0Vnd0TmtoVldVMWs3aUY3cFU9IiwiQyI6IjAyYjEwZjI1YjdiNzgxZTU1YzIxYmE3ZDQ3YjNlN2QxOTg2MDg1MzJlY2NkMDg2MzdhMjdkYjZhMWRiMzk1ZTlhMiJ9LHsiaWQiOiIwMDIzODI5ZjM1YjQ0OTIyIiwiYW1vdW50IjoxNiwic2VjcmV0IjoiR0JWR1BKU0RkdHp0QVJUeTZ3RkJUdkl5eGg4VENPVmhNeURhL1dOS01hQT0iLCJDIjoiMDI0YTM3NzA5NDEwNTk5M2UwZWI3N2E3ZmRjZjY0ZDc1YzBmMzM3YmI3NzQ2NTNlNGQ2YWJlZDEyNmI2NGQyY2RmIn0seyJpZCI6IjAwMjM4MjlmMzViNDQ5MjIiLCJhbW91bnQiOjMyLCJzZWNyZXQiOiJvWU1US2ozU2k2M2JHQnY1cHJFUS9OTWw5Ri80bXRNVVNEaURXcVlUS2JNPSIsIkMiOiIwMzg3Yjg2NzUwNDA4NmQ4NzUyNzVlNWUzNDAwNGY2YTRkMDlmNDE4MzE5NTJjM2U3YjhiMDkwNmM3YWQ3YjIwZmQifV19XSwibWVtbyI6IlRyeWluZyB0aGlzIG91dC4gRW5qb3kgeW91ciBzYXRzLiJ9

Is there any country on the planet that doesn't limit all payment infrastructure by tax regulation?

A legitimate business accepting Bitcoin payments is going to pay their taxes. Accepting Bitcoin is never going to change that

Someone selling shit on Facebook marketplace and accepting Bitcoin as payment, isn't likely to be of interest to any government. Unless they're seeing Ferrari's by the dozen for Bitcoin.

Replying to Avatar Colby Serpa

I think this is where nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s was getting confused. I’m not suggesting the outbox model that adds relays to your list of relays… your list of relays remain static.

I’m saying to only leverage the outbox model when there are missing notes your list of relays don’t have, that way you are reaching out to the potentially evil relays with a note hash — if the note matching that hash isn’t delivered, then the evil relay can’t do anything but get your IP.

This is more of a hybrid approach…

Read from relays you write to —> clients can store data like relays and sync missing notes with a secondary list of relays using negentropy (snort coded negentropy in typescript already) —> gossip model for fetching missing notes if the first two methods fail.

This seems like a solid plan/layers of redundancy for discovering missing notes…

Thoughts? nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6

Hhhmm, I'm going to go have a think about a way to exploit this model.

Oh the other hand, is note retrieval across relays a problem serious enough to warrant additional automated discovery of relays? A new user with a fresh client is going to have way more trouble than a long time user with a well curated list of relays. How often does a long time user have problems retrieving notes?

I'm not a fan of relays that bridge nostr to mastodon. I don't ever want mastodon posts filling my feed. What happens when the note that can't be retrieved wasn't actually a nostr note, but a bot created cross post from mastodon that I don't actually want to see, by not including bridge relays in my client?

Will that note be forced upon me?

Wait, this is a discussion about implementing a gossip protocol that adds discovered relays to your nostr client.

There are people that aren't happy that public relays have blocked them as spammers. Plus, people aren't adding the spammers private relays to their clients so their spam is effectively blocked, unless you intentionally add their private relay to your client. Then you can see their spam.

They call this censorship.

So their solution is to implement a gossip protocol that discovers new relays and automatically adds them to everyone's clients to force people to see their spam, which you'll have to block by adding the spam relays to blocklists on your client.

Their arguing that it's important that you read what they have to say, even if you haven't subscribed to their relay. They certainly seem to think they are important people.

So, should nostr keep the current method where you subscribe to the relays that relay the notes that you're interested in, or change to a system where you get random relays pushed to you by a gossip protocol and you have to block what you don't like?

Come on now buddy where did I say anything about execution of code? Stop the gaslighting.

Spam, is all I've ever said will be the problem with having relays pushed to clients by a gossip protocol.

I've never, ever said this is in anyway a security problem. So stop accusing me of saying that right now buddy.

But, users can never blacklist 0-day bad relays. It would be a never ending, constantly growing blacklist because there's no upfront costs to setting up a malicious relay. Unlike lightning nodes, that require an investment in Bitcoin to open channels that you put at risk if you attempt anything malicious.

Every day, users would have to put up with the shit from the latest spam relays pushed to their clients, as well as updating the blacklist of the spam relays discovered yesterday.

Spammers will flood any gossip protocol with hundreds of spam relays each pushing tens of thousands of bot generated spam notes.

That is no way I'd ever use a client that kept adding random relays discovered by a gossip protocol. It would also make Nip-65 useless because so many other accounts would be full of gossip discovered spam relays.

Relays should operate by reputation. If I offer a no NSFW, no politics, no crypto filtered relay that had a reputation for filtering everything except cat photos and cooking recipes, shouldn't people only ever use this relay by choice, and not have it forced upon them unknowingly by a gossip protocol?

Just as relays flooded with Alex Jones Protein Shakes spam should never be pushed to anyone.

Gossip protocol to find cheap routes for lightning payments makes sense because it's not being used to distribute human created metadata. There's no benifits to try and exploit this mechanism.

A gossip protocol to distribute lists of human curated relays, each and every one of them having an agenda, blatant or sublime, would be a disaster. It will be exploited because it can and will benefit spammers.

Letting people chose to use a relay that filters NSFW content has to be superior to forcing people to constantly be blocking NSFW relays they don't want.

Gossip model will be exploited by spammers. You'll end up flooded with relays with nothing but notes on penis extenders and Alex Jones Protein shakes.

You'll end up with huge lists of blocked relays that your client will have to use ro keep the gossip protocols from adding all the spam relays constantly.

A gossip protocol will make it really easy for spammers to push their spam relays onto everyone and flood feeds with scammy adds for shitcoins and penis extenders.

Then, well need a second gossip protocol to distribute lists of spam relays that clients can use to filter them from the relay gossip protocol.

And finally, well need human curated lists of clean, nice , inoffensive relays for people to use, that that don't want to deal with all the spam relays from gossip protocols.

Or, we let users add whatever penis extender advertising relays they want to subscribe to manually, or by following someone posting to that relay, giving people a choice rather than having relays thrust upon them that they then have to filter out.

Censored means actively blocking notes. Me, not wanting to subscribe to your relay and read your notes, is not censorship, it's me exercising my freedom of choice.

Are you asking if you should have a second node to do zaps? Then, no, don't.

Install #lnbits on your node and you'll be able to create sandboxed wallets on your node. You can have a sub-wallet on your nose just for zaps. And then, you can add a second wallet you can use for #Cashu. That's what I do. I even have another wallet setup for selling stuff using #btcpayserver.