Recent submissions

Comment · 2 months ago
> This investigation is a useful reminder: running boring technology in a non-standard way is a risk. The common paths and standard configurations are incredibly well-tested and reliable. Most people use SQLite in a standard configuration and never face this sort of issue. Everything we were doing was a public, documented, supported configuration—but by taking manual control of the checkpointing process and running at our own aggressive pace, we stepped off the well-trodden operational path.

I feel like they missed a key takeaway from their own argument here, they should not be running a non-standard configuration :)

Comment · 3 months ago
Comment · 3 months ago
I would be interested in a severity score or something similar -- otherwise I can't judge how important it is to fix -- is this a "friday right now" problem or a monday is fine problem ;)
Comment · 7 months ago
from a company (RHEL users) POV: EntraID support -- we're using https://learn.microsoft.com/en-us/entra/identity/devices/how... for SSH at the moment (not really happy with it but I don't have a better alternate) -- and that does not work for cockpit. So another way to authenticate against entra would be nice for corporate users
Comment · 1 year ago
maybe I missed that, but why not just combine ptp and ntp within chrony, it does support that.
Comment · 1 year ago
I would guess nextcloud
Comment · 1 year ago
I think a very short lived cert (like 7 days) could be a problem on renewal errors/failures that don't self correct but need manual intervention.

What will let's encrypt be like with 7day certs? Will it renew them every day(6 day reaction time), or every 3 days (4 days reaction time). Not every org is suited with 24/7 staffing, some people go on holidays, some public holidays extend to long weekends etc :). I would argue that it would be a good idea to give people a full week to react to renewal problems. That seems impossible for short lived certs.

Comment · 1 year ago
I'd say the primary problem of framework is security updates for bios etc
Comment · 1 year ago
yeah, that was my suspicion as well, seems that AI generated content is mixed with seo-spam or malware. I even tried to report feedback.azure.com as a deceptive site to the major browsers, but they don't share my concerns ;)
Comment · 1 year ago
Comment · 1 year ago
any of those switches in the right price range for home? I've been looking for a cheap SONiC switch for a long time but those on the supported hardware list are all rack/datacenter sized I would say -- and none do PoE which I really need for home usage (cameras, wifi APs)
Comment · 1 year ago
I have a Framework 13 (12th Gen). I have no complaints about the hardware quality. I love the replace everything concept. I rarely do that though, my ports are always the same - 2x usb-c, 1x usb-a, nic (bulky I remove that one for traveling and replace it with another usb-c).

Having said all that, I would not buy another one right now. The software side of things is just not up to what I expect. They still have not figured out lvfs for this notebook; the last bios update I could install was a manual EFI installer (which is beta at this point it in time I guess, only really "production" ready update is windows based installer). Also the bios I have is now a year old, and there only has been one non-beta bios upgrade in the whole lifetime of this model (~2.5 years). So the software side of things is just miserable... At this point in time I guess the next machine will be something with coreboot+lvfs and regular, timely updates (still taking suggestions ...). I guess I would be willing to give a framework+coreboot situation another try in a couple of years. The main reason for buying this is reusablilty once I decide to move on to the next hardware generation.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton