Dan York

Just a guy in Vermont trying to connect all the dots...

Author's posts

Two Major Challenges For Operating Mastodon Servers – Scaling and Content Moderation

The text "2 major challenges" on a blue and white gradient background

As more people embrace the decentralized world of the Fediverse - and as we WANT more people to migrate to the Fediverse - we are seeing an explosion of new Mastodon servers/instances set up by all sorts of people and groups. Friends of mine have launched their own just running in simple virtual machines. There are now “Mastodon hosting” springing up - ex. masto.host, although the person running it has paused new customers due to the high demand.

But there are two major challenges for people or organizations getting into the space:

1 - SCALING - If you just run a small server for yourself and maybe a few friends, you can limit the system administration workload. But if you launch a public server… you have to be able to handle the influx of new accounts, particularly during the current Twitter migration/exodus. This might be very cool initially, but at some point it starts to become a serious amount of work. You have the technical challenges of scaling to support more users - and you also have to meet the expectations of members in terms of availability, reliability, etc. You have to answer their questions, feature requests, etc.

Running a Mastodon server at scale (or really any kind of public server with user accounts) takes a considerable investment of time, energy, and money. You need to think about how you involve multiple people, how you will support all your users, and how you financially support it all.

[UPDATE - It was noted to me that there can be very real technical and cost requirements with growing a server in particular with storing media. Whenever someone uploads an image or video to the server, it must be stored on that server. Additionally, your server will host media coming from other servers with which you are federated. So as your server gains more users, who follow more people on other servers, there is more and more demand for file storage on your server.]

2 - CONTENT MODERATION - This is perhaps the BIGGEST challenge for hosting a public server. If you again run a small server for yourself and people you trust, then this may all be fine. You set clear expectations with your friends or people you think you can trust, and that may be all you need to do.

But the minute you start letting the broader public into your server, you run into all sorts of legal compliance issues you have to be aware of. As the Electronic Frontier Foundation (EFF) recently wrote, there are a range of legal concerns in the USA for operators of any service that hosts “user-generated content”. One big issue is copyright law and the Digital Millennium Copyright Act (DMCA). EFF also mentions FOSTA/SESTA, law enforcement requests for identity information, and child sexual abuse material (CSAM).

And this is just for the USA. Add in the need to potentially comply with European Union (EU) legislation such as the General Data Protection Regulation (GDPR) or the recently passed Digital Services Act (DSA) and Digital Markets Act (DMA). And… the legislation popping up in many other parts of the world. And, of course, your content moderation abilities needs to be able to grow as you scale to support more users.

[UPDATE - Aswath Rao pointed out in a comment on Mastodon that as a server operator its not enough that you trust the people who have accounts on your server. For every person your users follow on other servers, that person’s content and media are also copied onto your server. So you wind up hosting content on your server from all of those other external users, too. ]

These are also just the legal compliance issues around content moderation. You also have to think about what kind of community you want to foster on your server. Will you have additional moderation policies to create the kind of community you want? (For example, specifically not allowing “hate speech”.) If so, how will you then enforce those policies?

You need to again have the time, energy, and financial resources to be able to comply with the legal requirements, which may end up involving some level of monitoring / enforcement.

For both of those reasons, it will be interesting to see where the Fediverse goes - and in particular where Mastodon goes - in the time ahead. Will we continue to have the wide range of public servers as we do right now? Or over time will we see larger ones emerge that have the time, energy, and financial resources to address these challenges?

Automattic Promotes WordPress.com as a Platform for Email Newsletters (and provides improved support)

Screenshot of WordPress.com's page about setting up a newsletter, with the heading "Sign in. Set up. Send out."

Just as Twitter is killing off it’s Revue newsletter service, Automattic is promoting their hosted WordPress.com service for newsletters - and providing some new tools to make that easier. In their announcement blog post, they note that WordPress.com has already had the features to email posts out automatically. This “newsletter” functionality has been there for quite some time. What they’ve done now, though, is to bring those newsletter features together in a new theme - and they’ve also simplified the process of setting up a newsletter site.

[NOTE - this feature is part of the WordPress.*COM* hosted service, not part of the WordPress software (sometimes referred to as "WordPress.ORG”) that you can install on your own servers. However, they indicate that the theme used for this newsletter feature will be made more widely available in the future.]

In the announcement, they mention these features:

  •     Add unlimited email subscribers
  •     Import subscribers from other platforms
  •     Launch with a beautiful, ready-made theme or customize every detail with a myriad of Block Patterns 
  •     Stylize your newsletter with a background image, site icon, and accent color 
  •     Schedule email publishing
  •     Monetize your site (stay tuned for more paid subscription features)
  •     Use a free .blog subdomain or connect a custom domain with one of our paid plans
  •     Publish on the go with Post by Email – making writing a newsletter as simple as sending an email

They also mention that you can start up a new newsletter or add the features to an existing hosted blog.

Giving It A Try

Naturally, I had to try it out. 😀 I started by going to the newsletter page and simply choosing the link “Start building your newsletter”. I logged in with my existing WordPress.com account and was brought to a page to set up my newsletter:

Wp set up newsletter screen

This was simple and easy. After I took the screenshot I added a logo, which needed to be circular. 

Here is one place Automattic will monetize - the “Favorite color” allowed me to use blue for free. Several other colors are available as part of a premium upgrade.

Next they prompt you to set up a custom domain, and offer you some options while allowing for more. You can, of course, skip this (I did in my test) and just use the free default domain they give you.

screenshot of a screen where you can choose a domain to use with your new site.

As I noted, I skipped this part and just moved on to the new screen where I was asked to choose a plan - or start with a free plan.

screenshot of a screen labeled "choose a plan" with sections for the Personal plan at $4 per month and the Premium plan at $8 per month

I chose for the moment to stick with the free plan for this test. After clicking that link, I had one more screen where I could add some initial email addresses and then… ta da… I was at a screen to start publishing

screen shot of a WordPress editor screen and the works "You're all set to start publishing"

 

What Do I Think?

First, to be clear, there is not really any dramatically new functionality here. This is how WordPress has worked for quite some time. Even the field for someone to subscribe has been there as part of the “Subscribe Block”.

All that’s really new is this “Newsletter” theme and some of the onboarding screens.

Having said that… I think it can be a great way to get started with a newsletter!

You have all the power of WordPress editing. You can run it on your own domain. You can use it on your laptop or mobile device.

It’s WordPress!

Now, it’s not clear to me that you will get the kind of statistics that you will get from a Substack, Revue or other newsletter platform. I couldn’t see any way to find, for instance, the open rate, or to know how many people clicked which links. Maybe it’s there and I’ve just missed it. Or maybe there is the expectation that you might use Google Analytics for that as part of a paid plan.

I don’t know… and it doesn’t really matter for me, personally. But I could see people who want to use this as a newsletter platform wanting that kind of information.

My one criticism was with the information about the plans. I couldn’t find any easy matrix showing what I get on the free plan versus the paid plans. I could see the features across all the paid plans… but not how that compared to the free plan. It would be helpful to understand as it might cause me to jump into a paid plan.

All in all I think it is a very useful reminder that WordPress can support these kind of interactions over email.

I may consider moving an older newsletter over to this platform and trying it out in 2023.

What do you think about this news?

Ceremonies of Light and Dark

Fire in firepit

I have always enjoyed our ceremonies of light and dark, here in the cold mid-winter of northern New England.

The winter solstice here is always a time of celebration. For us, it is the shortest “day” in terms of daylight - and the longest night. It is cold here at this time of year.

The solstice gives us hope. From here on out, the days only get longer… and at some point will start to actually get warmer. (We have to go through some much colder periods first, though!)

We celebrate here so often with candles… with fires… with flames… with light to drive away the darkness.

In the Christian tradition, there are the candles of advent, the Christmas trees with their lights, and… today… the many lights that people decorate their houses with. In the Jewish tradition, there is the menorah with its 8 candles that are lit during the days of Hanukkah. In older pagan traditions, there were similar ceremonies of light. Today, in our less religious times, we cover our houses with “holiday lights”. In a school our daughters attended when they were younger, there was a beautiful advent spiral walk with candles.

Many of the ceremonies have different meanings, of course,

Yet each in their own way brings light into a time of darkness.

There is beauty and magic in that.

Mastodon – The Server You Are On Is Most Important When You Are Starting Out

The text "What server are you on?" on a blue gradient background

“How do I choose which Mastodon server to join? It’s SO CONFUSING! I just want to sign up to ‘Mastodon’!” 

This seems to be a common refrain from some people exploring Mastodon as part of the Twitter migration/exodus. 

The reality is that the Mastodon server you join is most important in the beginning when you are trying to discover new users. Over time, and as you follow more and more people, the server you are on becomes less important.

Let me explain...

I routinely point out to people asking these questions that it is a lot like choosing your email provider - do you use the email address your ISP gives you? Or Gmail? Hotmail? Yahoo mail? Protonmail? Or even run your own email server? 

No matter where you have an email address, you can send email to anyone else using email. Similarly, when you sign up on a Mastodon server (or “instance” to use the older term), you can view and interact with people on any other Mastodon server.

But that still doesn’t seem to register for some folks in an era when we are used to centralized, monolithic social platforms. You just join Twitter, Facebook, Instagram, or… whatever service. Mastodon is different - you have to make a choice.

I’ve been using Mastodon since December 2016, and in my opinion, which server you are on really matters the most when you are first starting out and seeking to discover new users. Here’s why. In your Mastodon view on the web or in apps, there are three “timelines” (or “feeds”) that you can view:

  • Home - all the posts (or “toots”) of people you follow
  • Local - all the posts of people on your local server
  • Federated - all the posts of people across the Fediverse who are followed by people on your local server[1]

When you are starting out, your home feed will likely be pretty empty, and so Mastodon will be a bit of a ghost town to you. What’s the point of going into it if you only see a couple of posts?

This is where the Local and Federated timelines are important. They help you discover new users to follow.

With the Local timeline, you get to see posts from all the people on your server. So if, for instance, you join techpolicy.social, you will discover posts and people to follow interested in technology policy. If you join mastodon.art, you will discover more people interested in art. If you join fosstodon.org, you’ll discover posts and people interested in free and open source software. If you join ipv6.social… you guessed it, you’ll discover people interested in IPv6. 😀

Beyond the Local timeline, the Federated timeline will help you discover all the Mastodon users on other servers that people on your server follow. So on techpolicy.social, odds are that you will discover other people interested in tech policy, as well as probably tech news sites, and all the other kinds of accounts people there follow. If your account is on mastodon.art, your Federated timeline will probably tend to have more artistic people mixed in. On fostodon.org, your Federated timeline will probably have more people using Linux, developers, and people advocating for free and open source software.

By viewing the Local and Federated timelines, you can find people to follow!

Each person you follow will then start to appear in your Home timeline.

At some point, you will follow enough people that your Home timeline is all you really need to pay attention to. There are sufficient people posting that you only really have the time to read your Home timeline.

The Local and Federated timelines aren’t as important any more. I mean… you still might dip into them from time to time to see if there are new people to discover, but you don’t really need to do so anymore.

This is the key point. The server you choose to join is most important in the beginning when you are trying to find people. But you don’t have to worry too much. Pick one you like and start there.

Over time, much like what email server you are on, it won’t matter quite as much.

-----

[1] Yes, it’s a little more complicated than that, but I’m simplifying for the purpose of this article.

The Term "Weblog" Is 25 Years Old Today

The phrase "Weblog is 25 years old" on a blue gradient background with a birthday cake emoji below it.

By way of a Mastodon post this morning, I learned that the term “weblog” is 25 years old today! 

The Wikipedia article for “Blog” says that the term was coined by Jorn Barger on December 17, 1997. Reading the Wikipedia article about Jorn Barger, we learn:

On December 17, 1997, inspired by Dave Winer's Scripting News and running on Winer's Frontier publishing software, Barger began posting daily entries to his Robot Wisdom Weblog in the hope of finding "an audience who might see the connections between [his] many interests." These postings featured "a list of links each day shaped by his own interests in the arts and technology," thus offering a "day-to-day log of his reading and intellectual pursuits” and coining the term "weblog" as a novel form of web publishing.

At two syllables, “weblog” was of course ripe for shortening and so did evolve into “blog” just a couple of years later.

A “log of daily activities published on the web” became a “weblog” which then became a “blog”.

I started what we now call “blogging” back in 2000 on a site called Advogato that actually referred to your content as a “diary”. But I do remember well that other sites were hosting “weblogs” and “blogs”.

Pretty wild to think that was 25 years ago! Happy Birthday to “weblog”!

Google IPv6 stats consistently peaking over 40%

When I looked at Google’s IPv6 stats recently, it was great to see that the peaks are now consistently all over 40%. Back in January, I wrote about crossing the 35% threshold, so there’s been a 5% growth over the space of the year.

Would we who advocate for IPv6 want it to grow quicker? Of course! And if you look at the per-country page, you can see that it has grown quicker in some countries than others.

But hey… we’ve been at this for a long time, so I’ll celebrate that 5% growth this year! Let’s see if it keeps on going more next year!

P.S. If you want another source of IPv6 statistics, colleagues of mine at the Internet Society are involved with measuring IPv6 on our Pulse measurement platform.

Google IPv6 stats consistently peaking over 40%

When I looked at Google’s IPv6 stats recently, it was great to see that the peaks are now consistently all over 40%. Back in January, I wrote about crossing the 35% threshold, so there’s been a 5% growth over the space of the year.

Would we who advocate for IPv6 want it to grow quicker? Of course! And if you look at the per-country page, you can see that it has grown quicker in some countries than others.

But hey… we’ve been at this for a long time, so I’ll celebrate that 5% growth this year! Let’s see if it keeps on going more next year!

P.S. If you want another source of IPv6 statistics, colleagues of mine at the Internet Society are involved with measuring IPv6 on our Pulse measurement platform.

Au Revoir Revue! Twitter to Kill Off Newsletter Service at End of 2022 – I Guess I Need To Move My Newsletter!

 

The text "Au revoir revue" on a blue background

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:

screen shot of a Twitter feed showing a newsletter box in the feed

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!

 

New collaborative book about IPv6 – available for free, and seeking contributors

screenshot of the readme page for a GitHub repository about a collaborative IPv6 book

Why is it that many of the “IPv6 books” are 10+ years old? Where can you find the most current info? Could a group of people using IPv6 today come together and create a new book about IPv6?

Brian Carpenter asked those questions … and then started a project on GitHub to do exactly this – create a “collaborative IPv6 book”. The idea is to capture current knowledge from people working with IPv6 – and then keep it up-to-date.

So far he’s had a number of people contribute text – and the work is underway. As the repository states:

The intention is a practical introduction to IPv6 for technical people, kept up to date by active practitioners.

The book will be available free of charge (and free of advertising) on-line, possibly with an option to obtain a printed copy at cost price.

This GitHub repository is a starting point. It may be replaced by a differently structured repo as the work progresses and we gain experience of how to do it.

You can read the book online, with the caveat that it is still very much in development. If you want to contribute text or edit, there are contributor guidelines that explain the process.

I think it’s great to see another book emerging, and I look forward to seeing how this collaborative model works for all involved.

New collaborative book about IPv6 – available for free, and seeking contributors

screenshot of the readme page for a GitHub repository about a collaborative IPv6 book

Why is it that many of the “IPv6 books” are 10+ years old? Where can you find the most current info? Could a group of people using IPv6 today come together and create a new book about IPv6?

Brian Carpenter asked those questions … and then started a project on GitHub to do exactly this – create a “collaborative IPv6 book”. The idea is to capture current knowledge from people working with IPv6 – and then keep it up-to-date.

So far he’s had a number of people contribute text – and the work is underway. As the repository states:

The intention is a practical introduction to IPv6 for technical people, kept up to date by active practitioners.

The book will be available free of charge (and free of advertising) on-line, possibly with an option to obtain a printed copy at cost price.

This GitHub repository is a starting point. It may be replaced by a differently structured repo as the work progresses and we gain experience of how to do it.

You can read the book online, with the caveat that it is still very much in development. If you want to contribute text or edit, there are contributor guidelines that explain the process.

I think it’s great to see another book emerging, and I look forward to seeing how this collaborative model works for all involved.