Flow used to work just fine before on the 16th, and yet when I want to send a link from my mobile today, the flow from my mobile isn't connected. Both have been updated before making this topic

From my mobile, in the setting menu, I click on the "+ connect device" button and open the opera.com/connect link on my browser, but the page didn't provide any additional instructions. It just stays on that QR code page indefinitely.

And what is a connection code, how are we supposed to read that 5x4 block for the code, and why isn't the option to enter the code isn't in the Opera android app?

Fortunately, the OPERA GX for mobile flow function and connect almost from the get go, so I have to manually move most of my active mobile tab there for now.

Opera should stop hiding the war. We (the users) want to see it.

Opera silently blocks trackers, and cookies and while that’s good, we (the users) can't verify if it works because Opera does so silently. The browser protects you in the shadows. That’s not enough. I want visibility, insights and evidence.

Opera should show me which sites try to fingerprint? Who’s pinging third-party servers? Which scripts are trying to detect my device configuration, canvas ID, audio stack? Who’s building a shadow profile off my font list and screen resolution?

Opera should not just block, rather, it should expose.

Opera should give us (the users) a per-site privacy dashboard. Every time a tracker is blocked, I want to know when it was blocked and have a knowledge of it being blocked. A notification, an alert, or a log should show up when creepy things happen behind the scenes when a site is visited. Opera should let me drill into the details. It should tell me who tried the creepy behaviour, what method did the user or organisation use to try the creepy act, and when did who-knows-who try the creepy act?

Right now, privacy on Opera is a black box. That creates trust for some, but limits control for the rest of us. Power users don’t want passive protection. We want a transparent firewall, a window into the fight.

Opera should let us (the users) whitelist specific scripts, let us (the users) see attempted tracking events, not just the ones you caught. Name the culprits (the user (s) or organisation (s)) responsible for it.

Opera already has a browser AI. It should feed the data into it. Let the AI summarize tracking attempts, score privacy aggression per site, detect emerging fingerprinting techniques — and let it speak to us (the users).

Data visibility is privacy’s second half. Without it, I’m blind, even when I’m protected.

Opera can lead the industry here. Brave already does this, but Chrome doesn't. Firefox makes it obscure (uncertain). Opera should make privacy visual, interactive, and actionable. It should let users feel the friction. It should let us see the claws behind the glass.

It should give us insight, not just insulation.

Benefits of this feature:

• It empowers users with real-time awareness of tracking attempts.

• It builds trust by showing what Opera is actually doing under the hood.

• It encourages transparency and user education on digital privacy threats.

• It appeals to power users and privacy enthusiasts who demand granular control.

• This differentiates Opera from some other competitors with a unique, AI-powered privacy visualization layer.

This should neither be buried in dev tools nor filtered through extensions. It should be a visible built-in and with the click of a switch - JavaScript are disabled.

Opera should let we (the users) to add and remove sites that JavaScript blocking will be excluded. If a site deserves trust, we (the users) should have the option to whitelist it. But JavaScript blocking should not assume trust by default. That’s outdated thinking.

Advanced users are tired of getting sandboxed by browsers afraid of offending ad tech. If a site breaks without JavaScript, that’s the site’s fault. Let it break. Let users decide what to permit, not the browser.

Right now, Opera is feature-rich, but this is a missing feature. Brave users can block scripts. Firefox users can too. Why not us?

It’s time to treat privacy as more than a marketing slogan. A script-block toggle is not a luxury, it’s a necessity.

Here are some benefits of JavaScript blocking:

• It blocks malicious, slow, or spying scripts in real time.

• It dramatically improves page load speed and battery life.

• It stops unnecessary CPU drain and memory hogging: This is beneficial for older devices or low end devices like my Galaxy A05s.

• It allows per-site control — power users can tailor their browsing experience.

• This will reinforce Opera’s commitment to privacy and performance.

In a world where cybercrime is prevalent, we need to protect our data so well so that we will not be the targets of cyber-criminals and it will be hard for cyber-criminals to access our data even to the barest minimum.
Privacy matters a lot.

This isn't how modern browsing should work. Subdomains are separate entities with different UI requirements. Treating them as one service, just because they have the same domain name, ignores how the web actually functions.

Opera needs a smarter layout control system.

Here are my suggestions/what we (the users) need:

• A toggle that can be used to switch between mobile view and desktop view per site and not per domain.
  For example, mail.example.com is not news.example.com.

• Persistent layout memory: Let users lock a site in desktop or mobile mode until they say otherwise.

• Temporal overrides: Sometimes you want desktop view just this once. Opera doesn't have to save it unless the user asks.

• A layout manager UI: A list of saved layout preferences, will help we (the users) to view and edit which sites are locked in which mode.

This upgrade is just about users' control. The Opera Team should give we (the users) the freedom to tailor our browsing experience site-by-site, not be stuck with clunky domain-level assumptions.

Opera’s always been the browser that dares to do things differently. This is another time to push that boundary again.

I'm using Opera for Android Beta 85

It's an absolute deal breaker for me. Looking at alternatives now.