How to backup a live gotosocial database
rm /gotosocial/backup.db
sqlite3 /gotosocial/sqlite.db "VACUUM INTO '/gotosocial/backup.db'"
How to backup a live gotosocial database
rm /gotosocial/backup.db
sqlite3 /gotosocial/sqlite.db "VACUUM INTO '/gotosocial/backup.db'"
@lianna @gotosocial @Codeberg For a web interface: Maybe have a look at Elk: https://elk.zone. You can either log in there, or selfhost it. It’s super easy to selfhost. It fits #GtS very well, because it is super lightweight and is actively developed, too.
migrate things: „My Mastodon instance is closing down in April, so I had to move to a new instance. And picking instances is hard, so why not run my own?“ https://www.splitbrain.org/blog/2025-03/12-mastodon_to_gotosocial_migration /via @splitbrain
Yes, I totally missed it in the announcements: https://gts.superseriousbusiness.org/@gotosocial/statuses/01JSHRBM7B8H7KNA05BVKSMRH8
What a banger release. #GTS is serving (kant)
Yes, #GtS is forcing it to lowercase. As I understand it, there's an issue open for it, but it hasn't been fixed yet.
@kopfkind Most current list available here:
https://thefedi.wiki/gotosocial/user/client-apps
All tested and work very well. Use Masto-FE if you want Mastodon-style experience. Otherwise Phanpy or Elk are amazing
Ada beberapa format video yang ga bisa diplay ama #gts
Overal udah lumayan banget sih dibandingkan tahun lalu.
Trus sekarang postingan udah bisa diedit juga
@electragician I'm not sure but this kind of message looks like to be more from your client than you instance; after maybe the instance returned an error and then client return its own error, I'm not sure...
you need to check your #gts settings, for upload normally it's also 40MB by default.
I usually have error messages for upload of video when video codec is not recognized (so when I have video I usually convert my video with ffmpeg with a supported codec to be sure to be able to upload them)
@electragician On my side the image is properly displayed, it has been downloaded and put in cache on my #gts server
It's a small image (1.64MB JPEG file)
Maybe you can take a look on your configuration file, if it has been modified, but default max-size to download media is 40MB so it should be downloaded
# Size. Max size in bytes of media to download from other instances.
#
# Lowering this limit may cause your instance not to fetch post media.
##
# Examples: [2097152, 10485760, 40MB, 40MiB]
# Default: 40MiB (41943040 bytes)
media-remote-max-size: 40MiB
@crossgolf_rebel morgen aus den #gts netzwerk
@jschwart : aan add-ons hebben we niks: die zullen door veel te weinig mensen worden gebruikt waardoor er niets verandert (bovendien bestaat het risico dat mensen nep-add-ons installeren).
Het gaat om een *combinatie* van wijzigingen die de EU zal moeten afdwingen.
Domeinnamen (inclusief het toenemende aantal TLD's) zijn namelijk het *probleem*. Je kunt ze vergelijken met telefoonnummers of woonadressen, potentieel iets- of nietszeggende strings die van een eigenaar *kunnen* zijn (en morgen van een ander). De enige voordelen ervan zijn dat ze uniek zijn en meestal kort.
De meeste internetters begrijpen echter niet hoe je ze moet interpreteren, zoals dat
www-example·com
iets heel anders is dan
www.example·com
(om het nog maar niet te hebben over IDN's zoals in
"https:⧸⧸lîdl·be/login").
Ik zie geen andere oplossing dan voor *mensen* begrijpelijke en traceerbare identificerende informatie opnemen in websitecertificaten, waaronder bijv. (indien beschikbaar) een KvK-nummer (in tegenstelling tot bij 'whois' kun je bij de KvK wel zinvolle identificerende info vinden). Alleen al betrouwbaar weten in welk land de websiteverantwoordelijke gevestigd is, zou al enorm kunnen helpen tegen oplichting.
In https://infosec.exchange/@ErikvanStraten/113990009126611573 zie je een screenshot van
https://play.google-ivi·com
waar Google Trust Services "gewoon" een ceetificaat voor uitgeeft (te zien in https://infosec.exchange/@ErikvanStraten/114061799937444243).
Oh fein ich hab mein Problem mit fedi.buzz gelöst, erst entmuten dann entfolgen dann klappt es auch scheint nen #GTS bug zu sein, ich werde nicht mehr von mastodon.social voll gespammt.
Dafür hab ich mir die Timeline von norden.social abonniert ;) ist deutlich weniger und ich hab wieder ne Möglichkeit Hashtags local zu Folgen *freu ;)
Anyone using #litestream for an #sqlite DB
I have a 3GB database, and Litestream is replicating it to another server. However, it seems to be running out of control with disk space. On the original server (where the live DB is) is a generations
folder under the hidden litestream folder. It is full of WAL files. Currently over 37,000 files consuming 118GB of disk space.
My config includes retention: 24h
and retention-check-interval: 1h
with a snapshot-interval: 4h
. I understood it would delete anything older than 24 hours. Am I doing something wrong? These wal files go back to the day I started using litestream
#GoToSocial #gts @gotosocial@thefedi.forum
I've just migrated my #gts instance to a new machine... hopefully I've copied all data properly
Anyone using #litestream for an #sqlite DB
I have a 3GB database, and Litestream is replicating it to another server. However, it seems to be running out of control with disk space. On the original server (where the live DB is) is a generations
folder under the hidden litestream folder. It is full of WAL files. Currently over 37,000 files consuming 118GB of disk space.
My config includes retention: 24h
and retention-check-interval: 1h
with a snapshot-interval: 4h
. I understood it would delete anything older than 24 hours. Am I doing something wrong? These wal files go back to the day I started using litestream