She absolutely would.
Good policy makers find a way to make their work happen.
Nope. It's an out-of-use term, but it is definitely a synonym of bullying.
I mean, you just keep asking different people whether a thing that does X exists. They've all said no, but you can use Y plus mods to do it. Doesn't seem good enough for you.
Now you've risen to "VLC cant do that". I've shown you it can, and you not only beak back at me about it being CLI, but downvote me as well. Thanks for that.
streaming not transcoding
Literally the first sentence:
"This functionality allows you to link VLC's transcoding capability with a segmenter which will in turn create the series of files needed for http live streaming to the iPhone"
You don't know what you're talking about, and you don't understand your own problem.
Regardless of any info you get here, you will still need to problem-solve. Good luck.
Come on, dude. Now you're just trolling.
https://wiki.videolan.org/Documentation%3aStreaming_HowTo/Streaming_for_the_iPhone
Quit while you're ahead and just go do some reading.
I believe photoprism does its face recognition in the cloud, which is a dealbreaker for many.
Oof, a lot of vitriol in this thread.
In the end, security is less about tooling and config, and more about understanding the risks and acting accordingly.
I expose jellyfin to the internet, but only to a specific public IP. That reduced my risk considerably.
Raspberry migrated away from x.org a number of months ago. You'll need to install all the x and x forwarding components.
How was your night on the sofa?
My favourite litmus test for coolness.
There are a number of ways to install nextcloud, and docker is only one of those.
Yes, NC isn't ideal in many ways, but it shouldn't be as painful as you're describing to run it.
It's easy to cast this as an all-or-nothing kind of thing, but it is possible to make multilateral deals where everyone involved gets what they want. That's why we want competent and trained people governing these transactions.
Paperless-ngx is great, but it is particularly bad at handling PDF documents. Roughly half my documents just won't import.
https://github.com/paperless-ngx/paperless-ngx/issues/3933
https://www.reddit.com/r/selfhosted/comments/yfjxww/paperlessngx_not_all_pdf_files_can_be_imported/
I live in bc, and I visited California last summer. It was a "don't meet your heroes" kind of experience.
Crossing the state line from Oregon into Cali was jarring: the (terrible) quality of the roads, local economy, even the cars... It reminded me of some impoverished parts of Louisiana when I visited in the early 2000s. Neglected houses, but $80,000 trucks in the driveway.
Then you get to the city... A never-ending spread of garbage and human encampments. Like watching a documentary about a war-torn country.
By contrast, I live in a small town in BC. It's pretty clean, quiet. I also travel to the metro Vancouver area for work; clean, easy public transport to many places in the valley, encampments can be found, but not nearly at the same, massive extent as I saw in Cali.
Don't get me wrong, I'm not expecting the California of "The Karate Kid", and I understand the amplification from population, but California was.... Kind of a shit hole.
This comparison the gov of california is making between bc and california is reeeeeally stretching. To compare the two, you'd have to imagine letting BC go to shit and be neglected for 75 years.
Turnkey images are usually built on popsicle sticks and chewing gum; they use old packages, their configs are often really janky and they do not like being updated.
I'm not kidding you, you'd be better off building nextcloud in a generic debian container.
As for the errors, as others have mentioned these are more or less easily fixed one at a time.
... Green snake in a sugar cane field.
HBC failed to adapt in the 70s to customers moving away from catalogue orders, it failed to adapt to malls in the 80s, and it failed to decommission its expensive white elephant department stores in the 90s.
By the time it was being passed around like an old car, it was already dead and gutted of its value.
I'm all for reminiscing on things lost, but this is just a funeral 45 years late. HBC died a long time ago.
There's a bunch of posts about the iptables-save function of the built-in iptables module not working in many cases, so I figured it was a safer bet to suggest the playbook include an actual command invocation.
In my personal experience, the module doesnt actually save the persistent rule in about half the cases. I haven't looked into it much, but it seems happen more on systems where systemd iptables-firewall is present. (Not trying to start a flame war)
I think in this case, there just isn't awareness.
deleted: recent similar post
Are you OK?
Generally, you set up a rule + command playbook, where the command invokes the iptables-save command.