Madis

uBOL is entirely declarative, meaning there is no need for a permanent uBOL process for the filtering to occur, and CSS/JS injection-based content filtering is performed reliably by the browser itself rather than by the extension. This means that uBOL itself does not consume CPU/memory resources while content blocking is ongoing – uBOL’s service worker process is required only when you interact with the popup panel or the option pages.

uBOL does not require broad “read/modify data” permission at install time, hence its limited capabilities out of the box compared to uBlock Origin or other content blockers requiring broad “read/modify data” permissions at install time.

Emphasis mine. No background processes, including a website-reading permission does indeed sound more optimized for mobile, where people may have limited resources.

Serious question though, has any other company matched their 4o model yet? Maybe Claude?

Except when you ask it how it works

Because it keeps getting updates?

Honestly, I’m shocked there aren’t way more. We have the Google Store, Samsung Store, Amazon store and…that’s it?

There are plenty of repositories for F-Droid, and from what I’ve heard, also for Aptoide.

That said, it is not really beneficial for most companies to compete with Google Play since they know the user base will be smaller, user experience will be worse (install warnings, no auto-update), and people may get affected by malware if they don’t pay attention to where they are downloading things from (may download a scam app directly instead of the legit app store).

It would be nice if a competitor entered the space where usability is the goal and be an open source solution.

ReactOS?

For other Chromium browsers or those who don’t see this yet, enable chrome://flags#extension-manifest-v2-deprecation-warning.

Search engine crawlers identify themselves (user agents), so they can be prevented by both honor-based system (robots.txt) and active blocking (error 403 or similar) when attempted.

With manifest v2, extensions could block the content however they wanted, reading and modifying DOM as they see fit.

Google claims that it is a security risk, so with manifest v3, extensions can only create and give the browser rules and the browser itself will block content based on them. The rules have a limit in size and capabilities.

If that was still not clear, try thinking of unrestricted SQL access vs a UI for modifying a database.

Floating?

tabs themselves ought to be part of the window decoration, not the app

Well, Windows did try that. It sounds cool as an idea, but it also severely limits what the tabs can do, as most programs don’t need tabs that are as advanced as browsers’, and even browsers’ implementations of tabs vary widely.

Sounds like a work profile, so you could probably simulate it already with something like Island. Although I can’t remember if it also has a PIN feature.

Well, if they wouldn’t, then someone else still would. Apple? Amazon? Yahoo?

Do they all connect to their phone networks at the same time? I doubt that…

What exactly is the great advantage of eSIMs if you have a dual SIM phone?!

If the phone supports a normal and eSIM at the same time, they are equivalent. Because in many countries, dual SIM phones are (and will be) harder to get than single SIM ones, so having eSIM at least allows that.

Ahh, now that explains why I just saw a smaller number.

Floorp is based on Firefox ESR. Floorp will be updated every 4 weeks, with security updates provided before each Firefox release.

Floorp looks nice and customizable, but in terms of updates it doesn’t seem very sustainable yet.

ChatGPT itself doesn’t know where it got the info from, so it makes up links and names - it’s a language model, not a search engine.

On the other hand, if you manage to find a reputable source and give it relevant metadata, it can format a nice citation for you, saving you time on that instead.

Indeed, they don’t have to bring back the XUL. The power users would just appreciate…

• new extension APIs that interact with the browser UI
• bring back toolbar customization that was removed for no reason (we can’t even move the extension button at this point…)
• bring back compact mode and better themes (without requiring CSS and about:config tweaks)

I think it will be back this March with the new laws (Digital Markets Act).