Yes, this project is still a going concern, and yes, it’s easier to say “I’ll write an update every week” than it is to actually do that. But rest assured, software updates and backups have been running right on schedule, regardless of posting regularity.
The news I wanted to share with you is that hosting Indivisible group websites on this network will now be provided free of cost. That has been the case from the start, thanks to an early, generous donation and modest expenses. But I’ve decided to make it official, and permanent: Indivisible.blue is free.
From the start of this project, I wanted to make sure it would be sustainable over the long years ahead of fighting the Trump/GOP agenda. If dozens or hundreds of groups signed up, I didn’t want to be on the hook for hundreds of dollars each month. But now it’s clear that growth in the number of sites has leveled off, and everything is still running fine on a $10/month server. I can live with that. (Though I’m still happy to accept your help if you care to chip in: see the financials page for donation details).
So to all the people who I awkwardly tried to describe the possible, maybe, semi-kinda-sorta estimated price, based on server costs divided by the number of sites based on the phase of the moon – I’m happy to say it’s much simpler now. And you don’t need to worry about the bill-collectors coming to collect $1.28 next month.
And to any new folks: come on in; it’s not too late. We have plenty of room to grow, so get in touch.
Lots of action in this update (especially since I missed last week’s).
- Site email – I discovered that automatic email notifications were exceeding my mail service’s quota, which sometimes caused delays in my receiving feedback. That’s been addressed, and I should hear from you more quickly and reliably.
Login security – I enabled a small – but I think important – security improvement on the login screen. Normally, if someone enters the wrong login information, WordPress will say either there is no user by that name, or that the password for the (correctly entered) username is wrong. This is a bad security practice, and I’m amazed that WordPress has this as the standard behavior. The reason it’s bad is because it gives brute force login attempts more information than they should get: it tells them which user IDs are valid (and worth trying to guess passwords for), and which aren’t (so they don’t waste time trying to guess those). The fix simply blanks out that message, which is admittedly less user-friendly, but the security improvement is significant.
New & updated plugins
- New sites – Last but certainly not least, we’ve added four new sites to the network. Several of them are still getting set up or kicking the tires, but one that’s wasted no time at all is CornynStakeout.com. Targeting one of the terrible senators right here in my own Lone Star State, I’m proud to have helped this site’s creator get this site live quickly and easily. It was mentioned by the national Indivisible Team on Twitter today, and has had about 3,000 unique visitors since then.
This past week on Indivisible.blue:
I updated to the new WordPress core maintenance release, version 4.7.4. From the release notes:
This release contains 47 maintenance fixes and enhancements, chief among them an incompatibility between the upcoming Chrome version and the visual editor, inconsistencies in media handling, and further improvements to the REST API. For a full list of changes, consult the release notes and the list of changes.
I installed a new theme (Bento), and a new plugin (Page Builder plugin). I also updated 3 plugins and 1 theme.
Lastly, I worked with the patient admins of the Bryan-College Station (TX) site, as we worked through some wrinkles with the security plugin that temporarily locked them out of their site. I continue to see a number of hacker login attempts, and this is an area where I’ll be working more.
I’ve been meaning to start posting updates about all the things happening here at Indivisible.blue for some time, and haven’t managed to get it going. But here goes! I’m going to try to post at least a quick blurb every week, just to be on a regular schedule.
One big step for the network took place in early March: I doubled our (admittedly small) server capacity. Increased usage was causing occasional database crashes due to lack of memory, so we went from a server with 512MB RAM and 20GB disk (costing $5/month), to another with 1GB RAM and 30GB disk (costing $10/month). That change only took one button click and a server restart, which is one of the reasons I chose Digital Ocean for server hosting in the first place. The new capacity has been working well since then.
That increased usage is due to continued growth in the number of groups setting up their sites on Indivisible.blue. The total number is now up to 21, and includes groups from:
- Bryan-College Station, Texas
- Harford County, Maryland
- Texas District 20
- San Diego, California
- Cranbury, New Jersey
- Illinois District 6
- Sausalito, California
Besides adding these sites and helping them to get going, I’ve also updated kept WordPress up-to-date, updating plugins six times, and themes twice. One new theme has been added (Bento), as well as a new plugin (Page Builder).
The last big news this time is that I added the first new HTTPS security certificate for a group’s custom domain, using the free Let’s Encrypt service. I plan to add those for remaining sites, but haven’t gotten to that yet. If you’re eager to get that set up for your group’s site sooner rather than later, let me know (by email or the contact form).
That’s it for now. As mentioned, I hope to make these updates more regular. I may also write on a few other topics, to maybe help get some conversations going about the issues groups face running their websites effectively.
Thanks to prodding from a site admin (hi, Shea!), I dug in tonight and got the Akismet comment-spam blocking plugin activated for all sites on Indivisible.blue. Which means that spam comments left on your sites’ posts will now automatically be filtered out. Admins of individual sites don’t have to do anything, no API key to sign up for or enter. (If you want to adjust the couple of options, visit “Jetpack -> Akismet” on your dashboard.)
I’m still getting things together around here, but if you want to keep up with what’s new, you might want to follow my brand-new Twitter account: indivisibleblue.
You want to make it easy for visitors to find you on social media networks, and here’s how to set that up. This process can be a little different with each theme. For starters, here’s how to set it up in the default “twentyseventeen” theme.
- From your Dashboard, hover your mouse over “Appearance”, and click “Menus”
- Click the link, “create a new menu”
- In the box by “Menu Name”, type a name, like “Social Links Menu” and click either of the “Create Menu” buttons
- Now that you have a menu, you can add custom links to it. On the left-hand side, click “Custom Links” to open up that section
- In the “URL” box, type or paste the URL of your Twitter, Facebook, Instagram, or whatever social media page you want. It should begin with “http://” (or “mailto:” for email); you can copy and paste it from another tab to make sure it’s right
- In the “Link Text” box, type a name for the link. On some themes, like “twentyseventeen”, this won’t be visible, but it’s still required. Just enter “Twitter”, “Facebook”, “Instagram”, or whatever. Linkable networks with built-in icon support include: Twitter, Facebook, Instagram, Tumblr, Medium, Snapchat, YouTube, Flickr, Vimeo, Reddit, and email
- Click the “Add to Menu” button, and the link will appear on your new menu
- To change or remove any links, click on them in the menu to open up the entry boxes again. You can also drag and drop those items to reorder them
- Click “Save Menu” to apply your changes
- Click “Manage Locations” to see where your WordPress theme lets you display menus (you have to display it somewhere)
- For the “twentyseventeen” theme, in the dropdown next to “Social Links Menu”, pick your new menu from the list, and click “Save Changes”
- Preview your live site, and you should see the icons for your networks in the footer of each page
There are other ways to display these – in “Widgets” in the side bar or footer, or in other menus – but this is one straightforward way that works well in this theme.
I moved this post! Now it’s right here (sorry for the extra click).