if I just type "foone blah" now...
argh chrome updated and it seems they've intentionally broken custom search engines. I have had a keyword search for "foone" which searches my own twitter, so I just type "foone BLAH" and it gives me a twitter search for when I said BLAH, right?

if I just type "foone blah" now...

1. this will break the "searched from the address bar" magic, which means google will make me do captchas if I search too fast
2. it will break search suggestions too
https://t.co/KShHdCMzeT
I finally figured out how to get back being able to press SPACE instead of being forced to use TAB while using custom search in Chrome.
— Artem Russakovskii (@ArtemR) February 3, 2021
If you see the pill, then you are currently forced to use TAB. To get spaces back: disable chrome://flags/#omnibox-keyword-search-button pic.twitter.com/U5UkEtNXpW
1. this is how it's been for years. I can type "foone blah" faster than you can blink, man. it's the #1 thing I DO in my browser. what appeals to me is THIS IS HOW IT FUCKING WORKS, DIPSHIT. CHANGING THINGS BECAUSE YOU FEEL LIKE IT IS NOT FUN
it's a very common key to press. the tab key is not so centrally located, because it's rare.
AND I SAY THAT AS A PYTHON PROGRAMMER

Maybe I could swap the keycaps and mod the key matrix or reflash the controller?

I have a keyboard from the mid-90s and I'm thinking about dumping a 8051 firmware, reverse engineering it, modifying it, and reflashing it onto the keyboard just to eliminate a tiny source of friction in using it.
C32191AE or 1001000220 have no results.
maybe I should just stick it in my EEPROM reader and see if it can dump it as a generic 8051, then flash the modded code onto a replacement flash-enabled 8051?

I'd want to desolder the 8051, but look, this controller PCB is basically sitting on top of the main keyboard PCB


what's a web browser? OH, YOU'LL SEE!


It's older than the US release of the Super Nintendo.
Zelda: A Link To The Past, The US release of the Super Nintendo, and the dissolution of the USSR hadn't happened yet, but would later that year.
This use a capacitive method to detect key presses. These seem to have been liked by some companies as a better feeling keyboard than a membrane, but the foam sometimes completely disintegrates so they don't last forever.

This is apparently for "overtravel". The key actually is detected shortly after you start pushing it down, but to make it feel like you can push it down farther, the foam is there and gets compressed.

https://t.co/syXLRu6Rly
https://t.co/8xEis5WHID
The two pins in the middle go off to other keys (since it's a matrix) so I can't really swap them without affecting other ones

This would be hard because they'd have to cross, so I'd either have to use insulating layers or drill through to the other side.

The ones on top are for a reverse-side jumper connection.

More from foone
More from Tech
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x

PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ

The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
You May Also Like
Krugman is, of course, right about this. BUT, note that universities can do a lot to revitalize declining and rural regions.
See this thing that @lymanstoneky wrote:
And see this thing that I wrote:
And see this book that @JamesFallows wrote:
And see this other thing that I wrote:
One thing I've been noticing about responses to today's column is that many people still don't get how strong the forces behind regional divergence are, and how hard to reverse 1/ https://t.co/Ft2aH1NcQt
— Paul Krugman (@paulkrugman) November 20, 2018
See this thing that @lymanstoneky wrote:
And see this thing that I wrote:
And see this book that @JamesFallows wrote:
And see this other thing that I wrote:
🌿𝑻𝒉𝒆 𝒔𝒕𝒐𝒓𝒚 𝒐𝒇 𝒂 𝑺𝒕𝒂𝒓 : 𝑫𝒉𝒓𝒖𝒗𝒂 & 𝑽𝒊𝒔𝒉𝒏𝒖
Once upon a time there was a Raja named Uttānapāda born of Svayambhuva Manu,1st man on earth.He had 2 beautiful wives - Suniti & Suruchi & two sons were born of them Dhruva & Uttama respectively.
#talesofkrishna https://t.co/E85MTPkF9W
Now Suniti was the daughter of a tribal chief while Suruchi was the daughter of a rich king. Hence Suruchi was always favored the most by Raja while Suniti was ignored. But while Suniti was gentle & kind hearted by nature Suruchi was venomous inside.
#KrishnaLeela
The story is of a time when ideally the eldest son of the king becomes the heir to the throne. Hence the sinhasan of the Raja belonged to Dhruva.This is why Suruchi who was the 2nd wife nourished poison in her heart for Dhruva as she knew her son will never get the throne.
One day when Dhruva was just 5 years old he went on to sit on his father's lap. Suruchi, the jealous queen, got enraged and shoved him away from Raja as she never wanted Raja to shower Dhruva with his fatherly affection.
Dhruva protested questioning his step mother "why can't i sit on my own father's lap?" A furious Suruchi berated him saying "only God can allow him that privilege. Go ask him"
Once upon a time there was a Raja named Uttānapāda born of Svayambhuva Manu,1st man on earth.He had 2 beautiful wives - Suniti & Suruchi & two sons were born of them Dhruva & Uttama respectively.
#talesofkrishna https://t.co/E85MTPkF9W

Prabhu says i reside in the heart of my bhakt.
— Right Singh (@rightwingchora) December 21, 2020
Guess the event. pic.twitter.com/yFUmbfe5KL
Now Suniti was the daughter of a tribal chief while Suruchi was the daughter of a rich king. Hence Suruchi was always favored the most by Raja while Suniti was ignored. But while Suniti was gentle & kind hearted by nature Suruchi was venomous inside.
#KrishnaLeela

The story is of a time when ideally the eldest son of the king becomes the heir to the throne. Hence the sinhasan of the Raja belonged to Dhruva.This is why Suruchi who was the 2nd wife nourished poison in her heart for Dhruva as she knew her son will never get the throne.

One day when Dhruva was just 5 years old he went on to sit on his father's lap. Suruchi, the jealous queen, got enraged and shoved him away from Raja as she never wanted Raja to shower Dhruva with his fatherly affection.

Dhruva protested questioning his step mother "why can't i sit on my own father's lap?" A furious Suruchi berated him saying "only God can allow him that privilege. Go ask him"
