kevincox @ kevincox @lemmy.ml

https://kevincox.ca/

---

Read more

Posts

6

Comments

809

Joined

5 yr. ago

Moderating

---

Oh, flac fixes for HLS. I wonder if https://github.com/jellyfin/jellyfin/issues/8722 was fixed. I'll have to try it out today.

You could go columns for the content, but I think my ideal layout would still have the main content in a single column. I would put all of the chrome horizontally through. For example no header before and footer afterwards, put everything in different columns. Maybe even throw some extra navigation on the screen.

You don't need to use every pixel, just avoid putting things offscreen unnecessarily.

That doesn't seem compatible with the MPL. Or is it just their modifications that aren't in the original source files that are licensed this way?

I also had a bad experience where I had a test website under a megabyte in a storage bucket. It was under the free tier and sat there for a few years. Then one month they sent me a bill (it was small, a handful of cents). Contact support saying that this use is under the free tier. They said that data was added then removed from the bucket. I hadn't logged into the account, no living API keys. They wouldn't forgive the charge.

Luckily my credit card had expired so they just locked my account.

I think so. IIRC there are a few different implementations. But if you configure any of them Android will automatically use it to run non-native apps.

Do you have an ARM emulator installed? I don't think the game ships an x86 build. Other than that it just worked.

This is also true in lots of places like Canada and (IIUC) California. But very frequently it doesn't happen. In Canada you can report it but then nothing happens.

With ansible you need to change the relevant step to use apt remove instead of apt install and to change the config file step in a step that removes the file.

Wait until you have 2 services that use the same resource. Now you need:

1. When both are enabled the resource is set up.
2. When either one is enabled the resource is still set up.
3. When neither is configured the resource is removed.

Doing this with Ansible is a nightmare. And 99% of the time you don't even realize that you have this problem until your configs don't work for some reason.

Or a crazy idea, just post the text as text.

I would try to avoid VP9. Hardware support is spotty and I suspect that new hardware is going to relatively quickly phase it out. AV1 is better in most circumstances except for a few devices that have hardware VP9 support but not AV1 (a few years of Android phones mostly). So unless you need a specific device you currently own to have hardware decoding support (only really matters if you are on battery for <=1080p content) just skip VP8.

I would avoid h265 if you prefer free (libre). The only real advantage it has over AV1 is that devices started shipping hardware decoding support a few years earlier. If you need that and care about file size/quality then yes, you may need to go h265. But otherwise I would lean towards AV1 (better quality) or h264 (basically 100% compatibility).

My short opinion:

Video

h264 is the best option for compatibility. There have been free software encoders and decoders forever and IIRC all patents have expired. Basically every device you will encounter and every software system can play h264 videos and the encoders are fairly good.

AV1 is the best option for quality. It is completely free and is becoming widely supported. It will likely be supported for a long time as it is the first widely available high quality free codec. It is significantly better quality than h264 so will result in smaller files for the same quality or better quality for the same file size. Hardware decoding support has only really become common in devices that hit the market in the last few years. But most new devices will have hardware decoding.

Both of these are web-compatible as well which is nice.

Audio

Opus for lossy and FLAC for lossless are both some of the best codecs in their class, completely free and widely available. There are also both web-compatible.

This is the science we need.

It's a greeting. It is meaningless other than a polite gesture. Just like when people say "Good morning" they aren't really wishing that person a good morning, just saying something friendly.

Plus the response is naturally escalated based on how well you know the other person. The first time you walk into a shop it is "How are you?" "Good, you?" "Good thanks" But if you have been getting your morning coffee there every day for a year maybe you do actually share something a bit personal. Probably starting off with a positive "Great, I found $5 on the street this morning" and eventually becoming personal and maybe even saying something like "Not great actually, ...".

So it is actually a nice way to transition into a more intimate conversation as you get to know someone.

Often what happens is that when you sign up they also make an API call to their email list service. Then when you delete your account they remove you from their DB but often forget to remove you from the other services. This obviously isn't acceptable but often not intentional.

It really depends on the quality of software you are running? A SMTP, IMAP, Mumble, Photoprism, Jellyfin, bittorrent, Tor, Subsonic compatible server, who even remembers what else? Fine. One small Minecraft world? Boom you're dead.

"Mouse movement detected, please restart for changes to take effect."

Although the Android kernel is slightly customized isn't it? I thought it exposed a few extra syscalls. How do these work on Waydroid?

I find rail more comfortable than bus and it is cheaper to run at high frequency. The main downside is flexibility (you basically need to close the route to fix the tracks, or if something is blocking them) but overall I find it much better, especially with grade separation.

A lot of cultures ended up with effective currencies. Whether that was grains of rice or chickens there ended up a small number of items that had a well understood value and ended up being the default item of trade, not because the receiver needed those items but because they were known to be easily exchanged with others.