I'd love to see a built-in reader mode that strips pages down to bare text, like in Firefox, Edge, Safari, and Vivaldi browsers.

As I'm getting older, it's getting harder to read small text. Also, in the mobile browser, sometimes pages have too many advertisements to read easily. Being able to just see the text at the right width and having the ability to scale up or down font sizes would be helpful. It would also be one less extension (and one less vulnerability) that I'd have in my browser. The ability to change colors (black text on white, white text on black, sepia tones) to reduce eye strain would also be a nice addition.

Since we can't install extensions in the mobile browser, is there any way we can increase privacy with features like forcing HTTPS wherever possible or doing a better job of blocking trackers?

According to EFF's Panopticlick (https://panopticlick.eff.org/), Opera Mobile blocks some tracking ads and invisible trackers, but not all and does not block trackers from "acceptable ads".

I far prefer Opera to Firefox mobile browsers, but I usually use Firefox because I feel that I have more control over my personal privacy.

Can we investigate ways to improve privacy management on Opera Mobile (and by extension Opera Mini)?

@sgunhouse It is listed on the Extensions page of Opera. I believe that's part of my initial confusion.

@burnout426 I think I've also had some luck with using mail.office365.com as the SMTP server.

I'd like to see the option to switch back and forth between those two options.

The question was whether or not changes to Chromium's base code would impact extensions. This is listed on the extensions page. I believe it's a fair question whether or not Opera's built-in adblocker will be impacted by proposed changes to Manifest V3.

I had a similar issue at home, with my network. I turned off this feature (in Comment #26) and it resolved my issue. Hopefully this will help you as well.

https://bugs.chromium.org/p/chromium/issues/detail?id=770201#c26

Not really. They CAN (and do) modify the Chromium code each time an update comes out. Vivaldi makes underlying changes each release as it makes new code work with their features. Brave has already stated that these proposed changes will not affect their manipulation of the code or how their built-in ad blocking feature works. Chrome tacks on Google-specific features to the Chromium code, and I'm sure that Opera does the same.

Chromium itself is designed to be modified by end users to add or remove features in their software.

Which is why we're hoping to get a response from someone on or familiar with the development team, I believe.

Which is why we're hoping to get a response from someone on or familiar with the development team, I believe.

Not really. They CAN (and do) modify the Chromium code each time an update comes out. Vivaldi makes underlying changes each release as it makes new code work with their features. Brave has already stated that these proposed changes will not affect their manipulation of the code or how their built-in ad blocking feature works. Chrome tacks on Google-specific features to the Chromium code, and I'm sure that Opera does the same.

Chromium itself is designed to be modified by end users to add or remove features in their software.

The question was whether or not changes to Chromium's base code would impact extensions. This is listed on the extensions page. I believe it's a fair question whether or not Opera's built-in adblocker will be impacted by proposed changes to Manifest V3.

@sgunhouse It is listed on the Extensions page of Opera. I believe that's part of my initial confusion.

I'm curious about this as well. Right now, I know that Brave's internal adblock is safe, but I really like Opera's adblocker on mobile devices. It'd be a shame to lose that as an option.

I get the following error when I try to log into sync.opera.com/web

AccountsAPIError: oauth2 server error (500)

@slytheringirl I appreciate the suggestion! I hope I didn't sound ungrateful.

@slytheringirl First time, I got an API error, then I got a 403 error.

If I'd have known I'd have lost functionality like this, I wouldn't have done it.

Is there going to be a workaround for this? I'd hate to think that by using a built-in security feature that I'd lose a feature that I really liked about Opera.

I'd like to see this optional instead of mandatory as well, please. Opera for Android is the only browser that still lets me use Facebook Messenger from the mobile website, instead of having to use the basic mobile site or the desktop site, but this feature/bug is enough of an irritant that I'm also using Brave or Firefox more often, when I'm not going on FB.