| Thi' Captain Spake |
Jabb'r: Limited access mode - past race analysis |
's many 's 15 answ'rs
|
|
|
Is there any particular reason i don't have access to my past race analysis pages in Limited Access mode?
As the account setting header states:
Limited access password - use this password when using third party tools, it grants access only to your race related data and keeps your private data safe
I would suspect past race data can be categorised as "race related data"... As long i was a supporter during the races targeted, obviously.
For a moment i suspected supporter-only data is hidden everywhere in limited-access mode, but checked ccp history, past testing and s&f history and they're all available, so it seems limited to past race analysis pages only.
|
|
|
|
Limited access is quite similar to Holiday mode where you can't see the managers previous data only the current data and the race before.
So it is not really surprising for me that it works like that.
|
|
|
|
Quote ( Miel Soeterbroek @ January 22nd 2019,19:16:15 ) Is there any particular reason i don't have access to my past race analysis pages in Limited Access mode?
To limit the access to said data to holidayers and server based team tools I suspect.
|
|
|
|
Quote ( Eduardo Sanchez Carenzo @ January 22nd 2019,19:20:51 ) where you can't see the managers previous data only the current data
As stated, many other bits of historical data are available.
Quote ( Florencia Caro @ January 22nd 2019,19:21:54 ) To limit the access to said data to holidayers and server based team tools I suspect.
The only reason i'd see here is one of server loads and traffic. It's true that the race analysis page is size-wise one of the bigger ones on gpro, but it dwarfs compared to the data swinging back and forth on the live race screen (to name one). It's also pretty similar in size to the group sponsor pages, to name another one.
But all of the above (related to size, traffic, bandwidth) doesn't really apply to the nature of the data: historic, immutable data. If tools grab these, i presume they're grabbed once and only once. It's not something that is fetched every race.
Additionally, it's perfectly fine to grab these locally with the full access account, which also renders the bandwidth argument moot in my opinion.
I just don't get the discrepancies here. Both in terms of historic vs actual and supporter vs non-supporter :D
|
|
|
|
Quote ( Florencia Caro @ January 22nd 2019,19:21:54 ) To limit the access to said data to holidayers and server based team tools I suspect.
To holiday your account though you should use the account holiday feature and not limited access mode.
As for server-based team tools, isn't that the point of limited access mode? Why would some data be available to be collected by those tools while other data (past race analysis in this case) not be available?
|
|
|
|
Quote ( Miel Soeterbroek @ January 22nd 2019,19:57:57 ) related to size, traffic, bandwidth)
Depends on how the tools are coded, there's always someone lazy enough to code a tool to crawl and save all supporter-saved past races every single time the tool runs :D. and that is not as static as you claim, I still have 20-30 races I could buy with supporter credits where I wasn't a supporter, and my team tool would collect it if I bought those.
But the strongest argument here is privacy, as I see it: if you want to share EVERYTHING, then you have the local full access password run-save option, as you mentioned. Limited access needs to be limited, if it means you share your full historic race data, I wouldn't call it limited access at all :D
|
|
|
|
Quote ( Florencia Caro @ January 22nd 2019,19:21:54 ) To limit the access to said data to holidayers
A little off topic, but is this necessary? When holidaying another account, I find it very useful to check previous races on the same track. They are often more useful than my own races if the other manager is in a different league or has a different taste in gameplay (like tyre supplier, driver stat distribution, car state).
|
|
|
|
Quote ( Florencia Caro @ January 22nd 2019,20:09:13 ) Limited access needs to be limited, if it means you share your full historic race data, I wouldn't call it limited access at all :D
I quoted the damn description of limited access for a reason! :D
Limited to race-related data. Which this is.
And if limited means limited to current state only, that'd also be fine. But the full-on access to staff history, ccp history, testing history, economy history and captain floppycock knows what else seems to contradict this.
I just hate discrepancies ;)
|
|
|
|
Quote ( Miel Soeterbroek @ January 22nd 2019,20:12:55 ) And if limited means limited to current state only, that'd also be fine. But the full-on access to staff history, ccp history, testing history, economy history and captain floppycock knows what else seems to contradict this.
I just hate discrepancies ;)
Be careful with what you wish for :D
Quote ( Ania Piekarska @ January 22nd 2019,20:10:56 ) A little off topic Not off-topic at all.
I think it's a matter of taste, really; I believe a manager with your skill is perfectly capable of holidaying an account without any past races data :) , but you'd still prefer to see that for reassurement :D
I do think fresher managers would find it useful as a reference, for the sole fact they lack data volume in general. So I might support the idea.
|
|
|
|
|
|
I'll be very short: +1 to Miel
|
|
|
|
|
May I remind you that fresher managers use Limited Access password with 3rd party apps, and not team tools? GO and blacklisted sites, mainly.
|
|
|
|
Quote ( Florencia Caro @ January 22nd 2019,20:27:51 ) May I remind you that fresher managers use Limited Access password with 3rd party apps, and not team tools? GO and blacklisted sites, mainly.
And that is a risk anyway. Not specifically related to past race data, is it?
|
|
|
|
Quote ( Miel Soeterbroek @ January 22nd 2019,20:33:18 ) Not specifically related to past race data, is it? Agree, but it's still a big part. I really wouldn't like to "see" how a blacklisted site accesses all past data with one login, while a manager decides not to use that site again and has only logged in there once.
|
|
|
|
|
|
I don't see any serious problem.
But if you're scary (I mean all admins team), allow it for all managers from top-100 teams or top-50 or only cat teams for example. It's not fair but it can be a solution. Just an example.
|
|
|
|
|
True, but (in fear of going in circles here) that also applies to testing history. Which is as 'valuable' as race data.
|
|
|
|
Quote ( Alexei Malkin @ January 22nd 2019,20:40:16 ) I don't see any serious problem.
But if you're scary (I mean all admins team), allow it for all managers from top-100 teams or top-50 or only cat teams for example. It's not fair but it can be a solution. Just an example.
Or create "Team Limited Access" :D
Quote ( Miel Soeterbroek @ January 22nd 2019,20:41:32 ) True, but (in fear of going in circles here) that also applies to testing history. Which is as 'valuable' as race data.
Without driver, car and other related data? I do not think so :)
|
|
English
Deutsch
Español
Română
Italiano
Português
Português
Français
Polski
Русский
Български
Македонски
Српски
Nederlands
Vlaams
Suomi
Lietuvių
Čeština
Magyar
Eesti keel
Slovenčina
Türkçe
Shqip
Ελληνικά
Hrvatski
Bahasa Melayu
Dansk
