After briefly enjoying 1 million users, Glide has now reverted to the initial user limit:
With the ‘privacy’ settings remaining the same as before the above changes (see image below), now every user who signs in will be categorized as a private user. This is different from the previous state.
I’m confused … What ‘Privacy’ setting will categorize users as ‘public’?
Public → Anyone can sign in.
do you mean the option “Anyone (Anyone can create profile)” or "No Sign-in (user do not have their own profile) or just “Required Sign-in”?
It doesn’t matter if you make sign in required or optional, as long as you allow anyone to sign in.
Thank U Darren
@ThinhDinh, I’m not focused on the number 1 million. I’m also not quite sure about the settings I did before this moment, I feel like I’ve set it up so that users who sign in are categorized as public, not private. Personally, I find it quite complicated that with the public option, they’re still categorized as private.
Yeah, I just wanna provide context on why that number was changed and reverted.
With legacy plans, It’s simply this…If you use any kind of whitelist table to determine who is allowed to sign in, then those users are private users because you are restricting who has access to sign in. Also, if any of those users utilize Role functionality, then they are also considered private users, even if you allowed someone to sign in without using a whitelist table, but you assign that user a role.
If your app is set to Private, it will of course count every user as private because you are required to force every user to sign in, and those users must be in a whitelist table.
If your app is Public, and anybody in the world can sign in unrestricted, and they don’t utilize a role, then they are a public user.
An app set as a Public app, that allows people to use the app without signing in, can still have Private users if you require a whitelist to restrict who can sign in…or you utilize roles for signed in users.
If you start associating it with update limitations, perhaps you’ll understand from a consumer perspective whether these limitations are necessary. I just chuckled when the limit was increased to 1 million users because you would never reach it, as in the end you’re still locked by the update limit (although there’s no such limit in classic pro). Simple would be better.
By the way, why can’t Google directly translate this chat page? It’s too much hassle to use a translator on another page. 
I didn’t notice the translator icon in the address bar. What I always try is the one on the right. Hahaha… same goal but different abilities. Still, the translation results are not clear.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
