Fedora, Manjaro, WordPress & Twitter

So, quite a few things have been happening recently.

I tried to go the next step on Manjaro and copy my home directory across ready for me to run the Ansible playbook to do the setups (I’ve been testing it would work via VirtualBox on my Windows laptop)

After waiting ages for the file copy, when I went to do the backup, there was a btrfs checksum error so I’ll have to try again some other time.

Separately, I got a message on an issue I raised at Fedora’s bugzilla the Fedora 36 (the version of Fedora I raised the bug on), was coming up to EOL so I should look to move away from it or upgrade. So I decided to try doing the upgrade.

The upgrade completed without error, but first boot after the upgrade hung with a weird Kernel Panic error (I have posted this on the Fedora Forums)

So I rolled my laptop back to preupgrade state for now.

I suspect I may need to end up doing a clean install, so I’ve prepared a btrfs and a ext4 lvm installation and have imaged those in preparation.

Finally, WordPress posted that they’re stopping Autosharing to Twitter because of Twitter’s Idiot-in-Chief screwing up the API usage.

Still, they have mentioned they will be adding autosharing to Instagram and Mastodon instead, and that helps me, since I’m slowly moving what little Twitter presence I had onto Mastodon anyway.

My Twitter has been disconnected from my WordPress and I’ve revoked its access from Twitter’s side anyway.

Training in Quarantine – Day 179

Late out today — my phone wanted to upgrade so I attempted it (it was an upgrade from Android 9 to Android 10), and it didn’t work, and I ended up having to factory reset and install from scratch. I did have some Titanium Backup backups, but they didn’t seem to work a lot of the time :/

So for the most part, I just reinstalled all the apps I remember using and logged in. For most, that was fine. But I lost the MFA codes on Google Authenticator, meaning I had to remove and setup:

  • AWS
  • LastPass
  • WordPress
  • GitLab

all over again

AWS was quick and painless after a security check to confirm I was who I said I was and they called me on the number on the account.

WordPress was painless too — I was already logged in, so just removed MFA and set it up again, then logged in again. Similarly with LastPass

GitLab however, is proving to be more of a pain. They no longer accept MFA removal requests for people on the Free plan. So I wonder if they will accept me going to a subscription model so I _can_ then request the MFA removal. I think it is better anyway, since I’m hitting the 400 minute CI limit pretty regularly. The 2000 minute CI limit would be better. At least until I can get my own GitLab install working.

As for the run, yes, it was a run — well, more of a jog, anyway. Still did the 3km lap, doing it in 20 mins rather than the 30 mins it normally takes me when I walk it.

WordPress and Twitter

I wondered why I didn’t enable auto-sharing to Twitter from WordPress,

Then I remembered, that method only puts the title of your blog entry, plus an embedded link. Unless you have a really informative blog title, I don’t think it works.

Instead, I use IFTTT, but have to remember to either add a picture somewhere in the post or manually shre it through force checking the IFTTT applets.

Wix gets caught “stealing” GPL code from WordPress | Ars Technica

Well… “stealing”? I guess it depends on how you interpret the GPL.  Nonetheless bottom line is — if you are going to use GPL code, your code and product must follow the same license. i.e.

“… if you’re going to embed GPL stuff in your code and produce a derivative product, you’re going to have to make that derivative compliant with GPL—either by shipping the code with it or providing the code on request”

So, the headline of “stealing” GPL code? Can you actually “steal” code that is open source? Using open source in a closed source product would be a violation of the GPL (which I believe is what’s being talked about here), but is that “stealing”?

I’m not siding with either side here, I’m just not sure the word “stealing” is the right phrase to use in this headling here, quoted or not. Guess that’s clickbait for you….

Source: Wix gets caught “stealing” GPL code from WordPress | Ars Technica


Evidently, even my blog is party to the Frozen craze….

Most popular posts so far:

Zombies, Run! — How to use Google Music (Final Edit) 9,433
Home page / Archives 4,672
33 Mistakes of Disney’s FROZEN You Didn’t Notice (And Easter Eggs/Secrets) 2,262
Grive & Fedora — Working 1,807
Building Docker.io on 32-bit arch 1,477
Training Plans on Endomondo 986
Zombies, Run! Building Requirements & Achievements 905
Concatenating Videos 672
Zombies, Run! 2 — Updated 371

Using a WordPress theme? You might want to read this … | Sherry Holub | LinkedIn

As of January 2015, more than 23.3% of the top 10 million websites are using WordPress (source). To say it’s a popular choice for a content management system is an understatement. Part of its appeal are the thousands of free and commercial, pre-made themes available for the system. They are an enticing way to publish a website with little or no knowledge of programming required.

It helps to understand the motivation different parties may have in creating a WordPress theme for sale or free download.

Individual programmers are often motivated to create a theme to upload it to a site that sells them at low cost. Much like a stock photo, think of these themes as stock themes. You pay a fee that is a fraction of the cost of hiring a professional to create a custom design and theme, you download it for your website, and the individual programmer gets a small cut of that fee. With free themes, the original programmer usually requires that a link back to them appear on the site, gaining them more internet exposure.

However, there’s also a third, more nefarious reason for creating free themes – to spread malware and other malicious code. That’s right, some unscrupulous individuals will code nasty stuff right into a theme hoping to cash in on the popularity of themes and the ease of installing them, as well as uneducated or uninformed user. So how do you avoid this one? Of course I’d recommend going custom (more on that shortly), but if you’re determined to use a pre-made theme, be careful where you get them. There are several popular sites that sell themes, and WordPress.org has a directory of themes. Those are your best bets but you often have little recourse if you purchase or download a free theme and install it yourself any of these occur:

  • you manage to screw something up on the site
  • your site is hacked
  • your site is flagged by Google for containing malware


Using a WordPress theme? You might want to read this … | Sherry Holub | LinkedIn.

%d bloggers like this: