• 15 Posts
  • 819 Comments
Joined 6 years ago
cake
Cake day: May 31st, 2020

help-circle
  • Eh, they’re alright, but you can usually find something better on F-Droid. As far as I’m aware, they’re mostly the AOSP apps with slight tweaks, so they might look familiar

    Apps where I use the default:

    • Calendar (alternatives on F-Droid, like Etar, are virtually identical)
    • Camera (there’s OpenCamera on F-Droid, but I don’t know, not really using the Camera much)
    • Clock
    • Contacts
    • Dialer
    • FM Radio
    • Messaging (doesn’t look super great, but don’t use it much)
    • Recorder

    Where I didn’t write anything, there’s probably something better out there, but I rarely use these apps.

    Apps which I’ve replaced:

    • Browser → Firefox
    • Calculator → Calculator++ (probably overkill for most folks, but I do think the default calculator app is terrible on virtually all Android flavors)
    • Gallery → Fossify Gallery
    • Files → Material Files
    • Keyboard → HeliBoard
    • Music → Booming Music (pretty much just because I want album-shuffle)
    • Trebuchet Launcher → KISS (personal preference)

  • While watching, I was thinking that roguelike could be a solution here. Cool to see that it’s actually working out.

    If I remember right, Cataclysm: Dark Days Ahead is also stealth-y + a roguelike. Gonna have to try that again. I believe, I actually found it too tense last time around, but might’ve just been past-me. 🫠


    I also have to say, I really hate that mark-enemies-manually feature. As the wisdom goes: “Given the opportunity, players will optimize the fun out of a game.”
    Source

    I’m that player. I will spend far too much time trying to mark any pixel of any enemy that shows up on my screen. It’s not fun, but I’ll do it anyways, because the game is telling me this is the big mission, this is where the prep work is important.

    It also never made sense to me lore-wise. How can you be able to track people once they’re marked, but you can’t detect them without marking? Whatever technology you use to track their movement after marking, it has to be able to detect that movement without line of vision. If anything moves in the area, just show me that. 🤨







  • To be fair, that has been a recommendation from experts for decades.

    But yeah, now you got oat milk advertising itself as being a source of fiber, just because it’s slightly less terrible than cow milk. My oat milk pack has 9g of fiber in a whole liter. Eat a fraction of a salad and you’ve easily got more than that…



  • This sounds exactly like your problem: https://bbs.archlinux.org/viewtopic.php?id=269796

    It’s quite a lot of detailed technology talk, which I don’t expect you to understand. The main takeaway should be this:

    So the problem is [temporarily] solved by running: rmmod hid_apple

    This command unloads a driver that’s potentially interfering here. The driver will be loaded again on next reboot.
    Which is useful, because you can just try it out and if it doesn’t work (or if it breaks something), you can just do a reboot and everything is back to normal.

    You will need admin/root permissions to run this command, so the real command you need to run is: sudo rmmod hid_apple
    It will ask you for your login password to confirm running the command.

    If that does fix it, then we can look into making it permanent.


  • my kb Fx keys are unusable for almost a year now and i exhausted all possible way to fix it.

    Unusable as in nothing at all happens, or do they do things like volume up/down when you press them?

    If the latter, there may be an “FnLock” key combination you have to press. Usually, it’s something like Fn+Esc. Or Fn + whatever key has a lock symbol or “FnLock” written on it…


  • Yeah, I didn’t even include technical debt into my list, but it comes up so often as well. Chances are someone else already saw the problem, considered fixing it, then saw the mountain of technical debt blocking a fix, and decided to ignore the problem in the end.

    For me, thankfully, folks have been understanding so far, when a bug fix takes significantly longer than expected.
    But we also explicitly don’t estimate bug fixes upfront, because of what you say. You have to diagnose the bug to figure out what solution is required. And the solution can range from a one-line-change to a refactoring of half the codebase. Good luck estimating that…




  • I feel like many bugs in the wild just come from business processes slowing everything down, especially in larger companies. It might seem like a bug that can be fixed in half an hour, if anyone spotted it, but instead:

    1. they need to file a ticket
    2. it gets discussed in planning, but postponed because there’s an extremely important™ deadline (repeat this step like 5 times)
    3. someone from upper management notices the problem and sends an angry mail; it is finally included into the sprint
    4. they implement the change
    5. it gets rejected in code review due to some nitpick
    6. they fix that nitpick
    7. it passes code review and is merged onto main
    8. it gets discussed again in sprint review
    9. it gets shipped two months later
    10. ah crap, something broke; need to bisect a few hundred commits to find out it was this change that broke it
    11. spend half a day preparing and testing a hotfix release, because the next proper release is months away
    12. it gets rejected in code review due to some nitpick
    13. …you get the idea.

    You go through that slew of bullshit exactly once before you learn to turn a blind eye to anything that looks easy to fix.



  • Yeah, I like crosswords as a concept, but so many puzzles have prompts like “Jebuses’ Dad’s cousin, thrice removed”.

    How would I ever just know the answer to that? And even if I work out most of the intersecting letters, it’s some random name/word in a foreign language, so there’s no way I’ll guess the rest.
    It’s just a dead-end in the word crossing logic, which is quite shite.



  • Well, politics isn’t about finding the one principle to rule them all. The folks/companies that find restricting access to children important, probably don’t particularly care about some Linux devices being excluded. And other folks/companies find not restricting their Linux server really important, so that’s a compromise that can be made.

    I imagine, they landed on specifically open-source being excluded as the more abstract rule, because open-source in particular has a problem here.
    Anyone can download open-source software and run it. In most cases, there is no central backend, which could handle age verification.

    And even if there is, it’s not really financially viable to offer that for anyone who downloads the software for free. Requiring payment to access the binaries or the source code would also effectively kill the open-source ecosystem, which is also not in the interest of most people.