stevestevesteve

joined 2 years ago
[–] stevestevesteve@lemmy.world -1 points 19 hours ago (1 children)

"Breaks all compatibility [with emby]" was my interpretation of that. Not a huge deal either way but I'd definitely have been calling it 11 with this DB rework myself

[–] stevestevesteve@lemmy.world 11 points 1 day ago

They're saying they left the voicemail as "on leave" when they were not in reality

[–] stevestevesteve@lemmy.world 22 points 1 day ago (1 children)

Basically, yes. Forces plugins not to use potentially database-engine-specific SQL so that server admins don't have to select their DB based on plugins for jellyfin being compatible.

[–] stevestevesteve@lemmy.world 12 points 1 day ago (6 children)

I kinda agree here. https://jellyfin.org/docs/general/contributing/release-procedure/

Claims to follow semantic versioning, explicitly mentioning changes to plugin APIs as reasoning for a new major version.

[–] stevestevesteve@lemmy.world 1 points 1 month ago (1 children)

While I appreciate that time zones change including dst... Your porch light shouldn't care about dst, it should probably just care about actual light levels

[–] stevestevesteve@lemmy.world 2 points 1 month ago (3 children)

Fwiw v clocks don't need to have WiFi to auto adjust for dst. Just being date-aware and having a method to configure dst is all it takes.

[–] stevestevesteve@lemmy.world 0 points 3 months ago

God damn why's the world so shit