Story time. There will be a couple crypto wallet addresses at the end of this one.
This is something that will stay up, maybe clear till the midterm election.
And it needs a significant amount of disk space, for unpacking and sorting and such.
0xc6301a7f5a750Aec37280ECabe45956405A4F92C
Nope, can't use any sort of cloud. Bare metal, encrypted drives, all that kinda stuff is required.
Nobody you know can tell you anything more about this. It's not a social media thing. At all.
So there you have it. If you know and approve of my past work, this is opportunity knocking.
More from Crypto
1/ Bitcoin: a bold new world.
Satoshi published the white paper on 10/31/2008. Right at the moment of peak despair during the 2008 financial crisis. Trust had been lost in a world that ran on trust.
2/ But why October 31st? It certainly wasn’t because Satoshi was a fan of halloween, it must have had a deeper meaning. With all of his actions, he demonstrated a careful precision.
He had been working on Bitcoin for at least a year and a half before publishing the white paper.
3/ “I believe I've worked through all those little details over the last year and a half while coding it, and there were a lot of them. The functional details are not covered in the paper, but the sourcecode is coming soon” - Satoshi Nakamoto
4/ On August 18, 2008 Satoshi registers registers https://t.co/rMWwiEwtxT through https://t.co/Uj8lMr10kB.
Satoshi was ready and waiting to hit the send button throughout 2008. What was so special about October 31st?
5/ I believe that Satoshi published the Bitcoin white paper on 10/31 as a hat tip to the ancient Gaelic festival of “Samhain” which was also the date in which Martin Luther nailed his 95 Theses to a church door. Both represent an end of the old and the beginning of the new.
Satoshi published the white paper on 10/31/2008. Right at the moment of peak despair during the 2008 financial crisis. Trust had been lost in a world that ran on trust.
2/ But why October 31st? It certainly wasn’t because Satoshi was a fan of halloween, it must have had a deeper meaning. With all of his actions, he demonstrated a careful precision.
He had been working on Bitcoin for at least a year and a half before publishing the white paper.
3/ “I believe I've worked through all those little details over the last year and a half while coding it, and there were a lot of them. The functional details are not covered in the paper, but the sourcecode is coming soon” - Satoshi Nakamoto
4/ On August 18, 2008 Satoshi registers registers https://t.co/rMWwiEwtxT through https://t.co/Uj8lMr10kB.
Satoshi was ready and waiting to hit the send button throughout 2008. What was so special about October 31st?
5/ I believe that Satoshi published the Bitcoin white paper on 10/31 as a hat tip to the ancient Gaelic festival of “Samhain” which was also the date in which Martin Luther nailed his 95 Theses to a church door. Both represent an end of the old and the beginning of the new.
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
The UN just voted to condemn Israel 9 times, and the rest of the world 0.
View the resolutions and voting results here:
The resolution titled "The occupied Syrian Golan," which condemns Israel for "repressive measures" against Syrian citizens in the Golan Heights, was adopted by a vote of 151 - 2 - 14.
Israel and the U.S. voted 'No' https://t.co/HoO7oz0dwr
The resolution titled "Israeli practices affecting the human rights of the Palestinian people..." was adopted by a vote of 153 - 6 - 9.
Australia, Canada, Israel, Marshall Islands, Micronesia, and the U.S. voted 'No' https://t.co/1Ntpi7Vqab
The resolution titled "Israeli settlements in the Occupied Palestinian Territory, including East Jerusalem, and the occupied Syrian Golan" was adopted by a vote of 153 – 5 – 10.
Canada, Israel, Marshall Islands, Micronesia, and the U.S. voted 'No'
https://t.co/REumYgyRuF
The resolution titled "Applicability of the Geneva Convention... to the
Occupied Palestinian Territory..." was adopted by a vote of 154 - 5 - 8.
Canada, Israel, Marshall Islands, Micronesia, and the U.S. voted 'No'
https://t.co/xDAeS9K1kW
View the resolutions and voting results here:
The resolution titled "The occupied Syrian Golan," which condemns Israel for "repressive measures" against Syrian citizens in the Golan Heights, was adopted by a vote of 151 - 2 - 14.
Israel and the U.S. voted 'No' https://t.co/HoO7oz0dwr
The resolution titled "Israeli practices affecting the human rights of the Palestinian people..." was adopted by a vote of 153 - 6 - 9.
Australia, Canada, Israel, Marshall Islands, Micronesia, and the U.S. voted 'No' https://t.co/1Ntpi7Vqab
The resolution titled "Israeli settlements in the Occupied Palestinian Territory, including East Jerusalem, and the occupied Syrian Golan" was adopted by a vote of 153 – 5 – 10.
Canada, Israel, Marshall Islands, Micronesia, and the U.S. voted 'No'
https://t.co/REumYgyRuF
The resolution titled "Applicability of the Geneva Convention... to the
Occupied Palestinian Territory..." was adopted by a vote of 154 - 5 - 8.
Canada, Israel, Marshall Islands, Micronesia, and the U.S. voted 'No'
https://t.co/xDAeS9K1kW