Hacker Newsnew | past | comments | ask | show | jobs | submit | f73b054's commentslogin

Surprisingly, this is actually a much more practical solution than what many other people here are proposing.

Sure, if one has money enough to sponsor a trust, then that'll work. But for those with more modest means, storing it on a blockchain is a solid(!) alternative.

The biggest factor here is the choice of the blockchain. One can go with special purpose ones like you suggest, they take care of the details of storing the data, but those blockchains risk losing momentum.

But it would be quite cheap (compared to setting up a trust) to use Bitcoin for this too. Bitcoin isn't meant for this, but there are ways of encoding the website's data and have it be part of the Bitcoin blockchain, spread out over multiple transactions.

The issue there is that the algorithm to deconstruct the data, as simple as it might be, would need to be separately communicated.

A slightly more riskier choice technically superior choice would be to do this on Ethereum, since the exact program for reconstructing the website from the data in the blockchain can also be deployed as a smart contract on the blockchain. So all the great grand children would need to be aware of is the address of the contract, and that it is on the Ethereum main net.

That said, one risk is -- while the specific blockchain might remain, who knows what it'll be called 500 years down the line. So the problem would be, while the website "exists", it's URI might change.

Interesting questions.


The point about the URI changing is interesting. One could imagine the current URL stored in metadata and then "virtual" DNS lookups could be done over time/across chains well into the future.


If you're new, start with "Tailwind CSS: From Zero to Production" (Video playlist, ~1 hour total, split in chunks): https://www.youtube.com/watch?v=elgqxmdVms8&list=PL5f_mz_zU5...

Alternatively, read this (it's a chapter from a book which is meant to help engineers "get" design): https://www.refactoringui.com/previews/building-your-color-p...

The book chapter outlines the philosophy, and Tailwind provides a functional system for putting it in practice.

For both of these, you don't need any CSS background. Not only does the video series teach you Tailwind, it'll also give a foothold onto CSS, and how to use it in practice to make reasonable websites even if one is design-challenged.


You can learn Tailwind but it’s not CSS. You’d be learning a proprietary utility class framework.

I use ITCSS, BEM and some utility classes in my projects.

I also like and use Tailwind’s presets for colors and spacing as SCSS variables - but still write my css.


Tailwind is almost CSS. Most Tailwind classes only apply one CSS property/value.

If you needed to code the same thing without Tailwind you can easily convert the syntax.

I would agree more with “Bootstrap is not CSS.”


> Tailwind provides a functional system for putting it in practice.

Alternatively, you could write CSS to get better at CSS.


Tailwind is CSS. You are writing CSS, just in a slightly different way. It's not a magical framework or a big box of ready-mades.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: