Unpopular opinion, if you’re going to use a Debian based distro you should just use Debian.

Yes, it is command-line/BASH heavy however, once you learn it it’ll make all the other Debian based distro’s even easier to manage. Only real difference is system directories are in different locations distro-to-distro.

deleted by creator

So… they’re doing exactly what apple was forced to do.

Yewtube Is a third party front end for YouTube using Invidious, more private, no ads and if you pair it with Freetube you can even skip in video advertisements/sponsors.

I’ll just leave this video guide here to cure world of this cancer

~~https://youtu.be/xL23Xvv1Pis~~

https://yewtu.be/watch?v=xL23Xvv1Pis

Fixed that for you.

Why not spin up a pihole instance? Once you setup your blocklists you barely have to maintain it besides the occasional update.

Hell, if you don’t have a spare machine to run it on you can likely run it locally and then change your PC’s network to use it as your DNS resolver.

As another person mentioned Proton is Linux’s compatibility layer for Windows applications, from my understanding it installs necessary .NET frameworks and other dependencies into a fake C:\ drive an then utilizes that fake C:\ to trick the game into thinking it’s running Windows.

Every windows applications I put through Proton has not once failed to open. Now the claims that Anti-Cheat for games isn’t supported is purely false, most popular anti cheat’s do support Linux however, it’s entirely up to the publisher to tick the checkbox to allow Linux users to play.

Battle eye, Punk Buster, Easy Anti-Cheat all support Linux natively.

This right here, if I can do the same to my work desktop I would be in my glory.

I dunno, I started with Debian and then many months later learned that it was one of the harder distributions given the outdated packages.

Glad I chose Debian because Ubuntu, Linux Mint, Kali Linux, PureOS, etc are all derivatives of it.

deleted by creator

or… better yet, not agree to the Russia’s terms and prevent the app outright?

Reverse proxying was tricky for me, I started with Nginx Proxy Manager and it started out fine, was able to reverse proxy my services in the staging phase however, once I tried to get production SSL/TLS certificates it kept running into errors (this was a while ago I can’t remember exactly) so that pushed me to SWAG and swag worked great! Reverse proxying was straight forward, SSL/TLS certificates worked well however, overall it felt slow, so now I’m using Traefik and so far have no complaints.

It’s honestly whatever works for you and what you prefer having.

I honestly never tried Ventoy myself so I can’t really give you a proper answer to this however, after reading into it I see no reason why it wouldn’t work? So long as GParted can access the systems disks there shouldn’t be an issue.

Put GParted ISO on a thumb drive using Rufus or BalenaEtcher, in your BIOs change the boot order so that GParted boots first, boot into GParted an then readjust/delete your partition as you need be.

Pretty straightforward for the most part.

I agree, hence why I left the note at the bottom of that comment, yes it does encourage bad practices but, if all OP cares about is that it works then it should be fine.

In my other comment I instructed OP to move the volume to their users home directory so they don’t run into permission issues like this again.

Taking a look at your docker-compose.yml I see this volume mount:

volumes: 
- /volume1/SN/Docker/searxng-stack/searxng:/etc/searxng:rw

Whereas /volume1/SN/Docker/searxng-stack/searxng is the directory on your system docker is attempting to use to store the files inside the container from /etc/searxng.

Example of a volume mount that’ll likely work better for you;

volumes:
- /home/YourUser/docker/config/searxng:/etc/searxng:rw

The tilde (~) acts as your current users home directory (aka: /home/YourUser) not owned by root and where docker persistent volumes should be stored.

Edit: I feel like I was wrong here, given that your run sudo in docker compose up -d the tilde will likely not work here and instead point to the /root directory instead. I’ve updated the above to reflect the appropriate directory for your volume mount.

After making the change over to that directory and configuring SearXNG how you like re-create your docker container with sudo docker compose up -d —force-recreate

Apologies for the poor formatting, typing this on mobile.

Edit:

Note: if you want to expose the port do not add the 127.0.0.1 like how I have in my docker-compose.yml.

Edit 2: Corrected some things…

have you checked the directory & file permissions with ls -la /Your/SearXNG/WorkingDir ?

The error in your log is telling you that the container does not have permission to that directory/file, you can essentially bypass this with sudo chmod 777 /Your/SearXNG/WorkingDir/* and sudo chown 1000:1000 /Your/SearXNG/WorkingDir/*

However, if you’re looking for security best practices this is not advisable but if all you care about is that it works it should be fine.

Apple left this little note in their article;

*Note: To use read receipts, you and your recipient must turn on iMessage.

Which leads to believe the toggle is for iMessage only.

as I do not get read receipts from some people with iOS and some I do.

This is what I’ve heard from my Android homies as well, it’s very much a hit or miss it seems.

TIL google developed the RCS protocol.

Another reason for me to leave it off.

They’re referring to iOS devices, the Read Receipts toggle on iOS is for iMessage not RCS.

I personally left RCS off until Apple addresses this.