Latest Yandex browser (Chromium based) throws an error if "document.hasStorageAccess()" is called (:
Ie the StorageAPI that allows cross-site cookie access on user-interaction

the iFrame sandbox flags that compliment it, ie "allow-storage-access-by-user-activation" also fails on execution.
Both of these work on Edge/Chrome/Firefox.

I thought Firefox and Chromium browsers are all ive to deal with and im done but NO.
Now within Chromium-based browsers theres differences of API as well?

Kill me.

First of all, Chrome is not chromium, as there's differences in the kind of flags they support, etc. This might be especially flagrant of we are talking bleeding edge experimental features.

Google then incorporates stuff into chromium.

All chromium derivatives also do not need to be based on the exact same chromium version, so that might also result in runtime differences.

@CoreFusionX But this isnt even bleeding edge, with more and more cookie restrictions it's standard practice at this point + it's been a few years since it's been supported (2019 as experimental, early-2023 as default)
A version-difference of Chromium seems to be the issue coz I looked it up in flags later and in Yandex it's still opt-in, while other chromium-derivatives already have it on-by-default

@azuredivay
Why the heck would anyone support umyandex browser.

@scor believe it or not, Yandex has been the best at perceived privacy
if I visit a site repeatedly even on Firefox the site starts remembering what i might want to see/search

with yandex browser no matter how often I repeat actions on sites I know might track, it's as if im on a clean slate everytime, which is refreshing

@azuredivay Yandex browser and edge are the worst according to the study reported here
https://arstechnica.com/information...

"From a privacy perspective Microsoft Edge and Yandex are qualitatively different from the other browsers studied. Both send persistent identifiers that can be used to link requests (and associated IP address/location) to backend servers. Edge also sends the hardware UUID of the device to Microsoft and Yandex similarly transmits a hashed hardware identifier to back end servers. As far as we can tell this behaviour cannot be disabled by users. In addition to the search autocomplete functionality that shares details of web pages visited, both transmit web page information to servers that appear unrelated to search autocomplete."

Sorry, @azuredivay.
Emphasising there is a dot at the end of the sentence: This wasn't a question.

@electrineer oh ofc it tracks a lot, hence I said "perceived", from an end user perspective I see results that aren't leaning to what I usually see, which is good enough for me + im not important enough to worry about who tracks what about me yet lol

@scor ( ._.) ahh

@azuredivay weak

@electrineer =.= I worked at an ad-tech company, one of them "unified IDs"
I gave up on privacy when I came to know how much one's tracked no matter what they do to avoid it, not worth the effort

Gonna make my own browser… Gonna disable JavaScript and can’t enable it. No CSS allowed either. In order to use it, you have to stick plugs in your ears. Content goes straight to the dome via brainwaves. Experience similar to huffing gasoline but days feel like minutes. Full brain function. Only language available for custom brian rendering is Lisp. Vibrating stick with exclusive purchase 😉

The idea of using Lisp as the language for custom brain rendering adds an interesting layer of complexity and flexibility. https://subwaysurfersgame.io