1,156 karma · joined April 12, 2019
Unfortunately, the ASR isn't great, so I'm holding off on marketing until it's better. Honestly, if I spent half the time learning the language as I have making tools, I'd probably be fluent by now...
[0]: https://letsyiya.com
* machine learning in tandem with GPUs https://azure.microsoft.com/en-us/blog/azure-confidential-co...
* autonomous key management https://docs.oasis.dev/general/oasis-network/overview#privac...
* signal contact discovery https://signal.org/blog/private-contact-discovery/
These will also work with next-gen enclave tech (mainly in the direction of total VM encryption), but those (AMD SEV, Intel TDX) aren’t as secure as SGX yet, so SGX has continued utility to applications beyond DRM.
It looks like this is targeted towards crypto whale hopefuls who, for whatever reason, store sizeable value in a hot wallet/CEX that's controllable using a phone number/SMS 2FA. The price point of $99/mo supports this hypothesis.
Honestly, not a bad idea. These people clearly have more money than sense.
Check out line 540 of the link above (section 1.7):
Master (hidden service) identity key -- A master signing keypair
used as the identity for a hidden service. This key is long
term and not used on its own to sign anything; it is only used
to generate blinded signing keys as described in [KEYBLIND]
and [SUBCRED]. The public key is encoded in the ".onion"
address according to [NAMING].
You can then follow that to line 2292 (Appendix 2) which describes the aforementioned generation process. It's a bit too long to be pasted here, but it turns out to be elliptic curve multiplication and hashing. This is not encryption for any common definition thereof.In fact, you generally do not use public keys to do encryption at all. What often happens is that you use a key exchange algorithm like Diffie-Hellman to derive a shared secret, which you then use to do bulk encryption using your favorite cipher (some asymmetric cryptosystems permit encryption, but they're much slower than symmetric ciphers, which also benefit from strong hardware acceleration).
You can also use keypairs for signing, key exchange (e.g., DH), key derivation (as used by Tor hidden services), and creating verifiable random functions. They definitely do not imply encryption.
onion_address = base32(PUBKEY | CHECKSUM | VERSION) + ".onion"
CHECKSUM = H(".onion checksum" | PUBKEY | VERSION)[:2]
[0]: https://gitweb.torproject.org/torspec.git/tree/rend-spec-v3.... (section 6)> Please don't comment on whether someone read an article. "Did you even read the article? It mentions that" can be shortened to "The article mentions that."
FWIW I don’t think that the parent comment is wrong, but rather over-generalizing. If you’re close to the project, I’d love to hear a proper rebuttal to what seems to be a common question.
> There is no single service that can go down [...]
> Each piece of content is loaded entirely independently, [...]
Both of these statements can be true, but in fact, what ends up happening is someone puts their site on a pinning service like Piñata or Infura, and then it's right back to being centralized and trackable. Filecoin helps decentralize who pins, but even then, one ends up using a pretty interface like web3.storage since using the real service is just too much overhead for just pushing a page.
I'm personally a big fan of IPFS, but I'd use it to make an entire site reliable for users who care to self-pin.
const canEat = [];
const cantEat = [];
for (const item of myObject) {
const name = item.name.split(',')[0];
(item.value === 'YES' ? canEat : cantEat).push(name);
}
One item I found in "can't eat" is cicada, which is amusing because I would never have thought to try! The distinction between French Fries and McDonalds French Fries is also interesting.[0]: https://www.centre.io/usdc
[1]: https://app.aave.com/markets/?marketName=proto_mainnet
[2]: https://curve.fi/pools (search USDC)
[0]: https://doc.rust-lang.org/book/ch00-00-introduction.html#who...
Obviously `ctx` is the most readable.
[0]: https://developers.cloudflare.com/pages/platform/functions/
The code is well organized, and compile times are short, so at least it’s hackable.