End of humanity (bug) (help wanted)

[learningBASh]

reporter:svjasonmchristosthefirstSP@proton.me

Assigned to me Starred by me CC'd to me Reported by me To be verified Bookmark groups Saved searches Hotlists Create hotlist Create bookmark group Browse components Issue 330744616 Chromium 330744616 1 of 3 End of humanity bug Comments(2) Dependencies(0) Duplicates(0) Blocking(0) Resources(6) Bug P2 Unconfirmed STATUS UPDATE No update yet.

DESCRIPTIONch...@google.com created issue on behalf of Sovereign Jason M Christos the First SP #1 2024-03-22 02:31

Steps to reproduce the problem

1. On Android Tap Menu {verticle3dot} then tap {Settings} From Settings tap {Privacy and security} From Privacy and security tap {Tracking protection} From Tracking protection slide {Block all third-party cookies} on Browse to a cookie using site such as google.com and find even google.com cookies have been blocked. (second-party cookie as Google Help would call it, a cookie of the domain visited) vis no way to allow cookies from google.com without allowing any and all third-party cookies. This SEVERE PRIVACY BUG may have been introduced far back a look at the history of the Chromium repo is in order. Regression help wanted: When was this bug introduced in the version history? Sometime after version 88 and before 120. Likely after 111 because ECOSIA has a whitelist. Original bug report here: https://github.com/learningBASh/chromium-debug/issues/1 Bug Google Chromium 122 regressive Block all third-party cookies seems to block all cookies. Point at the code handling these privacy options. While this may be a more valid use of the term "third-party" expect an intermediary option for the user to allow cookies from the domain visited without having to allow any and all cookies. As it is chromium 122 has no intermediary option for privacy involving cookies. "While this may be a more valid use of the term "third-party" " Let me explain when user is first party phone is second party google then technicly is thirdparty and whatever was called thirdparty is cross-site cookies. As I say regardless of what it is being called there needs to be an intermediary option. See screenshots on original bug report here: https://github.com/learningBASh/chromium-debug/issues/1 To quote Sam Altman in a testimony before a Congress this is the " end of humanity bug; I have found the end of humanity bug. Refiled Issue 329479339 for Android build, the guy skips android testing. Bug P1 Priority the First CONFIRMED reproducible and regressive. Refiled because the end of humanity bug is not getting looked at yet. Some guy shot down my bug report as if he didn't know it was for Android. I have confirmed it is reproducible and regressive as far back. Help is wanted to search the sourcecode for how far back this SEVERE bug was introduced. SEVERE Security and privacy bug no way to allow cookies from google.com without allowing any and all third-party cookies.

Google banned me for Google being wrong : or deleted my post : they don't really give explanation but I did say google help is wrong because of a serious bug in Chrome : looks like they are trying to force you to get attacked by AI by making it hard not to use thirdparty cookies: the bug is too convenient right at the time online biz are moving toward ChatGPT biz models : so guys in the google system can evade its own policies as a thirdparty : if you thought policy meant nothing wait until you see AI harassment tracking devices on thirdparty cookies. This is serious severity HIGH. Sam Altman testified before Congress about this, I have found the " end of humanity " bug. Why hasn't any dev touched this yet?

UPDATE Severity: HIGH how to change a bug name from " no cookie whitelist" to " end of humanity " bug buganizer: this is serious Sam Altman testified before Congress about this stuff; I have found the " end of humanity " bug. I may need to refile this bug because it isn't getting looked at.

"Here are the docs on the various ways to manage cookies " is exactly, exactly!, what I was talking about in my community post here https://support.google.com/chrome/thread/263788579?hl=en I do quote Myself " The BUG really proves Google Help files WRONG about block third-party cookies " with 3 updates and two replys missing. and it seems my post was deleted then suddenly reappears. I guessed it was because I said Google Help files are WRONG and now it is locked up. and no it is not a specific build. It is a persistent regressive bug from Android chrome 124 and 122 maybe all the way back to 111 if you read my original bug report I asked for help wanted searching the code for what has caused this and when it was introduced in the versions. Rerun your tests with any android build and regress until you get cookie whitelisting 88 is confirmed working for whitelists.

Seems like you are stalling to let an AI scourge run. Sam Altman warned a Congress about this to quote the " end of humanity ". With block third-party cookies turned on any attempt to login to google.com returns you need to enable cookies. Reproduce that. Turn off allow google login, turn on block cookies and attempt to login to my account.google.com. Apparently that is how you expect it to work? Third-party (cross-site) cookies required to login to Google? Wow, amazing stupor. Wow! And editing your posts after I comment to make my comments look bad isn't helpi

Problem Description

Wow, amazing stupor. Wow! And editing your posts after I comment to make my comments look bad isn't helping.

Priority the First -severe privacy bug - Are you selling out android users wholesale in human traffiking to the triads backing Google Play Services authentication? I recently noticed in the google session management my browser is listed when using the triad security mechanism of allow Google login. ( in google terms Devices list ) Will this be enabling third parties to handle my authentication which third parties not party to Google policies therefore completely nullifying any purpose or use of Google policies including privacy? Google is an American multinational company and a clear Annerican overstands the fourth clause of the First amendment concerning privacy right down to the minutia of personal effects.

Additional Comments

See screenshots on original bug report here: https://github.com/learningBASh/chromium-debug/issues/1

Summary

End of humanity bug

Custom Questions

Example URL:

www.google.com

Does the problem occur on multiple sites?

Yes - Please describe below

Is it a problem with a plugin?

No - It's the browser itself

Does this work in other browsers?

Yes - This is just a Chromium problem

Additional Data

Category: Content \ Chrome Channel: Not sure \ Regression: Yes

[learningBASh]

• change bug title to no cookie whitelist preinstall version (88) still has the ability to whitelist cookies. aurora version codes may be used to find the most recent version which had cookie whitelists.

help wanted: there should be some way to browse the sourcecode and see when this was changed.

further steps taken: tryed many browsers looking for a cookie whitelist and none found it is interesting most browsers are pulling from chromium and are rebranded chrome browsers.

FAQ What are you trying to do? A. Use Chrome sync. This bug was encountered trying to use Chrome sync for the purpose of saving bookmarks - attempts whitelisting only google for this specific purpose and any other google specific purpose.

[learningBASh]

[learningBASh]

Further steps taken: Even trying out Firefox(123.0) the whitelist is not possible as per Enhanced Tracking Protection in Firefox for Android > Manage your Exceptions list here https://mzl.la/3BUXdli the exceptions screen has no way to input sites. This bug may also be reported to mozilla.

[learningBASh]

help wanted: Question When was this bug introduced in the version history? Sometime after version 88 and before 120.

[learningBASh]

Filed bug with chromium devs and some guy shot it down claiming it is not reproducable bevause he failed to test it on android. Refiled the bug with new title End of humanity bug. Links to chromium bug reports to follow.

[learningBASh]

Yet another reproduction aside from google.com youtube.com also fails to login see screenshots: And the current settings:

[learningBASh]

For the r3cord the first shot down bug report is here https://issues.chromium.org/329479339 no cookie whitelist (bug) (help wanted) #1

[learningBASh]

The refiled End of humanity bug report here https://issues.chromium.org/330744616 End of humanity bug

[HolyNameSoftware]

This is how you would whitelist the Google domain and login without any third-party interference keeping your business with Google between you and Google alone. What is the wildcard symbol for chrome settings website URL in the list of exceptions for various block settings? Hint: it uses brackets. something like: [*].google.com

Blocking everything and then only allowing what is needed to login to Google.

[HolyNameSoftware]

The syntax for wildcard subdomain is [.]google.com and it seems to be a useful bug because [.] is treated as an array but you can't input * alone.

NOT DISPLAYING PROPERLY HERE

openbracket-asterisk-period-closebracket

[HolyNameSoftware]

More of this ongoing bug is unfolding: with a new android having android 13 Chrome locks up the phone and I highly suspect it is due to JavaScript. JavaScript debugging is needed to confirm. However that this my bug report has been ignored and suppressed by buganizer and further now my report of Chrome being shipped unusable in android 13 also being ignored in buganizer. To be linked here. That these intentional neglects happen suggests to confirm my aforementioned suspicion and description of human traffiking. Also note that Google's bug reporting system was changed to buganizer only some years ago as announced on Google's blog to be linked here.