Skip Navigation
InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)KU
KubeRoot @discuss.tchncs.de
Posts 0
Comments 177
Before your change to Linux
  • Windows 10. The reason I switched was pretty funny - I had previously bought a cheap SSD and moved my install over to it, and installed Arch on my HDD hoping to experiment with it.

    I never really did that, but one day before Christmas my computer booted straight to Arch to my confusion, and after a while I figured out my SSD failed. I ended up installing gnome to have something to use in the meanwhile, since I wasn't gonna be buying a new SSD in the next few days, but then I just decided to stick with Linux. As I learned more about it I realised I was barely missing anything, and I preferred Linux for what I had.

  • Flatpak haters seem to believe that if an app isn't on their distro's repos, it's the developers' fault.
  • I think you're actually agreeing with me here. I was disputing the claim that software should be made available in "a native package format", and my counterpoint is that devs shouldn't be packaging things for distros, and instead providing source code with build instructions, alongside whatever builds they can comfortably provide - primarily flatpak and appimage, in my example.

    I don't use flatpak, and I prefer to use packages with my distro's package manager, but I definitely can't expect every package to be available in that format. Flatpak and appimage, to my knowledge, are designed to be distro-agnostic and easily distributed by the software developer, so they're probably the best options - flatpak better for long-term use, appimage usable for quickly trying out software or one-off utilities.

    As for tar.gz, these days software tends to be made available on GitHub and similar platforms, where you can fetch the source from git by commit, and releases also have autogenerated source downloads. Makefiles/automake isn't a reasonable expectation these days, with a plethora of languages and build toolchains, but good, clear instructions are definitely something to include.

  • Flatpak haters seem to believe that if an app isn't on their distro's repos, it's the developers' fault.
  • The responsibility to figure out the dependencies and packaging for distros, and then maintain those going forwards, should not be placed on the developer. If a developer wants to do that, then that's fine - but if a developer just wants to provide source with solid build instructions, and then provide a flatpak, maybe an appimage, then that's also perfectly fine.

    In a sense, developers shouldn't even be trusted to manage packaging for distributions - it's usually not their area of expertise, maintainers of specific distributions will usually know better.

  • Nintendo sues Switch modchip seller and Switch piracy Reddit moderator | VGC
  • If the quote is accurate, he went a step further and put pirated games on the devices. Even if pirating the game is legal in some way (he owns it legitimately so putting a copy is fine or something), sending such devices out to customers then means he's also distributing pirated games.

    That said, somebody in the comments claimed he didn't distribute games, but rather software that made it easy to pirate games - I don't know what the precedent is for that being considered illegal, but it does call the original claims into question.

  • Ladybird - a brand new browser engine that isn't Google or Mozilla
  • GPL is virally open source, because code using it needs to also be open source.

    According to your comment, that doesn't apply to BSD, so BSD isn't virally open source, and the claim is true.

    The reason some consider this better is because a company can't fork the code, keeping it private, improving their version with paid workforce while also merging in changes to the original project, thus ending up with a superior version that they can then sell for profit, to no benefit of the opensource version or the people contributing to it.

    There's more reasons, and a whole ideological side, but I think that's the main practical reason for using copyleft licenses, and a big one.

  • Emotional overload
  • I think the lack of commas is a stylistic choice, the unceasing torrent of negative words relating to the frantic nature of parenthood, dealing with one thing after another without pause.

    If it's not, then that seems like quite a happy little accident!

  • Do animals have emotions like us?
  • If that's the case, then there's also something more complex going on - animals can certainly learn to anticipate things at specific times, like food, a dog gets excited by a doorbell because they knew that means somebody is coming, they can get stressed out by innocuous things if they associate it with bad experiences like beatings.

    Not saying you're wrong, but it warrants further explanation, because as is it doesn't match the simple experience of living with a dog.

  • China is attempting to mirror the entire GitHub over to their own servers, users report
  • Sure, you can probably clone it - I'm not 100% sure, but I think laws protect that as long as it's private use.

    You can also fork it on GitHub, that's something you agree to in the GitHub ToS - though I think you're not allowed to push any modifications if the license doesn't allow it?

    Straight up taking the content from GitHub, uploading it to your own servers, and letting people grab a copy from there? That's redistribution, and is something that needs to be permitted by the license. It doesn't matter if it's git or something else, in the end that's just a way to host potentially copyrighted material.

    Though if you have some reference on why this is not the case, I'd love to see it - but I'm not gonna take a claim that "that's very much a part of most git flows".

  • Steam announces game recording beta.
  • I imagine they made this specifically for Steam Deck, since windows users already have stuff like this built into GPU software. They'd want to offer feature parity on their handheld, so it'll probably work nicely out of the box.

  • Failed a spot check
  • I'm not clear on the details, but I know the constellations are made out of stars, I think planets like mars were thought to be major stars, and I'd think sayings like "the stars aligned" would have roots in astrology...

    I will also nitpick and say that they said astrology terms, specifically - if astrology considers constellations to be important, and acknowledges they are made out of stars, I'd imagine stars would be part of the terminology. (Doubly so if I'm correct about astrology having (at least previously) a skewed view on what a star is!)

  • Steam Deck Now Cheaper Than A Switch During Valve's Big Summer Sale
  • Those are fair points, I actually bought the switch pretty early on after seeing praise for Odyssey and BotW. I play on PC otherwise, but I enjoyed the experience, playing docked with joycons with motion controls.

    I'm not personally frustrated, while the games definitely seem overpriced, I always felt like Nintendo is just sitting in their niche doing their thing, not trying to one-up others and instead providing various gimmicks with their devices. They're selling consoles and games for a certain price, and it feels like if you think the deal is bad or unfair, you can just pass on it.

    I don't think I really have a point here, just saying my thoughts. I have my issues with Nintendo, but I do feel like their consoles and games provide value that is hard to get elsewhere.

  • Steam Deck Now Cheaper Than A Switch During Valve's Big Summer Sale
  • I do get the impression that Nintendo has consistently had worse hardware for a long time... And I appreciate it. Instead of cranking up the hardware, they make games that are fun and run on weaker hardware, often with neat stylization.