Open Peter-developer01 opened 10 months ago
Storing the user IDs would be impossible. I’ll store the usernames instead. A text file containing those who opted out should be enough. I’ll have to use os.system
to commit the changes while the program is running.
Why you can't store the user IDs? Storing usernames would be a bad idea because two users can have same usernames, chat allows it.
OakBot sends messages with the usernames, not the user IDs. It would be impossible to tell whether (for example) it was user
with an ID of 1 or user
with an ID of 2.
Ah, thanks. No better variant to store this then.
Also, don't forget to make an command to opt-in the pings, if the user wants.
I am testing an implementation
I’m adding a database to this, the command will be setting fishping false
to opt out. You will be opted out by default.
So I've been reviewing my inbox and I see there:
It was fun in the first times. However when you start to see so much "your fish is ready!" items, this is starting to be annoying.
I'm requesting a new command that would allow me to opt-in or opt-out the fish pings.
For example,
You can store the config for each user in the, for example, JSON file. You can of course select any file format you like.
And remember, to avoid the confusion, you store the keys as user IDs, not user names.