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)

they’ll mug ya for a ciggie all right!

okay but like there are actual ways of doing gendered spaces in australia… or at least victoria

here in melbourne we have the laird - a gay bar that is a male only space. and australia-wide we have female only gyms. they have an exemptions to the equal opportunity act and are allowed to deny entry based on gender. you have to apply to the state for them

ignoring what you actually think about those examples specially, imo they’d have a pretty good case to get exemptions should they apply for them since it’s art… it’s more a case (imo) of not doing their paperwork and getting the correct permissions… boring? sure… necessary? definitely

though with those exemptions you must strictly adhere to your own gender requirements otherwise you’ll lose it

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

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?

libs never even had to develop policies let alone have economically feasible policies. what makes you think ONP will need to do any different?

imo speaking with an american accent wouldn’t even particularly call you out… i know a bunch of people that speak english as a second language that speak with at least somewhat of an american accent

i know sometimes it does… it can even make your meter turn in reverse!

it’s pretty common for rooftop solar to supply the grid if you’re not using all their capacity

the same way it works when they connect a new generator to the grid, or solar panels on your roof

there’s nothing directional about a power point: it’s just copper wire