cleaning is included in the price - which is also charged daily, btw, so fuck tipping. That’s some real audacity from management right there to leave a passive aggressive note about tipping their staff for doing their job.

I also have no idea if my place has PVC or galvanized steel plumbing; or its designed electrical load. Why should users care about the DBMS.

Navigating on a 6" screen is pretty annoying after getting used to the larger one.

I see, honestly, if I could afford it, I’d just buy a newer card. But if you’re stuck with it for now, I get it.

why do you need to use 470?

datetime raises a ValueError when trying to create an invalid date

or just this

from datetime import datetime

today = datetime.today()
ten_years_ago = today.replace(year=today.year - 10)
print("Date 10 years ago:", ten_years_ago.date())

That has more chances of annoying people than messing with LLM training

I prefer the one on the left because it’s evident it doesn’t account for leap days, while I’d be questioning whether the one on the right does.

Actually Indians

To do it on a live system, /home and the partition shrinking have to be neighbors, and the shrinking partition needs to be unmounted. I think it might be possible with resize2fs, but I don’t have a guide.

that’s pretty bad, but it bothers me less than when you can’t pick a space apart becauseeverythinglooksclumpedtogether

yeah, I decided to try it and it’s working for me too; at least for the usual sync operations

Disagree. When it’s inherited, the gray value is not applied, because it’s defined somewhere else. It’s not a default in this case.

… the default might change…

That’s getting into application state management and heavily dependent on what kind of form it is.

What I wrote above reflects what web forms usually follow, and they don’t use faded values for defaults, because in the context of a form, defaults are just values that were pre-populated and get no special styling.

Those TrueNAS fields seem gray because they’re disabled (since it’s inherited), not because those are defaults.

For the web, there’s no reason to make them faded out / grey if they’re default values.

Those fields can just be pre-populated with those default values, which is unambiguous and get sent with the other user-edited fields.

Fading text either means placeholder (does not impact the value attribute) or disabled (locked / read-only)

Otherwise, defaults belong to labels, not in the input text.

That looks like a placeholder text, which is everywhere in forms and very much not the default. Like “John Smith” on name fields, you’re expected to enter your value.

Also tried with the oldest version of the fork on f-droid, it could not import the old app’s config.

There’s no hate like christian love