MaggiWuerze

I think the flashing is actually when an assistive system triggers the break

Yeah, just have an accelerometer that triggers them

Thats more an issue of using the same lamp for rear lights and turn signal

Be as pedantic as you want, but “reporting” is coloquially used to describe news. This is more akin to a blog

He is not reporting. What’s there not to get? It’s not a news outlet. He just says “I found this neat thing and will now build some insane project around it”. I’m sure if you actually went to look, you would find other sources that talk about the technology in detail and probably did so before he made his video

It’s not reporting on a technology. DIYPerks is a channel about cool projects he does. He shows the build process and explains everything and usually provides plans to follow along

You’re also skipping two energy conversions by keeping it in the wire

I fell like the way investments are currently made, coming up with something new is made almost impossible. Most of the hardware is designed with LLMs in mind

Was my first thought as well. These things really need to find a way to store a larger context without ballooning past the vram limit

Its called Microsoft Java for a reason

If you want to do something java like, try Kotlin. Its a more modern take on java and not developed by Oracle

I have a Philipps OLED TV from 2019, with Android 9 or smth. But WebOS is a different beast.

Well, just because they closed the issue (without resolving it), doesn’t mean it does not speak to their views on security and client breaking changes

The issue is their approach to security. I don’t trust them to properly secure their software, since they have proven to prefer client compatibility over security.

https://github.com/jellyfin/jellyfin/issues/5415

They argue against most suggestion with the notion, that existing clients can’t handle authentication. The devs prefer working clients over a properly secured backend.

You can now extrapolate this idea and every major change that would change the way the API is accessed by clients will be stopped for the sake of continued client compatibility.

Yeah, but since you basically need a VPN to share Jellyfin safely, you now also need to install and maintain that on their end

I will not make myself the tech guy for half my friends and family, just because I can’t share Jellyfin safely without a vpn

Also the people that know how to set that all up and still expose a Jellyfin server to the public internet

Because Jellyfin users like to feel superior. Accepting that other people have other requirements from software is hard, especially when you feel like you choice is the only valid one.

As a long time Plex user, who has a Jellyfin running in parallel, just not shared, I will keep using Plex until they either force me off of it or Jellyfin manages to make accessing servers remotely easier and more secure.