Closed fthues closed 1 year ago
I'll make a fix, although it might make more sense to update the lemmy endpoint than the bot.
Agreed!
How about adding a (temporary?) config option that when enabled would just skip the whole marking as a bot step, avoiding saveUserSettings
altogether?
IMO it would be better if it would check if it was already marked as bot, and thus only call saveUserSettings when it's not marked as a bot yet? Saves a config setting :)
Agreed!
How about adding a (temporary?) config option that when enabled would just skip the whole marking as a bot step, avoiding
saveUserSettings
altogether?
I am 100% for that as this is somewhat a possible ratelimit that could trip on too many times called ( for example script restarted )
I'll go with the config option. I would use @sylverstream's option if the login response included that information, but as it does not it would just add yet another request.
Added the config option in v0.4.3. Closing this issue.
Every login attempt results in a
user_already_exists
error. This probably happens in saveUserSettings() and looks like it's related to this issue, apparently one needs to include all user data insaveUserSettings()
.