Live, laugh, Lemmy?

I run wireguard and Android with chrome cause firefox doesn’t support pwa. Did you add it to your home screen?

https://silverbullet.md/PWA

Edit: Also I run release V2

It just works™?

Silverbullet supports working offline as a pwa, just click install on the website and you get a shortcut to the web app that you can use online and offline, open it when your online again to sync your changes to the other devices.

alias service="systemctl"

Or even

alias s="systemctl"

Can recommend, works offline and online with PWA support and stores everything in Markdown files for easy migration if you want to change your frontend.

Did you follow the guide?

https://docs.searxng.org/admin/installation-docker.html#installation-container

Nah i don’t. I can hope though and the backdoor is a threat not just for consumers but also companies.

I hope more follow, would be funny if “all chat apps have to include a back door” leads to “there are no official chat apps”

It is expected, the users inside the container are “real” users. They just get offset inside the container and some mapping is applied:

Root inside the container is mapped outside to the user running the container, everything that has the owner “root” inside the container can be read from outside the container as your user.

Everything that is saved as non-root inside the container gets mapped to the first subuid in /etc/subuids for your user + the uid inside the container.

You can change this mapping such that, for example, user 1000 inside the container gets mapped to your user outside the container.

An example:

You have a postgres database inside a container with a volume for the database files. The postgres process inside the container doesn’t run as root but instead runs as uid 100 as such it also saves its files with that user.
If you look at the volume outside the container you will get a permission denied error because it is owned by user 100100 (subuids starts at 100000 and usid inside container is 100).

To fix: Either run your inner processes as root, this can often be done using environment variables and has almost no security impact or add --userns keep-id:uid=100,gid=100 to the cmdline to make uid 100 inside the container map to your user instead of root (this creates a new image automatically and takes a while on the first run)

I though that was the point of surveys?

deleted by creator

Theoretically, google could keep that workaround in the code, yes.

I’m sorry to say but problem solving and computer skills are left at the door.

Maybe

Wouldn’t people use tissues and cause pipe blockage in the long run?

I don’t like Source-available software, especially when they’ve changed from a more open license to this.

To add to this, “Open WebUI” needs to be included, as is and without modifications in all derivations. The term is also trade marked and as such, cannot be distributed without the trade mark owners approval…

https://trademarks.ipo.gov.uk/ipo-tmcase/page/Results/2/WO0000001844530

Arch took away his right to remain silent.

it was of course a horrible laggy mess.

So the freezer froze?

There are multiple reasons but the most important one is: You didn’t enable it.

Caddy fully supports https to the reverse proxy targets, though you’d have to get those targets trusted certificates otherwise caddy wouldn’t connect.

The default protocol for backends is http, most of the time this isn’t a problem because:

• The web server runs on the local machine
• The web server runs in containers/vms on the local machine
  • or is running in a VM and has a direct virtual connection with the caddy vm
• The connection to the Backend is encrypted with a VPN
• Caddy and the web server are directly connected or connected through an otherwise isolated network

Because https requires certificates that are somewhat difficult to set up for internal servers (and were even harder to get before) the default mostly is just to encrypt on another layer of the stack. Afaik at least.