• 6 Posts
  • 224 Comments
Joined 3 years ago
cake
Cake day: January 23rd, 2022

help-circle
  • Pedophilia has a longstanding history in the music industry. Priscilla was 14 when she met Elvis, Lori Mattix admitted to sleeping with rockstars as early as 14, Sable Starr admitted to doing so when she was 12, both were part of an infamous group dubbed the “baby groupies,” it was so prevalent that it disgusted Danny Elfman into writing “Little Girls” about the record execs he had witnessed participating in pedophilia. There’s at least a dozen examples I could pull from recent times just off the top of my head, but they’re all more niche and less likely to catch people’s eyes.


  • Phones abaolutely do listen, but not to audio via the mic. When Apple and Google tell you they respect your privacy, they mean they don’t harvest data directly from a live feed of the mic nor camera; they still scan your files in some cases, and they harvest your browsing history, and read your text messages metadata, and check your youtube watch history, and scan your contacts, and check your location, and harvest hundreds of other litttle tiny data points that don’t seem like much but add up to a big profile of you and your behavior and psyche.

    So your friend was at a pub quiz with a couple dozen other people, and his phone knew where he was and who was nearby. A statistically significant portion of the people there were not privacy conscious and googled “Lord of the Rings runtime” or something similar. All that data got harvested by Google and Apple, and processed, and then the most recent and fitting entry from some master list of customers’ sites’ articles was pushed to all their newsfeeds.

    Humans don’t understand intuitively how much information is being processed through nonverbal means at any given time, and that’s the disconnect large companies exploit when they say misleading things like “noooo, your phone isn’t listening to you.”

    But it’s totally not privacy invasive, because at no point along the line did a human view your data (/s)






  • AI isn’t stupid because it doesn’t possess any intelligence to begin with, the term “AI” is just a marketing misnomer.

    Language Models are essentially really advanced Markov Chain generators. Once you understand that, you’ll realize why your question is like “I keep asking these water mills to make me a cup of coffee, but they all taste like dirt”: wrong tool for the job, it just happens to be tangentially related.

    You’re also asking if there’s a way to precisely word a request so that the computer will do what you want it to do. Luckily for you, there is! It’s a trick that’s been around for ~60 years and it’s called “programming languages”




  • none, and gods willing that will always be the case. Civil war isn’t just “good guys vs bad guys”—hell, it wasn’t even that the first time around, despite union propaganda trying to make it seem like their intentions were pure. War is also starvation and loss of access to clean drinking water and constant blackouts as supply chains get interrupted; it’s many people dependent on uninterrupted health care dying off because they can’t get their meds or do their testing; it’s r*pists and pedophiles and nazis and sociopaths having their way with others while society gets distracted; it’s your loved ones dying, not because they were fighting for what’s right, but because they were “acceptable losses”; it’s constant anguish that destroys lives for multiple generations as trauma gets handed down like an heirloom.

    Living through a war is about the most extreme form of hate I could imagine wishing upon someone. If someone who lived through one is willing to say “it’s time,” then I’m willing to listen. Otherwise, please excuse me if I don’t.



  • vim isn’t required for any files, you just followed online tutorials for how to edit those files instead of RTFM

    terminal text editing is convoluted because it has to strike a balance between figuring out when a keypress is part of the text you’re typing, vs when it’s a command you’re using, and making sure that all the editor commands the designer wanted are accessible.

    vim is great because it allows for thousands more editing commands and macros, and much more customization of the editor, up to allowing plugins that emulate other functionality. As it stands, my setup basically functions as a full, lightweight-ish, multi-language IDE that rivals Emacs or Visual Studio.

    On top of all that, I don’t have to move my hands away from the homerow of keys to navigate or edit, which may not seem like much, but adds up to a lot of avoid typos and time saved from moving my hands to reach the arrows/delete/home/end/pgup/pgdn.

    Some examples:

    h, j,k,l move left, down, up, and right respectively, but they can be combined with a number to move that many rows or columns; e.g. 6j will move down 6 rows

    dd deletes a line, but using a number + d + a movement will delete that many characters/lines in the path of the cursor: e.g. 34dl will delete 34 characters to the right of the cursor, 12dk will delete 12 lines up.

    gg will take you to the first line, G will take you to the last, and number + either will take you to that line: e.g. 3275gg or 3275G will take you to line 3275

    and finally you can use /text or regex pattern you want to search for and Enter to search the document for the first occurence below your current location, and then use n to search for the next occurence, or N to search for the previous

    That doesn’t even scratch the surface (that’s just the cheatsheet, which only scratches the surface), but if you can get a handle on only what I’ve said, and switching between input and command mode (i and Esc respectively), the speedup to navigation alone will make it seem more sensible.

    And as always, don’t forget to :wq (write to file and quit)






  • BaumGeist@lemmy.mltolinuxmemes@lemmy.worldnow I know why
    link
    fedilink
    arrow-up
    13
    arrow-down
    14
    ·
    1 month ago

    It’s always wild to me how these hateposts climb to the top, when all the complaints can be boiled down to “I don’t like the design choices”

    Have you tried… Just not using it? No one’s forcing you to use it. Have you tried using a different DE instead?




  • I will be using your example of Arch as a great stepping off point, because honestly imo the best way to learn is by having a project to work on

    1. RTFM - Read The Fucking Manual. Read the docs, read the code comments if need be. In the case of installing an OS, use the installation guide as a starting point; Arch’s is on their wiki, and links to several other sections that go more in-depth about what each step does and why it does it.

    2. DuckDuck it - if you don’t understand what something is or why you’re doing it, search it. If you understand it completely, search it anyway and check the docs because no you don’t, you just don’t know how little you know. If you know why we do something and what function it fulfills, but not how… Then you’re a power user.

    Using your example of commands from the internet, break the command down into as many parts as you can, and figure out what each part does. If there’s punctuation marks, don’t assume you know what those are doing. man [command's name] is your friend.

    1. Do all of the above as often as possible, no matter how slow it makes progress feel. Learning these things the proper way now will save you from days, weeks and months of troubleshooting in the future. I mean it, literally at every step of the process.

    2. secondary sources are invaluable, but for this it might help to get into the best way to self-educate. The only gospel are the docs and/or manual that were written by the code/OS maintainers - primary sources - everything else is opinion.

    Here’s a source i agree with on the best way to self-educate, but keep in mind even Artem is still just a secondary source.

    That being said, here’s a few secondary sources that helped me understand how OSes work and why:

    nand2tetris: build an operating system starting with logic gates and working your way up from there. It has a offshoot site that’s slowly being rolled out, that implements it all in a gamified interface: nandgame

    os-tutorial: build an OS from scratch

    Linux From Scratch: Learn everything about Linux by building your own distro from the kernel up.

    Unfortunately everything that taught about the behind-the-scenes aspects of OSes in general—and Linux in specific—were either projects like the above, or just seeing what came up in a DuckDuckGo, Youtube, forum, or wiki etc. search. Below are just resources that teach you about the “power user” level of knowledge, not “super user” but not your average user either.

    Fireships’ 100+ Linux Things you Need to Know: it’s not particularly good on its own, but it does introduce a lot of concepts and vocab for you to then look up elsewhere

    freeCodeCamp.org offers a lot of courses that will go over using Linux. None go too in-depth on the fundamentals of Operating Systems, but they will still introduce most of what you need to know for day-to-day use. I don’t want to link them all, but just search for linux freecodecamp on youtube and find one that piques your interest. The longer, the more in-depth—you don’t have to watch it all in one sitting.

    1. And of course, when all else fails: just ask. Participate in the community, don’t be afraid of looking stupid. The only people that get no respect are the ones who refuse to accept others’ help because they know better than those they’re asking to help them. (ignore the gatekeepers who want to project their own need for an identity onto you)