Haveno

Start a tor daemon with SOCKS5 proxy:

$ tor socksport 9050

Then run yt-dlp through it:

$ yt-dlp --proxy socks5://127.0.0.1:9050 <your arguments>

Yes you’re right. This is why the swap/bridge UI will simply be a website using remote RPC nodes, like most other dapps today. Only liquidity providing will require installing a program, because it will have to operate 24 hours a day and sign transactions itself on behalf of the user. But even then, we could imagine a network of decentralized liquidity providers based on MPC, to whom users could delegate their liquidity directly from the web app, without installing anything.

And yes once BTC is implemented, it would likely work natively with most of its forks such as BCH.

No, hyperliquid is a separate chain with its own (rather small) validator set, much like THORChain, Chainflip, and most “decentralized” bridges today. This one would directly settle atomic swaps between 2 arbitrary chains. Not a single additional validator trusted except those of the target and the destination chain.

How did you discover this was bypassable ?

Ah yeah that sucks, but you can access it from another lemmy instance over federation, like so: https://lemmy.ml/c/monero@monero.town

https://monero.town/communities

Yes, just create an empty room with only you inside

https://kycnot.me/?categories=exchange

Couldn’t you use HMAC with shared secret key to authenticate messages while keeping plausible deniability? Since the key is only supposed to be known to the 2 parties, the recipient can deduce that a message was actually sent by the sender if he did not create it himself. I think that’s what OTR was using.

Of course, but v1.x only supported gocryptfs. Also, new encrypted file systems may be added in the future.

To type with only one finger, there’s 8Vim.

:help i_CTRL-H

 or CTRL-H  Delete the character before the cursor (see i_backspacing                                                       about joining lines).

From a security point of view, it’s better to create a dedicated network for each of your containers, as apps won’t be able to communicate with each others directly.

You can even not setup networking at all and use UNIX sockets instead. However, back-end apps will need to support that.