Hello Thomas, Monday, February 21, 2022, 1:00:47 PM, you wrote:
> Hello Alex, > Sunday, February 20, 2022, 8:41:57 AM, you wrote: > >>>> 3. Generally, I do not like it at all to have a forced open channel to a >>>> The Bat server that cannot be deactivated. It should be for 'future >>>> plans', that are not explained further. >>> And I totally agree with this. This is a no-no. Furthermore, I read that he >>> have to use the "correct" email address, so Ritlabs is now telling us which >>> email address to use. I bought two licences, one for work (only release >>> verions) and one for home (also for betas), but I use about 10 email >>> addresses at home. >> First of all, there's no "open connection". After you log in for a first >> time, link your license, if there wasn't one on your account already, the >> only request we're sending is >> https://api.beta.thebat.net/api/beta-access/check, which is only being sent >> one time after each program startup. > So, this check is only for beta testers? OK, I can understand that you want > to accept only registered beta testers. > How about the other 5 checks? I've described them pretty clearly. They're used only until you're fully logged in. >> Second, I don't really understand, what "correct" email addresses you're >> talking about. > Several people here reported that they cannot log in and they were told that > they tried with the "wrong email address". I don't know what that means, you > tell me. "Wrong email address" means: 1. Email address they've entered is not associated with their key; 2. They've encountered a bug when they enter correct address, but the system shows it is wrong. This email check is only needed to verify that the real keyholder is trying to link to to their account. >>>> I consider that too risky. So I prefer to wait until I read here more >>>> trustful clarification. >>> Looking for the explanation what the 6x HTTP queries to the Ritlabs server >>> is all about, too. Only for beta testers, or for everyone who wants to run >>> TB!? >> It will be optional in release version, so you'll be able to choose, >> validate your copy through program key, like it was before, or through The >> Bat! Network account. > Every time you start TheBat! is has to be verified? When using the release > version? I don't really understand your question. What has to be verified? Key or account? If it is the key you're talking about, it is verified on every startup, just locally. As for account, as I said, it will be just an option, not mandatory. -- With respect, Alexander Tanurkov VP of Engineering @ Ritlabs SRL https://ritlabs.com ________________________________________________________ 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
