Avatar
CappyNate🍁
18fcc139950a9cce3fee5ee4f4f46f3e3f0e338277dcc8bcd692b3ce0e94084e
Tech, money, startups, free-markets. Sidelined by undiagnosed neurological issues since 2020. 🕔 heatstr.vercel.app (Busiest Nostr hours) Banned by LinkedIn Nov 11, 2024.

Easy. Two wallets, two accounts. Zap publicly, funnel back privately. Rinse, repeat.

The key is a hierarchical ability to revoke your WoT endorsement.

When you revoke a bad actor, you also revoke everyone that bad actor brought into the web too.

The branch gets cut off, then the market re-evaluates the leftover pieces of that branch, to decides who to endorse back into the WoT. Carefully, so their sponsor doesn't cut them off.

Something is wrong with those stats.

2 weeks ago the same days showed like 25% lower and downtrend. Now upend.

Look super close. The data got flat out changed.

Yup. Exactly. VPN's have effectively already been banned by the internet.

Replying to Avatar jb55

They weren't kidding they trained it off Reddit. 🤣 🤦‍♂️

IRS costs USA $4.7T per year.

Or, do direct Lightning to Fiat exchanges exist in Canada?

I usually went from WoS Lightning, to On-Chain Shakepay, Convert to CAD, Send to bank.

That's 4 steps and tons of fees. Not practical for a business processing regular payments.

Physical. Cool will check Zaprite.

Wallet Of Satoshi is so easy to use. But Bitcoin hesitant merchants won't want to hold BTC after accepting it. So I'm looking for an easy way to get them back to fiat.

nostr:npub1hcwcj72tlyk7thtyc8nq763vwrq5p2avnyeyrrlwxrzuvdl7j3usj4h9rq do you have any plans to offer fiat settlement? Either directly, or via partner? Actual fiat, not stablecoin.

(I notice you team up with Moonpay but they don't work in Canada.)

What's the easiest Lightning POS that automatically settles into Canadian Dollars? Either end of day, or per transaction.

#AskNostr

Good that you aren't. As you mention, others will.

Batch muting will occur regardless. It can't be stopped. The key fight against it is being able to see it occurring. To expose + address.

The second we can't see it (private), we're hooped.

I just put a post up, feel free to attack it. This definitely isn't a client-side or Damus issue, so not directed at you. Seems like a protocol-wide issue.

Private Encrypted Mute Lists could be catastrophic to #Nostr.

Muting users is an important function on a P2P level. Batch muting will occur no matter what. It can't be stopped, nor should it.

But the key to keeping batch muting in check is via PUBLIC mute lists. Because if batch muting starts to be abused, at least we can see it occurring, and possibly address it.

The second that mutes go private, we can no longer see it. Huge swaths of users can be shadowbanned, without anyone knowing the extent, and without any ability to address it. Defeating the entire purpose of a censor-resistant protocol.

Mute lists should have remained public. Further, mutes should be extensively monitored for abuse and mass #censorship formations.

If every Bitcoin financial transaction can be publicly auditable, then every Nostr event should be publicly auditable too.

Don't trust. Verify. Remember?

Unfortunately the encrypted mute NIP likely opened Pandora's Box.

That's cult response.

There's nothing wrong with muting. Muting is excellent. P2P muting.

The second you add batch muting and private muting, the game changes entirely. A function can now be weaponized without anyone knowing. Creating a shadowban effect with no way of stopping it.

All mutes should be public. And a mute monitoring service should be paramount to ensure batch muting isn't being weaponized. This can only be done publicly.

If every Bitcoin financial transaction can be public, every Nostr event can be too.