EDIT: Saw a few mention two solutions to disable the automatic verification on iOS & macOS.
https://blog.cloudflare.com/how-to-enable-private-access-tok...
It isn’t perfect but we are ahead of most others (Mastodon, Matrix). We have spent TWELVE YEARS building the free, permissionless open source platform for anyone to assemble and host their own community software with all the features of Facebook/Twitter/TikTok for their own community:
https://github.com/Qbix/Platform
We are about to roll out version 2.0 — I have never done this before but I would like to invite whoever wants to learn about it or build on it, to a Zoom webinar where I will demo anything and answer any questions. Starting in Q3 this year all the webinars will take place on our own platform — no Calendly, no Zoom, no Google, just the free open Web.
Anyway, sign up here if you want. Will do it every Sunday throughout August:
https://calendly.com/qbix/qbix-2-0-platform-demo
Whether you’re a developer, a businessperson, or just want to learn about the latest technologies moving the Free Open Source Web forward, this platform can help empower you to build and engage a community around yourself and your projects.
Disabling the feature on your device will make you fail attestation and thus websites requiring it will just stop working.
* CON: The problem is that the WEI server could change it's tracking faster than the browser app updates it's fakeness though. There's more money in bypassing adblockers than there is in blocking them.
* CON: If it does fake itself, when you return to the original website it can assume there's no adblocker and fail to load with the adblocker unlike now where it's usually ignored.
I have lost a big part of my former trust and want for writing OSS this last few months and one thing I have learned is that if those two can't be answered with a resounding no it is a project I won't ever contemplate even though I'm neither American nor Russian.
Why are you using Github then?
1. Someone could set up a server that proxies WEI required requests to regular clients. The client initiates the process, the request goes to the middleman, the middleman makes the proper WEI authorized request, gets the response, passes the response back to the client.
2. The private key could leak somehow, and so, software can forge the required signature.
I'm not holding my breath for either one. Some kind of regulation has to step in, otherwise Google puts the internet in a chokehold.
Why using calendly, zoom, and google? Well, as I said, we haven't launched Qbix Platform 2.0 to everyone worldwide yet. This is if you want to get involved pre-launch.
We dogfood our own stuff, but we also interoperate with everything else out there, such as Discourse (https://qbix.com/ecosystem for example incorporates it), Zoom, Google, Facebook, etc.
https://www.theverge.com/2021/1/5/22215588/github-iran-sanct...
As a side note, many people on our development team that has worked with us since 2013 have spoken Russian, coming from Ukraine, Armenia, Russia, etc. Many of them continue to work together despite the war their governments are conducting.
We are for empowering people uniting communities around the world, and are pretty critical of government overreach:
https://community.qbix.com/t/transparency-in-government/234
https://qbix.com/blog/2021/01/15/open-source-communities/
If that appeals to you, the lowest hanging fruit is just joining the community and introducing yourself:
https://www.theregister.com/2023/03/21/russian_foss_contribu...
But thank you for your reply.