Groxx

38 ms·

691.
by Groxx 11mo ago
no, they're saying the emissions needed to create that smaller, more efficient car may vastly exceed their car's emissions during its entire lifetime under their use. so it may be a net loss.
692.
by Groxx 11mo ago
I would agree if they weren't so clearly deserved. Calling shit out as being shit is fine.
693.
by Groxx 11mo ago
so to paraphrase: > GO: windows has become terrible for developers and this AI focus makes it worse > PD: we listen to feedback, people want reliability etc. we care deeply about developers. we know we have to improve on [things which
694.
by Groxx 11mo ago
I'm not entirely sure what you're claiming here, but broadly speaking no, this is not correct. RCS is, by spec and in practice, intended to fall back to sms/mms if it doesn't work for some reason (e.g. you're roamin
695.
by Groxx 11mo ago
I've had constant problems with the verification ever since it was introduced. As far as I can tell it hasn't improved at all. Sometimes it works, sometimes it repeatedly kicks me out moments after succeeding, and it's st
696.
by Groxx 11mo ago
As a follow-up, since I can't edit any more: https://news.ycombinator.com/item?id=45980788 ^ They are correct, the MLS / E2EE part of RCS is quite new and not yet implemented ~anywhere. So it gets no points until
697.
by Groxx 11mo ago
I was curious about the adoption timeline actually, yeah - hadn't looked at that in detail yet. Thanks! How wonderful that they've been claiming better security all along too. (it may be true, sms is terrible - but they know man
698.
by Groxx 11mo ago
By spec E2EE (via MLS, or something extremely similar) is in fact the default - it's part of the Universal Profile, at least as of 3.0 which I have been reading. Is Google following that with Google Messages? We have no way to verif
699.
by Groxx 11mo ago
thermal sand batteries might be interesting to you, if you haven't seen them before
700.
by Groxx 11mo ago
The problem with all these problems is that it makes RCS noticeably worse in both normal use and for your privacy than a regular web chat via some other system. And I do not see a path for it that escapes that. I'm very happy that t
701.
by Groxx 11mo ago
Yeah... I just started getting back into building sms/mms/rcs apps on Android and oh boy. It's much more of a mess than I expected, and much more "oh so it's basically just Google now, and they seem to be trying to
702.
by Groxx 11mo ago
I'm mostly happy with mine as a replacement. But it is absolutely nowhere near as polished a user experience as Pebble was. I have had constant disconnects for months at a time with Gadgetbridge, loads of edge-case bug-like behavior
703.
by Groxx 11mo ago
I try not to judge other cultures, but that seems like a strange name for a moon.
704.
by Groxx 11mo ago
entirely agreed, but in the context of this thread that means you just have to convince someone to enable it for the one app, rather than the phone as a whole. which doesn't seem to help at all with the coercion scenario (if anything
705.
by Groxx 11mo ago
I really think all permissions systems need what we had back in xposed/appops days: Permissions should ~always be "accept (with optional filters)", "deny", and "lie". If the game wants contacts access and
706.
by Groxx 11mo ago
browsers are really not much better. on an absolute level, I definitely agree they're better (e.g. they have per-url and only-after-click permissions for some things), but they've all got huge gaps still once you start touchi
707.
by Groxx 11mo ago
might have meant to reply to someone else? I haven't said anything about verification here
708.
by Groxx 11mo ago
yes, they're admitting that their APIs are powerful enough to build accessibility tools (which often must read notifications) and many other useful things (e.g. Pushbullet) that are not possible on iOS. powerful stuff has room for ab
709.
by Groxx 11mo ago
re OTPs, there's a special permission-less way to request sms codes, with a special hash in the content so it's clearly an opt-in by both app and sender: https://developers.google.com/identity/sms-retriever&#x
710.
by Groxx 1y ago
Strictly for BeeKeeb: I got my Corne kit from beekeeb several years ago and I'd happily buy from them again. I was a total custom-keyboard-and-soldering newbie and they helped me figure out what I needed, what I was missing, and even
711.
by Groxx 1y ago
Yea, I've got a Corne and a Kinesis Advantage2 and I mostly use the Advantage2. If it was available earlier (and a bit cheaper) I'd have almost certainly bought the 360 and I'd probably be happier with it - I think I need a b
712.
by Groxx 1y ago
This kind of thing is the only way I know of: https://hackaday.com/2022/12/26/standalone-touch-id-for-your...
713.
by Groxx 1y ago
a particularly egregious one, wow
714.
by Groxx 1y ago
Learning that RCS is even more of a monstrosity and a lie than I thought a few years ago. Yikes. Lots of groundwork a decade ago setting the stage for "the carrier creates a common service anyone can interact with" (like sms&#x2
715.
by Groxx 1y ago
some of this is simply that it is a counter-culture, because it's in the minority (by a significant margin). that doesn't mean it's defined by that decision, or even that it made that decision in the first place - the major
716.
by Groxx 1y ago
yeah, if it's only 20-30 lines then it's likely overkill to do any way except by hand. most of the stuff I've done has involved at least 20-30 libraries , many of which have other dependencies and config, so it's on the
717.
by Groxx 1y ago
AFAICT that uses go/types, loaded uniquely per execution via packages.Load¹, which is by far the primary reason why e.g. go.uber.org/mock (previously github.com/golang/mock) can become extremely slow. mockery v3 does n
718.
by Groxx 1y ago
I 100% agree with what you've written, but if you haven't checked it out, I'll highly suggest trying mockery v3 for mocks: https://vektra.github.io/mockery It's generally faster than a build (no linking
719.
by Groxx 1y ago
tbh this sounds pretty similar to go.uber.org/fx (or dig). or really almost any dependency injection framework, though e.g. wire is compile-time validated rather than run-time (and thus much harder for some kinds of runtime flexibilit
720.
by Groxx 1y ago
if they're finally changing, I'm thrilled - maybe I'll have one in a decade :) thermocouples are so dirt cheap that it's ridiculous it was ever a thing.

More ›