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
The entire discussion around Facebook’s disclosures of what happened in 2016 is very frustrating. No exec stopped any investigations, but there were a lot of heated discussions about what to publish and when.
In the spring and summer of 2016, as reported by the Times, activity we traced to GRU was reported to the FBI. This was the standard model of interaction companies used for nation-state attacks against likely US targeted.
In the Spring of 2017, after a deep dive into the Fake News phenomena, the security team wanted to publish an update that covered what we had learned. At this point, we didn’t have any advertising content or the big IRA cluster, but we did know about the GRU model.
This report when through dozens of edits as different equities were represented. I did not have any meetings with Sheryl on the paper, but I can’t speak to whether she was in the loop with my higher-ups.
In the end, the difficult question of attribution was settled by us pointing to the DNI report instead of saying Russia or GRU directly. In my pre-briefs with members of Congress, I made it clear that we believed this action was GRU.
The story doesn\u2019t say you were told not to... it says you did so without approval and they tried to obfuscate what you found. Is that true?
— Sarah Frier (@sarahfrier) November 15, 2018
In the spring and summer of 2016, as reported by the Times, activity we traced to GRU was reported to the FBI. This was the standard model of interaction companies used for nation-state attacks against likely US targeted.
In the Spring of 2017, after a deep dive into the Fake News phenomena, the security team wanted to publish an update that covered what we had learned. At this point, we didn’t have any advertising content or the big IRA cluster, but we did know about the GRU model.
This report when through dozens of edits as different equities were represented. I did not have any meetings with Sheryl on the paper, but I can’t speak to whether she was in the loop with my higher-ups.
In the end, the difficult question of attribution was settled by us pointing to the DNI report instead of saying Russia or GRU directly. In my pre-briefs with members of Congress, I made it clear that we believed this action was GRU.
Recently, the @CNIL issued a decision regarding the GDPR compliance of an unknown French adtech company named "Vectaury". It may seem like small fry, but the decision has potential wide-ranging impacts for Google, the IAB framework, and today's adtech. It's thread time! 👇
It's all in French, but if you're up for it you can read:
• Their blog post (lacks the most interesting details): https://t.co/PHkDcOT1hy
• Their high-level legal decision: https://t.co/hwpiEvjodt
• The full notification: https://t.co/QQB7rfynha
I've read it so you needn't!
Vectaury was collecting geolocation data in order to create profiles (eg. people who often go to this or that type of shop) so as to power ad targeting. They operate through embedded SDKs and ad bidding, making them invisible to users.
The @CNIL notes that profiling based off of geolocation presents particular risks since it reveals people's movements and habits. As risky, the processing requires consent — this will be the heart of their assessment.
Interesting point: they justify the decision in part because of how many people COULD be targeted in this way (rather than how many have — though they note that too). Because it's on a phone, and many have phones, it is considered large-scale processing no matter what.
It's all in French, but if you're up for it you can read:
• Their blog post (lacks the most interesting details): https://t.co/PHkDcOT1hy
• Their high-level legal decision: https://t.co/hwpiEvjodt
• The full notification: https://t.co/QQB7rfynha
I've read it so you needn't!
Vectaury was collecting geolocation data in order to create profiles (eg. people who often go to this or that type of shop) so as to power ad targeting. They operate through embedded SDKs and ad bidding, making them invisible to users.
The @CNIL notes that profiling based off of geolocation presents particular risks since it reveals people's movements and habits. As risky, the processing requires consent — this will be the heart of their assessment.
Interesting point: they justify the decision in part because of how many people COULD be targeted in this way (rather than how many have — though they note that too). Because it's on a phone, and many have phones, it is considered large-scale processing no matter what.
