they you could kick him out of the org for "creating a bogus account" - "our company isn't bad, you're the bad actor". The bad company he was try get to fix their thing didn't behave properly, end of story.
This happens over and over again because for so many companies their natural thing is to hid any problem and threaten to sue anyone who discloses. Software problems have broken that typical behavior, to some extent.
I salute the author of this post who dared to do the right thing. I hope the company comes to their senses and doesn't try to punish the diving instructor. Over and over companies have tried this same "attack the problem reporter" strategy when software problems are revealed.
Absolutely. Even though I don’t use arch (btw), the wiki is still a fantastic configuration reference for many packages: systemd, acpi, sensors, networkmanager I’ve used it for fairly recently.
You see it referenced everywhere as a fantastic documentation source. I’d love seeing that if I were a contributor
They may be preferred, but in a lot of cases they’re pretty terrible.
I had a bit of a heated debate with ChatGPT about the best way to restore a broken strange mdadm setup. It was very confidently wrong, and battled its point until I posted terminal output.
Sometimes I feel it’s learnt from the more belligerent side of OSS maintenance!
Why would you bother arguing with an LLM? If you know the answer, just walk away and have a better day. It is not like it will learn from your interaction.
The Gell-Mann effect? If you can't trust LLM to assist with troubleshooting in the domain one is very familiar (mdadm), then why trust it in another that one is less familiar such as zfs or k8s?
I think my position is that I don’t trust it at all carte Blanche, but if I know what I’m doing, then it’s helpful as a doc source. In this case, I wasn’t too familiar with the specific cli tools, flags etc and it was a shortcut.
Because I wasn’t 100% sure of the solution myself, and wanted to talk through how to actually implement the theory of what I wanted to do. I knew that what it was suggesting was 100% wrong, but not of the best path.
Arguing with an LLM is silly because you’re dealing with two adversarial effects at once:
- As the context window grows the LLM will become less intelligent [1]
- Once your conversation takes a bad turn, you have effectively “poisoned” the context window, and are asking an algorithm to predict the likely continuation of text that is itself incorrect [2]. (It emulating the “belligerent side of OSS maintenance” is probably quite true!)
If you detect or suspect misunderstanding from an LLM, it is almost always best to remove the inaccuracies and try again. (You could, for example, ask your question again in a new chat, but include your terminal output + clarifications to get ahead of the misunderstanding, similar to how you might ask a fresh Stack Overflow question).
(It’s also a lot less fun to argue with an LLM, because there’s no audience like there is in the comments section with which to validate your rhetorical superiority!)
I knew roughly the right path, and wanted guidance on that (cli guidance specifically). It was refusing to do so saying it wouldn’t work! It did work…:
This looks like some kids DT project presentation - focusing too much on things that the target audience aren’t really going to care about.
Also, how soulless is this car. Some cars I get into (previous gen Audis, used to with BMWs, Porsche) and feel that they’ve built the interior for the drivers enjoyment. This, no clue.
I suspect this is about work related MFA apps; for example, one of the reasons I switched to an iPhone many years ago is the MFA app used at work would not run if the latest Android version with security bugfixes were installed, and the manufacturer had stopped providing updates for quite some time. At that point I was looking at a costly upgrade to one of the Android flagships, or an iPhone, of which I chose the latter.
>At that point I was looking at a costly upgrade to one of the Android flagships, or an iPhone, of which I chose the latter.
That's your personal decision though, you don't need a flagship android phone to have the latest versions of android. I pretty much never spend more than $100-150 for android phones and they always support all the normal MFA apps.
Fair, I could just buy a new Android phone, but at the time every non-flagship appeared to stop updates every two years, and being on an upgrade treadmill on that time scale did not seem like a fair use of my money. I have no idea if this continues to be the situation or if Android manufacturers have gotten better with their update cycles.
That's fair assessment (and it pissed me off myself), but thankfully it's much better now with Android.
I mean, I still wouldn't trust Sony even if it give a blood oath (they used to abandon flagships after 16-18 month form release!), but there are also more reputable vendors.
It also should be on your employer to provide a compatible device (especially when it's your personal device that's not secure enough for the business)
They all work fine, you just have to be on a relatively current version of android, and that's dictated by which versions the apps enable support for and not anything inherent to android in general. The idea that MFA apps don't work for half of phone owners is silly.
Yeah I was really frustrated the other day to find that my steam controller doesn’t work with my LG TV as a standard XInput device, either on BT or receiver. Assumed it would.
reply