• 0 Posts
  • 177 Comments
Joined 4 years ago
cake
Cake day: May 31st, 2020

help-circle
  • Hmm, I don’t know anything about Whoogle, but from other privacy-conscious search engines, I would expect it to work when you use that URL in your bookmark.

    Three things I can imagine:

    • Something in your hosting stack strips the URL parameters, like maybe your reverse proxy, if you use one. You might be able to see in the Whoogle or web server logs, which URLs actually reach it. Might need to set it to debug/trace logging.
    • Maybe there’s a flag in the Whoogle configuration you need to enable to accept these preference URLs.
    • It’s a bug in that Whoogle version.


  • What I don’t like about the genre, is that I’m bad at it. 🙃

    More seriously, I do find it kind of frustrating at times. Restarting ten times in a roguelike, no problem, because it’s always a new challenge.
    But if I miss the same jump ten times, or have to retry the same platforming passage ten times, you’ll see me getting impatient, which means I’ll fail the next ten attempts, too…








  • Ah, yeah, I don’t think there was anything in the app. I guess, they could’ve mentioned it in the changelog, which gets shown in the app by default after an update.

    But yeah, I think we’ll have to excuse a bit of a bumpy ride here. I know, it says “Mozilla” on there now, but to my knowledge, it’s still just the one core dev…







  • I’d say, I’m primarily a very low volume gamer, so I don’t play a lot of games, and if I do, I don’t play them for long. And that certainly makes it easy to look at the news of a game releasing and to think, yeah, that’s probably neat, but if I’m buying another game then it’d be Undertale or Baba Is You or such, and it definitely doesn’t look as neat as those…


  • For a project called “Potato Peeler”, I’ll put it into a structure like this:

    ~/Projects/Tools/Potato-Peeler/potato-peeler/
    

    Tools/ is just a rough category. Other categories are, for example, Games/ and Music/, because I also do gamedev and composing occasionally.

    Then the capitalized Potato-Peeler/ folder, that’s for me to drop in all kinds of project-related files, which I don’t want to check into the repo.

    And the lower-case potato-peeler/ folder is the repo then. Seeing other people’s structures, maybe I’ll rename that folder to repo/, and if I have multiple relevant repos for the Project, then make it repo-something.

    I also have a folder like ~/Projects/Tools/zzz/ where I’ll move dormant projects. The “zzz” sorts nicely to the bottom of the list.



  • I find that difficult. Aside from code reviews, often times your job as a maintainer is:

    • getting a refactor or code cleanup in while everyone’s asleep
    • shuffling commits around between branches
    • fixing the CI toolchain
    • rolling back or repairing a broken change
    • unfucking the repo
    • fixing a security vulnerability

    A required review slows all of these tasks to a crawl. I do agree that the kernel is important enough that it might be worth the trade-off.
    But at the same, I do not feel like I could do my (non-kernel) maintainer job without direct commit access…


  • Ephera@lemmy.mltoLinux@lemmy.mlSome basic questions about Linux
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    19 days ago

    A distro is a complete installable operating system (+ a set of software repositories from which you can install updates and new software).
    Many distributions (or their flavors/spins) will come with a default desktop environment and then usually also apply some distro-appropriate theming to that desktop environment.
    If you look at screenshots of distributions, you’re likely just looking at screenshots of their themed default desktop environment.

    And a desktop environment is essentially the GUI of your OS.
    It includes software such as the panel/taskbar, the application menu, the systray, the audio system, icons, a login screen etc… It also typically comes with a set of default applications, such as a file manager, a terminal emulator, a text editor etc…
    In a sense, the desktop environment contains essentially everything that differentiates a desktop OS from a server OS (the latter is usually just a terminal, without graphical interface).