If you’ve met your deductible, you may not owe for the upcoming procedure.
However, you’d need to look at your policy or call the insurance company to see if the procedure counts towards your deductible. Normally the plan specifies that its 50% before the deductible and by an asterisk or buried somewhere in your plan’s terms, it may say that it’ll be 100% covered after tour deductible is met.
Is your deductible and out-of-pocket max the same? If you’ve met both, you may not even owe a copay. If you still haven’t met the out-of-pocket max, you will still owe co-pays.
Your plan documents or the company will be able to give better answers, as companies and plans can be very different in how they cover things.
I just got to work and plugged my surface pro into my external monitor. It didn’t switch inputs immediately, and I thought “Linux would have done that”. But would it?
Nope. My laptop for example doesn’t automatically use an output when plugged in, but that doesn’t bother me because I know other DEs would do that, and it’s my choice of having a minimal window manager that causes that.
And this goes into your next point, because I know that this comes from decisions I made, I’m okay with that. I also know I could probably fix it somehow, even if just by running a script in the background that checks if an output is plugged and tries to use it.
And for me that’s the big difference. As a general rule when things break or don’t work are not the fault of Linux as a general, but of a specific piece of the stack, and more often than not it’s because that piece was backwards engineered without any help from the manufacturers of the hardware it’s meant to be controlling, so I can be very tolerant of these errors since the bad guys here are the third-party who’s refusing to make their things work on Linux. But even things that don’t work as I want to, I can make them do so, and that’s a huge change in viewpoint.
In other words, on Windows I used to be of the thought of things you can do, and things you can’t, with time I noticed that in Linux this thought shifted, to the point that the only question I ever ask myself is: “HOW do I do this?”. This implies that there are no impossible things in Linux, which is obviously false, but I would argue that the correct way to think about this is “things that are impossible on Linux, for now”, and that’s a huge difference, because Linux is always evolving and getting better and better, things you thought are impossible now might be trivial in a few months or years whenever someone with the knowledge to fix it gets bothered with it.
And he will never really watch those videos more than one time. Which means it would have been better not filming and enjoying the performance right there, in better quality.
I don’t mind someone doing whatever on their phone out of sight. But this shit drives me insane. You won’t watch that damn video ever again in your life, stop ruining it for everyone else!
Infuriating. I’m thankful honestly when I’ve been to shows that force you to put your phone in a secured container that you cannot access during the show. Makes it a million times better
That would have pissed me off so much if it was last night because Squeeze is one of my favorite bands and I’ve wanted to see them since I was in elementary school.
There was another guy a few rows down capturing video with his lights on. Thankfully, he only did it a couple of times for about 30 seconds, but I felt bad for all the people he was shining that light on, and another lady who thought no one could see or smell the huge cloud from the vape she was “secretly” bending down and hitting every few minutes. This was in an indoor theater. I’m glad there were no kids around.
We were at a concert recently and i loudly said, “hold your phone in front of your face so you’re only messing with your own view.” The guy in front of me and his buddy did stop holding it up over their heads for a bit.
I think the keyboard shortcuts might have been part of RES.
I don’t think ‘LES’ exists, but since RES is licenced under GPL v3, would it be possible to copy features directly into the Lemmy codebase, or into the mlmym frontend (old.lemmy) codebase?
I read something about this in the Book “Introduction to Game Design, Prototyping, and Development: From Concept to Playable Game With Unity and C#” by Jeremy Gibson a while ago, maybe that can explain this a bit.
Basically, every Player has some Intention or the “Player Intent” which is described by the Personality Types of Richard Bartle. For example, you have:
The Achiever who seeks to get the highest score in the game and wants to dominate it
The Explorer who seeks to find all the hidden places in the game and wants to understand the game
The Socializer wants to play the game with friends and wants to understand other players
The Killer who wants to provoke other players and wants to dominate them
And then you have two others that you will be encountering:
The Cheater who only cares about winning and does not care about the integrity of the Game and they will bend or break the rules to win
The Spoilsport who doesn’t care about winning or about the game but rather will break the game to ruin the other player’s experience
So, the motivation to “cheat” could either be that this player doesn’t really care about the game, is able to get away with cheating and just wants to beat the game. According to Jeremy Gibson, a cheater might not cheat if they can win legitimately but I would argue that cheaters are usually not great players in the first place so the bar would be pretty low for them to “win legitimately”.
As for the spoilsport, this is extremely hard to work against or prevent because the motivation isn’t about the game anymore but other players, to make their experience miserable so that the spoilsport can gain satisfaction from it. Hence also the use of “don’t feed the trolls”.
With that being said, when you ask why someone would cheat, the question would rather be “What is their motivation” and the answer to that is “to win the game, at all costs”. And, most of the time, they will get away with this because they apparently cannot be caught as quickly as they can still continue doing it, if there is any action against them at all.
In general, I think genuinely that Linux requires a more hands on approach. But the best thing is, I solve a problem ONCE. Then I store the script to git and forget about it. The problem is done, it no longer exists.
The behavior isn’t normal - Without the error message itself it’s hard to say. You’re not seeing any tracker errors or anything like that within Deluge right?
Maybe you want to set the log level to “error” or “warning”, if those don’t yield anything new then set it to “info” to log whatever error it is.
Also maybe update your post with your OS and Deluge / LibTorrent version.
For what it’s worth in the past I’ve sometimes seen Deluge error on a brand new private tracker torrent, sometimes the private tracker needs a few seconds or a minute to update the tracker and show seeds/etc. - in those random cases Deluge ends up talking to the private tracker before all that & that results in it displaying some error like torrent not found at tracker, I forget exactly what the error was. It’s a bit odd since I’ve never seen rTorrent/ruTorrent have that issue, seemed like a Deluge thing. Been a while since i’ve dealt with that and can’t remember how I fixed it, think it involved having a delay before Deluge attempted to load/start the torrent.
for headless you get either Deluge or Transmission
The paid Seedbox providers usually default to rTorrent/ruTorrent for headless torrenting on their Linux based systems. Deluge/Transmission are the alternative clients in those cases.
Nowadays qBittorrent with webui enabled behaves pretty well on a headless system otherwise qbittorrent-nox is also an option.
Thanks…I don’t think think I have considered rTorrent before. But this one doesn’t have a remote GUI client the way deluge and transmission allow their UI to connect to a remote daemon, right?
Regarding all the troubleshooting steps, thanks a lot. I’m going to go about enabling logging by default on the service, which is disabled and definitely doesn’t help. I’m also considering to rebuild the whole thing, since it’s running off of an older Ubuntu 20.04 container. I might as well take the chance to do it on 24.04. We’ll see.
kbin.life
Oldest