Recently discovered on Aurora Store, and goes pretty quick. Supposed to haven't any tracker

I'm creating a TagGroup and trying to update it:

//background.js

chrome.tabs.group({ tabIds: tabIds}, function (groupId) {

  //1
  // chrome.tabGroups.update(groupId, { title: groupTitle });

  //2
  // chrome.tabs.update(groupId, { collapsed: true, title: groupTitle });

   //3
   chrome.tabGroups.update(groupId, { title: groupTitle, color: "blue", collapsed: true });

  //...

For some reason, none of these functions will set title of a TagGroup, nor collapse the tabs into one.

How to do it then?

MotionBox is a Video Browser built for the Internet.

Designed to access, organize and share multiple video resources.

Built for Motion Freedom and part of the tevolution initiative.

omega is building MotionBox to empower people.

MotionBox accesses and aggregates videos via the VBML language.

It supports DuckDuckGo, BitTorrent, TMDB, Youtube, Dailymotion, Vimeo, Twitch, TikTok, Facebook, Odysee, PeerTube, Last.fm and SoundCloud.

All of this inside multiple tabs and without ever showing an ad.

Is there any recommendations about lightweight browser (about ram management). I'm using Iceraven but is more a more eater. Anyone tried Naked Browser?

Are you using scripts, addons or just turn off images in browser's settings?

Chrome will be experimenting with defaulting to https:// if the site supports it, even when an http:// link is used and will warn about downloads from insecure sources for "high-risk files" (example given is an exe). They're also planning on enabling it by default for Incognito Mode and "sites that Chrome knows you typically access over HTTPS".

Source: https://blog.mozilla.org/addons/2023/08/10/prepare-your-firefox-desktop-extension-for-the-upcoming-android-release/

Archived version: https://archive.ph/x9dHq

Google Chrome will soon be supporting a hybrid elliptic curve + quantum-resistant Kyber-768 system for key exchange in Chrome 116. This should provide some protection in case the quantum-resistant part has flaws, like some other proposed solutions have had. They're looking into this now to give time for it to get implemented by browsers, servers, and middleboxes, and hopefully prevent Harvest Now, Decrypt Later attacks.

It looks like Google's long-running project to split up ChromeOS and its Chrome browser will be shipping out to the masses soon. Kevin Tofel's About Chromebooks has spotted flags that turn on the feature by default for ChromeOS 116 and up. 116 is currently in beta and should be live in the stable channel sometime this month.

The project is called "Lacros" which Google says stands for "Linux And ChRome OS." This will split ChromeOS's Linux OS from the Chrome browser, allowing Google to update each one independently. Google documentation on the project says, "On Chrome OS, the system UI (ash window manager, login screen, etc.) and the web browser are the same binary. Lacros separates this functionality into two binaries, henceforth known as ash-chrome (system UI) and lacros-chrome (web browser)." Part of the project involves sprucing up the ChromeOS OS, and Google's docs say, "Lacros can be imagined as 'Linux chrome with more Wayland support.'"

Previously ChromeOS was using a homemade graphics stack called "Freon," but now with Wayland, it'll be on the new and normal desktop Linux graphic stack. Google's 2016 move to Freon was at a time when it could have moved from X11 (the old, normal desktop Linux graphics stock) directly to Wayland, but it decided to take this custom detour instead. Google says this represents "more Wayland support" because Wayland was previously used for Android and Linux apps, but now it'll be used for the native Chrome OS graphics, too.

On the browser side, ChromeOS would stop using the bespoke Chrome browser for ChromeOS and switch to the Chrome browser for Linux. The same browser you get on Ubuntu would now ship on ChromeOS. In the past, turning on Lacros in ChromeOS would show both Chrome browsers, the outgoing ChromeOS one and the new Linux one.

Lacros has been in development for around two years and can be enabled via a Chrome flag. Tofel says his 116 build no longer has that flag since it's the default now. Google hasn't officially confirmed this is happening, but so far, the code is headed that way.

Users probably won't notice anything, but the feature should make it easier to update Chrome OS and might even extend the lifetime of old ChromeOS devices. This should also let Google more directly roll out changes on ChromeOS. Currently, there can be a delay while Google does the extra build work for ChromeOS, so the standalone browsers get security fixes first.

Archived version: https://archive.ph/EG7nc

I've noticed that FF doesn't like Streamyard (which I think runs on WebRTC) or Google Meet. Any idea why and how to mitigate?

cross-posted from: https://lemmy.ml/post/2039017

Have you ever been in a situation where you'd needed to work on different/new machines on a daily basis and wished there was a way to have all your essential Firefox configurations/addons/bookmarks on those machines without connecting your precious Firefix Sync account with all those stored passwords and credit cards?

For a while, I started to prefer an another web browser on Desktop, Min (besides Firefox). It's based on Chromium, but uses Electron for the interface. It's been around for a while, but I only discovered it a few years ago.

So this year's August, it got an early support for opening multiple pages on more than 1 window. To become a stable feature, it will take more time. However, Min's main developer had less free time to work on the project from September.

Also: https://bunatimes.com/technology/56403.html

Just interesting and a nostalgic watch.

Very lightweight browser for Windows and Linux (also a fork called 'White Star' for Mac). I find it to be really decent besides for watching videos and loading some websites. Just looking to see if anyone else has a different opinion on it