Add a way to block certain words per player #5323
Labels
No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/license
3. source/mod upstream
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#5323
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Parents wish to protect their children from possibly harmful words in chat. We need to maintain a list per player, which the parents in lieu of their children can extend by themselves.
Here's an implementation: https://github.com/devBurgSto/cleanchat/tree/main
Apparently this is more complex than anticipated. cleanchat cannot be integrated easily into our rather complex setup.
Contrary to the cleanchat solution, the filtering needs to happen in the output.
Maybe we need a limited account solution, where the limited accounts (of children) can be administred by other accounts (owned by the parents).
AliasAlreadyTaken referenced this issue2024-03-14 05:47:46 +00:00
We will need something like this to handle all of our needs X)
(I mean general "graph" for routing/processing messages...)