Core services CoC approach #3
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
spoons.technology/plots#3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
A goal of the project is making it easier to use small/self-hosted tech with people generally. This includes not locking people out for unexpected reasons.
For the core services (and in particular, authentication), having a normal "no cretins" policy might be counter-productive.
We should certainly have a CoC, but perhaps it should be looser? There may be something we can do with flagging accounts so service-providers need to opt in to hosting those users?