Did you read the quote? Point was the it’s lazy name-matching, not actual targeting people with objectionable social media posts.
Discussion
Like if we want to have a law which says social media posts promoting the Palestinian cause is illegal material support of terrorism then get that law passed or get the courts to rule that social media posts are material support.
Then go and investigate and arrest people who commit that crime. If convicted of the crime, then they can either directly be deported or serve their sentence and then be deported.
But what’s happening is not that legal process. It’s using an AI bot to find posts which might express a political view which might be by the person you think it is, which might be illegal. If it’s a crime, get a warrant to get records from social media companies and identify the actual person responsible for posting that illegal material.
Personally I’m on Nostr because I don’t believe the state has any business punishing people for their speech. But sounds like you the idea that a government official can just decide what people can and can not say.
Both of you are idiots. One of you because you don't understand justice, and the other one because you believe in justice.
We did some zap tests on this note… we made six attempts to⚡zap this note, at jimbocoin@btcpay175473.lndyn.com, over a period of 23 minutes. Six of the zaps were successfully paid... Please check for 6 satoshis received. Problem: we found that your lightning address server **did not** produce any zap receipts. This means that nobody else could see see that you got zapped... no number appears next to the ⚡icon after zapping.... We recommend that you use a cloud-based Lightning node to get more reliable zaps.
Zap receipts reveal the location of your node and are generally a really terrible idea.
Also I’m lazy and haven’t bothered to set it up
Given that zaps require a Lightning Address, do Zap Receipts add any more bad stuff? Also since Zap Receipts are sent via Nostr relays, I'm vague on how they would actually reveal your location. They can be sent by any computer, anywhere. In our case they're sent by our web application a Rizful.com, the same one that receives the http request to initiate the whole "zap" dance according to Nip-57.....
AFAIU they work through generic HTTP callbacks. Implementing a LN-Address server can create invoices without being on the same server as the node, or it can be behind a reverse proxy to hide it. You can proxy the outbound response but (a) I absolutely refuse to have a TLS client in my lightning node 🤮, (b) some websites block Tor anyway so callbacks may not be as reliable and (c) proxying through Tor is a bunch more work than just serving being a reverse proxy.
Generally the zap design is horrendous and only makes sense for custodial wallets that already run a bunch of HTTP infra. Luckily there’s a better way (just literally do a BOLT 12 payment and have the payer post the payment proof as a nostr event, rather than making the payee’s lightning node somehow nostr-aware), but need movement there.