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

help-circle
  • S410@kbin.socialtoPrivacy@lemmy.mlAndroid Microphone Snooping
    link
    fedilink
    arrow-up
    2
    arrow-down
    4
    ·
    8 months ago

    Android is sending a ton of data, though, even if you’re not doing anything internet related. It, also, kinda reacts to “okay, google”, which wouldn’t really be possible if it wasn’t listening.

    Now, it obviously doesn’t keep a continuous, lossless audio stream from the phone to some google server. But, it could be sending text parsed from audio locally, or just snippets of audio when the thing detects speech. Relatively normal stuff to collect for analytics purposes, actually.

    Now, data like that could “easily” get “misplaced”, of course, and end up in the ad-shoveling machine… Not necessary at Google’s hands: could be any app, really. Facebook, TickTok, random free to play Candy Crush clone, etc. But if that data gets into the interwoven clusterfuck of advertisement might, it will likely end up having an effect on the ads shown to the user.



  • Dualbooting is possible and easy: just gotta shrink the Windows partition and install Linux next to it. Make sure to not format the whole thing by mistake, though. A lot of Linux installers want to format the disk by default, so you have to pick manual mode and make sure to shrink (not delete and re-create!) the windows partition.

    As for its usefulness, however… Switching the OS is incredibly annoying. Every time you want to do that you have to shut down the system completely and boot it back up. That means you have to stop everything you’re doing, save all the progress, and then try to get back to speed 2 minutes later. After a while the constant rebooting gets really old.

    Furthermore, Linux a completely different system that shares only some surface level things with Windows. Switching to it basically means re-learning how to use a computer almost from scratch, which is, also, incredibly frustrating.

    The two things combined very quickly turn into a temptation to just keep using the more familiar system. (Been there, done that.)

    I think I’ll have to agree with people who propose Virtual Machines as a solution.

    Running Linux in a VM on Windows would let you play around with it, tinker a little and see what software is and isn’t available on it. From there you’ll be able to decide if you’re even willing to dedicate more time and effort to learning it.

    If you decide to continue, you can dual boot Windows and Linux. But not to be able to switch between the two, but to be able to back out of the experiment.

    Instead, the roles of the OSes could be reversed: a second copy of Windows could be install in a VM, which, in turn, would run on Linux.

    That way, you’d still have a way to run some more picky Windows software (that is, software that refuses to work in Wine) without actually booting into Windows.

    This approach would maximize exposure to Linux, while still allowing to back out of the experiment at any moment.


  • S410@kbin.socialtoLinux@lemmy.mlI dislike wayland
    link
    fedilink
    arrow-up
    21
    arrow-down
    1
    ·
    9 months ago

    Wayland has it’s fair share of problems that haven’t been solved yet, but most of those points are nonsense.

    If that person lived a little over a hundred years ago and wrote a rant about cars vs horses instead, it’d go something like this:

    Think twice before abandoning Horses. Cars break everything!
    Cars break if you stuff hay in the fuel tank!
    Cars are incompatible with horse shoes!
    You can’t shove your dick in a car’s mouth!

    The rant you’re linking makes about as much sense.


  • Simply disabling registration of new accounts using Tor/VPN should be sufficient and won’t affect existing users.

    Although, requiring verification of accounts made via those would be a better approach. Require captchas to prevent automated posting. Automatically mark posts made from new accounts and/or via Tor or a VPN for moderation review.

    There are way to mitigate spam that aren’t as blunt and overreaching as blanket banning entire IP ranges. This approach is the dumbest, least competent way of ensuring any kind of security, and, honestly, awfully close to being needlessly discriminating. Fuck everyone from countries with draconian internet censorship, I guess?







  • OpenSUSE + KDE is a really solid choice, I’d say.

    The most important Linux advice I have is this: Linux isn’t Windows. Don’t expect things to works the same.
    Don’t try too hard to re-configure things that don’t match the way things are on Windows. If there isn’t an easy way to get a certain behavior, there’s probably a reason for it.






  • Not OP, but I have the same setup.

    I have BTRFS on /, which lives on an SSD and ext4 on an HDD, which is /home. BTRFS can do snapshots, which is very useful in case an update (or my own stupidity) bricks the systems. Meanwhile, /home is filled with junk like cache files, games, etc. which doesn’t really make sense to snapshot, but that’s, actually, secondary. Spinning rust is slow and BTRFS makes it even worse (at least on my hardware) which, in itself, is enough to avoid using it.





  • On my devices like PCs, laptops or phones, syncthing syncs all my .rc files, configs, keys, etc.

    For things like servers, routers, etc. I rely on OpenSSH’s ability to send over environmental variables to send my aliases and functions.
    On the remote I have
    [ -n "$SSH_CONNECTION" ] && eval "$(echo "$LC_RC" | { { base64 -d || openssl base64 -d; } | gzip -d; } 2>/dev/null)"
    in whatever is loaded when I connect (.bashrc, usually)
    On the local machine
    alias ssh="$([ -z "$SSH_CONNECTION" ] && echo 'LC_RC=$(gzip < ~/.rc | base64 -w 0)') ssh'

    That’s not the best way to do that by any means (it doesn’t work with dropbear, for example), but for cases like that I have other non-generic, one-off solutions.