I'm referring to mass exports here as this is about making personal information available to 3rd parties. But yes, technically this concerns all project. Whether they care is another question so I can speak only for us, but we're working on general BOINC support for this.
My only concern is that sites like BOINCSTATS can continue or BOINC is finished for me. No stats, no BOINC.
As I wrote in my opening statement, the three main stats sits (did we miss any?) are already covered. Yet the individual users get to decide whether they want their data be part of those or not. By default we have to exclude their data but we probably won't do that for existing users and just announce that option's availability as part of our general announcements.
That sucks, I want to be able to look up people who I am competing with and what their host are. This is overreach by the EU.
Well, people have always had the freedom to choose whether their computers are publicly visible or not - it's been standard BOINC forever. The stats export opt-in only expands on that. It's in the user's power to decide and that can hardly be described as overreach, it's the whole point. But we probably shouldn't engage in a political discussion here since the law is what it is after all.
WCG (IBM), top heavy with lawyers, made a critical error by announcing nothing until a surprise implementation of new policies. Willy and Bok (and the others) would be foolish to sign a legal agreement with IBM which could open the possibility of litigation.
Neither can I speak for WCG/IBM nor am I fully aware of what happened there, but I can understand IBM's urge to try and comply with the GDPR the best they can as the violation penalties can be pretty threatening (for good reason IMHO). Just wanted to say that downstream data consumers like the stats sites can't be held accountable by the data provider (like IBM) itself. They have to answer to their local data protection authorities themselves. They'll only be notified of a data erasure request issued by the original data subject (project participant) and that's all.
That said, the three main stats sites haven't signed any formal agreement with us. We just have to have a way to know who's using our data since we are obliged to notify them about erasure requests, hence our requirement for registration of individual download accounts. The erasure requests will be part of the data exports themselves which should be compliant with GDPR as we interpret it right now.
Gary and Bernd already highlighted the actual point of this thread.
Please let's try and stay on-topic as it will help us designing the right solution for (hopefully) everyone involved - which is you and us
So far I haven't heard of anyone using our stats exports him-/herself. Please speak up if you do, focusing on the questions I asked in my opening post.
I'm referring to mass exports here as this is about making personal information available to 3rd parties. But yes, technically this concerns all project. Whether they care is another question so I can speak only for us, but we're working on general BOINC support for this.
Oliver
Ok.
I've never looked at the mass stat dumps. Is there something different between that and what's available via the link I mentioned (which isn't covered by GDPR and can be pulled anon)?
Not that I'm aware of. But it's one thing if someone scrapes our website, which could be considered abuse and can hardly be prevented, and another when we provide said data to third parties. We have to be in control of the data entrusted to us.
Instead we are thinking aboiut adding another possibility to access your personal statistics without e.g. having to parse the web pages, possibly similar to WCG's XML export or API.
This would be a great addition. I currently parse the webpages related to my computers but having a data export would be easier. Sometimes it’s nice to be able to see information on other people’s computers, but I am mainly concerned with how my computers are performing.
mmonnin wrote:Does this only
I'm referring to mass exports here as this is about making personal information available to 3rd parties. But yes, technically this concerns all project. Whether they care is another question so I can speak only for us, but we're working on general BOINC support for this.
Oliver
Einstein@Home Project
Chooka wrote: My only concern
As I wrote in my opening statement, the three main stats sits (did we miss any?) are already covered. Yet the individual users get to decide whether they want their data be part of those or not. By default we have to exclude their data but we probably won't do that for existing users and just announce that option's availability as part of our general announcements.
That said, you should be fine :-)
Einstein@Home Project
Betreger wrote:That sucks, I
Well, people have always had the freedom to choose whether their computers are publicly visible or not - it's been standard BOINC forever. The stats export opt-in only expands on that. It's in the user's power to decide and that can hardly be described as overreach, it's the whole point. But we probably shouldn't engage in a political discussion here since the law is what it is after all.
Oliver
Einstein@Home Project
Dataman wrote:WCG (IBM), top
Neither can I speak for WCG/IBM nor am I fully aware of what happened there, but I can understand IBM's urge to try and comply with the GDPR the best they can as the violation penalties can be pretty threatening (for good reason IMHO). Just wanted to say that downstream data consumers like the stats sites can't be held accountable by the data provider (like IBM) itself. They have to answer to their local data protection authorities themselves. They'll only be notified of a data erasure request issued by the original data subject (project participant) and that's all.
That said, the three main stats sites haven't signed any formal agreement with us. We just have to have a way to know who's using our data since we are obliged to notify them about erasure requests, hence our requirement for registration of individual download accounts. The erasure requests will be part of the data exports themselves which should be compliant with GDPR as we interpret it right now.
Oliver
Einstein@Home Project
Gary and Bernd already
Gary and Bernd already highlighted the actual point of this thread.
Please let's try and stay on-topic as it will help us designing the right solution for (hopefully) everyone involved - which is you and us
So far I haven't heard of anyone using our stats exports him-/herself. Please speak up if you do, focusing on the questions I asked in my opening post.
Thanks everyone!
Einstein@Home Project
Greetings Oliver I don't
Greetings Oliver
I don't export stats for myself or the team I am part of.
I use either Boincstats or FREE-DC to do a comparison on how I am going stats wise.
I also look at the stats you provide as well.
Appreciate all the effort that you and your team do as well.
Cheers
oliver.bock@aei.mpg.de
Ok.
I've never looked at the mass stat dumps. Is there something different between that and what's available via the link I mentioned (which isn't covered by GDPR and can be pulled anon)?
Not that I'm aware of. But
Not that I'm aware of. But it's one thing if someone scrapes our website, which could be considered abuse and can hardly be prevented, and another when we provide said data to third parties. We have to be in control of the data entrusted to us.
Oliver
Einstein@Home Project
What does this mean for
What does this mean for things like the BOINCPentathlon? Or just doing forum wars or other stats based competitions?
Bernd Machenschalk
This would be a great addition. I currently parse the webpages related to my computers but having a data export would be easier. Sometimes it’s nice to be able to see information on other people’s computers, but I am mainly concerned with how my computers are performing.
Ryan