Well okay if one tenant is renting the whole building it’s different.

For the SUM of your tenants’ rent to pay for your mortgage and most of the upkeep? Probably fair.

For ONE tenant to cover the whole mortgage? Geez, that’s not nice, to put it softly.

For what it’s worth, it works on one of my two PCs. But yeah. Clearly not finished.

If I were you I’d try to change every possible Windows display option I can on every possible monitor and change them back, in each possible combination of monitors plugged in/out.

There’s a possibility there’s an option that seems like it’s set one way but it’s actually not. It happens sometimes with Windows version changes.

I think you’re mostly dealing with the consequences of DisplayPort monitors being considered disconnected entirely when off. I tried a display dummy adapter once, and it wouldn’t go above 1080p, plus it didn’t completely solve the issue.

It’s really not an easy problem to solve. Using only HDMI all the time technically works, but very few computers offer more than 1 HDMI port.

A few ideas:

• Have you tried checking or unchecking the checkbox “Remember window locations based on monitor connections”?
• maybe this is the result of Windows putting all your windows on a screen with weird settings when the main one is off. Is this a laptop whose main screen you’re not using for example? Is there anything else that could be considered a “monitor” on this machine? (Including any sort of software-based thing that would connect virtual monitors)? Maybe there IS something at a weird display resolution or scaling but it’s hard to notice what.
• Disconnect the monitor manually and reconnect it. Is the issue the same? If not, the monitor itself may be doing weird things when the system tells it to go to standby.

Edit: Ugh didn’t notice the below wasn’t an option at first

There’s a relatively easy workaround to SOME of it: disable the screen turning off after X minutes of inactivity, and replace that with a screensaver that’s a black screen.

The screen will always be “on” , even though it won’t be displaying anything, which will prevent your windows from being messed with when your PC times out due to inactivity.

But if your PC goes to sleep or you turn a monitor off, it won’t help you.

They will truly do anything not to admit the problem is cars

What the fuck, HTML. I kinda like it in a perverse way.

That’s good and all but man is that person a big fan of aria properties.

To be clear, they’re not bad, but they’re a little brute-forcey. There’s often a way to achieve the same purpose without them.

For instance, instead of aria-pressed with buttons, you can just use radio buttons and labels. And your can just put heading elements in your sections instead of naming them with aria properties.

What the fuck

I used Voyager for a while and here are the issues i noticed before I switched to another app (which also has issues):

1. Gestures for actions tend to take big motions, bigger than is comfortable to me, and the difference between actions is small. Like, I need to swipe very far (and not too fast), and then within a few millimeters, it goes from upvote to downvote. In the end i was just wishing for buttons considering how much work was to reply or downvote.
2. The combo of auto-marking posts as read when scrolling and hiding read posts doesn’t work too well. I frequently refresh my feed to only see stuff I’ve already seen and the posts stick around until I manually click then, go back and refresh. When I drag down at the top of my feed to refresh, I want to see posts I haven’t seen before. Refreshing 2-3 times and seeing nothing new…i don’t think anyone expects that from a social media app. Nearly all Lemmy apps seem to have trouble with this behaviour.
3. I don’t think it’s a great idea to make “click = comment and thread disappears” the default. I often did it by accident and was very disorienting.
4. I would often accidentally swipe/touch something, not realize what, and end up at my feed, the post I was looking at entirely gone, and no easy way to go back. To this day I’m not sure how I did that, but each time it a bummer to give up the post I was reading.

Those game wikis are basically the only ones I use an adblocker on. They’re basically unusable on mobile.

I’m gonna be honest, if they used a feature that wasn’t ready for prime time, it’s still on them.

That’s not mileage infuriating, that’s fucking abuse.

I’ve read it.

Yes. Very unprofessional that the contacts in private ended up the way they did.

Also unprofessional that Linus thought Steve was ignoring him when he was just texting the wrong number.

But those sound a lot more like incompetence than malice to me. A lot of the story is things that could’ve been solved with better communication.

The “scale of blame” definitively sounds like it’s tilted towards LMG. But I don’t really care about that right now. What I care about is that I really hope they talk for real instead of trying and failing to understand each other by text/email and then involving the audience in their fight by taking it public.

I want them to talk like adults, and I want to stop feeling like I’m being made to watch a children’s quarrel.

Man, these people need to sit down and have a proper talk. It’s embarassing that they’ve been fighting in public for so long. A lot of that sounds like simple communication breakdowns, even.

Every goddamn time there’s a new step in these conflicts, my opinion of everyone involved tumbles.

Because they’re entertaining?

I’m trying to avoid Chromium clones altogether. I really don’t like the engine quasi-monopoly we have and I don’t want to participate in furthering it.

It’s not in Firefox mobile.

Sure, I could probably find the URLs to add it in at a new custom search engine. But if you’re gonna make such a bombastic announcement, I expect you to have the update ready beforehand.

Do they not realize that mobile is most Web traffic nowadays?

Hey, if it consoles you, three quarters of our pure back-end C# developers are as you describe, too.

All the full-stack devs I’ve worked with so far were just back-end developers who write terrible front-end code.