Yes, Google has miss reported my websites in the past, all of which were valid, but the person I’m replying to seemed to assume no-SSL is a requirement of the feature, and he doesn’t understand that a wrong/missing SSL is indistinguishable from a Phishing attack, and that the SSL error page is the one that warns you about phishing (with reason).

It is for pull requests. A user makes a change to the documentation, they want to be able to see the changes on a web page.

So? What that has to do with SSL certificates? Do you think GitHub loses SSL when viewing PRs?

If you don’t have them on the open web, developers and pull request authors can’t see the previews.

You can have them in the open, but without SSL you can’t be sure what you’re accessing, i.e. it’s trivial to make a malicious site to take it’s place an MitM whoever tries to access the real one.

The issue they had was being marked as phishing, not the SSL certificate warning page.

Yes, a website without SSL is very likely a phishing attack, it means someone might be impersonating the real website and so it shouldn’t be trusted. Even if by a fluke of chance you hit the right site, all of your communication with it is unencrypted, so anyone in the path can see it clearly.

I have, in fact I have migrated my home config to nix. The syntax is still a bit weird and still unfamiliar in some cases, especially around the inputs, overlays, etc. Next time I install a system it will definitely be NixOS, currently it’s only running on a backup laptop that I use for testing.

I used it for a couple of years, it’s great if you love customizability and want to run a very clean system. However, the last straw for me was when I needed to edit an image, realized I didn’t had Gimp, so I installed it (which took a long time since I needed to compile it), opened it and it wouldn’t open the image because it was a PNG (I think, or jpg, the specific format doesn’t matter) and that format requires a compilation flag to be enabled, I added that flag globally because why the hell would I not want to have support for it, and recompiled my entire system. By the time I had GIMP able to edit the image I didn’t even remember what I was going to do. I went back to arch not long after that, but always missed defining the packages I want in files to keep the system organized and lean.

I worked for almost 2 years at a company with my Linux PC, until one day I requested a laptop for travel and they were shocked that I didn’t had one, I asked for one with Linux but was told that that’s not possible, that they only had windows laptops. I thought, okays this is temporary, as soon as I’m back from traveling I’ll return the laptop and things will be back to normal… when I came back and wanted to return the laptop they said that that was my work computer that I should use for everything, I was like, “you do realize our work runs on a Linux server, right?”. But nope, I had to use the Windows laptop until I quit a few months later. I knew of at least a couple other devs who were running Linux, but didn’t say anything because then they would be forced to switch too, but at my exit interview I remarked that forcing me to use Windows was part of the reason I had left.

I guess my point is maybe don’t make a big fuss and don’t try to convince HR people about it, they just don’t understand.

This is usually the case, people make it a monster in their heads but it’s not bad as long as you’re willing to accept it’s a different OS to be used differently.

Let me guess, you might have tried Linux on n the past but only really started using Linux full time around 2021/2022, because every time I see someone saying “Linux only became user friendly around year X” is always around a 1 year mark after they started using it daily, because it’s a lot more a matter of being used to than actual usability. I have been using KDE since 2004, and while things have changed it wasn’t all that much, I don’t remember any big usability refactor or anything of the sort happening, I’m fairly confident that if I were to put you to use a KDE 3.5 UI you would feel right at home.

While YUNO is a great way to get started, I strongly encourage you to understand basic concepts, like docker, and maybe try to run something outside of it for fun. While not even remotely the same thing since YUNO is just the OS and “app store”, you would be very similarly tied to that ecosystem the same way you are to Google now. Not to mean that YUNO would have any control over your stuff, but you would be dependent on them for what you can self host.

Controllers I’ve had (all of which should work on Linux easily, some with minor adjustments needed) in the order I think you should consider them:

• 8BitDo Ultimate 2 Wireless
• PS5 Controller
• Xbox One controller
• PS4 controller
• PS3 controller
• Xbox 360 controller (only connects through dongle)
• Steam Controller (doesn’t have d-pad)

Most controllers should work wired, but I haven’t tested any of them like that because I like my controllers wireless.

In a world where I am limited by hours in a day and how many engineers I have on staff? A bug that nobody knows about is not a bug.

But people know about it, so much that they are reporting it, you don’t know about it, but everyone else does.

That is obviously playing with fire

Exactly, without the report you wouldn’t know what type of bug it is that affects people.

“linux users are smarter and make better bug reports and also have bigger dicks”

No one claimed any such thing, have you actually read the article? He claims Linux users are just more used to making bug reports, so they keep doing that on games the same way they would on any other piece of software. It’s about the mentality than intelligence, most people experience a bug, curse/laugh and carry on. Let me ask you, have you ever reported a bug in a game you played? I’m sure you’ve experienced many, but have you ever actually reported one?

But I think it DOES ignore the reality that adding actual support for a new platform does drastically increase the testing and build/deployment overheads which are usually the realest of costs anyway.

That is true, which is why the majority of games released for Linux are indie, since only indie developers have the necessary funds to carry such big overhead… But being serious, yes, there’s some overhead in setting a Linux build, but it’s usually one of the easiest to make, most games are already doing Windows/Xbox/Playstation/Switch adding an extra pipeline there should be much simpler than you’d expect.

Fix things as they come up" really is the best of both worlds.

How would you know things came up without bug reports?

Its not burying your head in the sand.

It is, just because people haven’t reported it doesn’t mean they haven’t experienced it. Maybe 90% of the people experienced that bug, but only the ones on Linux reported it. It had to be a very big number so that statistically less than 6% of the population experienced it enough to report it. Think about it, what are the chances someone specifically would get a generalized bug? If it’s 1% the chance that that 1% happens to be within the 6% of Linux users is very slim, for that to happen 400 times it’s inconceivable, those bugs were widespread, just not reported.

If it is isolated or people just don’t care? Then… it kind of doesn’t actually matter.

Again, you’re making an assumption, the bugs were probably not isolated, and we don’t know what they were so maybe they were big deals, just unreported big deals.

You scan the forums and optimally have community managers/PR people to do the same to keep an eye out for “This was weird?” style comments but you mostly focus on the stuff that naturally rises to the top or that you identify as an issue.

So you’re saying getting a bug with reproducible steps is worse than having to hire people to search the internet for posts and then pay engineers money to try to reproduce, so that you can finally have the same thing you would have gotten for free? Dude, sometimes people say “the game crashed, piece of shit” and that’s all the info you get in a forum, whereas a bug report is more akin to “When talking to NPC X the game crashed, here’s the stack trace, here’s my save file right before, I’ve confirmed that going and talking to X immediately triggers the issue”, but you do you, hire a community manager full time to read posts in case someone says the “the game crashed”, then pay a QA to sit on their hands until such report comes and then spend months to try to reproduce the issue, to finally get the same bug report that some random person would have given you for free.

The more bug reports you have? That is engineer time spent assessing what is and isn’t a priority.

No, engineers fix the bugs, project managers asses whether a bug is or isn’t a priority, or you thought their job was just to guide you through scrum practices?

And the sad reality is that it is a LOT easier to say “we have our five thousandth number one priority” rather than to say something doesn’t matter.

All you have to say is “your bug has been reported, we will look into it”.