• 0 Posts
  • 169 Comments
Joined 1 year ago
cake
Cake day: June 26th, 2023

help-circle



  • The amount of work actually doesn’t matter (except when it does; especially the EU may consider it). The specific wordings might matter but that’s not immediately obvious. A dictionary is at least close enough to mere database that its protected status isn’t automatic. The more selective the dictionary is the more obviously it is protected since the selection process is an expression of creativity.

    Fake entries are definitely used in practice, most likely because they move the dictionary from “probably protected but the court would have to decide” to “definitely protected”.









  • Jesus_666@feddit.detoTechnology@lemmy.worldPrivacy tool
    link
    fedilink
    English
    arrow-up
    14
    arrow-down
    1
    ·
    25 days ago

    All other things aside, which Logitech mouse are you talking about? Both my G Pro and my G 305 work out of the box. Logitech also advertises them as ChromeOS compatible and AFAIK the Logitech wireless dongles are USB HID compliant so seeing a Linux straight up refuse to interact with them sounds very weird.



  • I think a good way to handle this – as well as the wildly unpopular accessibility functions the post is about – would be to have it configurable and simply ask about it during initial user setup (aka OOBE).

    That way people who didn’t need it can turn it off and won’t stumble over it after accidentally pressing the Windows key or holding down Shift a bit too long. People who need it can have it enabled right from the get-go without having to trigger some dialog first. Everyone’s happy and having one extra step during initial setup isn’t that much of a hassle.

    Bonus points if Windows had configurable global hotkeys and I could make the Windows key do whatever I want. But the OOBE thing would be a good solution already.



  • I agree that it should be easily reachable. Just not through one single keypress. macOS’s Spotlight serves a similar purpose and is reachable via Cmd + Space (with the Cmd key being right next to the space bar). That’s just as easy to do as hitting one button but is extremely unlikely to happen by accident.

    I personally use the start menu mainly for shutting down the computer as all commonly used programs are pinned to the task bar. A shortcut that opens it has no value to me as opposed to e.g. one that shows or hides a terminal window or one that mutes/unmutes me in Teams even when it’s in the background.

    And I do consider it disruptive because having the start menu unexpectedly pop open and swallow several keypresses (and in the worst case launching some application I didn’t want to run) takes my attention away from what I was doing and forces it into something completely irrelevant. If this pulls me out of deep focus I can lose the equivalent of ten minutes of work due to one keypress.

    The core of the problem is that this behavior is very annoying for people who don’t use the start menu all the time and there’s no way to change it. If it was just a default for a rebindable shortcut then it’d be a minor hassle once and nobody would complain. But the way it is it feels like Microsoft is trying to force-feed me the start menu, workflow be damned.


  • I think it’s extremely badly designed. A single keypress – especially if the key is in such an easily reachable position – shouldn’t steal focus. It doesn’t matter if I’m in a game or in Visual Studio, it’s disruptive.

    This behavior would make sense as a media key somewhere near the F-keys. But as the default action on a modifier key it’s just bad design.

    I can’t believe that launching the start menu is an action on par with opening an application menu or typing a capital letter.