this post was submitted on 28 May 2024
754 points (98.0% liked)
Bikini Bottom Twitter
4133 readers
59 users here now
Ahoy, me buckos! Welcome to Bikini Bottom Twitter! Your digital reef for the latest salty gossip and treasure tales! And while you're at it, be sure to drop by the Krusty Krab for a delicious Krabby Patty so I can get yer mon- err I mean, 'cause they're the best treat under the sea!
Rule 1 - This is Bikini Bottom Twitter, all posts should be Spongebob related in "(Old-School) Twitter-like" form
Rule 2 - Political posts, as long as it follows rule 1, will be permitted, so long as you behave yourselves.
Bikini Bottom Municipal Code §33-07: Anti-Tankie Ordinance Residents are prohibited from circulating tankie ideology or other authoritarian propaganda on Bikini Bottom Twitter. Offenders will be permanently banned from BPT by the BBPD faster than Plankton is ejected from The Krusty Krab.
Rule 3 - Please no reposts within the last couple days, at least
Rule 4 - All posts should be at least above a "Squirdward-krusty-krab-shift" level of effort
Rule 5 - Be chill, be a Patrick not a squidward.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.