Core services CoC approach #3

Open
opened 2025-12-19 23:57:58 +00:00 by tom · 0 comments
Owner

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?

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?
Sign in to join this conversation.
No labels
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
spoons.technology/plots#3
No description provided.