Central Services: Difference between revisions
so Central Services includes distributing all data, from day one? that's hard to achieve
(moved and edited any and all that made any sense about threats of centralized storage) |
(so Central Services includes distributing all data, from day one? that's hard to achieve) |
||
| Line 15: | Line 15: | ||
For [[privacy]] and to push forward a [[Consumerium protocol]], however, we want to avoid central store of [[user data]] where ever it is possible, and we want [[label data]] and [[barcode]]s as well to be pushed out as far as the [[Consumerium checker]] as fast as any of it changes. | For [[privacy]] and to push forward a [[Consumerium protocol]], however, we want to avoid central store of [[user data]] where ever it is possible, and we want [[label data]] and [[barcode]]s as well to be pushed out as far as the [[Consumerium checker]] as fast as any of it changes. | ||
Centrally stored data is subject to all kinds of diseases and it's pretty much the primary place [[ | Centrally stored data is subject to all kinds of diseases and it's pretty much the primary place [[cracker]]s will target to get user data. ''The danger is that some kind of [[Consumerium Data Whorehouse]] will end up storing all the stuff that we need but don't want to admit we need, then, let anyone get it and do whatever uncontrollable things to it. Really, we want to avoid this outcome.'' | ||
Since it will be accessed only by [[server software]] probably via [[ | Since it will be accessed only by [[server software]] probably via [[SQL]] it is important that this software be quite careful to authenticate data requests. Ideally it would log them also for further [[privacy]] protection, and perhaps in [[Transparent Consumerium]] there will be so little privacy lost in publishing these queries that they can all be made safely publicly visible. | ||