LeetPeet reports: *Popular request*: A way for p ... #2685
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
4 Participants
Notifications
Due Date
No due date set.
Depends on
You do not have permission to read 1 dependency
Reference: your-land/bugtracker#2685
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?
LeetPeet reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
cf.
Question is, do we want all this info in the command?
With https://gitea.your-land.de/your-land/yl_settings we could make it that people choose what info they want displayed there.
allowing players to manage how data about them is shared is ... interesting. PII should clearly be blocked by default, but if we really want to manage player data, players should be able to opt-out of even sharing their last login time from other players. admins need to have access to PII for various reasons, but i'm not trying to propose a solution to that problem currently. this is about players controlling what other players can know about them.
looking at the information about players when they use /bug ingame Indeed. Private messages and mails are protected, and the information if someone votes regarding a building is sacrosant. But once /bug is used, all other relevant private data becomes public.