See a higher-up index of these blog posts here.
Get these updates in your RSS reading with my feed here: lukesmith.xyz/rss.xml
See old posts from 2019 here: 2019.html.
See old posts from 2018 here: 2018.html.
Font gone crazy in LARBS?
22 Mar 2020 (Sun) 01:40PM[link—standalone]
An Arch update to
ttf-inconsolata has temporarily broken the font.
If you're a member of an Arch forum or IRC, I recommend notifying them/the developer of this.
I don't have an account there.
Since Inconsolata is the default monospace in LARBS, I've been getting a lot of emails as to how to fix or patch this.
Just change your default monospace font in
~/.config/fontconfig/fonts.conf to another install monospace font.
If you don't know what monospace fonts you have installed, list them with
fc-list | grep -i mono.
See our Github issue.
What should be the default browser for LARBS?
16 Mar 2020 (Mon) 10:59PM[link—standalone]
I'll probably record a video on this tomorrow, but I might as well ask my blog audience first, What should be the default web browser in LARBS?
Right now it's Brave, since that's what I do and it comes with a lot of features I consider basic already built in.
The problem with nearly all web browsers is that it's pretty hard and annoying to put together "dotfiles" for them, a default profile that has sensible defaults.
Brave is especially nice because it comes with add-ons that block adds, redirect to HTTPS and add Tor and torrenting capabilities.
But while sometimes Brave will prompt the user on first run for their preferred start engine, on some systems after running LARBS, it will just assume Google, which I absolutely want to avoid.
I'm sure you all have the agency to change your search engine to something more sensible, most use DuckduckGo (I prefer Searx), but when it comes to the default, the sileny majority is going to continue with the default idly, and I don't want to set them on the wrong path.
Why even use Linux if you're just going to send everything straight to Google anyways?
- Brave – Again, great defaults, but Google might end up as the default search engine.
- Ungoogled-chromium – Possibly the safest bet, no cringe branding or bad policies, but it doesn't look like it has any search engine by default... That will be a big annoyance to novices.
- Palemoon – Manjaro i3 uses it, fast, good-looking, but it has an incestuous development team which has made... odd choices (`~/.moonchild productions/` makes me want to kms whenever I `ls -a`), but okay on privacy (weird startup screen, but could be worse). Bad/limited add-ons/extensions.
- Icecat – I'll admit it, two years, Icecat was absolutely unusable on pretty much all sites, but it looks like it's evened most everything out. Probably the best browser for raw privacy, but still probably the least usable since users have to keep in mind if they need to turn some script blocker off for a site, etc.
- qutebrowser – I haven't used it in years and I don't know if I want to get back into figuring it out for the third time, lol. I don't know where it is nowadays, but if I'm making normies use it, it's going to have to be able to play YouTube videos and without 400% CPU usage. qutebrowser does have the _massive_ advantage of __actually having dotfiles__ so I can easily change defaults.
- Waterfox – Well, a better form of Firefox on most fronts, but Bing is the default search engine.
Premptive 'no' to the following
- surf – Too much work for an individual, let alone managing one build to rule them all. There are cool suckless things you can do with it, but it's also just slow.
- Browsers I'm not familiar with (uzbl, luakit). I hear they're really cool, but for me to install it on other peoples' computers, I need to be organicly familiar with it. You'd have to convince me to use them individually first.
I'll also say, and I had never heard this take until I did my video on Brave, I obviously have no qualms about using a chromium-based browser. Apparently there are people out there who have the idea that source code is just magically evil if it was written by Google, even if it is 100% free and open source and well-audited.
Anyway, share your opinions! What did I miss?
Email me what you think at firstname.lastname@example.org and you might influence me before I record the video tomorrow morning.
I'll be at Linuxfest Southeast June 12-14 in Charlotte, NC
15 Mar 2020 (Sun) 08:49AM[link—standalone]
I'll be at Linuxfest Southeast June 12-14, 2020 in Charlotte, NC. (vid).
I'll probably be making some presentations as well.
Although I missed the 2019 conference, I had gone in 2018 and it was a good experience.
If you're in the region, I recommend you come.
I'll be commuting from a distance, but I expect it will be worth it.
I met a lot of subscribers in 2018 (and there were many more who were too awkward to come up and greet me 😉).
Anyway, check out their website at southeastlinuxfest.org.
I don't think they've opened sing-up for attendence, but I expect it to be in a month or so.
By the way, if you want to see my talk at the 2018 Linuxfest the link is here: Linux Is the Wild West! And let it be that way!.
Big fix for the st/suckless 'Crash-On-Emoji' error
Suckless software has long been burdened by a peculiar error that causes crashes whenever trying to load a colored emoji.
This has meant extreme annoyance for me and confusion for people who use my dotfiles.
The only band-aid for this error has been just installing a font with good unicode coverage and hoping that monospace fonts dare not to print out colored emojis, and making a fontconfig that keeps it that way.
Recently, however, a fix has been posted to the AUR in the
libxft-bgra package, which will hopefully become part of the Xft upstream soon.
This will avoid the error, and allows unpatched st to view colored emojis without a problem.
I do a video on this here.
For those who use my dotfiles, update everything: the st build, the dwmblocks build if you use it, the dotfiles, etc. and install
Sat, 01 Feb 2020 16:53:04 -0500
I had variously patched software to avoid these problems, but those patches have now been reverted to allow color emojis if you want them.
That's only slightly a hyperbole.
I'm thinking about bringing back the podcast; it's probably the only old content I get constant requests to bring back. I'm already compiling stuff for a few new episodes for Season 2, which might actually include some joint episodes with people you may or may not know... We'll see!
Anyway, I finally finished and put up an episode I did in a stream months ago:
The Flaws of Academic Statistics: the Null Ritual which you can see
on YouTube as well.
This episode is talks about some of the fundamental and acknowledged issues in how statistics is used in nearly all sciences.
Nearly every science paper you've heard of in the popular press and in academia is built on flawed statistical footing.
Add the podcast's RSS feed to your RSS reader! You can also go to the podcast's webpage https://notrelated.xyz to get links to other services to get the episodes from (Spotify and Google if for some reason you do that stuff (just use RSS)).
Mon, 20 Jan 2020 18:55:42 -0500
Return to main page
New video on new books
I did a video covering every book I got in 2019.
Check it out, as
some people often ask me what kind of books I tend to get.
You can also check out
my library page
at my website for a full inventory of my library if you have interest in that.
Fri, 03 Jan 2020 00:12:30 -0500