Have you tried it with the original GL.iNet firmware? There might be some optimisations in there that are missing from plain OpenWrt.

To quote myself:

There’s just one little quirk: since this app started out in China, many actors show up with their Chinese names - but can be easily edited to their English names.

The author of the app is Chinese (but speaks English, too).

The actors get imported upon the very first import of a movie/show. And when a movie is imported from Douban first, the actors will all show up with their Chinese transliterations. If you import a new movie from TheMovieDB, they’ll show up with their English names. But as mentioned above, you can edit the names - which is what I usually do for US-movies. Descriptions support multi-language, though. Once an English description has been imported, it should show up for you while Chinese people will continue to see the Chinese description.

And the more English-language users start to use NeoDB, the more initially-English content will pop up.

After Trakt changed to a subscription, I’ve went with NeoDB. This is a federated network, so you can also host it yourself if you like. All entries there can be published into the Fediverse, too. It tracks movies, shows, books, and games. And it automatically imports from IMDb, TheMovieDB, Amazon, Steam, and many more. There’s just one little quirk: since this app started out in China, many actors show up with their Chinese names - but can be easily edited to their English names.

There’s also eggplant.place which is the development build of NeoDB and might be unstable but has more English content.

https://neodb.social/@mbirth/posts/522457362146719720/

Apart from the stuff already mentioned, never stop shouting into the void about stuff that interests you or projects you’re working on. Add a few relevant hashtags so your toots can be discovered. It may take a while, but people will come. Don’t give up.

¿Por qué no los dos? Make Home Assistant your master automation system because it supports a huge amount of devices. And then expose those to HomeKit using the HomeKit Bridge service.

This makes all compatible devices (i.e. everything HomeKit can interpret) show up in Apple Home, too.

That’s how I do it, so I can ask my HomePods to turn lights on and off or lower the blinds.

Let’s Encrypt is. But tools to keep 100s of certificates up to date sometimes are not.

I’d still like some algorithm in my RSS aggregator. One, that detects articles talking about the same thing and groups them.

Then there’s the older way of checking CRLs which any tool of the past few decades should support.

I’m pretty sure it’s the SSL seller lobby just wanting more money, tbh. Selling snake oil security.

And selling “certificate automation” tools.

The point is, if the certificate gets stolen, there’s no GOOD mechanism for marking it bad.

That’s what OCSP is for. Only Google isn’t playing along as per that wiki entry.

Settings --> Posts --> Interaction Bar

Then remove the combined up/down thingy and add the separate up and down chips. They show separate numbers.

Then do the same thing under Settings --> Comments --> Interaction Bar.

Mlem - replaced Voyager for me.

Removed by mod

But will they continue to moderate content by German leftist standards?

GL.iNet also has a KVM now.

Or a better SD card. I’ve used my various Raspberrys with SD cards for years without any issues. The only single incident I’ve had was a card turning read-only. Which I’ve only noticed because system updates were gone after a reboot. But all the main data was still there and accessible. And a simple clone to a new card followed by fsck restored full functionality in the Pi again.

Also: https://rss-bridge.org/

Ah, gut zu wissen! Danke! :)

The important bit is -v /opt/podman/searxng/config:/etc/searxng:Z in the podman call. This will mount your local directory (i.e. on the host the container is running on) /opt/podman/searxng/config into the container as /etc/searxng (which is where SearXNG is searching for its config). Make sure that the local directory exists and is writeable by your user account before starting the container. This way your config will persist even when the container gets replaced by an updated version.

IIRC, after running the container for the first time, SearXNG should put a settings.yml and uwsgi.ini there. You can edit them and restart the container for the changes to take.

On later container updates, SearXNG will put the latest versions of the default configs as settings.yml.new and uwsgi.ini.new. This way it doesn’t overwrite your config and allows you to manually merge the new defaults into your running config. (If you only see the *.new files after starting the container for the first time, rename them and remove the .new part.)

Can Dockge manage/cleanup unused images and containers by now? That’s the only reason I keep using Portainer - because it can show all the other stuff and lets me free up space.