6 ms·
the thing is, making backups on a blog is actually non-trivial. if i host my own then it's easy to just have an automated backup of the database or the static
by em-bee 5y ago
the thing is, making backups on a blog is actually non-trivial.
if i host my own then it's easy to just have an automated backup of the database or the static files. but on any online tool it depends on the APIs that are available. if there is RSS i could find an RSS download tool, but if not then it would most likely have to be manual copy-paste which you have to remember to do and is quite inconvenient if you are on the road.
- tppiotrowski 5y agoMost simple blogs today can get by with a git repository and a github action that converts Markdown to HTML and pushes the output to free static hosting.
- em-bee 5y agowell yes, that's what i meant with hosting my own. but if you use svbtle, medium or substack or any other hosted platform, how do you back up that?
- Irongirl1 5y ago"but for a non technical person it is too much to ask.” *Waves hands frantically* over here that's me....and it is just one reason I keep talking myself out of blogging.
- slim 5y agoIMHO it's as trivial as CTRL-S after you publish the blog post. If you care
- em-bee 5y agothe point is, it's manual, and any manual process is messy and errorprone. you can forget to do it or you can be on a device where it is not practical, or simply not have the time. and saving that whole html page instead of the actual text also produces a very messy result. have fun restoring that.
- chipotle_coyote 5y agoSure, it depends on your blog software and/or your workflow. I don't know how good Svbtle is in terms of its API, or indeed, if it even has one. I would personally suggest that if you're using blogging software that has no APIs for either exporting or importing, you should carefully consider whether that software is a good choice (and if you are creating blogging software that has no APIs for either exporting or importing, you should get on at least the first and ideally both). Svbtle's most obvious original competitor/inspiration, Medium, appears to have at least rudimentary export capabilities, and it's has a publishing API for years -- I could write an article in an editor that supports its API, like Ulysses, and publish right to it. Of course, I could also write an article in any editor and just copy and paste the Markdown to Svbtle, and then just...save my articles in their original form. This has been the way I've written anything much more considered than, er, replies on HN for many years, and it doesn't require whatever I'm publishing on to have any concept of an API whatsoever!
- em-bee 5y agoas a programmer you can probably rig together a script that will extract your content, but for a non-technical person that is to much to ask. the best solution would probably be a prompt in the web-editor of the site to save your text once you are done writing it. like publish and save in one step or something like that. and a url that exports your content as a zip archive.