this post was submitted on 16 Nov 2023
529 points (95.5% liked)

Lemmy Shitpost

26717 readers
3883 users here now

Welcome to Lemmy Shitpost. Here you can shitpost to your hearts content.

Anything and everything goes. Memes, Jokes, Vents and Banter. Though we still have to comply with lemmy.world instance rules. So behave!


Rules:

1. Be Respectful


Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.

Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.

...


2. No Illegal Content


Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.

That means:

-No promoting violence/threats against any individuals

-No CSA content or Revenge Porn

-No sharing private/personal information (Doxxing)

...


3. No Spam


Posting the same post, no matter the intent is against the rules.

-If you have posted content, please refrain from re-posting said content within this community.

-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.

-No posting Scams/Advertisements/Phishing Links/IP Grabbers

-No Bots, Bots will be banned from the community.

...


4. No Porn/ExplicitContent


-Do not post explicit content. Lemmy.World is not the instance for NSFW content.

-Do not post Gore or Shock Content.

...


5. No Enciting Harassment,Brigading, Doxxing or Witch Hunts


-Do not Brigade other Communities

-No calls to action against other communities/users within Lemmy or outside of Lemmy.

-No Witch Hunts against users/communities.

-No content that harasses members within or outside of the community.

...


6. NSFW should be behind NSFW tags.


-Content that is NSFW should be behind NSFW tags.

-Content that might be distressing should be kept behind NSFW tags.

...

If you see content that is a breach of the rules, please flag and report the comment and a moderator will take action where they can.


Also check out:

Partnered Communities:

1.Memes

2.Lemmy Review

3.Mildly Infuriating

4.Lemmy Be Wholesome

5.No Stupid Questions

6.You Should Know

7.Comedy Heaven

8.Credible Defense

9.Ten Forward

10.LinuxMemes (Linux themed memes)


Reach out to

All communities included on the sidebar are to be made in compliance with the instance rules. Striker

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] Kyyrypyy@lemmy.world -4 points 11 months ago

That is actualla good feature then, if you need it for accessibility... But why on earth does it need to prompt you to enable it with such an annoying way? To my knowledge, it's the only accessibility option that agressively advertises itself specifically when you don't want, or need, it to.

More logical behaviour to prompt the enabling would be if a "modifier" key, and "non-modifier" key is pressed in sequence, but not at the same time. As the assumption of sticky keys is that the user is not able to press two buttons down simultaneously.

That said, it is likely that a person who has need for this feature, but is not aware of it's excistence, would not use other modifiers than shift, as they are needed exclusively for hotkeys, which is on the far end of the learning curve (as mouse, and right klick are more apparent to learn), and if such feature is needed, it's excistence is apparent at the time you start to use the systems via hotkeys. Instead, if you hammer shift repeatedly while typing, it indicates that you light benefit from tjis feature. Thus only requiring detection of the writing cursor being active, which is already possible, because there is an accessibility feature to highlight that. I know this, because a fresh install of windows suggests that you go trough accesdibility on first startup.

Sorry, I know you're not developing Windows UI (but what do I know, if you did), but I kindawanted to rant a bit about such an apparent solution to a problem that has plagued from Win 3.11 at least.