journalctl --follow --unit rpm-ostreed.service

[Daemon]
#AutomaticUpdatePolicy=none

Initiated txn AutomaticUpdateTrigger for client(id:cli dbus:1.1625 unit:app-org.kde.discover@df0f43f8979843c0a34d36ad199c7eda.service uid:1000): /org/projectatomic/rpmostree1/fedora

So I found the setting that configures automatic updates in general… in the three dot menu (questionable UX decision?):

which actually just leads to the system settings:

I had this configured to be weekly, there isn’t even a setting as granular as seconds, the smallest span of time is daily, but what I’m guessing is that the “Update frequency” acts on when they should be installed automatically rather than when they should be fetched, so this is a limitation of the system as I understand it

That is insanely cool, but isn’t it even more manual? ( °ヮ° ᵕ)

You were far ahead of professors that make you write it out with pen and paper

Bro thought SIGTERM was enough

Oh I see, with the help of another thread I understood what that is

Locally integrated menu = menu in title bar

I guess the improvement that it provides is space saving right?

What’s LIM?

If I can’t be a milk cow, then at least let me be a cash cow

I want my ifunny logo

wayback machine and bookmark, name a more iconic duo…

But it sounds cooler when they don’t know what it’s about, right? Right??

Could be, it looks pretty unknown for now though

They’re too busy compiling the 15678th generation of their systems

There truly is something for everyone! :D

That does make sense! I like the point about older systems, I didn’t even stop to think about how much storge space has exploded in such a short amount of time and how it started from incredibly small capacities at very high prices that could have been hard to justify for any company that realistically just needed to keep some records

That’s really interesting!

The good news is it sounds like this issue is being taken into account.

Is there a part in that page that says so? I wasn’t able to find it

I wouldn’t be surprised if they added a YEAR2 though. T-SQL has a datetime2, after all.

Ok I wasn’t expecting that, it sounds like a meme, but it’s actually real lol

Yes 2 bytes is absolutely fine for me in fact (waiting for this comment to age like milk in my cryo pod), but then if YEAR will just stay the same forever, will it become a relic of the past? If so, why YEAR in the first place, who would actually make use of it?

Am too surprised that it is an evolving standard, so I was curious to read a little, then…

Purchase for non-member: $676.00

What???

You can keep all the lines of those who didn’t accept to the change with the original license, it will end up as a bad mix, but it’s doable if the licenses are compatible

nahh, you’re lying, and you know that

good point

…time to remake it in SVG!