Pouet data-dump opt-in participation request thread
category: offtopic [glöplog]
This is pulled from the comments on an issue in the Pouet .9 github repo. Most people probably won't see this, and while I did comment about it at the end of the open source thread that could be quickly buried.
If you agree to allow your data to be exported in a publicly available data dump, please comment below indicating your wish to be included. This would be helpful to all. Thank you.
Users who have so far agreed:
randomi/randuev
tomaes
psenough
Preacher/elsewhere
Quote:
Just got this idea while washing my teeth: What about dumping the data submitted by people which explicitly agree to see their data dumped ? I can be the 1st one.
Technically it means something like "mysqldump where user_id IN (list_of_users_ok_with_it)", and for now list_of_users_ok_with_it would be me.
It will keep the dump small, legal, and real.
What do you think ?
If you agree to allow your data to be exported in a publicly available data dump, please comment below indicating your wish to be included. This would be helpful to all. Thank you.
Users who have so far agreed:
randomi/randuev
tomaes
psenough
Preacher/elsewhere
FWIW, i don't mind. Not that i contributed much to pouet :)
i don't really understand - does it include only prods/groups/parties etc. that one has added, or also personal data like email, name and so on?
Quote:
i don't really understand - does it include only prods/groups/parties etc. that one has added, or also personal data like email, name and so on?
analogue has previously stated releases won't contain any e-mails, and I believe such a dump described above wouldn't include any information that isn't already publicly available.
But is it not easier to dump the db without all personal user-data instead of waiting for the 18418 users to give their permission. Or did I misunderstood something here?
Yes, you have. This is comment by analogue is from the database dump GitHub ticket started by psenough.
Quote:
I know I'm not the most legitimate to try to make a point about it, but legally we can't.
People added stuff to pouet knowing how their data would be displayed (comments on prod, bbs post in a thread, user profile), they never agreed to have their data dumped in a way that makes it easy to do whatever you want with it.
REST of everything + CSV of selected data (prods, groups, ...) is still doable, and open IMHO, you just can't crunch data about people and what they've written/voted.
We also have moderation stuff, and some people clearly expressed to no see their data out.
@randuev The pb of the database to develop on it is another subject IMHO and is super important, see #42
I don't mind too. If it's to be used for testing and such, I don't care if my account data is in there too.
ah, so this is part of the "we'll work on the 0.9 source as if nothing has happened" campaign. in this case, obviously, no.
Quote:
ah, so this is part of the "we'll work on the 0.9 source as if nothing has happened" campaign. in this case, obviously, no.
Nothing of the sort. I was not trying to take sides here. The reality is that it seems unlikely people are going to get the dump they want in a timely manner. Thus given the prior analogue statements this seems like a likely way to get something out that could be helpful to anyone. I am sorry you feel that trying to bridge things should be obstructed.
I haven't explicitly said so before, but I don't feel what has happened was done in the best or even most tactful manner either. Obviously it would be impossible to pretend nothing happened. However if we all try better to work together, then perhaps this can evolve into something sustainable which I think all this is currently not.
Yeah, sure. Whatever that means. :)
gaspode: the thing is, dumping the db entirely is probably illegal, since users own copyright to their comments and posts even though their content is scrappable. i find it stupid myself. but i'm not a lawyer, i'm guessing neither is analogue, and in light of all the controversy from "the takeover" i am guessing analogue is trying to avoid the risk of enfuriating users further more and so prefers they give their permission for their data to be used on dev dumps.
ok, go ahead. Not much data from me here but...
BTW, how are you going to handle all the "fix me beatiful" requests ? Is that part of the user-owned data as well ? Because if so, I think you've got a problem...
BTW, how are you going to handle all the "fix me beatiful" requests ? Is that part of the user-owned data as well ? Because if so, I think you've got a problem...
I think it's not really about ownership and about other kind of law like privacy protection and individual's right.
Facts such that a particular demo was released publicly at a particular party, or that it is for amiga etc.. are likely not copyrightable and can remain in this database.
Comments however are clearly the copyright of an user. Without a clear policy they remain the ownership of their users and could be removed or controlled, and certainly cannot be distributed without their consent.
Facts such that a particular demo was released publicly at a particular party, or that it is for amiga etc.. are likely not copyrightable and can remain in this database.
Comments however are clearly the copyright of an user. Without a clear policy they remain the ownership of their users and could be removed or controlled, and certainly cannot be distributed without their consent.
Quote:
: the thing is, dumping the db entirely is probably illegal, since users own copyright to their comments and posts even though their content is scrappable. i find it stupid myself.
AS IF ANYONE IN THE SCENE WOULD SUE YOU ABOUT THE COPYRIGHT OF THEIR COMMENTS? come on, this is ridiculous.
asking 18421 users to opt in is just a lame excuse to hog on the data.
here's a sane method: (all companies make it that way)
as you have the email-addresses of your users write them a mail, stating that the terms of use have changed and their posts will made available. then they have, lets say a month or two to opt-out instead if they don't agree with it. and make a announcement on the front-page too.
then wait - and voilá you have a perfectly legal way to make the data available. (from all users who doesn't disagree - (which will be <0,xxx%, i'm sure)
could someone explain to a troll why someone wants to dump the data? what for?
could someone explain why someone would not want to give the (access to the) data back to whomever had it before?
(I mean, apart from "harharhar, this is my site now and I don't even care what you're thinking")
(I mean, apart from "harharhar, this is my site now and I don't even care what you're thinking")
dubmood: well you could do all kind of interesting statistic analysis and visualizations with it for a start, like wordclouds or sth. like this only way more advanced
dubmood: in one sentence: to ensure the continued existence of pouet and the data
Imo it would work better to just send a mail to anyone that contributed telling them they can 'opt out', and have like one month to do it.
There are probably many people who contributed but are not active anymore, and losing their contributions just because they did not say there are ok is not super awesome.
There are probably many people who contributed but are not active anymore, and losing their contributions just because they did not say there are ok is not super awesome.
Ok, what v3nom wrote :p
@psenough: Yeah, »dumping the db entirely is probably illegal«. I know, that’s why i asked above, if it’s »not easier to dump the db without all personal user-data«.
Do whatever you want with my data as long as it is correctly attributed.
My comments are super precious.
be funny if the statistical data ended up resembling a spike ball
Just to clear things up, this is to have a free *small* dump to work on pouet locally, without the need to use the live dump.
It's to do a "mysqldump where user_id in $$" and put the data somewhere, without legal issue, so that anyone can import it to work on the codebase.
This is not about asking people permissions to do a full pouet dump, heh, good luck asking this to 18k users !
It's to do a "mysqldump where user_id in $$" and put the data somewhere, without legal issue, so that anyone can import it to work on the codebase.
This is not about asking people permissions to do a full pouet dump, heh, good luck asking this to 18k users !
