I waddled onto the beach and stole found a computer to use.

🍁⚕️ 💽

Note: I’m moderating a handful of communities in more of a caretaker role. If you want to take one on, send me a message and I’ll share more info :)

  • 92 Posts
  • 650 Comments
Joined 3 years ago
Cake day: June 5th, 2023
  • Otter@lemmy.catoTechnology@lemmy.world•A generation taught not to think: AI in the classroomEnglish
    46·
    6 days ago

    I always saw the rules against Wikipedia to be around citations (and accuracy in the early years), rather than it harming learning. It’s not that different from other tertiary sources like textbooks or encyclopedias. It’s good for learning a topic and the interacting pieces, but you need to then search for primary/secondary sources relevant to the topic you are writing about.

    Generative AI however

    • is a text prediction engine that often generates made up info, and then students learn things wrong
    • does the writing for the students, so they don’t actually have to read or understand anything
  • Otter@lemmy.catoLinux@lemmy.ml•Installed homebrew on wii
    6·
    7 days ago

    Neat! I’m somewhat familiar with homebrew but I haven’t kept up with it in years. I didn’t know you could put Linux on it too

    I wonder how it would do as a media center for the living room. I’d much rather use a Wii remote to navigate on a TV instead of buttons.

    Being able to play Jellyfin off of it somehow would be amazing, I imagine it will need a custom app. Possibly based off of this thing? https://www.wiimc.org/about/

  • Otter@lemmy.catoTechnology@lemmy.world•GitHub Takes Down Rockchip MPP Repository After FFmpeg Copyright ClaimEnglish
    100·
    22 days ago

    Relevant bit

    The DMCA filing states that several files in the Rockchip MPP repository are derived from FFmpeg’s libavcodec sources. It lists AV1, H.265, and VP9 decoder files, and claims the copied code is clear because of matching structure, comments, and commented-out calls to FFmpeg functions with their original names.

    Much of FFmpeg, including libavcodec, uses the GNU Lesser General Public License version 2.1. This license allows reuse, but only if certain rules are followed. These rules include keeping copyright notices, giving proper credit, and ensuring any shared code remains under an LGPL-compatible license.

    The DMCA notice says Rockchip broke these rules by removing the original copyright and author details, claiming the copied code as their own, and sharing it under the Apache license, which does not meet LGPL requirements here.

  • Otter@lemmy.catoAndroid@lemdro.id•SmartTube’s official APK was compromised with malware — What you should do if you use itEnglish
    14·
    2 months ago

    From the comments of the article

    Deleting it and re-installing from the new uncompromised release is not a big deal, but having to go and factory reset all one’s streaming devices and re-configure them from scratch is rather time consuming (I have several).

    In yuliskov’s github announcement, he doesn’t come across as this being particularly urgent, and is NOT making statements like “reset all your devices, change all your streaming account passwords”. He just said going forward there won’t be updates and it will have to be re-installed from the new tree.

    It seems at this point for most people, if google and amazon haven’t uninstalled it and you are not running 30.43 or 30.47, then keep using it, and when the new version is released, remove the old one and install the new one.

    Factory resetting is likely overkill. Android apps are, theoretically, sandboxed, so they shouldn’t be able to affect the system or other apps. Uninstalling the infected app should be enough to clean up, but a factory reset is a guaranteed way, which is why I mention it.

  • Otter@lemmy.catoLinux@lemmy.ml•Sick of reinstalling every year? My 8-step 'reinstall-proof' Linux desktop setup that actually survives hardware swapsEnglish
    2·
    2 months ago

    You can view the source for my comment and copy paste :)

    Do this in order:

    1. Install with LUKS full-disk encryption and Btrfs subvolumes for @ and @home so snaps are atomic.

    2. Enable automatic snapshots with Timeshift or snapper.

    3. Export your package lists:

      • Debian/Ubuntu: dpkg --get-selections > packages.txt
      • Arch: pacman -Qqe > pkglist.txt
      • also flatpak list --app > flatpaks.txt

    4. Put your dotfiles under version control and manage them with chezmoi or GNU Stow.

    5. Use Flatpak for GUI apps, containerized toolchains (podman) for dev environments, and keep only system-critical packages in the distro manager.

    6. Back up with Borg: borg init --encryption=repokey /path/to/repo ; borg create repo::$(date +%F) /home /etc --stats ; borg prune --keep-daily=7 --keep-weekly=4 --keep-monthly=6

    7. Keep a small, bootable USB with the exact kernel/tools you use so you can unlock LUKS and mount Btrfs snapshots.

    8. Test restores quarterly: restore a snapshot to a spare partition and boot it. Do that for a year and tell me reinstalling is fun again.

Moderates