141–150 of 171 posts
- https://github.com/nalinbhardwaj/shiit-coin
- https://www.youtube.com/watch?v=_dZpRryIuQ0In the same vein: https://github.com/william-fields/witless
I have also built a site designed to poke a bit of fun at the idea of artificial scarcity on the internet: https://ipaidthemost.com/ Came up with it before NFTs, but it's only more relevant these days.
I see that CSVCHAIN is "held in cold storage on this USB drive" a 1 GB thumb drive. This seems to imply an upper bound on the number of NFTs on CSVCHAIN. How, I wonder, does the creator of this project expect to scale CSVCHAIN beyond this limit? Additionally, can we secure guarantees that the project owner is safely ejecting the USB drive in question?
Once Roy makes some $ he could horizontally scale to a 2GB drive. Or 2 1GB drives and keep one in his sock draw so it's distributed in his house.
Minor nitpick: I believe you wanted to write "vertically scale".
Earlier quoted context omitted.
Check the name in the private key ;)
Ok, yeah I did think it was part of the joke. Still tho, what is the point of this page? Is it trying to say 'you dont need a blockchain?' or 'this is a deliberately bad solution that is solved by a blockchain'?
Where's the smart contract capability? Smart contracts are important in certain applications, which is why I store purchases in XML and do transformative contracts in XSLT. Version 2.0 of XSLT is Turing-Complete, with the added advantage that XSLT syntax is a specialized form of XML, so I only have to use one syntax for coins and contracts. I call mine Dotcom Bubble Chain.
It may or may not surprise you to find out that the U.S. Navy came ->this2018, so that we could use XSLT and other XML technologies so that they could "Enable maximum use of commercial products built to this standard", "Improve cybersecurity at the data element layer by using the XML Security Assertion Markup Language (SAML) protocol", and "Enable compression of data using the XML EXI specification for efficient bandwidth usage over limited satellite communication channels".
Critical security flaw: right-clicking is enabled!
I don't understand why people view the ability to copy something as a negative with NFTs. Everything can be copied. Even physical objects can be copied. Why does a museum buy a Van Gogh when they can just commission a replica, or easier yet, take a photo and print it on canvas?
A photo of a Van Gogh is not a Van Gogh. But JPEG bytes that SHA-256 to 97db5f2753176670ae8b2d8a2aad44d8bb830aee768629488685f4fc1d7a75f1 will also have a copy hash to the same value. The copy is the original, in a way you can't do with a Van Gogh.
NFT fans try to fix this by making something other than the art itself 'non-fungible', but in the real world it's the art itself that is fungible (and where it's not, such as buying a CD, you don't see people freaking out about how valuable their Taylor Swift RED album #22,724,123 is so special and unique).
Earlier quoted context omitted.
Check the name in the private key ;)
Ok, yeah I did think it was part of the joke. Still tho, what is the point of this page? Is it trying to say 'you dont need a blockchain?' or 'this is a deliberately bad solution that is solved by a blockchain'?
I see that CSVCHAIN is "held in cold storage on this USB drive" a 1 GB thumb drive. This seems to imply an upper bound on the number of NFTs on CSVCHAIN. How, I wonder, does the creator of this project expect to scale CSVCHAIN beyond this limit? Additionally, can we secure guarantees that the project owner is safely ejecting the USB drive in question?
Where's the smart contract capability? Smart contracts are important in certain applications, which is why I store purchases in XML and do transformative contracts in XSLT. Version 2.0 of XSLT is Turing-Complete, with the added advantage that XSLT syntax is a specialized form of XML, so I only have to use one syntax for coins and contracts. I call mine Dotcom Bubble Chain.
> I call mine Dotcom Bubble Chain. It may or may not surprise you to find out that the U.S. Navy came ->this 2018 , so that we could use XSLT and other XML technologies so that they could "Enable maximum use of commercial products built to this standard", "Improve cybersecurity at the data element layer by using the XML Security Assertion Markup Language (SAML) protocol", and "Enable compression of data using the XML…
That's quite a lag. Peak XML was probably 2000 if I recall correctly. That said, XSLT is pretty cool from a language standpoint. I wouldn't want to program in it all day anymore than I'd want to program all day in Brainfuck, but you have to admire the weirdness of it.