You may be wondering why @bristoliver rather cryptically RT’d a chart that I posted last night. The answer is not just that he loves quadratic fits on log axes, but that this chart may –and I stress may– hint at a vaccine effect amongst the over 80s THREAD
ok, I lied. but strictly it's not a new graph, just a new trendline (now a quadratic on the log plot). looks um... quite a good fit. so I'd say that was interesting. pic.twitter.com/qkgyMf1ya8
— James Ward (@JamesWard73) January 27, 2021
Been thinking about where we are, where we might be going, what effect vaccines might have and how to tell. This thread may not happen all at once, and will get a bit mathematical in a couple of places (sorry!), but I will put in pictures. It's yet another argument for log scales
— Oliver Johnson (@BristOliver) January 24, 2021






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
BREAKING: @CommonsCMS @DamianCollins just released previously sealed #Six4Three @Facebook documents:
Some random interesting tidbits:
1) Zuck approves shutting down platform API access for Twitter's when Vine is released #competition
2) Facebook engineered ways to access user's call history w/o alerting users:
Team considered access to call history considered 'high PR risk' but 'growth team will charge ahead'. @Facebook created upgrade path to access data w/o subjecting users to Android permissions dialogue.
3) The above also confirms @kashhill and other's suspicion that call history was used to improve PYMK (People You May Know) suggestions and newsfeed rankings.
4) Docs also shed more light into @dseetharaman's story on @Facebook monitoring users' @Onavo VPN activity to determine what competitors to mimic or acquire in 2013.
https://t.co/PwiRIL3v9x
Some random interesting tidbits:
1) Zuck approves shutting down platform API access for Twitter's when Vine is released #competition

2) Facebook engineered ways to access user's call history w/o alerting users:
Team considered access to call history considered 'high PR risk' but 'growth team will charge ahead'. @Facebook created upgrade path to access data w/o subjecting users to Android permissions dialogue.

3) The above also confirms @kashhill and other's suspicion that call history was used to improve PYMK (People You May Know) suggestions and newsfeed rankings.
4) Docs also shed more light into @dseetharaman's story on @Facebook monitoring users' @Onavo VPN activity to determine what competitors to mimic or acquire in 2013.
https://t.co/PwiRIL3v9x
