HN user

pinum

723 karma
Posts0
Comments132
View on HN
No posts found.

Thanks, I was familiar with encryption but not with bitlocker.

So this only affects a particular mode of bitlocker in which the drive is automatically decrypted on boot without the user providing any secret. Meaning the key is basically stored in plaintext on-device, albeit in a convoluted way.

To me it seems intuitive that such a mode isn't secure. It's a bit like protecting your door with an unpickable unbreakable lock, but then putting the key in a lockbox on the wall with a flimsy padlock that can be raked or cut off in seconds.

It seems roughly equivalent to not encrypting the drive at all so it doesn't seem surprising that there's a way to bypass it.

If I was releasing a laptop with Linux support as a key selling point, and the battery life was bad on Ubuntu 24.04 but good on the pre-release 26.04, then I'd advertise the good figures and write "tested on Ubuntu 26.04 beta, requires Linux 7.0 or later" in the footnotes.

I definitely /wouldn't/ rely on just Windows figures for a machine that's otherwise advertised as "Linux first". If the battery life was the same on both, I'd prominently mention that.

I can second this 0.9mm transparent stuff, I've run it successfully and it's very subtle.

Depending on the media converter pair you're using, you probably want UPC instead of APC. I also found that the cheapest generic bidi media converters tend to be SC, so I want with a 30m pre-terminated SC/UPC cable. Total cost (cable plus media converters) was about £30.

Alternatively, you can order a custom 30+m white 0.9mm cable from FS: https://www.fs.com/uk/products/12285.html Lead time is fairly long.

Anecdotally, everything works flawlessly on my work machine: Optiplex Micro, Intel iGPU, Fedora KDE 43, 4K 32" primary monitor at 125% scale, 1440p 27" secondary monitor at 100%. No issues with Wayland or with anything else.

Everything actually feels significantly more solid/stable/reliable than modern Windows does. I can install updates at my own pace and without worrying that they'll add an advert for Candy Crush to my start menu.

I also run Bazzite-deck on an old AMD APU minipc as a light gaming HTPC. Again, it's a much better experience than my past attempts to run Windows on an HTPC.

As with everything, the people having issues will naturally be heard louder than the people who just use it daily without issues.

Instead of shutting down completely, why not this:

For goo.gl links that were created by google, continue redirecting them as normal. For others, show a warning page explaining to the user that the link wasn't created (or vouched for) by google. If they press an "agree" button, still don't show a clickable link, but instead show it as plain text to be copied.

This looks like it could be very valuable for quite a lot of people- thank you for making it!

Just a couple first impressions from your site... loading it on a phone, the first thing I see is this: https://imgur.com/4maP1vV

(1) The entire contents of the site is completely covered by a cookie warning. This is honestly quite annoying even for an SWE like me, never mind your target audience.

I know at least one older person who doesn't understand these cookie modals at all and refuses to touch them. They either continue using the site in the background without accepting/rejecting(!), or if that's not possible they just leave the site.

I'd suggest you carefully check whether you actually need this modal at all. If the only cookies you use are technically necessary, then (based on my layman understanding of the law) you don't need to show it. If you absolutely must use tracking cookies, then maybe consider a more subtle approach that allows the user to continue reading the page without deciding.

(2) "Join Now" makes it sound like I'm signing up to a subscription, rather than making a one-off payment.

Thank you! Just used this to clear away a load of tabs.

Some gripes:

I wish I could just use it standalone without it replacing the "new tab" page.

I wish I could view the full title of a tab, maybe on hover.

I only want to use it to manage tabs, not history or bookmarks, so I wish I didn't have to grant those permissions.

Your GPU is 6 years, 7 months old. As an analogy, consider someone in 2007 objecting that their 2001 GeForce3 Ti500 can't run Crysis/Mass Effect/etc. The PS4 generation really messed with the usual conventions and expectations of PC upgrade cycles.

(I appreciate that GPU prices have creeped up and up over time, though.)

It appears that, during our transition to the digital age, the internet completely disappeared. We scoured the globe for it, but it seems to have been completely erased from existence. This has caused immense disruptions to our business, leading to the unfortunate layoffs that are necessary for continued success.

Those results look excellent. I'm trying to gauge whether something like this could potentially work in realtime, i.e. in games. I know it inevitably depends on hardware, resolution, settings, etc but do you have a ballpark figure for how long it takes to apply this to a frame? (And does it have a temporal aspect which requires access to frame N+k to render frame N?)

Pressing "See it in action" shows an empty black overlay.

Opening that link in a new tab works, but the demo/story isn't as helpful as it could be. For example it talks about screen recordings, so I was expecting to be able to play one back. If a live demo isn't practical, I think I'd prefer a short video showing typical usage.

in the US people very often use DS very differently from how the title is used in the UK

I haven't heard about this before and now I'm curious- can you elaborate on the differences?

The MODELVIEW_MATRIX is assembled in the vertex shader by combining the object’s MODEL_MATRIX and the camera’s VIEW_MATRIX

I was taught that MV/MVP should be calculated CPU-side per-model, and that doing it in the vertex shader is wasteful. Is that advice out of date?

I looked into building something like this for a React Native app. (Actually I first considered the practicality of making a reactive version of sqlite... I decided it would be too complex and not something I'd want to use without upstream support).

We ended up doing something a bit more traditional/basic/manual, but this looks nice. It would definitely have been in consideration if it'd been available at the time, and I'll keep it in mind for future projects.