fog VS nheko

I had an idea that you could shard the blockchain into multiple parallel networks representing a fraction of the total supply each. This could spread tx volume among each sub-network. Combined with something like Fog for txo recovery could greatly increase the upper bound of scaling on the base layer.

https://github.com/mobilecoinfoundation/fog#overview

This explains the issues fairly well. tl;dr most blockchains require a large CPU and/or network expensive sync which is prohibitive on mobile. As a fix/hack many web and mobile apps have a SPOF gateway which the client must trust absolutely.

“Monero isn't fast enough and doesn't support transaction recovery (it also has probabilistic linkage which MobileCoin doesn't due to our use of secure enclaves). We spent almost 18 months building MobileCoin Fog to solve the second problem (https://github.com/mobilecoinfoundation/fog). It's a non-trivial stack of code to allow users to recover strings from servers they don't control without the operators of those servers being able to learn what strings are being recovered. Don't get me wrong, we stand on the shoulders of giants, but there's a lot of new tech here.”

I personally love Dash. One thing that was a requirement for me was that privacy in the system can't be optional if you want to give system-wide guarantees about the privacy of the system. That is to say, non-privacy-protecting transactions weaken the privacy of correlated privacy-protecting transactions. Second, I don't personally think CoinJoin goes far enough, specifically there's still a transaction graph to analyze. MobileCoin does not have a transaction graph which is a distinguishing factor from other cryptocurrencies. Finally, other privacy coins have implemented encrypted ledgers (see CryptoNote), which is something MobileCoin has; to the best of my recollection CoinJoin does actually have an encrypted ledger which is a big distinguishing factor. In order for users to recover transactions from an encrypted ledger, you need an encrypted recovery service which, again to the best of my knowledge, no one had ever invented. This is where Fog comes in, which allows fast mobile recovery of user transactions even in an encrypted ledger (https://github.com/mobilecoinfoundation/fog).

Hi,

Before you label MobileCoin a scam, I would encourage you to take a look at the Github. I think you'll see that we've made a lot of very carefully considered choices on how to deliver a great payments experience without many of the compromises other cryptocurrencies have chosen. Of note, the speed of transactions, much greener energy design, privacy-protections, and mobile-first UX are differentiators. Many cryptocurrencies have some of these features, but I don't know of any other that has all of them.

Believe me, I have a lot of feelings about how absurd cryptocurrency has become in the last decade. At its core, I still believe that there is something beautiful in decentralized ledgers and I think that this is the way that the world will settle debts over the next hundred years. Signal chose MobileCoin because nothing else met their performance and privacy standards. In order to meet those goals we wrote a lot of new technology that is fundamentally different from how other cryptocurrencies are architected today (check out our oblivious RAM implementation, for example: https://github.com/mobilecoinfoundation/fog).

I love Signal and I started MobileCoin to help fund their work. For me, a world with Signal in it is a better place.

Look at this, notice anything different? https://github.com/Nheko-Reborn/nheko/issues/new/choose

Nheko has been around for a number of years. Never used it myself though.

https://github.com/Nheko-Reborn/nheko

Matrix clients hit different than pretty much any other chat client I've use before. Theres multiple clients I've found like nheko, moments, element that are a pleasure to look at and smooth as hell. Even better you can have users use web services like Element Web to sign-up and chat. Its sick.

The Nheko flatpak is official. Just compare the source to the nightlies we build and upload to our nightly repo.

Like almost every client out there it has no support for e2ee. I was happy to find https://nheko-reborn.github.io (I'm a KDE user so Qt apps are preferred).

There's also FluffyChat or Nheko if Element is too heavy.

I probably wouldn't have guessed that `e.dataTransfer.items` gets cleared at the first await (since I'm not a proficient web developer), but I would've been extremely wary of this code in general. Additionally (not tied to async-await but race conditions in general), is `item.getAsFileSystemHandle()` a TOCTTOU vulnerability where the type of an item can change between folders and files and symlinks etc., while this code is running?

Rust's & vs. &mut system largely eliminates shared state hazards in both threading and asynchronity (&mut is exclusive/unaliased and can't be mutated by other threads or event loop jobs, and & is difficult and unidiomatic to mutate), though it doesn't solve async cancellation errors (https://carllerche.com/2021/06/17/six-ways-to-make-async-rus..., discussed at https://news.ycombinator.com/item?id=27542504), or filesystem TOCTTOU (https://blog.rust-lang.org/2022/01/20/cve-2022-21658.html as well as user code).

Qt event loop reentrancy is fun(tm) as well. It looks like a blocking call, but spawns a nested event loop which can do anything (but rarely enough to lull you into a false sense of complacency), resulting in segfaults like https://github.com/Nheko-Reborn/nheko/issues/656 (workaround at https://github.com/Nheko-Reborn/nheko/commit/570d00b000bd558..., I didn't look into it). And Qt lacks "easy" await syntax and a framework based on calling red functions (though I didn't look into C++20 coroutines yet, perhaps https://www.qt.io/blog/asynchronous-apis-in-qt-6 or https://github.com/mhogomchungu/tasks or https://blog.blackquill.cc/asynchronous-qtquick-uis-and-thei...?).