Porn websites will most likely going to have age verification enabled. So, it might not matter what OS or browser kids use to visit such websites.

Is it even technically possible to enforce it on open-source application, with code readily available for tweaks and modifications?

Any mainstream Linux Distro + https://www.privacyguides.org/en/tools/

Make it publicly available to the world or just for you (and people you know)?

I hadn’t switched from Windows to Linux for someone to tell me what to do with my system.

I’ll do whatever I wished to do. I don’t care about others’ option.

At this point, the count stands at 1500+ https://www.phoronix.com/news/Arch-Linux-AUR-More-Than-1500

You can self host the LT service as a docker container.

https://github.com/languagetool-org/languagetool

https://tailscale.com/docs/features/containers/docker/how-to/connect-docker-container

Tailscale

If running as rootless docker then it’s free. But, if running as rootful docker then pay up.

/s

A true man of culture, I see 🫡

Librewolf.

Huh!, just Disconnect the drive from power source and it will OFF.

Please refer to this comment: https://lemmy.ml/comment/24567541

If you need any further information, let me know.

Note that I’m running it on a rootless docker instance, and NOT on Podman. So, the following solution might or might not work for you.

services:
  degoog:
    image: ghcr.io/fccview/degoog:latest
    volumes:
      - ./.data:/app/data
    user: "0:0"
    ports:
      - "4444:4444"
    restart: unless-stopped

Explanation: rootless docker works a bit different from rootful docker. user 1000 (which is you on your server/machine) will be mapped to a different UID (e.g. 32555). This is to ensure that any process in docker container can’t have access to folders/files that you have access to, in case it manages to break free of docker containerization.

When you put user: “0:0” in a rootless docker container, it will assume your UID 1000 (which is you on your server/machine) inside docker container.

While it solves the file permission issue, but it is NOT a recommended way.

with user:1000:1000

with user:0:0

Ah! Forget about that part. The docker-compose file you provided on repo works for rootfull docker.

For rootless docker, it works, but library import is not possible for file permission issue.

I think I know how to solve it, I will give it a try over weekend, and will let you know.

First of all, thanks a ton.

I have been using SearxNG for more than year, running it as docker container on my Homelab. It’s connected to internet via Mullvad VPN.

Lately, I have see both Google and Bing search engines are either not working or returning complete garbage results.

My firewall setup doesn’t allow any incoming connection to homelab, except from LAN. So, bot accessing my SearxNG instance might not be the issue.

With degoog installed in the same fashion (docker + VPN), google engine seems to be unblocked for me (so far).

Not sure why degoog is not getting rate limited like SearxNG on the same system and same VPN. But, at least I’m happy :)

Tailscale, if you don’t want to make your services available to anyone else than you (and people you want to grant access to).

Sharing release log is not all about what “I” find as interesting. It is rather a notification to all other users of the software that a list of new features or big fixes are now available.

Not all of us are actively tracking release cycle of tools we use.

Each of us have our own use cases. What I might find trivial, another person who frequent this forum might find really helpful.

If you are not interested in the same software or not intended to use it or not using it currently, feel free to skip the post.

The other day I posted another article[1] from linuxiac.com highlighting only important changes, and someone suggested[2] to post link to actual change log, instead of URL to 3rd party article.

Today you are asking the other way around :D

[1] https://linuxiac.com/truenas-25-10-open-source-nas-released-with-nvme-of-zfs-enhancements/ [2] https://lemmy.ml/comment/21935248