• 0 Posts
  • 31 Comments
Joined 2 years ago
cake
Cake day: July 2nd, 2023

help-circle




  • Not the guy your responding to and I 100% get your frustration, but I want to provide a little anecdote.

    Back in November, I built a new desktop to replace my 7 year old one and put OpenSUSE on it. No matter what I tried, I could not get either Bluetooth or WiFi working. I tried updating drivers, restarting controllers, reinstalling the OS, replacing the OS with Mint. Nothing worked.

    I did a lot of searching over the next few days, and it turned out that my motherboard was so new that it’s built in WiFi chip did not have Linux drivers yet. Like at all.

    Most products aren’t created with Linux in mind, so compatibility isn’t a concern. It’s up to the community to create patches & drivers to make things work, and it can take a bit to get things working.

    I’m genuinely sorry you had the experience you did, but I hope that if you do return to Windows that you’ll give Linux another try in the future. Search your products to see if others have had issues, along with potential solutions, before you dive in.


  • My sibling ran into this issue once. I’m not sure if it’s a setting or a default, but vscode would assume they were working in a blank repo until they made a commit.

    Sounds like this person had the project (without source control) in another IDE, tried out VSCode, and it assumed that it was all ‘changes’. I don’t use VSCode, do I can’t say for certain, but I know my sibling lost ~4 hours of project set up for the same reason (though they immediately realized it was their fault).


  • That’s basically how I did it.

    To properly learn it using this method, create a directory that contains only text files and sub directories and treat it like a real project. Add files, delete them, play around with updating the repository. Try and go back a few updates and see how the things react. Since it’s not a real project there’s no risk of loss, but you’ll still get to see the effects of what you do.


  • A really good way to do linux is to play around and break things, but to have a backup you can restore from.

    I don’t know about other distros specifically, but Mint comes shipped with Timeshift, which is easily configurable and can be set up to include your home directory. Make a backup on an external drive every now and again so that if you break everything, you only lose a bit of work instead of all of it.

    Search engines are your friend. If you want to do something, look it up first (ex/ “How do I [x] on linux”) and read some of the answers. Don’t just go with the first option you see, and if it looks decent but you don’t understand it try looking up the commands it uses to find some documentation.

    Learning linux isn’t something you can do as passively as you can with Windows, so take time to really try and learn things you’re looking to do.

    And a good rule of thumb is that if you think your system should be able to do something, it probably can.









  • This was with regards to Air Canada and its LLM that hallucinated a refund policy, which the company argued they did not have to honour because it wasn’t their actual policy and the bot had invented it out of nothing.

    An important side note is that one of the cited reasons that the Court ruled in favour of the customer is because the company did not disclose that the LLM wasn’t the final say in its policy, and that a customer should confirm with a representative before acting upon the information. This meaning that the the legal argument wasn’t “the LLM is responsible” but rather “the customer should be informed that the information may not be accurate”.

    I point this out because I’m not so sure CVS would have a clear cut case based on the Air Canada ruling, because I’d be surprised if Google didn’t have some legalese somewhere stating that they aren’t liable for what the LLM says.