-
-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce new /privacy
group of commands
#1836
Comments
I think
|
Introduced in #1857, but since the design is yet to be completed, I did not introduce full set and limited it to logging, to keep things simple, especially since it's a new feature. I would suggest to add additional commands after logging integration. We can gradually introduce them or use full command reference to add all suitable commands at once. |
Add ability to completely turn logs off, Needed since `/logging` and `/history` didn't stop history logging in the DB, only in files. Command might break something on usage, hence it was primarily introduced for privacy geeks. Privacy command discussion profanity-im#1836
Add ability to completely turn logs off, Needed since `/logging` and `/history` didn't stop history logging in the DB, only in files. Command might break something on usage, hence it was primarily introduced for privacy geeks. Privacy command discussion profanity-im#1836
Add ability to completely turn logs off, Needed since `/logging` and `/history` didn't stop history logging in the DB, only in files. Command might break something on usage, hence it was primarily introduced for privacy geeks. Privacy command discussion profanity-im#1836
Add ability to completely turn logs off, Needed since `/logging` and `/history` didn't stop history logging in the DB, only in files. Command might break something on usage, hence it was primarily introduced for privacy geeks. Privacy command discussion profanity-im#1836
Add ability to completely turn logs off, Needed since `/logging` and `/history` didn't stop history logging in the DB, only in files. Command might break something on usage, hence it was primarily introduced for privacy geeks. Privacy command discussion profanity-im#1836
Add ability to completely turn logs off, Needed since `/logging` and `/history` didn't stop history logging in the DB, only in files. Command might break something on usage, hence it was primarily introduced for privacy geeks. Privacy command discussion profanity-im#1836
Add ability to completely turn logs off, Needed since `/logging` and `/history` didn't stop history logging in the DB, only in files. Command might break something on usage, hence it was primarily introduced for privacy geeks. Privacy command discussion profanity-im#1836
Idea started here: #1827 (comment)
I think we could use something like a new
/privacy
command.Recently we received
/account
./session_alarm
)I think we should group them together in something like
/privacy
.And maybe also include other already existing commands in there:
/os
/silence
?I also think the accounts structure can get too bloated. And we should put some things in a different structure. The settings still can be individual per account. But leave the account structure for really account related settings (I hope you get what I mean).
And things like session alarm need to be off by default and configurable by the user.
So we also need to check that preference like mentioned in: #1827 (comment)
The text was updated successfully, but these errors were encountered: