this post was submitted on 23 Sep 2023
159 points (97.6% liked)
Games
16371 readers
976 users here now
Video game news oriented community. No NanoUFO is not a bot :)
Posts.
- News oriented content (general reviews, previews or retrospectives allowed).
- Broad discussion posts (preferably not only about a specific game).
- No humor/memes etc..
- No affiliate links
- No advertising.
- No clickbait, editorialized, sensational titles. State the game in question in the title. No all caps.
- No self promotion.
- No duplicate posts, newer post will be deleted unless there is more discussion in one of the posts.
- No politics.
Comments.
- No personal attacks.
- Obey instance rules.
- No low effort comments(one or two words, emoji etc..)
- Please use spoiler tags for spoilers.
My goal is just to have a community where people can go and see what new game news is out for the day and comment on it.
Other communities:
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Oh it definitely would be grossly negligent, but the amount of technical systems I've seen that somebody should have a stake in but wasn't actually involved with... well, if Legal's purview ends at writing up those terms, Compliance made sure they're up in an appropriate place and nobody thought to put "make sure they are automatically involved of any change affecting this" on the checklist, all the boxes have been ticked and they won't notice until the fallout starts hitting.
In an ideal world, any change to the master branch of that repo or to the repo itself should require the approval of a technically versed member of Legal/Compliance (or one of each, if they're separate teams). In reality, that approval process may well exist only on paper, with no technical safeguards to enforce it.