• 40 Posts
  • 2.69K Comments
Joined 6 年前
cake
Cake day: 2020年5月31日

help-circle




  • the company says the change will only impact “4% of Game Pass subscribers.”

    I bet, they averaged the play times and that’s how they came up with that figure. I can believe that only a small percentage of their customers average more than 15h per month.

    But you know how these things go.
    You start playing a game that you really enjoy and suddenly you’re binging that for the whole weekend. That’s your 15h for the month gone.

    Or you’ve got your two-week vacation in a particular month and suddenly you’re playing multiple hours each day. Don’t even need math to figure out that 15h are not enough for 14 multi-h sessions.

    There’s just going to be variations in playtime and now you’ll have to pay up for 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.


  • Lemmy uses Markdown for storing/displaying comments, specifically the CommonMark flavor with some extensions, as documented here: https://join-lemmy.org/docs/users/02-media.html

    And yeah, no, that doesn’t have a way to underline,

    except

    maybe

    one

    of

    these
    here,

    depending on the Markdown implementation in the client. Some clients might also choose to underline the highlighting, that’s normally 𝘪𝘵𝘢𝘭𝘪𝘤.

    Links may be underlined as well.

    Well, and then you’ve also got this thing, which is certainly a line under this text:


    On Lemmy, we also got strikethrough. Priorities, I guess. 🙃

    But yeah, no proper, consistent underlining in Markdown/Lemmy. 🥴


  • Oh man, I just checked what it looks like in Firefox:

    The underline after the first character and ends one character after the last.

    I had written that comment in the Jerboa app (and fiddled with it to make it look reasonable):

    The underline starts and ends in the middle of the first/last character.


    when the software (in this case, lemmy’s md to html engine) tries to do the rendering instead of the browser.

    And nope, in this case I added the Unicode for the underline myself. Well, I used this app. That passes straight through the MD→HTML conversion without being touched.
    And it actually is rendered by the browser, but yeah, by the browser’s Unicode+font rendering, not the CSS engine. Or in case of Jerboa, by Android’s Unicode+font rendering.
    Would certainly be nice, if these would look the same. 🫠