WriteFreely VS simonwillisonblog-backup

Mastodon is a microblogging service, so not meant for large bodies of text. This is why the text entry box is small, the columns are somewhat narrow (especially in deck mode) etc.

Platforms like https://writefreely.org/ , which are designed to be for blogging and long-form writing, are the place to write this. Write Freely federates so one can follow accounts and interact with posts via Mastodon etc.

Write Freely, open source writing space

Docs - https://writefreely.org/

It's all about federation, in these federated networks all these servers talk to eachother and exchange messages about stuff going on on the servers. So it's easy to set up a hidden service for the webui of one of them, but it's sometimes quite obscure to try and set up the federation for one of them. It depends on what settings they honor and what other types of encryption and authentication they require and stuff. But, if you put some effort in ahead of time, you can make it really simple: I don't know how to do it in rust(lemmy is written in rust), but here's a neat example of how to do it in Go: https://github.com/writefreely/writefreely/pull/710 which requires no complicated configuration.

An alternative to Plume is WriteFreely, which is a pretty clean & simple experience. Just don't expect to much regarding customization.

I also wish write.as were more popular. It's like old Medium, but less popular but with a more reader-friendly business model and self-host-able (AGPL v3)

And since you've mentioned you want to write a blog, take a look at WriteFreely: https://writefreely.org/

> I’ve been running that for a couple of years in this repo: https://github.com/simonw/simonwillisonblog-backup - which provides a backup of my blog’s PostgreSQL Django database (first converted to SQLite and then dumped out using sqlite-

I'm curious, what is the reason you chose not to use pgdump, but instead opted to convert to to sqlite and then dump the DB using sqlite-diffable?

On a project I'm working on, I'd like to dump our Postgres schema into individual files for each object (i.e., one file for each table, function, stored proc, etc.), but haven't spent enough time to see if pgdump could actually do that. We're just outputting files by object type for now (one tables, function, and stored procs files).

My personal blog runs on Django + PostgreSQL, and I got fed up of not having a version history of changes I made to my content there.

I solved that by setting up a GitHub repo that mirrors the content from my database to flat files a few times a day and commits any changes.

It's worked out really well so far. It wasn't much trouble to setup and it's now been running for nearly three years, capturing 1400+ changes.

I'd absolutely consider using the same technique for a commercial project in the future:

Latest commits are here: https://github.com/simonw/simonwillisonblog-backup/commits/m...

Workflow is https://github.com/simonw/simonwillisonblog-backup/blob/main...

If you really, really need to be able to see a SQL schema representing the current state, a cheap trick is to run an automation on every deploy that snapshots the schema and writes it to a GitHub repository.

I do a version of that for my own (Django-powered) blog here: https://github.com/simonw/simonwillisonblog-backup/blob/main...

My blog is Django and PostgreSQL on Heroku, but last year I decided I wanted a reliable long-term public backup... so I set up a scheduled GitHub Actions workflow to back it up to a git repository.

Bonus feature: since it runs nightly it gives me diffs if changes I make to my content, including edits to old posts.

The backups are in this repo: https://github.com/simonw/simonwillisonblog-backup