Lettuce eat lettuce

Always eat your greens!

  • 7 Posts
  • 446 Comments
Joined 1 year ago
cake
Cake day: July 12th, 2023

help-circle



  • You misunderstand me. When I say, “copyright is bullshit” I don’t mean that I don’t like it, or that it doesn’t work. I mean it’s bullshit in the same way that the crystal healing or mushroom cancer therapy is bullshit.

    You cannot steal an idea, it’s impossible. So creating laws that punish people for doing things like copying a digital file doesn’t make sense. Copyright supposedly was created to create an incentive for artists and inventors to make cool and enriching stuff.

    But what it actually does is protects business savvy people and allows them to game the system, get first mover advantage over all others, and then punish any potential competitors in that space.

    As if nobody was creating artwork or inventing useful devices before copyright law came into being.

    Just because something is useful doesn’t make it good, atomic bombs are useful, factory farming is useful.

    I think the only thing people should be protected from as a creator is fraud. You can copy a person’s works and modify or distribute them in any manner you see fit, as long as it’s clear that you are not the original creator. You cannot claim to be them or to be affiliated with them unless you actually are.

    That is what the principle of copyleft is all about. If copyright worked in principle, then you should see millions of individual creators enriched and protected by it.

    But you don’t see that, instead, a few giant mega corps and super wealthy tycoons own and control enormous swaths of “intellectual property” and small time creators struggle to make ends meet and are sued into oblivion by the same powerful groups.

    Sure it’s great for boosting wealth and GDP, but that boost does not apply to most of the population, it applies to the tiny elite that has now captures enormous segments of the market and fight tooth and nail to keep it that way.

    Copyright is structurally flawed, it doesn’t work because it cannot work. It’s fundamentally based on a the nonsensical concept of “intellectual property” which as I said at the beginning, is bullshit.








  • Lettuce eat lettuce@lemmy.mltolinuxmemes@lemmy.worldMany such cases
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    edit-2
    15 days ago

    You’re just wrong on literally every point dude.

    1. Nope, I’ve installed Linux Mint for multiple people, several different apps, never touched the terminal. I even updated the kernel all through the GUI.
    2. Basically the same on all the most popular distros. Searching “startup” or “autostart” in KDE Plasma, Cinnamon, and Gnome DEs all bring up an easy GUI app for getting programs to start automatically.
    3. Same as #1. You don’t need to use the terminal to install most software, especially not anything popular. And guess what, you need the terminal to do hardcore stuff on Windows too. I know because I’ve worked for years in IT and have to use the Windows terminal for all kinds of random stuff, I literally had to use Powershell today.
    4. This happens in Windows too. Just ask me how many times I’ve had to install old .NET frameworks or other random drivers/3rd party software to get some piece of software/hardware to work on Windows. Something that I thought would be a 10 minute install turns into an hour because of random shit not working right.
    5. Bruh, I play Minecraft all the time. Hundreds and hundreds of hours. It’s one of the easiest games to play on Linux. And I play with tons of mods, texture packs, and shaders. I’ve been playing Minecraft on multiple Linux distros for 4 years, it runs great.
    6. All major distros auto-mount external drives. I have a whole bag of thumb drives, external HDDs, and SSDs that I use in my day job. Never had a problem with them not being picked up and mounted by any of the Linux systems I work on.

    I mean, don’t use it I guess, but stop spreading these obviously false claims, man. Have fun getting all your personal data farmed by a multi trillion dollar megacorp and fed into AI engines to churn out infinite heaps of sludge. Oh yeah, and all the endless popup ads in an OS that you already paid for…



  • We’re lucky that the SBC space has gotten really solid over the last couple years. ARM-based, X86-based, and even some RISC-V systems.

    The PI isn’t the only only game in town now, and actually gets beat in several different applications depending on use case.

    As shareholder value and line-must-go-up takes over the company culture, progress and innovation will happen more and more in the hands of companies and orgs that actually care about their product’s quality and features.

    Still disappointing though, the Pi was my first introduction to IoT and low power computing.







  • Look up “CompTia Network+ course”

    Watch everything in the “Power Cert” series, then watch everything in the “Professor Messer” series.

    You won’t get through everything in a month unless you are a really fast learner, but you can get through a large amount of content.

    Complete both courses, and you will have a solid base level of understanding for computer networking.

    The key things to know IMO:

    1. The whole OSI model top to bottom for troubleshooting. If I ask you, “What’s the difference between a layer 2 and a layer 3 switch?” You should be able to instantly answer.
    2. Understand IP addressing well. Know what they are, why they work they way they do, and how they apply in a basic network. You should know what CIDR is.
    3. Understand subnetting well. It will confuse you at first, keep watching videos on it until you actually understand it.
    4. Know what DHCP and DNS are and how they are used in a network. This will be CRITICAL to effectively troubleshoot a network problem. A huge number of networking issues boil down to problems with DHCP, or problems with DNS.
    5. Understand VLANs and how they are used and why they are important.
    6. Understand network ports, memorize the most common dozen or so. Know what and how they work and why they matter for security.
    7. Understand the basics of packet anatomy, what they are, how they are formed, packaged, sent, routed, received, unwrapped, and responded to.
    8. Understand VPNs at a basic level and how they work. Know the difference between an IPsec implementation, an OpenVPN implementation, and an overlay network like TailScale. Understand why somebody would chose one over the others.
    9. Practice basic commands and tools like ping, tracert/traceroute, and nmap. These are incredibly useful and necessary to troubleshoot connectivity issues. I use them on a weekly basis at my job.

    That all should get you going. It’s intimidating, but very rich and rewarding when you start to get it.

    And of course, practice practice practice!!! You will NOT learn by just sitting in front of your screen and watching the videos. Get into the command line and start messing around. Grab an old tower or laptop, throw a Linux distro on there and play with SSH, ping, nmap, Uncomplicated Firewall (UFW), start opening and closing ports. Tell certain services like SSH to listen on different ports than the default port 22. Etc.