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.

Comments on Do SE users have the right to have their SE posts removed from Codidact? If so, how?

Parent

Do SE users have the right to have their SE posts removed from Codidact? If so, how?

+6
−0

I don't know what the etiquette is here for bringing up Stack Exchange, and I don't want anyone thinking I'm trying to start any cross-site drama. In fact, I'm hoping to snuff any such drama out before it begins, by resolving the issues detailed below in a diplomatic fashion. I'm posting this on the overall Meta instead of the Writing Meta because, while the dispute is specific to Writing, it could apply to other sites on the network.


There is currently a user on Writing.SE who is objecting - quite vocally - to the fact that their questions and answers have been imported to Writing Codidact under an account bearing their name. I won't repeat their exact statements on the matter, but their belief is that hosting posts that they never wrote, under an account in their name that they never created, could mislead people into thinking the site is more active than it is.

My understanding is that the Creative Commons license gives Codidact the right to repost content from Stack Exchange as long as it credits the originals - which it does - and therefore, this site has done nothing wrong. Nonetheless, I can also understand why someone would object to having content posted under their name in a context that they disagree with.

Setting aside the reasons for this user's disagreement, or whether their objections are valid: do they have any recourse here? Is there a way they (or other SE users) can have their imported posts and profile(s) removed from Codidact, and if so, how?

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

General comments (3 comments)
Post
+1
−0

My understanding is that the Creative Commons license gives Codidact the right to repost content from Stack Exchange as long as it credits the originals

Yes, the Creative Commons licensed knowledge is free and can be displayed anywhere as long as you abide by the conditions of the license. Any objection of the author after the original publication to sharing the knowledge is ineffectual.

However, one of the other main points raised seems to have been the creation of fake or ghost user profiles, i.e. user profiles that looked like they would have been created by real persons with activity over many years, while that was not the case. They might even have earned reputation. These user profiles have a sentence "This user was automatically created as the author of content sourced from Stack Exchange." which may sound a bit odd if you assume that users must be real persons (then they cannot really get created).

It might be that this was simply the easiest way to import content from SE, but maybe there should be a way to not count the fake/ghost users as users but as something different and make the difference better visible in the user interface.

Of course users can become inactive at any time, but these users have never been active at all, so they aren't really users in the sense that they never used the service, I'd argue.

I think there is something about that second point, we should not continue to create user profiles automatically anymore (if we ever import more data) and we should think about ways how to demote the affected user profiles. We basically have content that has not been written by a human user of the network and we should have ways to show that and include it in the workflow.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

2 comment threads

Less of an issue going forward (1 comment)
Stub users (1 comment)
Less of an issue going forward
Mithical‭ wrote almost 3 years ago

We've moved away from importing content from SE, especially mass-imports. It's unlikely to be much of an issue in the future.