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 »

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.

Review Suggested Edit

You can't approve or reject suggested edits because you haven't yet earned the Edit Posts ability.

Approved.
This suggested edit was approved and applied to the post 9 months ago by matthewsnyder‭.

7 / 255
  • As Monica already explained, making the software open source does a lot to reduce the barrier to entry for competitors. This provides both an escape hatch in case codidact does end up following SX, but also is a self-breaking prophecy. The fact that it people could just host their own instance easily will help encourage humility in management, I think.
  • A second step could be taken that would reduce the barrier even more and strengthen the protection against codidact developing problems. The licensing/software availability barrier is solved, but there is still a large advantage in the form of critical mass. If codidact grows large, and then management decides to be evil, yes others could run their own instance but they would have the challenge of acquiring enough users, just as codidact does now.
  • The solution to this would be federation. If codidact instances could share questions and answers, this would empower the userbase to vote with their feet. Of course, federation is technically laborious to implement, and there are some nuances to exactly how it would work. However, it looks like there's already a system for importing questions, so that can be built on to set up full federation.
  • As Monica already explained, making the software open-source does a lot to reduce the barrier to entry for competitors. This provides both an escape hatch in case Codidact does end up following SX, but also is a self-breaking prophecy. The fact that people could just host their own instance easily will help encourage humility in management, I think.
  • A second step could be taken that would reduce the barrier even more and strengthen the protection against Codidact developing problems. The licensing/software availability barrier is solved, but there is still a large advantage in the form of critical mass. If Codidact grows large, and then management decides to be evil, yes others could run their own instance but they would have the challenge of acquiring enough users, just as Codidact does now.
  • The solution to this would be federation. If Codidact instances could share questions and answers, this would empower the users to vote with their feet. Of course, federation is technically laborious to implement, and there are some nuances to exactly how it would work. However, it looks like there's already a system for importing questions, so that can be built on to set up full federation.

Suggested 9 months ago by meta user‭