| Age | Commit message (Collapse) | Author |
|
Move the Windows Update stuff somewhere else; it's (a) a big
tangent (b) a shaggydog story.
|
|
The latter makes a couple of cross-references to the former.
Considered using Org "internal links" and writing some glue to turn
them into "text fragment" links¹, but… some other day.
¹ https://developer.mozilla.org/en-US/docs/Web/URI/Reference/Fragment/Text_fragments
|
|
* brew coffee
* jot down results of the previous day
* sip coffee
* google something on a hunch
* shake head in disbelief
|
|
|
|
|
|
|
|
|
|
It's clear he holds a dim view of Packman; it's also clear that this
view is informed by his own packaging experience, the standards he has
for the craft, and Packman allegedly failing to meet that standard.
> Official openSUSE repos have LAYERS upon Layers of checks and balances
>
> A submitter SHOULD have their changes reviewed by someone else in
> their devel project
>
> A submitter WILL have EVERY change reviewed by the openSUSE release
> team
>
> A submitter WILL ALSO have EVERY change reviewed by the openSUSE
> review team
>
> A submitter WILL ALSO have EVERY change checked by an army of bots and
> possibly also openQA
>
> A submitter touching security sensitive stuff (eg Polkit, default
> services, etc) WILL ALSO have that change viewed by our separate
> security team
>
> That’s 2 to 4 extra pairs of eyes on EVERY submission to openSUSE plus
> all the automated checks
>
> Packman does NONE of that
— 2025-02-24 <https://old.reddit.com/r/openSUSE/comments/1ix1f4z/is_using_tumbleweed_without_packman_a_viable/mejtoto/>
So cut the dude some slack. I don't see myself using Flatpaks over
Packman; OT1H the release model makes sense to me, as someone who
likes the latest-and-greatest straight from upstream, OTOH
- latest-and-greatest is why I use a rolling release, Flatpak brings
nothing new there;
- having to pick-and-choose apps which need codec-smuggling is a
bother;
- containerized apps break in subtle ways precisely because of the
security benefits containers bring: too many holes to punch in order
to integrate smoothly with the rest of the desktop.
So just nod and move on.
|
|
|
|
> # The Crossroads Renewal Project
> · The moon now shows different phases in the Training Grounds vista scene
I may never succeed in fixing my framerate woes, but you know what?
Reading this still makes me happy 🥲
|
|
Do I smell link rot?
|
|
The jank. THE JANK.
(Note sure the whitespace-mode itch is still relevant; thanks for no
repro recipe Past Me)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Current regret level: mild.
|
|
Mostly as a pretext to stick a footnote. There shall be margin notes
in this saga, so says I.
|
|
|
|
Mainly so Org stops re-indenting that quote block whenever I edit a
neighboring paragraph. Also partly because I wanted to understand how
I went from GitHub to Reddit on that one, tho no clue on that count.
|
|
> If I only could
> locate this bug
|
|
|
|
|
|
|
|
|
|
https://lobste.rs/s/gvo8fy/thoughts_on_having_ssh_allow_password
I feel seen 🙈
|
|
|
|
|
|
|
|
|
|
Into bona-fide hardware notes, and notes specific to desktop
maintenance that bear increasingly little relation to "hard"ware.
|
|
|
|
|
|
|
|
|
|
"Some day" has come.
|
|
|
|
|
|
Tuck everything under guides/emacs.
|
|
If I eventually start tracking changes down, those will help.
|
|
|
|
-ish (sort "# Motherfucking websites" at 'M'). No idea how I
proceeded back then (date of discovery?); now I can stop wondering and
insert new sites the same way.
|
|
To make the next commit easier.
|
|
Might try upgrading mobo firmware next; push notes in case computer
goes down in flames.
|
|
|
|
|
|
|