Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
radlad
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
60 ms
·
841.
▲
by
radlad
3y ago
Can you define newer? Which watch do you have? I have a Fenix 6s and with Always On mode it lasts about a week. However, if I record activities, I'll need to charge it that night. At one point, battery life got really bad but a factory
842.
▲
by
radlad
3y ago
I owned one!
843.
▲
by
radlad
3y ago
Thank you! I will give this a try.
844.
▲
by
radlad
3y ago
Wow, thanks for that. I will have to try this. It is annoying that it is hidden under the Bluetooth breadcrumbs.
845.
▲
by
radlad
3y ago
The rider leans forward to accelerate the OneWheel, so they are not "actively balancing" - the OneWheel self-balances "against" their lean. Until the motor gives out, that is.
846.
▲
by
radlad
3y ago
> Unfortunately my own experience with Linux audio processing has been nothing other than encountering one bug after the other one. You kind of buried the lede there...
847.
▲
by
radlad
3y ago
Why do you think that? I literally just wrote an app to do this. From my notes: > Android 13 still requires `ACCESS_FINE_LOCATION` to call `startScan()` and `getScanResults()` - `NEARBY_WIFI_DEVICES` is not sufficient See here: https:&#
848.
▲
by
radlad
3y ago
There are 8,736 hours in a year.
849.
▲
by
radlad
3y ago
However, scanning and connecting to Wi-Fi IoT devices still requires it.
850.
▲
by
radlad
3y ago
> I mean, sure. But again: that's just my point restated. What is this doing that a standard search engine does not? And again, it is quicker than clicking multiple links and can generalize / contextualize what it finds, mappin
851.
▲
by
radlad
3y ago
> I am dreadfully curious what use cases you're envisioning where a fast, bad/wrong answer is better for anything than a correct, slower answer. >> For some people - I am reluctant to say "for some use cases" -
852.
▲
by
radlad
3y ago
Because having the AI do it for you is faster than doing it yourself. Not as accurate, but faster. For some people - I am reluctant to say "for some use cases" - that's very appealing.
853.
▲
by
radlad
3y ago
Webkit is a fork of KHTML (part of Konqueror from KDE) created by Apple.
854.
▲
by
radlad
3y ago
I don't think that's really fair - the recommended way to run Home Assistant is to run HA OS (on a VM or dedicated machine, like a Raspberry Pi), or to run it in a Docker container. The "Supervised" installation (i.e. in
855.
▲
Bringing back the Incus (LXD fork) demo server
(stgraber.org)
1 points
by
radlad
3y ago
|
0 comments
856.
▲
by
radlad
3y ago
Yes, and Red Hat has metrics and explanations showing why Go is not exactly ideal here. And yet I am surprised they chose C as a replacement... hence my question above!
857.
▲
by
radlad
3y ago
On this note, I was really surprised to find Red Hat's OCI runtime is written in C: https://github.com/containers/crun Is anyone working on a Rust version?
858.
▲
by
radlad
3y ago
I think the argument is that file permissions may not be applied as rigorously, with the assumption that SIP is in effect.
859.
▲
by
radlad
3y ago
Unsolicited dick picks is not the same thing as CSAM...
860.
▲
by
radlad
3y ago
Sure... but it's still not "the same as" running on your host.
861.
▲
by
radlad
3y ago
> it's the same as "curl | bash" While I understand the argument you're making, the exposure of running "curl | bash" on your local machine is much higher than running arbitrary code inside of a container. E
862.
▲
by
radlad
3y ago
I did say "mostly." :) I almost mentioned this bug, but it's so famous, I doubt any mainstream OIDC libraries fall prey to it these days.
863.
▲
by
radlad
3y ago
100% - XML vulnerabilities are the biggest issue. JWTs have also had their fair share, though I think they were mostly implementation bugs that have mostly been ironed out at this point. XML's complexity is inherent to the language.
864.
▲
by
radlad
3y ago
Works great for me?
865.
▲
by
radlad
3y ago
Honestly, as someone who has implemented both SAML and OAuth2 (+ OIDC) providers, I found SAML much easier to understand. Yes, there are dangerous exploits around XML. Yes, the spec is HUGE. But practically speaking, people only implement a
866.
▲
by
radlad
3y ago
FYI, your account might be shadow banned. I vouched for this comment, but most of yours are dead.
867.
▲
by
radlad
3y ago
Boston 3?
868.
▲
A DIY near-IR spectrometer
(caoyuan.scripts.mit.edu)
365 points
by
radlad
3y ago
|
73 comments
869.
▲
by
radlad
3y ago
Most users do not want a running program to corrupt / crash on them - even if they deleted the backing exe.
870.
▲
by
radlad
3y ago
Mine is also a 2017 and can barely charge my phone. :(
More ›