their snapshots are marked as copy on write, so my assumption is that for every write, there is replication somewhere.

I might be wrong here, but my understanding is that their snapshots are the kind we find in modern filesystems (ZFS/BTRFS/…) : that is a point-in-time kind of functionnality, where a file will be duplicated (and the original version then will only belong to the snapshot) only when it is written to. This is just the way snapshots are implemented here - and a rather common way of doing it efficiently - not a reliability feature.

Nope, doesn’t seem so at all. I’ll stay with the web version of LibreOffice, myself (and OnlyOffice as a second choice if the first one were to went south)

It seems recent versions of Lemmy don’t have that problem anymore, right?

Well, I’ve finally found a way using plemmy instead of Lemmy.py. Basically :

from plemmy import LemmyHttp

lemmy = LemmyHttp('https://my.lemmy.instance/')

lemmy.login('username','password')

lemmy.edit_community(community_id=XXX,banner="http:/yyy.tld/img.jpg")