Well, they do share one thing in common and that they are all massive users of or suppliers for datacenters. This makes sense since Linux is used in all kinds of servers and appliances. The possible bias of these companies is going to more towards the Cloud and SAAS rather than anything else. Likewise, generative ai is marketed nearly solely as a cloud technology, when it can be hosted locally. We are like a year or two off the average person’s web ai usage being possible to replace by ewaste gpus or entry level consumer hardware.

Nevertheless, I don’t see how the Linux foundation can really be steered towards that bias in a way that is concrete. Its just the kernal. All the userspace development is done by other parties.

sudo apt install kate it is then!

Fuck yeah! This slaps. Brb while I get my headphones to listen to it again.

What made you switch from Notepadqq to Kate? I’m currently still stuck on my Notepad++ bias too.

We should celebrate these kinds of changes. Like its great that they’ve already achieved so much and not just that, but left behind a group of folks just as committed in the future of the project.

I always feel that posterity of your work beyond your own contribution is the real achievement and a sign of humility.

Oh, I’ve been there! lol Yeah, you sometimes don’t expect to have to update an entire stack, not just one thing. Possible the companion app image was just released later and it wasn’t on you either. :P

But yeah, give the cron job a try. I’d be curious to try it out myself! In theory your webinstance shouldn’t cut out unless you click on something the exact moment the container is resetting.

What kind of issues have you had? How did you resolve them?

I haven’t used this tool specifically, but anything involving Youtube is always going to be an uphill battle. In the instance of a video downloader like Channeltube, you frequently need to feed it fresh cookies to make sure Youtube doesn’t flag it as a bot. I assume this is a similar situation.

The requirements also list ‘‘2gb if you restart frequently’’ so there might be a memory leak issue, or the way it’s setup means the RAM usage will increase in perpetuity.

I would just script a task to restart the docker container every hour. Shouldn’t be too much a hassle, you’re unlikely to ever notice since it shouldn’t take more than a few seconds. I would track its RAM usage over a few days too. See if there’s something fishy happening. Something like Beszel will let you track your docker socket, so usage per container. Preferably left on read only imo.