HN user

Kuraj

645 karma
Posts2
Comments286
View on HN

I think most people would interpret “scanning your computer” as breaking out of the confines the browser and gathering information from the computer itself. If this was happening, the magnitude of the scandal would be hard to overstate.

But at the end of the day, the browser is likely where your most sensitive data is.

I've come to realize that barely anyone I know uses swipe typing anymore, and that this is why using it laying flat is viable in the first place

KDE is SO GOOD.

I've distro hopped and DE hopped a lot before settling, but it's been amazing for me as somoeone who has switched over from Windows. It just doesn't get in the way, is super familiar for me, AND lets me do a lot of things I wish I had in Windows.

I was worried about the "choice fatigue" due to it being super configurable and all, but honestly the defaults are so sensible I haven't really had a reason to tinker with it much if at all.

I locked myself out of Azure after losing 2FA which turned out to be different 2FA than the one tied to my Microsoft Account.

All support channels are now AI and refuse to help and redirect me to self service. There is _no_ self service path for Azure account recovery if you lose your 2FA token.

It's infuriating. I lost access to a bunch of hobby projects I had hosted on DevOps. Microsoft will never see a dime from me.

All your monitors are combined into a large canvas where every pixel can be written and read by any X11 client.

Heh. I learned this hard way when trying to set up multiple monitors with different refresh rates

I don't know how to get my point across, I guess I'm just thinking emotionally more than logically right now lol. Either way it's not my comments being visible verbatim that irks me but rather the processing part. But I get your point and the "damage" is already done, so /shrug

I dunno man. When I first joined it was unconcieveable that someone could just take everything and build a trivially queryable _conversational_ (that's a big part of it) model around everything I've posted _just like that_. Call me naiive but I would consider it some sort of a social contract that you would not do that. I feel the same way about LLMs being trained on Reddit. I suspect with a large enough dataset these models can infer things about you that you wouldn't know about yourself.

To make another example, even though my reddit history is public (or was until recently because I didn't have a choice) I would still feel uneasy if I realized someone deliberately snooped through all of it. And I would be SUUUUPER uncomfortable if someone did that with my Discord history.

It's not against the rules or anything, I just think it's rude.

Polish person here, I can confirm that x-rated stuff on teletext was very much a thing. I have no reason to believe the ad is fake

The original comment was about whether these things should be treated as errors during the local development process, or during CI for greenfield projects.

I deleted it after realizing that the article actually does address this. But I'm still relieved that I'm not the only one with the dillema.

which if you miss, just means you may end up with a failed CI build to fix…

Honestly as a developer if I miss this up until CI, that's on me. The important part is that these issues are still visible during the local development, even if as warnings, and that the developer knows (maybe after making that mistake once or twice :-)) that they can't just be ignored because they will fail down the road.

We don't really have this problem in .NET 8, we mock stuff just fine using an in-memory database provider.

But I admit my tone missed the mark. It may have been much harder to do in the past, or maybe I'm missing some nuance.

But also at this point why not just have your DbContext directly implement an interface that you can mock? Surely that must be more straightforward than adding an entire abstraction layer, that you have to extend with each new usage scenario, and without sacrificing implicit transactionality.