Disruptive Conversations

I was a little surprised to learn this morning that Twitter is shutting down its Revue newsletter service. Casey Newton first wrote about this back on November 3 in his Platformer newsletter, but subsequent articles after the massive layoffs confirmed that Revue is shutting down - and basically all the associated staff have been let go.

I had missed all those articles and just randomly saw a reference this morning when scanning social feeds.

It’s NOT actually surprising if you think about the fact that Elon Musk has to be laser-focused on revenue right now, particularly as his self-induced chaos is causing users and advertisers to leave Twitter. Revue was about long-form content published in email - and was not really a quick and easy way to increase advertising 

So as they note, it’s all going away:

• December 20, 2022 – Revue will set all outstanding paid subscriptions to cancel at the end of their billing cycle
• January 18, 2023 – Revue will shut down and all data will be deleted

It’s too bad as it was a nice platform… if you were a strong Twitter user.

It had the nice feature that it showed up right on your Twitter profile page, offering people the ability to easily subscribe:

On the back end, there were some simple tools to easily add tweets into your newsletter.

Also, unlike Substack, you could set up your Revue newsletter with a custom domain, such as I did with choices.danyork.com.

So What Will I Do Next?

As that image shows, I started a newsletter on Revue called “A Choice of Futures” back in October 2021 and published a whopping two issues! 🎉

I had great plans to do more, but ran into several challenges in timing and then got super busy with work and volunteer responsibilities in 2022.

But I was thinking about getting back to it in 2023.

So what now?

I could move that newsletter over to Substack, Medium, AWeber, or any of a zillion other places.

Or.. I can just shut down this particular newsletter. 

Realistically, that’s probably what I’ll do. Send one final issue as the period at the end of the sentence, and then be done.

You see… I actually already have a Substack newsletter at danyork.substack.com called “A View From The Crow’s Nest” where the intent is to write about new technology out on the horizon. It’s an even older newsletter that I used to run through an email service provider. I moved it to Substack back in March 2020 when Substack was getting a lot of attention. I wanted to learn about Substack and it was my intention to start doing more with it.

But then.. pandemic… and so much else of the craziness of COVID-19 and how our world was changing. I dropped that newsletter and so much else, just caught in the moment of trying to make it through each day.

By the time late 2021 came around and I was interested in a newsletter again, I had some concerns about the direction Substack was going… and so I thought I’d give Revue a try.

Ha!

Turns out the concerns would end up being with where Twitter and Revue were going instead!  (Although I do still have concerns about Substack!)

So that will be my personal plan. I’ve hit the button to export all my data from Revue, and I’ll invite folks there to join my other newsletter on Substack.

Any of you reading this are welcome to join too!

Joe Brockmeier, who I’ve known from back in the amazing early days of Linux in the early 1990s, recently posted to his Mastodon account:

With the renewed focus on owning your content and DIY web / #IndieWeb ethos, I'd love to encourage folks to think about more long-form content.

Mastodon allows for longer thoughts than the birdsite, but I miss the days of blogrings, conversations in comments, and so forth. I don't think we're going to get back to blogging's heyday, but a revival would be great.

And with that, he announced he was going to do a “100 day blogging challenge”. As he writes, “let’s get those RSS feeds going again!"

He then invited others to join in on the creation of long-form content:

If you’re reading this, consider this an invitation to start or dust off your own blog and update it regularly. If 100 days straight is too much, how about twice per week?

So… okay, Joe, I’m in! Since I said way back on January 1 that I hoped to create more content this year… and haven’t really… let’s see if I can finish strong!

I’ve long wanted to start writing again on sites that *I* control, versus writing on the platforms and social sites. (See… POSSE … from four years ago! 🤦‍♂️)

Today is December 1 - a random site on the Internet tells me that 100 days from today will be March 11, 2023.

Let’s see if I can go that long. If so, hopefully it will then be back to being a “habit” that I will just continue indefinitely.

To be clear, I’m not going to commit to write here on THIS site alone for 100 days, although maybe that would be good. My goal will be to write across my various personal sites and other sites like CircleID and the Internet Society’s blog. I’ll also be scheduling content in advance, since I don’t expect to actually be writing on Christmas. We’ll see!

If you care to follow along, or just want to hold me accountable 🙂, you’ll be able to see my writing at danyork.me. In theory, that little calendar on the right side should show a bold date from here on out to March 11!

Care to join in? 

Let’s bring some more long-form content back to the Web! (Tip: you can use this site to find your end date.)

I may have just found my new favorite "Lorem ipsum" text generator - HIPSTER IPSUM!

https://hipsum.co/

For the longest time, my choice when I just needed some columns to fill in with filler text[1] was Bacon Ipsum, which is always fun. The companion to that is of course Veggie Ipsum

But now I think I may indeed use "hipster ipsum". I mean... I just smile when I read through the text. :-)

P.S. I noticed in searching today that there is a WordPress plugin (of course!) called "AnyIpsum" that lets you create your own lorem impsum generator.

[1] Why do I need filler text? When I'm working on a web design, it is often helpful to have some text in the columns and text blocks so that you can see what they look like with text in them. You can of course read more about the history of "Lorem ipsum" on Wikipedia.

Yesterday (Dec 6, 2018) was TheBigDay when WordPress 5.0 with the Gutenberg block-based editor landed in all of our WordPress sites for upgrade. Some of the places to learn more about the launch include:

• WordPress 5.0 launch announcement (with videos)
• WordPress 5.0 Field Guide
• Gutenberg information
• Twenty Nineteen theme info

Changing the core editor over to Gutenberg was a massive effort over the past two years - and the launch this week was both an amazing accomplishment... and a very divisive event within the WordPress community.

I was very much hoping to be down in Nashville for WordCamp US this weekend, where parts of the community will be gathering. I expect it will be quite a passionate weekend! (Unfortunately some family medical issues kept me closer to home.)

I *really* like Gutenberg...

My initial reaction was... I really LIKE Gutenberg!

Now, I've been playing with it for much of the last year, and the more I work with it, the more I like it.

It really DOES enable more beautiful and powerful publishing with great ease.

I'm looking forward to doing even MORE with it and learning how far we can go with using Gutenberg.

... but it needs to work! :-(

However, after the upgrade to WordPress 5.0, the Gutenberg editor didn't work on all my sites. For several of my sites, I had NO PROBLEM after the update. It "just worked." I was immediately able to go in and start editing with Gutenberg.

But on a couple of other sites, when I went in to edit an existing page or post - or to create a new one - I made all my changes and pressed the "Update" or "Publish" button and...

"Updating failed" in a big red bar across the top of the screen!

Amusingly to me, some searching on the web brought me back to a Github issue I had opened back in August 2017.

All I had to do to "fix" the issue was this:

1. Go to Settings -> Permalinks, and change it from "Month and name" to "Day and name" and press "Save changes". I received the message "Permalink structure updated."
2. Change it from "Day and name" back to "Month and name" and press "Save changes". I received the message "Permalink structure updated."
3. Switch back to the tab where I was editing the post and had the error message. Pressed "Update" and.. ta da... the updating worked perfectly fine.

I had to do this on two different WordPress sites (both running on the same WordPress multisite server). Strangely, other sites on the multisite server were fine.

While the fix was easy, it concerns me that I had to do this and that I didn't really do anything. But somehow my act of changing the Permalink Settings did SOMETHING internally to make things work.

That concerns me.

Now, someone in that ticket or elsewhere suggested that this particular issue was NOT a Gutenberg issue, but rather an issue with the REST API, which Gutenberg uses.

Regardless, my point was that I couldn't use the editor to make changes on my site.

And beyond my own issue, I see many other Gutenberg issues piling up on Github. Now, yes, these may be initial launch pains for launching such a massive change.

But I do hope the team of developers can fix these in the 5.0.1 release that I'm sure will come quickly.

I really DO like the Gutenberg editor - and I look forward to seeing all we collectively can do with it!

P.S. This post was NOT written using Gutenberg because this Disruptive Conversations site is sadly still over on TypePad. I look forward to migrating it some day so that I can use Gutenberg!

Have we given up on personal blogging? Are we instead doing that all writing in Facebook, Twitter, LinkedIn, and similar services?

Is the personal blog dead? [1]

I had lunch this week with a friend who, like me, has been online since long before this thing we now call the “Internet” came into being. We were having one of those “back in the old days” conversations where we talking about the discipline that came from programming in assembly language, the challenges of early computing and networks, how the programmers these days no longer need to understand how things really work, how they write bloated code, etc., etc.

Along the way we talked about the changing nature of the Internet and the growing consolidation / centralization of so many key services. We talked about how so many people no longer host their own web servers (both she and I do (for some of my sites), but talked about the issues with that and how attractive it is to look at hosting options)… about how many people no longer run their own mail servers (I don’t, but she does)… and how people have just generally given up running their own services because the hosted services are just so incredibly convenient and useful. And somewhere in there she just tossed in a comment along the lines of:

“… and then we’ve given up on blogging in favor of Facebook…"

It was just a throwaway comment in the midst of a longer discussion that went on into the rise of CDNs, overlay caching networks, cloud computing and more. (It was a great conversation!)

But that comment stuck with me… and as it rolled around inside of my brain, I sadly had to conclude that for the most part[1]...

… she’s right.

My Own Example

I look even at my own writing. Despite my post in September about “Returning to POSSE - Writing on my own site, THEN on Facebook, Twitter, etc.”, the truth of the matter is that I haven’t been writing on my own sites.

If you take a look at my danyork.me aggregator site, you’ll see that I’ve been writing for the past week, but if you go back beyond that, or use the little calendar on the right sidebar to look at past months, you’ll see there is very little activity.  And what there is of my writing is most often on the Internet Society websites, rather than my various personal blogs.

For example, when I wrote on my Disruptive Telephony site on Monday, it was my first post there since March 2017 - that is 21 MONTHS!

Some of my other sites are worse.

Now, you could argue in my case that this just a matter of changing priorities. I don’t work as much with voice-over-IP or messaging, and so NOT writing on Disruptive Telephony makes sense. The site chronicled by activities in the VoIP world when I was active there. Now maybe it’s time to just park it and leave it alone. I could make similar cases for why I haven’t written on other sites.

And this may just be the consequence of my choice many years ago to spread my writing across multiple topic-focused sites, instead of just writing about a wide variety of topics on a single site such as danyork.com.

And it may be that it’s just me with everything else going on in my life over the past year.

The Directory Dilemma, Again

Or maybe not.

My lunch companion mentioned the challenge of finding where companies have their main information. Are their hours of operation most accurate on their website? Or on their Facebook page? 

And the same is true of personal blogs and sites. 

How do I find where people are writing?

Back in the early days of blogging (mid-2000s), of course,  many of us used RSS readers and got our feeds from sites that way.  We found new feeds from references, from searches, from different directories. But while I’m still one of those dwindling number of people who use a RSS reader, the vast majority of people do not. 

How do you find writing?  Well, usually through mentions in social media. It’s the “syndication” part of POSSE.  

But if you are using social media to distribute and promote your writing… it’s not a huge step to simply just write in the social media platform because it’s so easy and distribution is automatic. I know people who have moved all their writing to LinkedIn, for instance. Or people who are writing long threads in Twitter now that the site supports longer tweets and threading.

It’s another version of the Directory Dilemma - it’s easy to find content within those nice hosted walled gardens.

Running Servers Takes Work

And let’s be honest - running your own personal website can be a bit of a pain. If you use a self-hosted content management system (CMS) such as WordPress (as I do), you find yourself pretty much constantly needing to apply updates. Updates to the core… updates to the plugins… updates to the theme.  And then of course possibly updates to the underlying operating system if you are running the CMS in a virtual machine.

And then if you want to set up TLS certificates to support HTTPS, that can be a whole adventure! And if you mess it up, your sites are offline.

It’s enough to make you say… "<expletive> it, I’ll just go write on Medium!” … or hosted WordPress.com … or… to just write inside of Facebook or Twitter or LinkedIn.

After all... I just want to write! 

Every minute I spend doing system admin or applying plugin updates is a minute I could be doing more writing.

Add in that all of those social sites have very easy-to-use mobile applications. It makes it so easy to just start writing inside those pretty walled gardens.

In contrast, many of the blogging and website hosting services have a less-than-stellar mobile UX. WordPress does a nice job with its mobile apps... but others? Not so much.

So is personal blogging dead?

Wellllll... no. There will always be some of will write on their own sites.

And I'd like to hope not for the larger independence of the Web. I'd like to hope many people will continue to embrace the “POSSE“ content publishing model from the “IndieWeb” movement:

Publish on your
Own
Site,
Syndicate
Elsewhere

I am going to continue to try.

But I also understand why some give up on it. The sweet convenience, ease-of-use and simplicity of the social networking platforms is extremely seductive. And they encourage consumption of content (because that helps get them the ad eyeballs they need to get paid) - and finding the balance of consumption and creation is hard!

What about you, dear reader? Have you given up

[1] Realizing that there will always be outliers in terms of very active personal blogs - and people who just choose to write on their own - but are personal blogs no longer of interest for the vast majority of people?

Photo: an image I took in the Woodlawn Cemetary in Keene, NH

Here is a quick 3-step process for launching WordPress in a Docker container. You can use this to easily launch a new WordPress instance on your local system to test out new versions, new plugins or anything else.

First, though, you need to have Docker installed on your system. The simplest way for Mac and Windows users is to install Docker Desktop. This desktop download also gives you Docker Compose, which you will need. If you are running Docker on a Linux system, you will need to manually install Docker and Docker Compose.

To run WordPress, you also need a database running. The steps here use Docker Compose to launch TWO containers: one for WordPress and one for MySQL.

Three steps

Step 1 - Create a directory (a.k.a. "folder") and install the docker-compose.yaml file found in this Github repository. You can get the file three ways:

• using git: git clone https://github.com/danyork/wordpress-basic-docker.git
• direct download: https://raw.githubusercontent.com/danyork/wordpress-basic-docker/master/docker-compose.yaml
• copy / paste the text into your own file named docker-compose.yaml

The key is to have this all in a separate directory because your WordPress installation will store some plugins there (see the notes below).

Step 2 - In a terminal window[1] type 'docker-compose up’

This will launch the two containers and link them together. You will see logging to your terminal window. You can press Ctrl+C to stop the containers and get your command prompt back. To launch the containers in the background add a "-d" option:

docker-compose up -d

Step 3 - Connect to your new WordPress server at http://localhost:8080/

That's it!

Now you simply go through the normal WordPress installation process and within a few screens your new site will be fully active.

Next you can update WordPress to the latest version, install whatever plugins you want, etc.

For example, I installed the WordPress Beta Tester plugin, went into its settings and turned on "Bleeding edge nightlies", performed an upgrade... and now I'm running the very latest WordPress 5.0 build. Perfect for the testing I want to do.

Credit for the simplicity of this approach is due to Github user "wglambert" who answered a request I made about help using the WordPress Docker container. Thank you!

Notes

• Stopping the containers - do 'docker-compose stop'. This will stop the containers from running. Doing 'docker-compose start' will start them up again.
• A 'wp-content' directory is created is created inside the directory in which you put the docker-compose.yaml file. Any plugins or themes you add will be stored here. This allows you to do a reinstallation and have all the plugins and themes available.
• WHEN YOU ARE DONE and want all this to go away, just type 'docker-compose down' and the services will be stopped and the containers removed.

There are many more things you can do with docker-compose. The command-line documentation can help you learn more.

Next parts

I labeled this as "Part 1" because I'm planning to write about my own ongoing testing with Docker and WordPress. In future parts of this series, I intend to cover:

• How to load in an existing site for testing
• How to save your changes in a Dockerfile (so you don't have to start at the very basic installation each time)
• ... and other things I learn along the way.

I also expect I may update THIS article over time as I do more with using WordPress and Docker.

I hope you found this helpful. Please feel free to leave comments here (unfortunately I have to moderate due to spam, and so comments will not appear immediately).

I also welcome pointers to other "WordPress and Docker" tutorials that people have found helpful. If you want to follow along with some of my other experiments with Docker and containers in general, I'll be writing about that over on Code.DanYork.com.

[1] or "command shell" or "powershell" or whatever you call it...

Over the past few weeks as I’ve been grappling with colon cancer, it has been soooooooooo tempting to just pop open the Facebook app, write a story in the box and press “Share”.

Simple. Easy. Done!

Or inside the Twitter app… or LinkedIn… or… or...

But here’s the problem with that...

All the stories get LOCKED INSIDE A PLATFORM!

They are there living on the platform’s servers, inside the platform’s systems.  Maybe they are visible publicly, maybe they aren’t.  Maybe they will be around in two years, maybe they won’t.  Maybe people will find them, maybe they won’t.

The future of your stories is entirely at the whim of the platform.

As I wrote about on the Internet Society’s blog earlier this year, one of my own guiding principles is “POSSE“, a content publishing model from the “IndieWeb” movement:

Publish on your
Own
Site,
Syndicate
Elsewhere

And so over these past few weeks, I tried really hard to do that with my journey through cancer: the diagnosis, followed by the recovery, followed by the results.

But it’s HARD. It was so insanely tempting yesterday when I got the great news just to pop open Facebook and share it with everyone.

But when I do that… it’s shared ONLY within Facebook’s shiny “walled garden”. It’s not shared with people I know who choose NOT to use Facebook. It’s not shared with the communities I’m in on other social networks.

The “open Web” on top of the “open Internet” is really the only way to do that. But it’s hard. There’s extra steps involved for me right now with the way my various blogs are set up.  I want to work to make that easier and simpler… but doing so will take time… which is challenging to find.

But if we don’t find ways to OWN OUR OWN STORIES then they will stay locked away in closed, proprietary walled gardens.  And maybe that’s fine for some of those stories. Maybe they are small and mundane… “in the moment” stories that we don’t really care about. But even so, we feed the platforms. We help them to grow.

 I’ll keep trying to follow the POSSE rule… and I’ll be writing more here about that.

Image credit: Tom Kelly on Flickr CC BY NC ND

I woke up this morning frustrated that I simply haven’t been writing across my various sites. In theory I am a “writer”, but I haven’t been writing! And as I wrote in My 3 Words for 2018: “because if I don't write... the stories build up inside of me until they want to explode like a pressure cooker without a relief valve. Writing is my relief valve. I need to do it.”

So I said to myself- I know, I will impose a new rule on myself... no social media usage until I publish something new! A blog post, a podcast episode (such as my The Dan York Report short audio segments), an article on some site (ex CircleID), a longer update on a social site... something.... anything.... BEFORE I get sucked into the vortex of social media updates. 

And I will start with a blog post like this one...

Except... I discovered I WROTE THE EXACT SAME POST TWO YEARS AGO! July 24, 2016, to be precise.

And... I noted that on day #2, July 25, 2016, I had already failed. ☹️

So this morning’s great idea turns out to be nothing new. 

In fact, I can go back 10 years ago, to a post in September 2008, where I wrote about Jeremiah Owyang’s “Pay yourself first” philosophy. Or may many other posts about struggling with consistent writing.

Now, maybe this rule is like the “no sweets today” diet rule that turns out to be an aspiration that just doesn’t happen. And maybe EVERY day is too high a goal. Maybe every other day. But I have to do something, or consumption will win over creation. 

Unless, of course, I want to reframe my own perspective and think of myself as an “occasional writer”... and just accept only writing now and then  

I am not quite ready for that. Let’s see how I do this year!

Today is the day! Every year on November 1 some number of writers across the world challenge themselves to write EVERY SINGLE DAY in November.

Some amazingly choose to focus on writing a novel. They go the "NaNoWriMo" route, a.k.a. "National Novel Writing Month"... where "national" is really any nation in the world. Best place to learn more is the simple address: nanowrimo.org

Given that the target of NaNoWriMo is to write 50,000+ words, that's a serious commitment!

Others of us, and I'll add myself this year, choose to focus instead on writing at least one blog post every day as part of "NaBloPoMo", a.k.a. "National Blog Posting Month".

NaBloPoMo started back in 2006 and since 2011 has been championed by the BlogHer community. BlogHer is supporting NaBloPoMo again in 2016, but it wasn't clear for a while if they were going to do so. Meanwhile, another group at the "Cheerpeppers" site started a "blog once a day" challenge under the name "Nano Poblano".

Regardless, the point is to challenge yourself to write every day.

And of course being in our social world, you can follow along at the hashtags #NaNoWriMo and #NaBloPoMo - and also now #Nanopoblano (the hashtags all link to Twitter here but you can find them used on other social networks as well).

For myself, I am going to give it a try. Writing (and publishing) every day. As I recently wrote, I'm struggling to write consistently... so this provides a goal for me to strive for.

Now, I won't be writing here on Disruptive Conversations every day. My personal goal is publish some article across all my various blogs each day of November. That includes the blogs at the Internet Society, my employer.

You - and I - will be able to track how I am doing at my danyork.me site where I aggregate all my posts across all my sites.

We'll see how I do!

And best wishes to everyone else who are pushing themselves to do one of these challenges this year. Let's see the writing happen!

P.S. I haven't signed up for either the BlogHer or Cheerpeppers challenges. I'm just doing this for me right now.

No social network usage until I have created something online.

No Facebook. No Twitter. No Instagram... Ello... Google+... or anything else.

Nothing on any of those each day until I have done something such as:

• Published an article on one of my blogs / sites, including the ones for where I work.
• Published an episode on one of my podcasts.
• Done something else to add content online.

The issue is that I've noticed lately that I've been doing more consuming of content versus creating content.

And as I looked at why, I've noticed that I've been spending a longer time inside of social networks. Before I start my work day I'll fire up Facebook... and 30 or 40 minutes later I emerge. Or on a break I'll scan Twitter or Instagram... and... again time goes by.

Which isn't to say that Facebook / Twitter / Instagram / etc. aren't useful... they definitely are.

But I find I am letting them distract me into consumption of news, updates, etc., instead of creating my own.

So my little experiment is NOT to check any of those until after I've created some content in some form.

Now, I've given myself permission to "cheat" a little in that I might schedule several posts to go out in advance... but the point is to be publishing more than I am doing now.

We'll see how this goes...

Image credit: A few years ago Donna Papacosta posted a photo of this button on her Facebook page. I liked it so much that I printed it out and taped it up on the cross-bar of my office window so that every time I look up from my computer I see that image! The photo is of that image between the blinds that I have covering the window on sunny days.

UPDATE #1 - So on the second day I already failed... I was just getting going and had my phone open checking something else... and bam... I fired up Facebook and started surfing through my Newsfeed. Almost an unconscious action at this point! Will take some re-training to break this habit.

An audio version of this post is now available: