Every developer wishing to offer applications on F-Droid will have to register their identities and package names to Google for Android devices to install their apps, regardless of the distribution platform (F-Droid, Obtainium, GitHub releases, etc.)
From my understanding, it will only allow apps that were registered, so since ReVanced uses identical package names to the patched apps, it probably won’t work unless they start using ReVanced-specific package names that are tied to their identity. But that would allow Google to block these package names (or ban ReVanced completely) if say, Spotify or YouTube complain about them.
Hopefully, the EU and other jurisdictions block this.
This is very similar to the notarization process Apple introduced to comply with the EU requirement of allowing third-party stores, and yet the EU doesn’t seem concerned (maybe because Apple did not allow third-party stores in the first place, will it be different for Google?)
I first read the original report from Android Authority thinking it would only be an additional hurdle for third-party stores and developers, but I’m now thinking that it would potentially block the use of ReVanced
What’s your issue exactly?
Personally, I set up Caddy with subdomains like radarr.local.example.tld, added a DNS entry on my domain so that *.local.example.tld points to the local IP of Caddy, then followed this guide so that Caddy issues TLS certificates using the DNS challenge (since the subdomains don’t point to anything accessible from Internet) along with the caddy-docker-proxy plug-in to easily manage upstreams.
Don’t you have any off-site backup? It would help keeping some peace of mind knowing you have a copy somewhere else.
In my experience with unbound, it tends to return expired records in the hope that they are still valid, causing issues with services hosted in the cloud, where IP addresses rotate regularly. What I did was update the serve-expired-ttl setting in unbound’s configuration to 3 hours (down from the default 24h)
Ah, good idea! I just don’t have any non-magnetic screwdriver at home, I’m afraid as to what might happen if I get its magnetic tip close to a drive.
Oh wait, I found a lousy screwdriver, it works like a charm! It’s definitely the bottom one. Thank you very much!
I personally ended up running my containers on a VM on top of TrueNAS to get the best of both worlds (and because back then running applications directly on TrueNAS SCALE was convoluted)
You could read this article where the author runs NixOS in VMs on top of TrueNAS.
This. I have been using it a lot lately to manipulate CSVs, it is such a godsend.
I guess the only appeal of third-party browsers on iOS is synchronization with their desktop counterparts. Maybe ad-blocking if the capability is offered (I’m not so sure about this one)
There’s an issue on Bazzite’s repo asking for new-lg4ff and other kernel modules to be added. While the issue is still open, it describes a workaround[1][2] but it requires building the DKMS module and layering it on top of Bazzite on every kernel update.
Edit: re-reading your post and Oversteer’s README your wheel should be supported by the default kernel, I’m not sure new-lg4ff will fix your issue (and the latter does not list the G920). The issue must be somewhere else. I wish I could help you, but I have yet to try Assetto Corsa and Dirt Rally with my Driving Force GT on Bazzite.
I haven’t used an immutable distro, but if it’s a problem, I’m sure that there’s a way to defeat the immutability. If it just mounts the root filesystem read-only, then
# mount -o remount,rw /Will probably do it.
It will work until the next reboot (and I believe it won’t work on Fedora 42 as it now uses composefs), on Fedora Atomic Desktops you have to use layers to add additional packages using rpm-ostree
(Edit: formatting)
This. Just setup fail2ban or similar in front of Jellyfin and you’ll be fine.
Oh, that makes sense.
The fuck is “non-tariff cheating” supposed to mean?
I believe Linux Server builds images every day for most of their containers, even though there has been no code changes.
The first one also has better code coverage and way more pulls on Docker Hub.
What’s wrong with GTA V? The RTX 3080 fares better than the RX 9070 XT. The 9070 performances are also all over the place in Quake II RTX.
I would add that you can follow this guide for building Caddy with DNS Provider modules. For Docker you can start from the instructions for Caddy Docker Proxy