For very basic things maybe, but it has a lot of other weird problems and restrictions. Mutability, no real timezone support, very limited arithmetic, to name a few. As soon as you move beyond the very basic, you want someting more robust.

There is a reason almost everyone use some Date lib, like Luxon and not the built in. And well, having a horrible built in lib that they can’t change due to legacy code breaking is nothing really new or unique to JS.

I open the series folder from the mounted network share and watch it in VLC.

Similar, but I have a RPI by the TV running LibreELEC and Kodi.

The unstable part is just compared to other versions of Debian. Every now and then a package dependency breaks, but usually nothing serious and you can still use the system until it is fixed within hours. It is not like the system will constantly crash, it is still linux.

I have used sid for years without any major problems. Usually only on desktop though.

It should be doable to so some audio analysis of the episodes. They “always” (I am sure some forget every now and then), have an outro and intro around the ad block. With a clearly defined jingle per podcast. You should be able to make a program that analyses the audio and listens for that block and cuts it out for you.

Or if you want some basic configuration, like user management and repo creation. Use something lightweight like gitolite

Nice rack!

That exact same phrase is used in a very different context in other communities!

If it free, there is an incentive to release quantity and not quality, it could become a spam problem. I am all for having a lower percentage though, but 0 could be a problem.

Yepp. Started using Debian around the Ham/Slink releases, haven’t found any reason to change yet.

More often than not that is corporate speak for “we fired the old team and replaced them with cheaper workers. And we didn’t want to pay them to learn the old code/they tried but failed, so we are dumping features now”

I think the last two seasons were very much hit or miss. Some really good eps but also some really awful ones.

Obviously Scarlet Monastery, everything is HR need tank and healer!

But then it is the developers fault, never management

Yepp, and no one really listens to the others, just trying to remember what you did and make sure no one dumps more work on you.

Sure, but even if they started tomorrow it would probably be years before it even could be considered experimental outside of the most daring early adaptors.

Having a combability layer is not ideal but it would mean they could have something worker for more users faster and at the same time see which modules/drivers they should focus on.

What I meant was that if you are returning 404 for example when a user doesn’t exist. You can’t tell if the user doesn’t exist or someone changed the API to remove the endpoint.

But forcing HTTP codes without a moment to think it through seems to be the new fad.

The clown, but flipped with a success field. If it is true then command succeeded, if it false something was wrong and there should be an error field as well.

HTTP codes should be used for the actual transport, not shoe-horned to fit the data. I know not everyone will agree with this, but we don’t have to.

Rounded corners tho… <shudder>

Just a small gif (as png didn’t exist/widely supported) that had the rounded corner. Then if someone wanted to change the color or background you would have to redo all the images. Fun fun.

Approximately at 2024-08-09 09:30 MFA had been removed for all users due to a mistake when MFA was intended to be reset for an individual user.

An UPDATE without a WHERE?

…and it drives me insane when it is not real links but some javascript/button/div-with-onclick/etc and middle click won’t work