https://t.co/D9Qwt9Y6zu
1. Ultimate blockchain, NFT and crypto learning thread ЁЯСЗ
(warning 100's of hrs of content)
https://t.co/D9Qwt9Y6zu
https://t.co/DRQwQWHVho
https://t.co/B8HfP2USOH
https://t.co/btUuUALVc8
https://t.co/ypUJxbCBRT
https://t.co/61llZyS0z5
https://t.co/4gQEOviQ5A
https://t.co/PTSoWCUYJN
https://t.co/qp161jfGve
https://t.co/5aPOxzIgne
https://t.co/P6tJZvlnHC
https://t.co/9jx6rCIQHa
More from Crypto
Out of curiosity I dug into how NFT's actually reference the media you're "buying" and my eyebrows are now orbiting the moon
Short version:
The NFT token you bought either points to a URL on the internet, or an IPFS hash. In most circumstances it references an IPFS gateway on the internet run by the startup you bought the NFT from.
Oh, and that URL is not the media. That URL is a JSON metadata file
Here's an example. This artwork is by Beeple and sold via Nifty:
https://t.co/TlJKH8kAew
The NFT token is for this JSON file hosted directly on Nifty's servers:
https://t.co/GQUaCnObvX
THAT file refers to the actual media you just "bought". Which in this case is hosted via a @cloudinary CDN, served by Nifty's servers again.
So if Nifty goes bust, your token is now worthless. It refers to nothing. This can't be changed.
"But you said some use IPFS!"
Let's look at the $65m Beeple, sold by Christies. Fancy.
https://t.co/1G9nCAdetk
That NFT token refers directly to an IPFS hash (https://t.co/QUdtdgtssH). We can take that IPFS hash and fetch the JSON metadata using a public gateway:
https://t.co/CoML7psBhF
Short version:
The NFT token you bought either points to a URL on the internet, or an IPFS hash. In most circumstances it references an IPFS gateway on the internet run by the startup you bought the NFT from.
Oh, and that URL is not the media. That URL is a JSON metadata file
Here's an example. This artwork is by Beeple and sold via Nifty:
https://t.co/TlJKH8kAew
The NFT token is for this JSON file hosted directly on Nifty's servers:
https://t.co/GQUaCnObvX
THAT file refers to the actual media you just "bought". Which in this case is hosted via a @cloudinary CDN, served by Nifty's servers again.
So if Nifty goes bust, your token is now worthless. It refers to nothing. This can't be changed.
"But you said some use IPFS!"
Let's look at the $65m Beeple, sold by Christies. Fancy.
https://t.co/1G9nCAdetk
That NFT token refers directly to an IPFS hash (https://t.co/QUdtdgtssH). We can take that IPFS hash and fetch the JSON metadata using a public gateway:
https://t.co/CoML7psBhF
You May Also Like
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
