Avatar
crimsonleaf363
8829a79aa18928efc9b888590186f24082b45a7a51509aca4d40a20136d69c3a
Running software. Supporting open source projects.
Replying to Avatar arkinox

nostr:npub1a00wj229auzjswlq4s77y4u8eqdx5k9ppatgl8rtv8va65f6mwksum9q3h I want to believe what you're saying but your operating system, which is effectively your hardware, is lumped in with everything else in your business, and this privacy policy states that it collects personally identifiable information from nearly every interaction possible including pen strokes and will share this personally identifiable info with anybody for any reason, including marketers and law enforcement.

If your hardware/OS is private in any capacity, you need to separate it from the rest of your business legalese. I get that websites will track mouse movements, etc, from anon visits and use it for marketing optimization; I've seen this type of privacy policy for websites and other apps. But that shit is unacceptable if it's baked into the OS, and your privacy policy makes no distinction.

We're discussing closed source hardware and software?

Who's running Dojo or RoninDojo?

Replying to Avatar Super Testnet

> is that validation difficulty in the room with us right now?

No, thanks to the fact that no significant amounts of people use monero. During the stress tests, block sizes went way up. Imagine that for years. I don't think regular node operators on cheap hardware could keep up.

> we should have this conversation when bolt12 is actually widely used

Let's have it now: bolt11 already gives users better receiver privacy than a monero public address.

In monero, the sender always knows the recipient's "real" address (the one on the blockchain) and can provably map it to their stealth address. But in lightning payments, the invoice has to tell you the pubkey of the *node* which received the payment (though you can spoof it), but that pubkey doesn't contain any money. It's like a stealth address in monero, except the sender *cannot* map it to the *real* address that received the money, or at least, not necessarily. There are *some* people who've managed to figure out the receiver's address on the blockchain just from their lightning invoice, but even that information is spoofable. In monero, it isn't. So even in this respect, LN > Monero.

> and channel management isnt only for total nerds

It's already easy to manage channels. Try electrum.

> it is *easier for *more people to get *better privacy on #monero

it is only easier for them to get worse privacy. If they are willing to take the steps to get good privacy, setting up an LN node privately is barely more difficult than setting up a monero node.

"Try electrum."

"Setting up an LN node privately is barely more difficult than setting up a Monero node."

You're a wizard, Super!

Replying to Avatar Super Testnet

> Only a select few can arguably claim they have better privacy on Lightning. Vanishingly few Lightning users are transacting privately and non-custodially.

I do not understand this argument. To me it completely misses the point: I argue that self-custodial lightning has better privacy than custodial lightning and your response is "yeah but most people prefer custodial lightning." So? Who cares if most people prefer something inferior? Why does that matter? *You* (or anyone who wants good privacy) can choose the *better* solution. You are not subject to the choices of others.

> Correct me if I'm wrong but your whole forecast seems to rest heavily on technological advancement remaining stagnant over time. Historically we see the exact opposite.

I don't think my argument relies on that assumption. Making blocks dynamic in size with the hope that someday technology will solve all the problems it brings <-- that seems like wishful thinking. Limiting their size to a small value seems like a far better idea: it pushes adoption of layered scaling while also penalizing spam attacks.

> Dynamic block size means fees will always stay low even with increased adoption

I think monero is pitched between the horns of a dilemma: if blocks get big and fees stay low then it means miners do not have to worry about orphan rates, which means mining is centralized. If blocks get big and mining is *not* centralized the miners *do* have to worry about orphan rates, and that incentivizes them to place *their own* limit on the size of their own blocks so that propagation and validation is faster and the orphan rate is smaller. If that miner-selected limit ever applies, you get the worst of both worlds: rising fees *and* large blocks.

> meaning more sovereign usage and better operability with L2s

You're not sovereign if you're not running a node

> Tail emission means we don't have to roll the dice on tx fees securing our blockchain in the future

You do: monero uses permanent inflation mixed with a fixed issuance of 0.6 XMR or less. Permanent inflation means the XMR issued is designed to constantly deflate in value. So at some point 0.6 XMR will have no material value. It will be worth less than 60 cents of today's money. Consequently, miners will need another source of revenue. You're rolling the dice that one will exist.

You can audit the supply. The real risk is in the implementation. It's a tough pitch. It's even harder when there's so much fear mongering and bad faith arguments.

The absolute worst case scenario is the network isn't worth securing.

Ross was pardoned. Let's recognize the real harm done: years of his life lost, productivity stifled, and freedom denied. Society took a big L. It's time to welcome him back to society with dignity. The rest is between him and his creator.

I wondered about this because Cash App doesn't work for me either. I thought it might be risky to enable the exploit protection compatibility mode.

What happened to the keyboard bug in Amethyst? It was about a year ago? You couldnt use OpenBoard or similar keyboards with Amethyst. I don't remember how the bug was fixed.

OpenBoard like keyboards and Amethyst about a year ago. Vitor said there was nothing titWasnt it last year happen last year?