3 ms·
Dear author, if you're reading this: please don't write such a superficial entry. It doesn't actually bring any resolution to the "I get things are bad, but wh
by pmlnr 6y ago
Dear author, if you're reading this: please don't write such a superficial entry. It doesn't actually bring any resolution to the "I get things are bad, but what are we doing to fix it?" /Tomorrowland/ problem, and it could.
Link to static generators that can import WordPress. Link to `wget --mirror` tutorials to archive. Link to https://www.archiveteam.org/ https://www.archiveteam.org/ so people could participate. Mention the Web Archive, point to IPFS, and to DAT.
SHOW SOLUTIONS. Lamenting won't fix it.
Personal story: yes, dynamic sites suck. My 2002 archives are static HTML; no problem getting them. 2004 is a PHP4 CMS, I needed a Debian Sarge to run it. 2007 is FUBAR character encoding mismatch between server, HTML, any DB, plus PHP < 5.3 with MySQL > 5.6. 2010 and up is WordPress, but if you don't save it all - MySQL same version, WordPress same version, all plugins the same version, etc - it's hard work to get it back.
- brunoamaral 6y agoIf you mean the article’s author, that will be me The site is only marginally aimed at developers, it is mostly for people in communication or marketing fields. Some of the ones I know are not even aware of the problem of content decay (lets call it that for now). It is also about the mistakes the web community made while building the sites we use daily. Not assigning any blame, the web will always be uncharted territory. Most of all, I wanted to write down that we saw good things being built. There are a lot of good reasons to keep moving forward. Regarding tools, and as side note, that blog is running on https://goHugo.io https://goHugo.io , a static site generator, and uses the self hosted version of https://commento.io https://commento.io to manage comments. It’s my way of trying to make it future-proof.