My Keychron Q11 showed up recently and I've been super happy with it. Main reason was that my Noppoo Choc Mini finally lost a switch and I don't have any on hand (nor a soldering iron ...yet) but it turns out I actually really wanted the pair of rotary encoders on this and didn't even realise.
Specifically, I've got it bound to Ctrl-PgUp/PgDown so I can scroll through my tabs with it and close them with a click binding to Ctrl-W and that's working out really well.
Anyone else use the knobs like that? I've got the other one set to volume and the vendor had zoom as a suggestion but I wonder what else people do with these?
Bonus newb Q: On the product page they demonstrate binding Ctrl-+ zooming to the encoder via a macro but neither macro13 nor the {KC_LCTL,KC-W} type syntax would let me click "Confirm" when trying to associate it to the knob in Via (eg. it wouldn't let me follow their example). Luckily it was happy with the alternative of LCTL(KC_W) that I stumbled on somewhere but now I wonder how to properly associate a macro to a knob?
Last time I needed to add rf to a desktop, Intel AX200 seemed like the chipset to get. But now there are various new standards and the BE200 apparently has issues with AMD systems? So is there something newish from Qualcomm or others that I should be aiming for or would I probably be better off just picking up an AX210?
Since the card might be kicking around a while I'm curious what has the best overall Linux support with as many significant 802.11 standards and Bluetooth codecs as possible for general future-proof-ness. Would also be nice if it had good support for AP mode as that's sometimes handy or I might repurpose it into a router at some point.
Apparently, while it's closed for new donations, liberapay is still going to renew existing ones.
https://thelocal.to/small-claims-court-delays/
While Ontario’s other court systems bounce back from their pandemic-era backlogs, analysis by The Local shows that “the people’s court,” where many low-income people seek justice, is lagging far behind.
cross-posted from: https://lemmy.ca/post/1926125
Too many perfectly usable phones are put into a questionable security situation by lack of vendor support for keeping key software up to date.
But what's the actual risk of using an Android phone on a stock ROM without updates? What's the attack surface?
It seems like most things that'd contact potentially malicious software are web and messaging software, but that's all done by apps which continue to receive updates (at least until the android version is entirely unsupported) eg. Webview, Firefox, Signal, etc.
So are the main avenues for attack then sketchy apps and wifi points? If one is careful to use a minimal set of widely scrutinised apps and avoid connecting to wifi/bluetooth/etc. devices of questionable provenance is it really taking that much of a risk to continue using a device past EOL?
Or do browsers rely on system libraries that have plausible attack vectors? Perhaps images, video, font etc. rendering could be compromised? At this point though, that stack must be quite hardened and mature, it'd be major news for libjpg/ffmpeg to have a code-execution vulnerability? Plus it seems unlikely that they wouldn't just include this in webview/Firefox as there must surely be millions of devices in this situation so why not take the easy step of distributing a bit more in the APK?
I'm not at all an Android developer though, perhaps this is very naive and I'm missing something major?
Too many perfectly usable phones are put into a questionable security situation by lack of vendor support for keeping key software up to date.
But what's the actual risk of using an Android phone on a stock ROM without updates? What's the attack surface?
It seems like most things that'd contact potentially malicious software are web and messaging software, but that's all done by apps which continue to receive updates (at least until the android version is entirely unsupported) eg. Webview, Firefox, Signal, etc.
So are the main avenues for attack then sketchy apps and wifi points? If one is careful to use a minimal set of widely scrutinised apps and avoid connecting to wifi/bluetooth/etc. devices of questionable provenance is it really taking that much of a risk to continue using a device past EOL?
Or do browsers rely on system libraries that have plausible attack vectors? Perhaps images, video, font etc. rendering could be compromised? At this point though, that stack must be quite hardened and mature, it'd be major news for libjpg/ffmpeg to have a code-execution vulnerability? Plus it seems unlikely that they wouldn't just include this in webview/Firefox as there must surely be millions of devices in this situation so why not take the easy step of distributing a bit more in the APK?
I'm not at all an Android developer though, perhaps this is very naive and I'm missing something major?
cross-posted from: https://lemmy.ca/post/653849
I'm trying to follow conventional wisdom and have more and more of our portfolio as straight up VGRO but want some more US exposure (though I am aware there are arguments in favour of a home-country bias). I was also interested in picking a USD fund as not only do they tend to have a lower MER but also get an extra boost from witholding tax exemption if I hold them in an RRSP.
An S&P 500 fund seems the way to go, but it seems awfully slanted towards giant tech megacaps. Apple alone is over 7% of VOO. With a P/E over 31 it's hard for me to feel like there's not extra risk with the concentration here--is it really such a safe bet to think the largest company in the world has that much more growth ahead of it? And VGRO already has a solid chunk of cap-weighted exposure.
And so, after my inexpert research failed to dissuade me, I'm probably going to use an equal-weight ETF like RSP or EUSA for this portion---there are no penny stocks on the S&P 500 and it doesn't seem to perform much worse (and indeed better depending how far back you test). At this point I'm more comfortable with either of those than VOO and will probably do this just for the irrational psychology, but I do wish there was something that combines an equal weighting with a screen for quality (something like SPHQ) as a big drawback seems like for as much concentration risk as it avoids it also keeps rebalancing more and more into failing companies as they crash and burn.
Anyone else subscribe to a similar reasoning and incorporate an equal weight fund into the passive portion of your portfolio? Which one did you go with?
https://www.tvo.org/article/good-luck-olivia-chow-youre-going-to-need-it
https://money.tmx.com/quote/AP.UN/news/6622298329971614/Allied_to_Sell_UDC_Portfolio_to_KDDI_Corporation_for_135_Billion
There's an election soon in Toronto! A publication I like has some detailed profiles on the candidates but I bet others do too. Seems like it'd be best to start a thread and collect links to that kind of coverage in top level comments.
@BuoyantCitrus
@lemmy.ca