rezonant

21 ms·

271.
by rezonant 2y ago
Thankful for not pushing Edge if you decide you want this feature. This feature is something the community has been independently creating for years. Personally I don't think people should actually allow this type of feature. It's
272.
by rezonant 2y ago
I didn't say we should be grateful about that. I'm saying that thankfully they are not using the threat of your guarded personal data being exposed because you want this feature but don't want to use Edge.
273.
by rezonant 2y ago
Actually Timeline was a semantic store from what I understand-- it didn't store screenshots of what you were doing, instead apps that used the Microsoft Graph API could contribute information about what you were doing to be included in
274.
by rezonant 2y ago
Thankfully it looks like they've already added support for Chrome, Firefox and a bunch of other browsers: https://support.microsoft.com/en-us/windows/retrace-your-ste...
275.
by rezonant 2y ago
Well bitlocker (ie device encryption) is only protecting you from offline attacks, ie when someone pulls your hard drive to examine it. Code running on the machine itself wouldn't be affected by it.
276.
by rezonant 2y ago
Your post here is repetitive, we get your point.
277.
by rezonant 2y ago
The folder view thing genuinely seemed useful, because you could lay out several folders onto your desktop. Alas, when I stopped using desktop Linux (because I realized I valued my time), the feature constantly broke and reset the positions
278.
by rezonant 2y ago
Also there is no standard for exposing the schema, and sometimes there isn't a schema at all . Sometimes a vendor will have the schema downloadable from their dev docs, sometimes it will be an endpoint that serves it up, and sometimes
279.
by rezonant 2y ago
This has been my experience when integrating with a vendor's APIs where they've been bit by the GraphQL bug. They have a full featured, stable and easy to use REST API, and then a poorly implemented GraphQL solution that doesn&#x2
280.
by rezonant 2y ago
I have never bought the GraphQL hype, but have never explained my rationale as well as this article does. Kudos Matt on succinctly nailing the issues here. As for how to tackle things today, I alternate between REST+OpenAPI and RPC models f
281.
by rezonant 2y ago
> you don't want footguns in the codebase where you could change something in one place, but forget to change the same thing in other places This. Ironically the example on TFA is vulnerable to this issue. Each of the deadline setti
282.
by rezonant 2y ago
If it's about repurposing phones, then just root the phone. On Android, that's generally not restricted. The benefit of not rooting is that device attestation (used in banking apps and other sensitive things) still works. If you d
283.
by rezonant 2y ago
If you just changed "but" to "and" you'd get your point across with less a sense of whataboutism. Yes, all platforms should be free. Personally it feels like devices that are marketed as general purpose have a highe
284.
by rezonant 2y ago
If the revocation use case is soft, then totally fair. But if the application is potentially dangerous and the user says "Sign out all devices", I think that should be a deterministically successful operation. Similarly, if there
285.
by rezonant 2y ago
I'm pro JWT, but reducing load on the DB itself isn't a massive argument in favor of JWTs, because an opaque token solution can simply cache the result of a revocation check at whatever time interval is comfortable for the use cas
286.
by rezonant 2y ago
What's interesting about this argument is that nothing is stopping you from doing this same thing using JWTs. Just generate your token and store it as a claim in the JWT. You can check the revocation of the stored token without even va
287.
by rezonant 2y ago
Since JWTs can't handle revocation on their own, the main benefit (other than the ability to do validation without a central authority) of JWTs over opaque tokens is the ability to embed data that an untrusted holder (ie client) can ma
288.
by rezonant 2y ago
I'm not sure cache was the right word in the parent post-- you don't want to use a cache (at least one with LRU/bounded size) to store revocation without a backing store, or else the revocation could get pushed out of the cac
289.
by rezonant 2y ago
One thing missing that I use all the time , "git cherry". Without arguments it will show you what commits in your local branch are not in your remote tracking branch. Use "git cherry <ref>" to list the commits in
290.
by rezonant 2y ago
My problem with this is that clearly a big portion of AI Overview's issue is bad training. That is a problem with a straightforward solution. A lot of the publicized cases of bad information actually do have a source on the web, indica
291.
by rezonant 2y ago
I think you glossed over the importance of the term process failure . The idea is that this one particular form missing the appropriate care is indicative of a wider lack of discipline amongst the engineers building it. Definitionally, you
292.
by rezonant 2y ago
It could be that, but it also could be a cascade of non-LLM checks and retries to GPT with additional prompting.
293.
by rezonant 2y ago
I'm far from being versed enough here, but from an adversarial standpoint, is having the client offer up the trust stores and certificate IDs it has going to increase the server's knowledge of aspects of the client we don't w
294.
by rezonant 2y ago
There's no reality where a competent customer isn't going to ensure Google pays for this. I'd be surprised if they have a bill at all this year.
295.
by rezonant 2y ago
> and also confirmed soft delete behavior. Where exactly do they mention they have confirmed soft delete behavior systemically? All they said was they have ensured that this specific automatic deletion scenario can no longer happen, and
296.
by rezonant 2y ago
One assumes they are getting a massive credit to their GCP bill, if not an outright remediation payment from Google.
297.
by rezonant 2y ago
I suppose if mitigation fell over the weekend it might still make sense.
298.
by rezonant 2y ago
Hard agree. They clearly were more interested in making clear that there's not a systemic problem in how GCP's operators manage the platform, which read strongly and alarmingly that there is a systemic problem in how GCP's op
299.
by rezonant 2y ago
Things to avoid: Whatever programming language you are currently using. This sort of "language/tool/framework is a dumpster fire" post is not helpful or curious. Every tool has its flaws and places where it excels. Pai
300.
by rezonant 2y ago
By the way, this is perhaps my biggest problem with Ruby. It is far too easy to have a lot of private methods and to lose sight of the fact that you're in the private section.

More ›