abra app cmd ... with backup-bot-two
i ran it again but it didn't timeout now...
you can also do it from the admin web ui, that's what i did finally. the secret should be hashed anyway, so the issue is with autogenerated secrets (unless abra can be told to hash secrets! a wild…
i tested it myself and works ok! just a note @decentral1se before upgrading abra (i was on 0.10 rc but i'm not sure which one now) i could tell when a new config was being installed, with 0.10…
they do warn you it's super unsupported and not even bother them about it:
https://docs.gotosocial.org/en/latest/advanced/builds/nowasm/
you're already providing a cache, so this is…
yeah i did ask them about ram usage on the upgrade from 0.17 to 0.18 and was recommended to try out the nowasm version. i'll collect some energy to ask properly...
@decentral1se left you a note to add a note for the next release. i think this may be an issue for upstream too, but i don't have the energy to go through with a report...
when you merge, and before tagging, could you add something like this to the release note?