Vmody2

This will change in some years though. Conversion will cost less gas with L2. Things are progressing quickly on those problems. Dexs and liquidity pools will have near zero fees.

Personally, I think unless coinbase pivots, their current business model is not sustainable in the long term. But right now, coinbase is capturing value in a way that the early majority of crypto's adoption curve can digest.

> - Booleans in the API are `true` or `undefined`. Seriously.

But why???

I choose to read "tries" as the data structure and I am endlessly amused at the pun.

Pretty cool to see non-crypto projects being built using IPFS.

I'm a technical writer for a tech software start-up, but I started in sales. There's always some content that needs to be written. Blogposts, documentation, whitepapers, etc.

I started by... well writing. I wrote a some blogposts, and a few of them trended on HN. Eventually, when we hired our CMO, he saw what I had been putting out and asked me to help out more. At a certain point, it made sense for me to transition entirely to writing.

Since you're not a professional writer, don't expect to be given a lot of writing responsibility. You basically have to prove yourself. If you have an editor at your company, work with them. I didn't have any formal writing training, but I applied the feedback I got from our editor and slowly my quality improved. It took me about 4-5 months before I was fully trusted to write quality pieces without hand-holding.

Given that you're a software engineer, you have the domain knowledge to write some very useful content. It's just about finding your style.

Considering I'm flying tomorrow, this is a reassuring read.

But cabins aren't the whole story. There's arguably more human interaction in the airport and terminals before the flight itself (check in, security, buy a coffee)

Quick search came up with this: https://www.forbes.com/sites/suzannerowankelleher/2020/07/20... which has some more cautionary numbers.

This is why it's important for STEM and tech people to have some understanding of liberal arts. "Understanding" means having perspective, it's easy to get caught up in our world, thought patterns, echo chambers, and biases. I think that's why curiosity is such an important trait, it promotes understanding, not the accumulation of facts. Next time you're at a book store, pick something up on a topic that sounds interesting that's outside of your traditional scope.

Nailed it. I played fortnite consistently for 2 years. They milked everyone for in-game purchases. This is fun to watch play out, but at the end of the day they're both large companies with fat margins.

Symmetric keys encrypt the entire session but asymmetric keys encrypt each communication during the session.

But yeah, non embedded systems aren't as constrained. At least for practically generating SSH keys, RSA is just as fine.

This story is still developing, but I think a forced buyout or outright ban is shortsighted.

The underlying fear is the impact that a foreign entity will have on our political and social fabric (because America has never done that before). It's a valid concern, especially after Cambridge Analytica. But TikTok falls into the same regulatory challenge forces that can impact change through social media platforms. Building a better framework is a long term solution that encodes into law American values, transparency, and constraints by the legislative branch, not precedent set by the executive branch.

At the same time, every time there is a major hearing against big tech, it's always disappointing.

Hello, author here. First off, thank you for taking the time to read this.

The original draft started out much more technical than this version, but it was simplified to read less like a whitepaper. In the original draft, I discussed the Authorization Code Grant with the PKCE extension, which is for public clients (clients that cannot be trusted):

  "The barebones authorization code grant is used for server-side applications, where confidential clients are trusted with a secret. By using the PKCE (Proof Key for Code Exchange) extension, this same flow can be used with public clients like browsers or mobile applications. The only modification to this flow is cryptography.

  1. Client generates a random string of length 43-128 characters and turns it into a URL-safe 256 hash. Other hashing methods can be used

  2. Client directs the resource owner to sign into the authorization server. The hashed string is included as a parameter in the query

  3. Resource owner signs in and approves client, then redirects back

  4. Client makes an HTTPS POST request for a token. Included is the unhashed randomly generated string

  5. Authorization server hashes this string with the same hashing method (SHA256) and compares its calculated hash to the hash received in step 2. If the hashes match, and access token is issued

  The trick here is knowing that the odds of two hashes with different inputs being the same are infinitesimally small and can be ignored. If even one character is different in the input, the outputted hash will be entirely different. By sending the hash in step 2 and then the original input string in step 4, the authorization server can verify it is still communicating with the authorized client by comparing what it received to what it produced. Any fraudulent client would have no way of knowing what the input string is."

I still have some more research to do for the OIDC article, but in theory, yes. OIDC runs as an identity layer on top of OAuth. The only thing that makes OIDC unique is that there's a widely accepted "scope" that provides standardized ID information, which is bundled into an ID token and sent with the access token. So there's no reason two applications that are built on the same protocol can't communicate.

Good question, I'll include it when I write the next one.

Connect2id and OAuth.net were great resources. But unless you were already familiar with the topic, they were a bit difficult to follow. That's why I started this article with some analogies!

Hi all, the author here, this article is somewhat of a thought-piece. It was a bit difficult to write as there is much to be explored between blockchain and K8s, but I tried to synthesize the information out there into a coherent narrative. I would appreciate any feedback, especially critical.