|
2015-01-27
, 16:12
|
|
Posts: 1,055 |
Thanked: 4,107 times |
Joined on Oct 2009
@ Norway
|
#3242
|
Yes, and that is the part that does not work when two devices with different app sets share the same account.
One way to reduce that is to split it in two parts: 1) names and versions, 2) dependencies. That way, the difficult part (parsing the dependencies) would be done only for the specific package the user selects for installation or upgrade and only when he choses to do so.
Please note that there is still an information leakage ("Johny is installing package X"), but only to the repository that provides that package and that is unavoidable anyway.
The Following 11 Users Say Thank You to w00t For This Useful Post: | ||
|
2015-01-27
, 16:25
|
|
Posts: 6,447 |
Thanked: 20,981 times |
Joined on Sep 2012
@ UK
|
#3243
|
It does work, it's just not working at optimal efficiency. It says: "please give me a list of all my installed packages in the virtual repository", and then, locally, discards the ones that don't apply.
|
2015-01-27
, 17:22
|
Posts: 285 |
Thanked: 1,900 times |
Joined on Feb 2010
|
#3244
|
You are suggesting nothing more than moving this backup out of your control and have it on some central server in Helsinki. Not that there is anything wrog with that per se, but it should not be compulsory.
[*]Making sure you have the same applications installed on two different devices.
This is basically about the "centralized backup" as mentioned above. Well, I am the kind of a person who
a) May want two devices with completely different application sets;
b) Does not mind to install the same appliocation twice;
c) Would be p!$$ed off if the device forced the same app sets on my two devices because I used the same account. As happened with Android: the same patch from Motorola was forced on another device in our household. Who cares that the other device was a Samsung? It used the same account
The transfer of intellectual property.
This is the only case when "something" - not the application, but the right to install it - is associated with the person. An account does not entirely answer that if it can be shared but it is better than nothing. An account also does not help if the app developer wants you to buy a different license for each device, so the developers will just have to suck it and put up with Jolla's distribution scheme. Luckily (for Apple followers, that is) there is alraedy a precedence that people are used to.
Not unconditionally since, as I explained above, it also has its caveats.
It could work as a "convenience" for some but not for others.
The Following User Says Thank You to JulmaHerra For This Useful Post: | ||
|
2015-01-27
, 18:46
|
|
Posts: 6,447 |
Thanked: 20,981 times |
Joined on Sep 2012
@ UK
|
#3245
|
If app is bound to the device, then the device needs to be identified somehow.
I said that I'd like to have a list of my purchased and/or installed apps, from which I can choose which ones I want to install on my other/new device. This can be done manually, searching and installing all apps one by one, but it's more time consuming and can be made more streamlined.
Usability and convenience should never be sacrificed for ideological reason, especially in consumer space.
The Following 3 Users Say Thank You to pichlo For This Useful Post: | ||
|
2015-01-27
, 20:33
|
|
Posts: 764 |
Thanked: 2,888 times |
Joined on Jun 2014
|
#3246
|
|
2015-01-27
, 21:24
|
Posts: 285 |
Thanked: 1,900 times |
Joined on Feb 2010
|
#3247
|
We don't know anything about purchased apps yet as there is no such support. But my case with two Jollas in the family sharing the same account shows that the streamlining you mention above does not work. At least not at the moment.
And therein I believe lies the crux of the whole thing. It is so common to bring up ideological issues to every discussion about anything even remotely connected to "Linux" and "open source" that people tend to automatically assume that every discussion is about ideological issues. I tried to convey all the time that I had technical reasons in mind, not ideological.
I know this is not the common way in the modern world but my approach to any problem is, "take as little as you need", as opposed to "take as much as you can get." That applies to buffer sizes as well as how much to pack on a holiday and... how much the central repository needs to know about each client.
The Following 5 Users Say Thank You to JulmaHerra For This Useful Post: | ||
|
2015-01-27
, 23:16
|
|
Posts: 4,118 |
Thanked: 8,901 times |
Joined on Aug 2010
@ Ruhrgebiet, Germany
|
#3248
|
BTW
can anybody tell me where the data goes that you have to enter on first switch on, i.e. account, name, surname, telephone, birthday and so on?
I would to see that anywhere in settings or in a file or?
And would like to know if this data gets synchronized with jolla online account data?
|
2015-01-27
, 23:34
|
|
Posts: 6,447 |
Thanked: 20,981 times |
Joined on Sep 2012
@ UK
|
#3249
|
I can hardly see any technical reason to implement the store otherwise
Requiring username (which by itself does not identify person behind it in any way) and password is IMO quite far from "take as much as you can get."
|
2015-01-28
, 06:53
|
Posts: 285 |
Thanked: 1,900 times |
Joined on Feb 2010
|
#3250
|
That's the scary bit. People are so used to the Apple way that they can't even imagine anything else. The technical innovation stopped in 2007.
True but it is just as far from "take as little as you have to", since "as little as you have to" can be absolutely nothing.
The phone says the info stays private and I have no reason to apriori assume otherwise. I would imagine its primary purpose is to identify your phone in case of getting lost or stolen but I would also like to know where the info is stored.
Tags |
jolla, review, sailfish, the other half, user experience |
|
Debian based systems are plagued by the fact that each time the catalogues are refreshed, the whole shebang with the dependencies is transferred (up to about 10MB per repository in Maemo's case) and parsed. One way to reduce that is to split it in two parts: 1) names and versions, 2) dependencies. That way, the difficult part (parsing the dependencies) would be done only for the specific package the user selects for installation or upgrade and only when he choses to do so.
Please note that there is still an information leakage ("Johny is installing package X"), but only to the repository that provides that package and that is unavoidable anyway.
Русский военный корабль, иди нахуй!