> Using a static website like this isn’t new – my inspiration was Twitter’s account export, which gives you a mini-website you can browse locally. I’ve seen several other social media platforms that give you a website as a human-friendly way to browse your data.
I've read somewhere that Telegram exports work this way, you get a bunch of raw files somehow organised with directories and browsable by themselves, with a tiny local static website to browse them more conveniently.
So different from the last such mass export I used: Google Takeout, which produces a dumb dump of cryptic xml and raw files named in some nonsensical (to the user) scheme. To this day I'm not even sure I got all the data I asked for before deleting it cloudside.
Facebook does (or at least used to when I left it a few years ago) this too. They give you a huge dump of your data and photos, with an html file to help you navigate it better.
HTML ready sucks for archiving.