For me it works fine, but I guess that might be because I use the flatpak version of Firefox.
For me it works fine, but I guess that might be because I use the flatpak version of Firefox.
deleted by creator
That sounds like browser.download.start_downloads_in_tmp_dir combined with “open with…”. That setting should download to tmp whenever you open it directly in an application. The other setting (browser.download.open_pdf_attachments_inline) should only be enabled if you want to open PDFs in the browser without downloading them.
For general usage, it doesn’t really matter. Distrobox is inspired on toolbox and provides some added functionality and configurability, like init scripts and the ability to run different distros, as well as creating desktop shortcuts on your host system. If you don’t need all of that, I’d stick with toolbox, as it’s preinstalled and works well.
Average none, though 2.5 Gbps is getting more and more common and WiFi is catching up too. You could max out multiple slower devices at the same time without hitting the limit of your uplink. I don’t have a use case for that, so I’d only upgrade from my current 1 Gbps to higher speeds if the price is comparable. That doesn’t mean that others don’t have a use case for it.
Agreed. In the past you would pay for calling and text messages and data was often unlimited at the higher tiers, but since nobody pays extra for calling and texting anymore, they’re now charging for data. Luckily they can’t charge extra for EU roaming anymore.
Data caps on landlines is something that I haven’t seen for a very long time in my EU country. The last time I had a subscription with a data cap must have been with a 56k modem, if at all. Cable and DSL might have had fair use policies back in the day (or maybe they still do, who knows), but no hard cap. Or at least not that I can remember.
Internet nowadays is way too important to have data caps, especially at home. 5G should definitely be next. Differentiate in speed all you want, but ditch the caps.
The regulation actually enforces that PD is implemented if high speed charging is available and that it can’t be limited in speed compared to any other charging protocol that’s also available on the device, irrespective of the charging device used.
We don’t need to guess if we can just read the regulation: https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32022L2380&qid=1691523718368.
Note there are also instructions to make this (partially) work in browsers that are not supported by this extension: https://gitlab.com/magnolia1234/bypass-paywalls-clean-filters. I’m using it in Safari on iOS with Userscripts and AdGuard, which works pretty well.
That’s slightly different and more often than not completely ignored. This is a better alternative: https://feddit.nl/comment/1153941.
That already exist: https://community.mozilla.org/en/campaigns/firefox-cookie-banner-handling/. There is also a flag to enable it in the GUI (to let it appear in the settings).
If there’s anyone that hates what Red Hat has done here, it’s me, but what AlmaLinux is doing is exactly what Red Hat was aiming for according to their statement, which is that clones would use CentOS Stream as their upstream and develop and contribute their own patches instead of copying RHEL bug-for-bug. The other reason is of course to convert people that need that bug-for-bug clone to paying customers.
With SUSE having announced a RHEL compatible alternative, I’m hoping that some people/businesses will consider switching their environment over to them as a more OSS friendly competitor that also offers support. If that distribution gains some traction, I foresee that some of the clones might use that as their upstream and that OEMs will follow suit and test their drivers on those distributions. There are enough people/businesses that are reliant on a mixture of RHEL and Alma/Rocky and for those life got a bit harder because of RHEL’s actions.
The next release of Fedora will ship DNF5 as the default package manager, which is supposed to be much faster.
The base os is immutable, but you can still change configuration files, compile and install local software (but not in the immutable directories), install desktop environment extensions, add custom repositories, etc. You can also layer packages, but most graphical software is best installed as flatpaks (but not mandatory). So it depends on what tinkering means for you. If it means messing around with binaries in the default locations, like /usr/bin, then it’s not for you, but for many other things there is a way, it’s just a matter of getting used to the separation between the immutable base layer and the things that you build around and on top of it.
Your title too :)
I thought for a second that the top one was an e-ink price tag, which would’ve been even dumber.
It is, though. Safari has native support for 3rd party adblockers, it’s just that many people don’t know. AdGuard is one of the good options. Safari is doing the actual blocking for the most part (the extension just hands over the filterlists), but nowadays some of the adblockers include an optional extension that applies some rules for complex ads that are not supported by the Apple API, such as on YouTube. As an end user you just have to install and enable the adblocker.
Then there are also other browsers available with built-in adblockers. Admittedly those are all limited in some ways because they’re forced to use the same browser engine (outside of the EU), but they are very effective at blocking ads.