Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Post History

84%
+9 −0
Q&A Deficiencies in the Terms of Service

This is already being discussed in a comment thread, but I'm bumping it up to an answer for visibility and so it can be voted on. "We may update our terms from time to time without further notic...

posted 2y ago by Monica Cellio‭

Answer
#1: Initial revision by user avatar Monica Cellio‭ · 2022-05-01T16:50:19Z (almost 2 years ago)
This is already being discussed in a comment thread, but I'm bumping it up to an answer for visibility and so it can be voted on.

>  "We may update our terms from time to time without further notice to you, unless notice is required by law. Your use of the Service after the Terms are updated constitutes your acceptance of the updated Terms."

As a user, I would be very suspicious of a TOS document that includes that.  It invites abuse, especially if the community has no way to validate when a TOS change was made.  It opens us up to suspicion that we could sneak unfavorable changes into the TOS, something that other companies have done.  We want to be open, transparent, and accountable to our communities here; it's one of the things that sets us apart.

I agree that we need to be able to modify the TOS; any service that exists for long enough will run into situations that require changes.  However, I think we *must* notify users, *in advance*, as a matter of principle and possibly a matter of law.  (I don't know the legal requirements of every jurisdiction in which we have users.)

We don't have code for this now, but I think we'd need to add a way for an administrator to send an inbox notification to every user on the network.  I don't know if we need email notifications if we have on-site notifications, and I don't know how hard it would be to send them, but we at _least_ need the on-site notification, in my opinion.

----

I agree with the other points you raised: severability, linking the privacy policy, and enabling changes (I'm just disagreeing on implementation of this last).