blue_rog's comments

blue_rog | 3 years ago | on: Evolution of the Ethereum proof-of-stake consensus protocol

Nitpick:

Why do the first two images after the LMD-Ghost section [1] look like they were made on an iPad? All the other images are made using proper tools. I didn't realize that the letter in the first image was a V because it looked like a N. Feels slightly inconsistent.

[1] - https://github.com/ethereum/pos-evolution/blob/master/pos-ev...

blue_rog | 4 years ago | on: I made $50K in three days with NFTs

Although you may be right, OpenSea (the NFT Marketplace used in the article) does lazy minting. Of course, one can still not make any money if no one buys the NFT.

The author writes about it here:

> There's a bit of nuance to how OpenSea does things. They do so-called lazy minting. While you may need to pay an initial gas fee to list a new collection, each NFT listing does not require any fees. This works because the NFT is not actually minted yet. It gets officially minted once the buyer pays the gas fees to mint the artwork on the blockchain.

blue_rog | 4 years ago | on: WhatsApp – Security of End-to-End Encrypted Backups [pdf]

Slight Nitpick: This is only available for Apple to Samsung devices.

However,

> Unfortunately, it’s still not possible to migrate your chat history [from iOS] to a different Android phone, but WhatsApp is planning this in the future. It’s also not possible to migrate your chat history from Android to iOS right now.

blue_rog | 4 years ago | on: Algorithmic Math Art

Previous HN Discussion (2018-Nov-07): https://news.ycombinator.com/item?id=18397804

blue_rog | 4 years ago | on: Twitter starts to require login to view tweets

> "I can understand them not fixing their search because that increases engagement..."

Do you have any citations for this?

blue_rog | 4 years ago | on: On academic writing: a personal note (2016)

> That is a big problem tho, because it means journalists can't understand the papers. ...

When I thought about this, I immediately thought of a "TL;DR" section for any academic paper... until I realized that that's what the Abstract / Conclusion is sort of meant to be.

> ... the majority of academic CS papers are opaque and inaccessible like most other academic papers I've read.

The majority of CS papers' Abstract / Conclusion are also quite 'opaque and inaccessible'. Having gone through a fair share of CS papers myself (being a part of CS research), trying to get into a new area of CS is really hard when I try to read more recent academic papers, not just because of the technical jargon involved, but because of the unnecessary complex sentences that are required to convey the author(s) idea. A lot of things could be made simpler and easier to grasp. I largely agree with "it is helpful for people to bring this up and make people (especially people in academia) realize that this is a bigger problem than they think."

blue_rog | 4 years ago | on: Affinity 1.10

Thank you for the reference for "Breaking Paragraphs into Lines". I attempted to implement something like this (quite naively) a few years ago; to read something in detail makes me realize the impressive lengths people go to in order to do something as 'simple' as breaking paragraphs into lines and further realize how little I appreciate 'tiny' things like this.