Many of my traditional blog post live on this site, but a great majority of my social-style posts can be found on my much-busier microbloging site at updates.passthejoe.net. It's busier because my BlogPoster "microblogging" script generates short, Twitter-style posts from the Linux or Windows (or anywhere you can run Ruby with too many Gems) command line, uploads them to the web server and send them out on my Twitter and Mastodon feeds.
I used to post to this blog via scripts and Unix/Linux utilities (curl and Unison) that helped me mirror the files locally and on the server. Since this site recently moved hosts, none of that is set up. I'm just using SFTP and SSH to write posts and manage the site.
Disqus comments are not live just yet because I'm not sure about what I'm going to do for the domain on this site. I'll probably restore the old domain at first just to have some continuity, but for now I like using the "free" domain from this site's new host, NearlyFreeSpeech.net.
I'm more comfortable using the Chromium web browser supplied by the Fedora team instead of Chrome as packaged by Google.
The only problem is that video doesn't generally work because the codecs that you might have installed so video works in Firefox don't work for Chromium.
The solution is to install the chromium-libs-media-freeworld package from the RPM Fusion Free repository.
If you haven't already added the RPM Fusion repos to your Fedora installation, I recommend you do it as soon as possible. (If you are a hard-charging software-freedom zealot, you already know why you do what you do or don't do.)
Once you have RPM Fusion hooked up, run this command to add the codec:
sudo dnf install chromium-libs-media-freeworld
Then restart Chromium, and you should be able to watch video from YouTube and others.
When my Fedora 28 upgrade blew up, I didn't turn to Google's repository for Chrome when I reinstalled F28, sticking with Firefox only for as long as I could.
Eventually I needed a Chrome-equivalent browser, and I turned to the Fedora-packaged Chromium. It runs great, and I like that it's packaged by Fedora developers.
But it ships without the codecs required to watch video from places like YouTube.
It didn't bother me for awhile, but situations do come up where I need to see a video, and it's a little interruptive to start Firefox if I'm not using that browser already.
So I did a little web search and learned that there is a package from RPM Fusion that will take care of this issue.
If you already have the RPM Fusion repositories set up on your Fedora computer (and I recommend that you do it if you haven't already), just open a terminal and run this:
$ sudo dnf install h264enc
That will get you video in the Fedora-packaged Chromium browser. That's it. Easy, right?
Modularity is one of the big new features in Fedora 29, but it's also available in Fedora 28.
What is Modularity? As the project leader says in Fedora Magazine:
Modularity lets us ship different versions of packages on the same Fedora base. This means you no longer need to make your whole OS upgrade decisions based on individual package versions. For example, you can choose Node.js version 8 or version 10, on either Fedora 28 or Fedora 29. Or you can choose between a version of Kubernetes which matches OpenShift Origin, and a module stream which follows the upstream.
I want Node.js 10 instead of v.8, so I figured I'd try it out. I'm still running Fedora 28. I haven't upgraded yet. The upgrade from F27 to F28 didn't go so smoothly that I'm eager to do it just yet.
If you want to try Modularity in F28, it helps to read the docs.
First you have to enable the Modular Repository:
$ sudo dnf install fedora-repos-modular
Then you can check for available modules:
$ dnf module list
I like to live on the edge, so I'm going to install Node.js 11:
$ sudo dnf module install nodejs:11
That worked, and now I have Node.js 11. Remember, read the documentation -- that's how I got this far.
After I made a permission change on the server and broke the ability of Unison in Cygwin to sync with same, I decided to blow away the files on the Cygwin-controlled filesystem in Windows and try again.
I created a file in Cygwin, and that synced fine. But once I created a file on the server and tried to sync from Cygwin, I got a bad bigarray kind error, and that was that.