“krill oil contains particularly rich amounts of choline-containing phospholipids and a phosphatidylcholine concentration of 34 grams per 100 grams of oil”
“krill oil also contains an appreciable content of astaxanthin”
“krill oil contains particularly rich amounts of choline-containing phospholipids and a phosphatidylcholine concentration of 34 grams per 100 grams of oil”
“krill oil also contains an appreciable content of astaxanthin”
(as long as you don’t have a shellfish allergy) krill oil – specifically “Neptune Krill Oil” (NKO) processed
Chang Beer
a list of named vulnerabilities would be a great starter
still in the setup phase and running LabWC rather than a full desktop – but actually rather enjoying it and have been stumbling across a lot of cases finding out that even with a GUI installed, terminal programs do just as good a job if not better than their graphical counterparts (ex. I don’t think I’ll ever be a full vim/emacs convert, but for basic text editing, nano does just as well as mousepad/leafpad/featherpad/xed/gedit)
doas apk -iU upgrade
blood sucking leeches versus privacy sucking websites …
don’t really have a favorite – started with Thunderbird a long time ago but switched over to webmail fairly early on
now that I’ve started to build a new system, I started to look around at the various options (and maybe getting off webmail or at least having local storage “backup”) – the standard GUI clients (Thunderbird, Evolution, KMail, BlueMail, Mailspring) seem to be … fine – but none of them really stand out
recently stumbled across some nice screenshots of aerc and the idea sounds really appealing, but I’ve never had any contact with terminal email programs and found out they’ve followed a completely different evolutionary path than GUI apps (even terminology has diverged between the two) – GUI apps keep trying to be an all-in-one (email, contacts, calendar, tasks, …) whereas terminal programs almost seem to to favor a “balkanization” of effort – aerc looks like it’s grabbed a middle-ground, you can run it as standalone or go all in with a fully customized setup – problem I’m running into is I can find lots of “how” guides, but very little in the “what” or “why” side of things …
nano -m <file>
or set mouse
in your nanorc
and sometimes you just need a text editor, not an entire thesaurus
as others have mentioned, a window manager is one component of a desktop environment – under ideal conditions, a desktop environment collects and integrates a whole set of packages (both primary and supporting), unifying functional aspects as well as look-and-feel – whereas people starting with a window manager add in tools where working for them takes priority over working with other tools
such a weird dichotomy in Windows – secure kernel space and privacy-nightmare user space … “we’re the only ones allowed to steal your data”
(completely sidetracked here – there’s a reason Dirk Hohndel (and Linus) decided to go with Qt instead of GTK)