Pup Biru

hard disagree on what belongs in the same commit history… a single merge should be an entire feature, and your commit history should read like a change log

Squashed commits are not atomic … overall task requires modifying multiple different systems

that’s why monorepos exist

i’d say squashed commits aren’t always atomic, but this is one of the biggest reasons people add the complexity of a monorepo: if changes cross multiple systems, ideally their merge/revert should be an atomic operation

you either have deployment complexity (ensuring the feature is in all deployed systems before switching over), code complexity (dealing with the feature only maybe exiting in parts of the system), or repo complexity (where tools manage a monorepo and thus commits and PR/MRs are atomic across your system)

either… some apps have just started to do single factor login with just email, profile options can be optional, if there are required fields or terms of service to agree to then that can come after email validation

i think these days the best practice for mobile apps re retention (other than sso or passkey) is to just ask for an email, then from the validate link continue with register

reason being that more steps to register means more ways people are likely to drop out of the flow, and this is basically about as short as it can be

when the user has validated their email, then they’re more invested so they are more likely to complete

that also fits nicely with what we’re talking about with good security

“not actively harmful” and “notionally the bare minimum” are pretty low bars and i’m glad that, for once in modern memory, mozilla cleared them

codeberg seems to be the new hotness

you install a distro because of all the software it includes and how they interact out of the box

you’re completely right that systemd is a background service that most people don’t care about, but it does make the whole system more reliable, and much easier to administer for servers or workstations (enterprise management; not personal)

you certainly do want an init system… even sysv-init is an init system: you need something that runs as pid 1 that triggers other services. systemd starts services, and also ensures they’re in the correct security contexts, running as the correct users, makes sure they’re healthy, tracks dependencies (not just order; this speeds things up because it can be parallel, ensures failures don’t cascade, and means there’s far less jank in random bash scripts)

this isn’t a big political statement: this is an acknowledgment that linux users - not all, but some - will want/require something like this… and systemd user database is the place where that information is stored on modern linux systems

waiting for california would be us-centrism… california isn’t the only place in the world that exists; it was just the trigger

forget cookies, reload, begin; forget cookies, reload, begin

… auto clicker

they’ve said “we speak for the widest used extended user service in linux”… because… that’s what they are

to say they “speak for the distros” is ridiculous: in that case, every time they merge a feature they “speak for the distros”… they speak for their own software, which is implemented by distros precisely because they implement things like this

because theyre being pragmatic… laws are starting to be introduced around the globe for parental controls - whatever that means in each jurisdiction. given that, there needs to be options available to people wanting to, or required to comply with said laws… the best place to do that is in a user record, as an optional field… extensible user records, in modern linux, are stored in systemd

it needs it in a similar manner to how it needs location, email, real name, etc: it doesn’t functionally need it, but it’s a place to store the metadata associated with a user such that other applications can use it

because whilst systemd-initd is the part that everyone is generally aware of, that’s linked to systemd-logind so that processes can be started as different users… process init, session management, and user management are intertwined

they don’t have to be for sure - sysv init proves that - but in modern linux, they are and that comes with a load of benefits

https://deepwiki.com/systemd/systemd/6-user-and-session-management

https://systemd.io/USER_RECORD/

good thing it’s entirely optional then!

or just don’t set it

tell me you have only a passing understanding of how modern linux is architected without telling me you have only a passing understanding of how modern linux is architected

idk about the US but in australia most ceiling fans plug into standard outlets in the roof, so a smart plug is usually all you need

i have a humidity sensor in the bathroom that turns the ceiling fan on, and the way that works is that it compares the bathroom humidity to humidity in other areas of the house, so it takes into account humid/dry days automatically

At this point, I’m surprised there isn’t an app gamifying posting about “bathroom breaks”.

i mean, i feel like this garbage comes close

https://www.gadgetreview.com/your-toilet-just-got-smarter-kohlers-599-dekoda-analyzes-what-you-flush

with such lines as

AI-powered health monitoring, transforming your most private moments into diagnostic opportunities.

who could possibly say no to an AI camera in your toilet?

PWAs do have severe limitations though… i wish it wasn’t; i love PWAs but they’ve been massively hamstrung by the big players. sadly, they’re not really comparable other than for basic apps IMO

i think the control group should actually be telegraph because PSTN hasn’t existed for the entire history of electronic communication so it’s not really an apples to apples baseline