D.Draker Posted November 21, 2023 Posted November 21, 2023 (edited) 11 hours ago, Tripredacus said: there is no reason to try to catch people in a grammar trap. I wasn't catching anyone in a "a grammar trap." Come on, there's one million of live witnesses. Also, as religious people would say, God sees everything, fear of God. A fair solution would be now you both apologize. EDIT: Maybe then I reconsider postings of my valuable information, 3 hours ago, UCyborg said: I think it can be safely assumed they won't come up with a feature name with a space in it. Take a note, it also says --flag-switches-begin, it's the beginning, also no quotes. Edited November 21, 2023 by D.Draker 4
Dixel Posted November 22, 2023 Posted November 22, 2023 13 hours ago, Tripredacus said: There is a red arrow pointing to where the quotes mentioned are being used. Try to be more reasonable on the forum. We make everyone post in English and people from other countries may not be 100% accurate and clear when they post, so it is to be expected that sometimes things can get mixed up. You have the ability to figure out what a person is trying to say, there is no reason to try to catch people in a grammar trap. This was not the question D.Draker asked, he asked if there were quotes in the command line under chrome://version/ on his screenshot. For me, it doesn't seem like the member has troubles understanding English. 4
Dixel Posted November 22, 2023 Posted November 22, 2023 13 hours ago, D.Draker said: Take a note, it also says --flag-switches-begin, it's the beginning, also no quotes. Indeed, I wrote my own unified starter app for Chrome and Opera, it passes a gazillion of flags and enabled/disabled features to the executable, I shared it with several members, everyone's happy with it, I never used quotes. I must be not educated enough. 4
D.Draker Posted November 24, 2023 Posted November 24, 2023 On 11/21/2023 at 4:01 PM, Tripredacus said: Try to be more reasonable on the forum. My answer is reasonable as one can ever make. On 11/21/2023 at 4:01 PM, Tripredacus said: There is a red arrow pointing to where the quotes mentioned are being used. When D.Draker writes something, it means the information is solid. My military background demands to be disciplined, thus don't spread fake news. He can draw whatever amount of red arrows he wants, it doesn't change the facts. There are no quotes at the place where he drew that red arrow. Here's proof that quotes aren't needed, directly from Microsoft, about Edge, with one of the same flags/features he uses. Link to the source: https://techcommunity.microsoft.com/t5/discussions/you-can-now-enable-encrypted-client-hello-encrypted-sni-or-esni/m-p/3600372 I'm still waiting for the public apologies and his attacking/offensive post, the one where he makes a mockery out of me, to be edited. 2
D.Draker Posted December 8, 2023 Posted December 8, 2023 On 11/21/2023 at 11:58 AM, Sampei.Nihira said: Here's what you requested. You will notice that the experimental flags + Command-Line Switches with "": I will also include a Github link, even if archived, with the Command-Line Switches in question with the correct syntax: https://github.com/melo936/ChromiumHardening/blob/main/flags/chrome-command-line.md I found another error in @Sampei.Nihiralist of flags, seeing this user tends to be hard privacy oriented, I want to help him with the error. At least one the flags I see is wrong, also the order is very questionable. Besides, he didn't switch off the variations fingerprint, which makes him unique, maybe forgot? 2
D.Draker Posted December 8, 2023 Posted December 8, 2023 He either needs to specify the fake time zone, as an example we take UTC. --time-zone-for-testing=UTC or switch the time zone completely. --disable-per-user-timezone No quotes are used. 2
Sampei.Nihira Posted December 8, 2023 Author Posted December 8, 2023 (edited) If you assume that there is an error in my browser that is not oriented to hard privacy but rather to security (your first error) (,also because you don't know my access needs at all,for example I have significant limitations to accessing government websites where I collaborate) you have to prove it with your browser by a test that of course I will not provide you have to know. Second mistake you are highly OT in this thread And I will not read anything that does not follow the above parameters. So if you want to run various tests with your browser, I suggest you open a new thread. I promise I will gladly read them. Have a nice day. Edited December 8, 2023 by Sampei.Nihira 2
dmiranda Posted December 9, 2023 Posted December 9, 2023 (edited) Have you tried with istilldontcareaboutcookies-1.1.1? They are community run, and (they say) answer to requests. It works better (more comprehensively) than the old idontcareaboutcookies. Cheers @Sampei.Nihira, and thanks for continuing to share your knowledge with us, retired and all. Don't mind them digital flies. Edited December 9, 2023 by dmiranda 4
mina7601 Posted December 10, 2023 Posted December 10, 2023 On 12/9/2023 at 9:39 PM, dmiranda said: Cheers @Sampei.Nihira, and thanks for continuing to share your knowledge with us, retired and all. Don't mind them digital flies. I second this! @Sampei.Nihira, Don't let anyone discourage you from your job as a security expert, I am pretty sure most people already appreciate what you do to us. Even though I also am concerned about security vulnerabilities (although not very much, but still concerned), I appreciate every knowledge you share with us. Please keep continuing to share knowledge with us! 1
Sampei.Nihira Posted May 31, 2024 Author Posted May 31, 2024 (edited) https://blog.chromium.org/2024/05/manifest-v2-phase-out-begins.html?m=1 Quote .....Starting on June 3 on the Chrome Beta, Dev and Canary channels, if users still have Manifest V2 extensions installed, some will start to see a warning banner when visiting their extension management page - chrome://extensions - informing them that some (Manifest V2) extensions they have installed will soon no longer be supported. At the same time, extensions with the Featured badge that are still using Manifest V2 will lose their badge. This will be followed gradually in the coming months by the disabling of those extensions. Users will be directed to the Chrome Web Store, where they will be recommended Manifest V3 alternatives for their disabled extension. For a short time after the extensions are disabled, users will still be able to turn their Manifest V2 extensions back on, but over time, this toggle will go away as well. Like any big launches, all these changes will begin in pre-stable channel builds of Chrome first – Chrome Beta, Dev, and Canary. The changes will be rolled out over the coming months to Chrome Stable, with the goal of completing the transition by the beginning of next year. Enterprises using the ExtensionManifestV2Availability policy will be exempt from any browser changes until June 2025. Edited May 31, 2024 by Sampei.Nihira 1
Dixel Posted May 31, 2024 Posted May 31, 2024 3 hours ago, Sampei.Nihira said: This will be followed gradually in the coming months by the disabling of those extensions. Does this concern old Chrome versions users? Below 122. Thanks. 2
Sampei.Nihira Posted May 31, 2024 Author Posted May 31, 2024 (edited) Probably not. You should check if you don't have this flag: chrome://flags/#extension-manifest-v2-deprecation-warning I for example in Edge do not have the flag above. Although they will probably implement it in future versions. P.S. Those who will use Thorium/Supermium will have available the company policy in the browsers inserted by the developers themselves: https://github.com/Alex313031/thorium/issues/677 Edited May 31, 2024 by Sampei.Nihira 1
Sampei.Nihira Posted May 31, 2024 Author Posted May 31, 2024 This will be the notice of disabling MV2 extensions:
Sampei.Nihira Posted May 31, 2024 Author Posted May 31, 2024 Mozilla will continue to support MV2 extensions but certainly not indefinitely: https://blog.mozilla.org/addons/2024/03/13/manifest-v3-manifest-v2-march-2024-update/#comments Quote ....And even if we re-evaluate this decision at some point down the road, we anticipate providing a notice of at least 12 months for developers to adjust accordingly and not feel rushed. I assume that Mozilla will disable MV2 extensions by June 2026.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now