zlacker

[parent] [thread] 4 comments
1. V-2+(OP)[view] [source] 2022-07-14 10:52:11
Works fine on Vivaldi (which is Chromium-based), unless the error is only supposed to occur after an actual logging attempt, which I can't test without an account.

So I don't doubt there's a limitation, but it doesn't seem to disallow every derivative browser (assuming I'm not misunderstanding you somehow).

replies(1): >>jorgem+j1
2. jorgem+j1[view] [source] 2022-07-14 11:06:03
>>V-2+(OP)
Vivaldi workarounds these kind of issues by identifying itself as chrome. When a site blocks vivaldi because it is not chrome the site is added to a list and it will identify itself as chrome in the future (I know because it happened with the web version of whatsapp).
replies(1): >>grishk+E3
◧◩
3. grishk+E3[view] [source] [discussion] 2022-07-14 11:28:53
>>jorgem+j1
It's actually a whitelist. Vivaldi always uses the Chrome user agent, unless it's a website known to not block it, like vivaldi.com, and probably some of their partners too.
replies(1): >>jorgem+Rh2
◧◩◪
4. jorgem+Rh2[view] [source] [discussion] 2022-07-15 00:30:18
>>grishk+E3
I though it was the opposite, I guess WhatsApp was doing something weird to detect Vivaldi. Do you know how they solve it?
replies(1): >>grishk+XF3
◧◩◪◨
5. grishk+XF3[view] [source] [discussion] 2022-07-15 14:14:03
>>jorgem+Rh2
No idea tbh. I haven't used WhatsApp for several years and deleted my account a year ago.
[go to top]