In order to load a custom OS you first must be able to unlock the bootloader ofthe device. The list of OEMs allowing that is sadly getting smaller and smaller and vendors are becoming actively hostile towards custom firmware development.
see: https://github.com/zenfyrdev/bootloader-unlock-wall-of-shame
icanhaz tools:
Ferengi Rules of Acquisition
-
- War is good for business.
-
- Peace is good for business.
won't get better
Adblock is digital self defense against malware for your pc, as well as your mind.
https://xcancel.com/SwiftOnSecurity/status/1569083806224715776
this isn't properly remapped and depending on implementation of the key-up events by the keyboard vendor, requires an ugly time delay hack.
qed. https://github.com/Rast1234/copilot_key_on_my_keyboard?tab=readme-ov-file#the-bad
You can get a 2020 M1 / 2022 M2 Macbook air for ~400€, that will mop the floor with all new hardware in that price range released even today (completely fanless/noiseless btw.). It also has decent linux support via asahi and Apple will still probably provide 5+ years of macOS updates anyway.
- geekbench: https://browser.geekbench.com/v6/cpu/compare/16388159?baseline=16471197
- ebay.de sold macbooks: https://www.ebay.de/sch/111422/i.html?_fsrp=1&_udlo=150&rt=nc&_nkw=macbook+air+%28m1%2Cm2%29&_sacat=111422&_sop=13&LH_PrefLoc=3&LH_Sold=1&LH_ItemCondition=1000%7C2010%7C1500%7C2020%7C2030%7C2500%7C3000
- random lenovo: https://www.notebooksbilliger.de/lenovo+v15+g5+83gw00a7ge+820626
The simple trick to owning nice hardware is to never give vendors your money directly, let others burden the depreciation.
It's arguably worse, because Samsung has full control over software, hardware, and firmware of their devices.
Even if MS would like to fix this mess, they can't.
I've made an update edit: Some hardware vendors fucked up when to send the key-up-sequence apparently so now every keyboard can behave differently. I don't know if this makes the situation better or worse.
Who would've guessed radishes were so rad^ical^ vegetables.
The new Microsoftslop copilot key always sends the following key-sequence when pressed:
copilot key down: left-shift-down left-meta-down f23-down f23-up left-meta-up left-shift-up
copilot key up: <null>
This means there's no real key-up event when you release the key --> it can't be used (properly) as a modifier like ctrl or alt.
The workaround is to send a pretend key-up event after a time delay, but then you mustn't be too slow / fast when pressing a shortcut.
- Linux workaround: https://github.com/m-bartlett/remap-copilot?tab=readme-ov-file
- Windows workaround https://github.com/randyrants/sharpkeys/issues/560
- https://xcancel.com/dcolascione/status/2019936377408811319
tldr: AI took a perfectly working modifier key from you.
--- edit ---
Some keyboards apparently do the "right" thing and don't send the whole sequence at once, you can remap those properly with keyd, see: https://github.com/rvaiya/keyd/issues/1025#issuecomment-2971556563 / https://github.com/rvaiya/keyd/issues/825
copilot key down: left-shift-down left-meta-down f23-down
copilot key up: f23-up left-meta-up left-shift-up
this will still break left-shift + remapped copilot and left-meta + remapped copilot, but RCtrl remaps should work as expected
Therapist: USB3.0 Micro-B is dead, it can't hurt you.
Nintendo: Invents dual USB-C
view more:
next ›