On the website itself, "OS" "Included" and "Not Included" is strange. I don't see that I need "Not Included", unchecking "Included" should show you everything but instead it shows you nothing. I don't see the value of "no os included" verses a copy of Windows that I will overwrite.
Reading the rest of the pricing page gives me the clear impression that it wasn't free initially and then changed it to free recently and the rest of the text on that page wasn't updated. If I am making donations why do I need to be reassured that I can have a refund if I don't like it?
It's what people who didn't understand the separation of concerns with HTTP, HTML, CSS, JavaScript and server side were did by deciding to jam it all into JavaScript and entangle it in code complete and gang of four constructs and then call it superior, easy, efficient, well designed, robust ... It's ... It's simply wild.
HTML content? In the javascript. Style information? In the javascript. A way to negotiate network loading and resources, document structure? You guessed it. Want the back button to work again? More JavaScript. URLs to be universal? Even more!
Eventually you'll get the page to be almost as functional as it would have been by default had you not used any of it.
Read the mdn and w3c documentation guys, I promise you 99.9% of what you want is in there without reinventing it from base principles. It's not 2010 anymore
It's like a bad cook who is trying to fix a poorly made meal by making more mistakes, covering it in salt and oil, smearing honey over it, and calling it delicious.
That article gave an example of a "typical European floorplan". It did have multiple stairs they were just not normally accessible from all apartments. If you had some emergency-only provision to enter your neighbor's apartment and then bust their wall to access the apartment behind it, more than one egress would be possible. Some emergency doors where an alarm would sound perhaps? I come up with all kinds of problems with this, but that was my thoughts looking at that floorplan.
Design flaw. In IPFS every piece of data (even every chuck of large files) is globally indexable on the same namespace. You need namespaces and/or a path to restrict yourself to just the subset of peers that might actually have the data.
It would be possible to add a layer on top of IPFS to include some context with every hash lookup so the search can be more focused, but the original design just assumed it was ok to do a log2 search for every chunk.
That is not a problem specific to IPNS though. Using a DHT for something like IPNS is fine. Publishing roots of large data sets is also fine(ish).
Using it to publish every tiny chunk of a large file is a horrible idea. It leads to overwhelming traffic.
If you publish a few TB of data, due to the randomness of the DHT xor metric you have to basically talk to every node on the network. Add to that the fact that establishing a tcp libp2p connection is much more heavyweight than sending a single UDP packet like in the bittorrent mainline DHT, and you are basically screwed.
In iroh we don't publish at all by default. But if you have to use a DHT, the fact that we have a single hash for arbitrary large files due to blake3 verified streaming helps a lot.
I was confused by the comments here. Surely someone is going to post the Technology Connections video on the toaster. I see you did it indirectly. That video is great.
I always think I will watch just 10-15 and end up watching the whole thing and then wonder why learning about a crappy refrigerator was so interesting.
So I would just have an "OS Included?" checkbox.