Conversation

Notices

1. Moon (moon@shitposter.club)'s status on Saturday, 04-Feb-2023 07:33:45 JST Moon

   • Mauve 👁💜
   @cuaxolotl @mauve it's an incentives thing, no one has seriously attacked it. Kademlia mainline DHT as implemented doesn't have serious protection against spinning up invalid nodes and shitting up the address space. However, while you can do that trivially (the node IDs are literally just a random 160-bit integer) each node keeps multiple lists of other known nodes at exponentially further away from itself in the keyspace. It periodically polls these nodes for liveness and keeps track of and ranks them according to how long they've been up. So, if you need to find something and you have access to a nodeid/ip combination that you have some out of band means of knowing it's been around for while, you can query it and it will forward requests to its neighbor nodes preferring the longest-lived ones. Effectively this means that if I shit up the network with a million fake nodes tomorrow, but your bitorrent client cache still has nodes from yesterday, your searches will be alright. If you come onto the network for the first time tomorrow though, and you just have to pick a random node to start from, your odds are as bad as what percentage of the nodes on the network are now fake ones. additional problem: just because a node is long-lived doesn't mean it's good, nodes don't really know that except if they try the node's info and it's valid, your node keeps an internal reputation for those nodes but afaik all attempts to make this info shareable to other nodes don't work.
   
   there are some extensions to kademlia that make the node id to be a cryptographic hash and make it dependent on the ip/port so you are extremely limited as an attacker in making plausible fake nodes but i don't know if anybody even uses that and in any case not enough to matter. also problem with that is if your node changes ip/port its reputation has to start over because it will need a new node id. but like i said nobody uses it, but it does demonstrate the difficulty in addressing the problem.
   • iced quinnsmas :blobcatsanta: (icedquinn@blob.cat)'s status on Saturday, 04-Feb-2023 07:33:42 JST iced quinnsmas :blobcatsanta:

     in reply to

     • verified neko :verified::verified::verified::makemeneko:
     • Ademan
     • Mauve 👁💜
     @roboneko @cuaxolotl @mauve @Moon @ademan filecoin was supposed to be their answer to this.
     Disinformation Purveyor :verified_think: repeated this.
   • verified neko :verified::verified::verified::makemeneko: (roboneko@bae.st)'s status on Saturday, 04-Feb-2023 07:33:43 JST verified neko :verified::verified::verified::makemeneko:

     in reply to

     • Ademan
     • Mauve 👁💜
     @mauve @ademan @cuaxolotl @mauve @Moon well someone has to host the data at the end of the day. so if literally no one has ever pulled a particular piece of data up then where are you going to get it from except from the origin?
     
     or in the case of a busted implementation you have to pull it up out of band so someone would have to go to the trouble of then explicitly loading that back into the network on a node that works properly
   • Moon (moon@shitposter.club)'s status on Saturday, 04-Feb-2023 07:33:44 JST Moon

     in reply to

     • Mauve 👁💜
     @mauve @cuaxolotl I need to do a deep dive on ipfs sometime because I don't know it as well. I know it's pretty similar but that's all.
     
     I can tell you though that the use of IPFS on NFTs is in significant part a shell game, tons of NFTs use IPFS links for their data but I have found that attempting to look up the data using any IPFS gateway except the marketplace's or special provider's own very frequently just does not work. But that is more of an NFT thing than IPFS thing. The protocol is working fine, the marketplace's gateway is just busted (and they seemingly never get fixed) and no one else is sharing the file so you just have to use a regular HTTPS request to their gateway for the file.
   • Ademan (ademan@thebag.social)'s status on Saturday, 04-Feb-2023 07:33:44 JST Ademan

     in reply to

     • Mauve 👁💜

     wait does ipfs require explicit “seeding” ?

     Man for all it’s faults, freenet takes another W if that’s true…

   • Mauve 👁💜 (mauve@mastodon.mauve.moe)'s status on Saturday, 04-Feb-2023 07:33:45 JST Mauve 👁💜

     in reply to

     @Moon @cuaxolotl Yeah, I feel like with #IPFS being more popular lately we'd at least see people attempting black hole attacks on ipfs.io or on some popular NFT collections.

   • Moon (moon@shitposter.club)'s status on Saturday, 04-Feb-2023 07:34:29 JST Moon

     in reply to

     • verified neko :verified::verified::verified::makemeneko:
     • iced quinnsmas :blobcatsanta:
     • Ademan
     • Mauve 👁💜
     @icedquinn @roboneko @cuaxolotl @mauve @ademan some NFT projects are using a blockchain that stores the image data on-chain, it's called Arweave. I also started hearing there's another blockchain that now lets you store up to almost 4MB of arbitrary data per transaction on it, it's called Bitcoin, been meaning to check that out.