🇮🇹 🇪🇪 🖥

  • 0 Posts
  • 86 Comments
Joined 1 year ago
cake
Cake day: March 19th, 2024

help-circle





  • Well, your argument at the moment seems to be purely based on your opinion on on the fact that someone people do use the term in a derogatory sense, but this absolutely doesn’t translate to “it is generally used” as such.

    The argument of the other person seems to be grounded on the empirically easily verifiable point that you can find plenty of non derogatory uses of the word in mainstream media, which is a solid argument against the word being “generally used” in a derogatory way.

    In fact, I believe your argument really is “incels and others in the manosphere use this word as a derogatory term, and using this word can associate the user with them, hence I don’t use it and I don’t recommend to use it”. Which is a perfectly fine position, which I personally disagree with, but that doesn’t rely on a distortion of reality and is a consequence of a personal political choice (that I respect fully).



  • I presume you mean running Plex in host namespace. I don’t do that as I run the synology package, but I can totally see the issue you mean.

    Running in host namespace is bad, not terrible, especially because my NAS in on a separate VLAN, so besides being able to reach other NAS local services, cannot do do much. Much much much less risk than exposing the service on the internet (which I also don’t).

    Also, this all is not a problem for me, I don’t use remote streaming at all, hence why I am also experimenting with jellyfin. If I were though, I would have only 2 options: expose jellyfin on the internet, maybe with some hacky IP whitelist, or expect my mom to understand VPNs for her TV.

    (which doesn’t harden security as much as you think)

    Would be nice to elaborate this. I think it reduces a lot of risk, compared to exposing the service publicly. Any vulnerability of the software can’t be directly exploited because the Plex server is not reachable, you need an intermediate point of compromise. Maybe Plex infra can be exploited, but that’s a massively different type of attack compared to the opportunities and no-cost “run shodab to check exposed Plex instances” attack.



  • Well, as an application it has a huge attack surface, it’s also able to download stuff from internet (e.g., subs) and many people run it on NAS. I run jellyfin in docker, I didn’t do a security assessment yet, but for sure it needs volume mounts, not sure about what capabilities it runs with (surely NET_BIND, and I think DAC_READ_SEARCH to avoid file ownership issues with downloaders?). Either way, I would never expose a service like that on the internet.


  • Not to be “achtuallying” bit VPN is not a way to remote stream, it’s a way to bring remote clients in the local network.

    Likewise exposing services on the internet…not really going to happen esepcially for people - like me - that run plex/jellyfin on their NAS.

    I don’t have a horse in this race, i don’t use remote streaming, I only ever streamed from my nas to my 2 TVs, and I am experimenting with jellyfin. But for those who do need remote streaming, jellyfin is going to be problematic.





  • I have opposite experiences! Multiple Linux laptop, with multiple docking stations: a bit of xrandr magic and everything works, forever. (BTW, try setting manually the refresh rate at different values for the two monitors via xrandr, I have solves a similar problem to yours in the past by creating a dedicated display class.)

    On a Mac, it’s impossible, I have to plug one cable directly in the computer to make it work, and the quality of the output on 2k monitor is way worse since they disabled sub-pixel rendering or some stuff.

    Windows also works decently on this regard, until it doesn’t (my partner’s PC stopped recognizing HDMI monitor at some point, and the debugging was frustrating as hell).




  • I can relate with your story as a fellow acrophobic (relatively mild…), and it reminded me of a similar but very different situation I lived.

    I was on a holiday with friends, we were planning to do some canyoning. I scouted the path beforehand just not to get stuck, and everywhere I read that there are always alternative paths to jumps. The day before we make a hike, 700m of climb over 5km, steep as hell and in the evening my legs were butter (not sure if the same is for you, but the more I don’t feel my body in control, the more fear takes over).

    Next day, we go canyoning and I could legit barely walk. I start the course already thirsty, and after almost 1h we were barely halfway. Having to climb and jump (small stuff) made me sweaty AF, I was completely dehidrated. At some point we reach a place and I clearly realize there is no way back. I am the last one of the group, tired and thirsty as fuck, we are all tied on a rope, and we are on top of a big boulder. There are 2 ways down: jump 10m or go down with the rope.

    I have spent close to 10min on top talking to the guide, asking completely moronic questions, and I have 8 of them on video because my friend was just before me and filmed.

    I ended up jumping, I figured that with the energy I had left, I would rather do something that takes 2s rather that rope myself down. I probably managed to do that just because I was that dehydrated and almost in a delirious state. I remember looking down the water and just the memory makes me dizzy. But the feeling of not having an option B (or C) is what really gets you, this is why I could relate with your story even though this is a completely different situation.

    Fun fact, I ended up being the only one in my group to jump 10 meters, and now the memory is a mixed bag of emotions, but I will always have brag rights with my friends.

    Edit: I added a picture of the jump as seen from top. It’s a screenshot from the infamous video.

    The view from below maybe is more realistic…