• 0 Posts
  • 43 Comments
Joined 1 year ago
cake
Cake day: June 25th, 2023

help-circle

  • Would definitely not recommend KDE Neon. It’s more of a showcase of new KDE features than an actual usable OS. I currently use Kubuntu and it’s fine. I wish it updated more frequently but the update frequency isn’t slow enough to really be a deal breaker.

    I disabled snap Firefox, not really because I’m ideologically against snap, but because snap Firefox is annoying to use. Other than that, the OS generally just works out of the box.

    I’ve heard good things about OpenSUSE, but I’ve never tried it. My personal opinion is that I want to stick to the most common distros so that it’s easier to find troubleshooting advice






  • Linux is really a superfamily of loosely-related OS’s (called distributions). Arch and Debian are 2 of the more common ones. Arch in particular has a reputation of being really beginner un-friendly, particularly in that, to my understanding, you have to build the OS yourself.

    There’s also the caveat that many Linux distributions end up sharing/copying code from each other, so you end up with a kind of “OS lineage.” The most common distribution, Ubuntu, is copied from Debian. And then the most beginner-friendly distribution, Linux Mint, is copied from Ubuntu. Arch, to my knowledge, doesn’t copy code from elsewhere, so much of the advice given from users of other distributions won’t apply to Arch (hence the meme, “I use Arch btw”)

    Anyways, the real advice for a Linux beginner is to stick with a beginner-friendly distribution: either Ubuntu or Linux Mint or Pop!_OS. Most or all distributions have various “flavors,” which are basically like how the OS looks. I think the real difficulty is picking a flavor that you like. I personally like the look of KDE Plasma (IMO resembles Windows 10 the most), so my personal recommendation is Kubuntu, which is the KDE Plasma flavor of Ubuntu













  • Asking ChatGPT for advice about anything is generally a bad idea, even though it might feel like a good idea at the time. ChatGPT responds with what it thinks you want to hear, just phrased in a way that sounds like actual advice. And especially since ChatGPT only knows as much information as you are willing to tell it, its input data is often biased. It’s like an r/relationshipadvice or r/AITA thread, but on steroids.

    You think it’s good advice because it’s what you wanted to do to begin with, and it’s phrased in a way that makes your decision seem like the wise choice. Really, though, sometimes you just need to hear the ugly truth that you’re making a bad choice, and that’s not something that ChatGPT is able to do.

    Anyways, I’m not saying that bosses are good at giving advice, but I think ChatGPT is definitely not better at giving advice than bosses are.


  • To be clear, the issue that many people have with Threads is not that Meta can’t be trusted with our data. It’s true, but that’s not the main issue. The main issue is that there is no reason for Threads to try to federate with us unless they are trying to kill the Fediverse.

    Meta is a big company, they can attract users on their own and support their own ecosystem. Isn’t it strange that they would try to federate with us? We are much smaller in comparison, and we won’t help their user activity just simply because we are much fewer in number compared to the users on Threads. The only reasonable explanation is that Threads is trying to federate with us because they are pre-emptively trying to kill the Fediverse before it becomes a serious competitor.

    This is a very standard practice for tech companies, so much so that it has its own name: EEE (Embrace, Extend, Extinguish). If a tech company notices an up-and-coming potential competitor, they will adopt the same technology as the competitor by passing it off as a partnership (embrace).

    Then, they’ll slowly start introducing changes to the technology, and they’ll introduce those changes in such a way that it’s intentionally difficult for the competitor to implement something similar (extend). This could be anything like making an extension to the ActivityPub protocol that only works with a Threads account (proprietary extensions) or publishing the change but intentionally obfuscating the documentation for that change, so that the competitor’s implementation is buggy (sabotage). This all occurs behind the scenes, so the users will start to wonder why the competitor seems so buggy and slow. They start to switch to Threads because it’s more stable and fast, not realizing that the whole reason why Threads appears more stable is due to sabotage.

    Then, once the competitor has developed a bad enough reputation and once enough users have jumped ship, Threads will defederate. The sudden loss of users and the bad reputation that the competitor picked up during the “partnership” will destroy the competitor so much that they will never fully recover (extinguish).

    If a big tech company comes to you with a partnership deal and it’s not apparent what exactly they’re getting from the deal, you can generally be sure that they’re only offering because they want to destroy your brand. I don’t trust Threads.