The Jellyfin community here is !jellyfin@lemmy.ml
The official forum is at https://forum.jellyfin.org/
What you've got seems to be a truenas specific docker problem.
When you spin up Jellyfin docker, you normally specify a config volume and a data volume, so that as you upgrade, the users and watched lists etc are maintained.
You should be able to save those directories, delete the broken Jellyfin docker instance, and then recreate it pointing at the old volumes.
That way it would bind to the valid IP, but have the old configs and data.
At the command line I could help, but I don't know anything about Truenas sorry.
it’ll work just like SMS does now
I agree with this part of your statement 100%.
It will work POORLY.
Whether it's in the same app or simply a different colour like SMS is currently, it'll be a half assed implementation, designed to segregate your iphone and android friends.
Got an existing iphone group chat? Bet you can't add an RCS participant to it.
Create a new RCS group chat so you can include everyone? Bet it's missing features that you'd get in imessage.
Receive a high resolution video from a friend via imessage? Forward that to another friend via RCS and they'll receive 5 blurry pixels.
And throughout all of this, apple will blame the RCS protocol and say "We're actively working with GSMA to improve RCS".
No one trusts apple for the very simple reason that they have a habit of saying the quiet part out loud: Tim Cook Says 'Buy Your Mom An iPhone'
There's some gotchas in Apples statement:
They have promised to implement "RCS Universal Profile"
This means the bare minimum, not the advanced features implemented by Google and Samsung etc.
An example of a missing feature from Universal Profile is end to end encryption.
They also said: "This will work alongside iMessage, which will continue to be the best and most secure messaging experience for Apple users."
The implication of this is that it won't be in the iMessage app, it will be in a separate but official app, siloing your Android friends from your iPhone friends.
When this comes out, every European is going to shrug and keep using Whatsapp.
It's not the android side that's failing, it's Apples refusal to implement anything other than SMS for cross ecosystem compatibility.
Think about your audience and the specific features that will potentially appeal to them.
Depending on who that user is, the same feature/quirk can be either a pro or a con.
There's lower user numbers here compared to something like Reddit, but the people involved tend to be of an average higher tech literacy.
So there's not as much noise, but there's also not as much signal.
As a user, you can spin up your own instance, which gives you complete control... But it also introduces a financial and moderation expense, not to mention inherently leading to fractured communities.
Just look at the Android discussion, it's occurring on at least:
Android@lemmy.world
Android@lemdro.id
Android@lemmy.ml
etc etc
I don't think it's strictly compliant, although they claim to have based it's syntax on Korn shell, which is the strictest definition of POSIX shells.
You can do pretty much everything in powershell that you can do in something like bash BUT, it will be done slightly differently, so trying to make a script cross compatible is pointless (you might as well just write it natively in powershell etc).
Powershell isn't inherently bad, unlike bash for instance which just allows piping out text output, Powershell can pass around true .net objects.
But if what you're looking for is cross OS compatability, you're pushing shit uphill.
99.9% of the time, I open powershell and just ssh into a "real" linux box.
Isn’t the foam lining replaceable?
A helmet is like an Ogre (or an onion, but never parfait).
I did a quick search for a diagram to illustrate this, and this one will do:
On the outside, there will be a hard layer, normally made out of Fibreglass, Polycarbonate or Carbon Fiber depending on your budget and tolerance for weight. Beyond simply protecting the next layer, it's primary purpose is to spread any impact trauma across the next layer.
Under that will be a thick layer of expanded polystyrene foam - this is what saves your head in the event of unplanned rapid deceleration.
Under than will be some comfort padding, normally attached to removable liners, which helps to keep the helmet comfortably in place on your head.
This is the layer can be removed for washing/replacement.
The one we are really worried about degrading is the polystyrene one, which isn't readily replaceable.
The outer shell is normally sculpted somewhat to assist with aerodynamics, which decrease wind buffeting and noise for the rider.
There's also vents and air channels, visor ratcheting mechanisms and on some helmets provisions for bluetooth communications systems, but that's a whole other story.
Your helmet is arguably the most important piece of kit you have, and the groupthink is to pay as much as you can afford about every 5 years (whether you ride every day or bi-annually).
I ride a motorcycle as my commuting vehicle and I find my helmet needs replacing every 5 years max, as the inner foam lining has compressed to point where it is no longer snug to my face and therefore unsafe.
Push bike helmets would be made of similar materials, just with less coverage.
So as @wander1236@sh.itjust.works says, it would be materials degradation.
FOSS is enshitification-hardened, not proof.
VLC remains awesome because the guy (maybe Jean-Baptiste Kempf?) that controls the project has refused to be bought, has in fact refused HUGE sums of money.
The original author of any project has to right to sell it with the corresponding licence changes at any time.
There's some legal grey area on something like Linux or VLC which have MANY MANY developer hands in the pie, and existing users could certainly fork off the existing releases, but VLC could pivot tomorrow to a for profit company and make future releases of the official VLC a paid product, if they choose too.
@Mountaineer
@aussie.zone