Nothing is safe in absolute terms.

I assumed a certain line of defense in not having auto-updates and wish Google never had switched the default from off to on. Learning that off is not off leaves the user with zero protection against exit scams even if aware of auto-updates. I wonder if OP was really getting updated from iTunes or from testflight.

To my understanding, the BTCPay server integration requires the use of the ln address as your nip05. I don't want to do that.

(Also it's nostr:npub1a3xjg8pngvgm8gcygvlwx3ptu2wsaz88asvmshkl9waznwf4vh3qqrx0r7 server, not mine, so while that's "Uncle Matt" model and thus better than one big WoS waiting to get hacked or "hacked", it's not really self-custodial neither.)

That is ... not funny.

I review security aspects of mobile wallets and the one biggest way of scamming people that without exception all wallets could do is to grow the user base and then push a malicious update that leaks the keys. My recommendation always was to switch off auto-update for any Bitcoin wallets but if the wallet provider can provoke to override this setting, nobody is save.

So on Amethyst I see somebody zapped this 21sat. On Snort I don't see it. nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 is this a bug or does Snort not like that my two test accounts also use the same ln address maybe?

Tell me more! There are ways to deal with DDoS. Would it help to limit access to a relay to a group of paying users? I'm working on that as I always found it weird how relays do not count at all the resources that go towards answering read queries.

Can the message default to "I liked note-id"?

Today is a sad day. I gave up on trying to get started with zapping in a self-custodial manner and set it up with WoS, mainly to get a friend setup quickly, too.

Questions: I zapped myself from a test account that uses the same WoS ln address and there on Amethyst, payment failed with WoS but with BlueWallet it worked ... sort of. Now, in Amethyst I see 500sat zapped but on Snort I don't see it when loading and reloading that same note.

Can I receive zaps now or not?

(Also thanks to those who tipped me without the zap that would tell me what it was for. I'm not sure, clients made clear that those zaps would be anonymous.)

Once again, where is the controversial content that would get banned on Twitter?

https://www.reddit.com/r/watchpeopledie got banned on Reddit but I just ran into something quite similar on Twitter which did not get banned in months: https://twitter.com/1secB4disaster

Thinking back what else got banned for being gory or sexual ... how come, almost nothing of that made its way to nostr yet? Is it because relay operators keep things nice and civilized? Is there anything ban-worthy happening in Chinese or Russian? What are we doing here?

Last time I asked this, the "best" answer was "zaps get banned on Apple". Come on guys, this is not what we are building for, right?

I hope to see stuff on nostr that some government or another genuinely wants to see banned. Wikileaks maybe?

I find his constant references to JFK tiring. This man lives in the past.

"dinner" ... that doesn't look like dinner to me.

Did they? In DMs? I'm pretty sure they would not.

Ok, zapping is over what Damus and Apple are currently fighting but my OP was more aimed at finding the regime critics that finally can voice their opinions freely. Where are these TextNotes that Government X or Y wants to see blocked? Not what Apple wants to get a share of because they can.

You could DM them sats using LNURL "vouchers".

TIL: For waste water treatment, noodle-shaped plastic is thrown into the water so micro organisms get more surface to grow on.

And when those MBBR leak into the ocean, slightly bigger organisms like this crab live on them.

https://void.cat/d/5JzXWoTJdMH1kg1ZsNAAUw.webp

seriously?

Show me a post that needs nostr due to its censorship resistance.

Funny VALKYRIE 😄

https://void.cat/d/4aH3mjLAjmy3Uq8EAYe3XU.webp

https://www.sec.gov/Archives/edgar/data/1841175/000138713123007682/valkyrie-s1a_062123.htm#valkyries1aa018

That is where I see the use of pet names. You would not talk about "nip101" or if you did, you would have something in place that would resolve to an actual parametrized replaceable event via maybe indirection. Or you would explicitly reference Alice.nip101 and then the nostr client would search for Alice's definition of "nip101".

My argument above was that we are probably irrationally shocked by the data volume of things we want to decentralize.

Collaborative curation would be awesome and we could start small but maybe not too small. I would love to move the nip registry onto nostr. Let nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 maintain a list of nips and other approve of the list or not. How hard can it be?

With the WoT idea, I imagine being able to refer to "nip1" in a way ... like %nip1 such that your client would know where to look up what my understanding of "nip1" is. If I define ["nip1", "fiatjaf.nip1"] in the right place, your client would get you there. I think there is little missing for this to work. The idea of pet names is there and the rest can be done with some parametrized replaceable events.

https://github.com/nostr-protocol/nips/blob/master/89.md

Completely automated tests to tell computers and humans apart based on what they said ... once ... is almost impossible today.