> Later on Truth Social Mr Trump said the non-fungible tokens (NFTs) were "very much like a baseball card, but hopefully much more exciting".
> The "one-of-a-kind" assets in the digital world can be bought and sold like any other piece of property, but have no tangible form of their own.
> They can be thought of as certificates of ownership for virtual or physical assets.
> Advocates say NFTs are the digital answer to collectibles, but critics have warned about risks in the market, which emerged from the wider world of cryptocurrency. Activity in the space has dropped this year, alongside a plunge in cryptocurrencies.
As I understand it, the actual files of #NFTs tend to be hosted on #IPFS, but if someone doesn't "pin" the files, they can eventually be deleted. And some have been hosted on a regular website, which really stinks if and when the site shuts down or even rearranges and replaces its former content with something new.
> A report for the US Congress this year noted that NFT sales have been used to collect credit card and other financial information, and been subject to other scams.
Which isn't surprising. Every other sales channel has been abused that way, from restaurant purchases to retail stores, to mail order. This line makes it sound like those are unique threats to NFTs, but they are part of the danger when one uses a credit card to buy anything.
By the way, #Trump's #Truth_Social #socnet is supposedly a modified version of the #Mastodon software. As far as I know, it does not federate (so there's no need to get excited about #blockwars and push #fediblock).
Oh ffs, #IPFS changed it's API pretty dramatically, and while there's plenty of examples on how to integrate IPFS with React, Vue, or whatever latest godawful framework du jour, I cannot find a single working example of how to *get a file* from IPFS in the browser.
Afterwards, I thought that they stayed too high-level. They mentioned some similar concepts, such as #IPFS and #Tahoe-LAFS, but it felt like talking to a sales person. I'd rather know a little more about how it works.
If someone were to set up a #RasPi to be a node on one of these types of #peer-to-peer networks, would they need to set up NAT passthrough, or do their protocols already include something like STUN / TURN?
Mostly an academic question, as I’m not willing to potentially open up access to my home network.
When I woke up this morning, my Firefox had upgraded to v57 and of course that meant that New Tab Homepage[0] doesn't work anymore. I guess it actually does work, but extensions aren't allowed (as I learned from the New Tab Override documentation[1]) to load things from the local file system.
So I put it up on #ipfs instead. Now the inline images from #coingecko won't even try to load. No idea why. Tried my localhost gateway and gateway.ipfs.io. Help?
> IPLD is a single namespace for all hash-inspired protocols. Through IPLD, links can be traversed across protocols, allowing you explore data regardless of the underlying protocol.
Seems not super active though. And not sure if they really mapped anything other than #ipfs yet? Lots of #ETH talk in the issues, but not sure of the status.
> “We call these mutable items. So what you could do is generate a public key, which can be thought of as your address, and share this with the world. Then you use this public key to store stuff in BitTorrent’s DHT network. And, because it’s your public key, you (and only you) can change the value pointed by your public key.”
> As mentioned earlier, only a 1000 bytes can be stored (less than 1kB), but Luca points out that it’s possible to store the info hash of a torrent, 79816060EA56D56F2A2148CD45705511079F9BCA, for example. Now things get interesting.
I wonder if ipfs will be put back into Beaker, now that it seems ipfs people have decided on an `fs:` scheme as an interop prefix with things that insist on URIs.