Author Archives: Michael Descy

Eye Round Roast Recipe

Notes

At my local grocery store, eye round roasts are relatively cheap and plentiful in the cold weather months. They are all cut to just over 2 lbs, as well, so this recipe works pretty well for me. If your roast is larger, set the oven’s “on” time to 5 minutes per pound.

The exact measurements of the spice rub are not important, but it should consist of mostly salt. It is important to heavily salt the roast and to let it sit at room temperature for at least an hour prior to putting it in the oven. If the roast is too cold, it will not cook through properly.

I have found that these roasts leave enough fat in the pan to allow me to make a pan gravy with just a bit of flour (about 1 tbsp) and 1 cup of liquid (often just beef broth). (It there isn’t enough fat left over to make a roux, add butter to the flour.)

Ingredients

  • 1 eye round roast, 2 1/4 lbs
  • 4 tbsp kosher salt
  • 1 tsp freshly ground black pepper
  • 2 tsp onion powder, 2 tsp
  • 1 tsp garlic powder
  • 1 tbsp olive oil

Directions

Dry off roast with paper towels.

Create a spice rub by mixing the kosher salt, black pepper, onion powder, and garlic powder. Coat the roast on all sides with the spice rub. (You will likely not use all the spice rub.) Let it sit at room temperature for 1 hour.

Set an oven rack to the middle or upper middle position. Heat the oven to 500º F.

Coat the roast with a thin layer of olive oil and place it on a pan. A 12-inch cast iron or stainless steel skillet works fine. A rack is optional.

Put the pan in the oven and roast it for 10 minutes, or about 5 minutes per pound. Then, shut off the oven, and do not open it for 2 hours.

After 2 hours, the internal temperature of the roast should be about 145° F. Set the roast aside and, optionally, make a pan sauce from the drippings.

Chicken Sausage and Escarole Soup Recipe

Notes

This is a hearty, pasta-free soup, fit for a winter meal. Lots of vegetables, sausage (either chicken or pork sausage can be used), and cooking liquid from cannellini beans (canned or homemade) lead to a chunky, filling soup with a rich mouth feel.

Developing a fond while cooking the sausage will add an important foundation to the soup’s flavor. Deglazing this fond early, before cooking the vegetables in the same pot, will prevent it from burning.

Ideally, the vegetables should be soft but not browned; if they are not softening sufficiently during the sauté, simmer them longer in the broth, rather than extending the sauté.

You can substitute your preferred herbs for the Italian seasoning that I use. If using fresh herbs, add them at the very end, or just before serving.

If you wish to add pasta, ditalini works well. Cook the pasta separately, and add it just before serving, to avoid the pasta absorbing too much of the broth during cooking or storage.

Ingredients

  • 1 12 oz package chicken sausage
  • 1/2 cup water or chicken broth, for deglazing
  • 2 tbsp olive oil
  • 1 cup chopped carrots
  • 1 cup chopped celery
  • 1 cup chopped yellow onion
  • 1 7 oz bag fresh chopped escarole
  • 2 15 oz cans cannellini beans, not rinsed or drained
  • 8 cups low sodium chicken broth
  • 1 tsp Italian seasoning
  • Salt and pepper, to taste
  • (Optional) Fresh squeezed lemon juice, to taste
  • (Garnish) Freshly grated Parmigiano-Reggiano cheese

Directions

In a large pot or Dutch oven, brown the sausage in 1 tbsp of olive oil for 4 minutes per side over medium heat. This will likely not cook it through, which is fine; it will cook through later in the soup. Remove the sausage and set it aside.

Deglaze the pot with 1/2 cup water or chicken broth. Retain this liquid in a cup or bowl; it will be added back to the soup later. If the retained liquid contains any solids, strain it to remove them.

Once the par-cooked sausage is cool enough, cut it into coins and set it aside, to be added back to the pot later.

Dry out the pot and add 1 tbsp olive oil. Sauté the onion, carrots, and celery over medium heat until they are soft but not browned, about 10 minutes. If the vegetables are not completely soft after the sauté, that is OK; they can be softened after the liquid is added. Add the escarole and Italian seasoning and stir everything to combine.

Add the chicken broth, and add back the retained liquid from deglazing. Raise the temperature to high until the broth starts to boil; then lower the temperature to medium or medium low, to maintain a low simmer. Simmer until the vegetables are soft, which can take 5 to 10 minutes.

Add the cannellini beans, including their cooking liquid, and the sausage. (These ingredients are added later to avoid overcooking them, which would lead to split beans and tough sausage.) Continue to simmer until the sausage is cooked through, which will take only a few minutes.

Season the soup with salt and pepper to taste. If, at this point, the soup tastes dull, add some fresh squeezed lemon juice, little by little, until the broth tastes as bright as you want it to.

Serve topped with finely grated Parmigiano-Reggiano cheese.

Plaintext Productivity: Still productive after all these years

I am still using the Plaintext Productivity system that I wrote about in 2013. It is a productivity system, based primarily on plaintext files, for Microsoft Windows users. Since I published a few people have asked me to write an update to Plaintext Productivity. The fact is, the system has held up so well for me that I really don’t have any updates to report.

One reason my system remains pretty much the same as it was in 2013 is that the operating system it is based on, Windows, despite some cosmetic changes, remains pretty much the same as it was in 2013. Sure, it got a better UI when Windows 10 supplanted Windows 7 and 8, but Windows still works just as well and just as poorly. Another pillar of the system, Sublime Text, also had a design change recently, to display more crisply on high-DPI screens, but it, too, works pretty much the same as it did in 2013.

A little bit of history

I developed my Plaintext Productivity system slowly over the years, as a result of the limitations I faced on my relatively locked down work computers, and my frustration with third party productivity apps going out of business and disappearing over the years. Gradually, I stripped down my productivity system to a great text editor and a todo.txt-format task list (with a good client), with some clever ideas about using a journal for planning, and for managing files.

Because I was stuck on Windows, an operating system I did not particular like, I had to make do with built-in functionality, portable apps that I could sneak onto my system, and a universal file format: plaintext. Even this was challenging. Windows, for all it’s ubiquity, has a dearth of good third party (non-Microsoft) software for it. There is a lot of crapware in the Windows Store, several world class apps from Adobe that everyone knows about, and not that much in between. Macintosh, iOS, and to a far lesser extent, Android, have attracted the attention on small, boutique publishers and indie developers who have contributed great plaintext-based apps. Like me.

Notes and drafts

I still firmly believe in writing lots of notes and drafts to help document thoughts as well as meetings. I draft emails, write planning documents, write out procedures for work I have to repeat, and so on. I also keep a work journal every day (well, I’m not perfect about writing it every single day, but I try). At the start of each workday, I write a short journal post to plan my top activities for the day. At the end of each workday, I wrote an even shorter journal entry to help remind me where I left things, which sets me up for the next day. I set up calendar entries to remind me to do these journal entries. These activities help keep me, a person who works remotely and alone, organized, engaged with my work, and on task throughout the day.

My text editor

Sublime Text is still my favorite Windows text editor. It is even better than when I first bought it, over five years ago, and it was worth every penny. I love that it is lean, fast, flexible, and handles both my short notes and huge data files with aplomb. Its plugin system makes it a serviceable Markdown editor. I have syntax highlighting for Markdown, HTML, todo.txt, TaskPaper, and the various programming languages I use at work: ACL scripts (which I created myself), SQL, C#, VBScript, and Python (and there are far more available).

Best of all, in my opinion, are its numerous, well-defined keyboard shortcuts for shifting lines around, selecting words, selecting whole lines, deleting whole lines, and so on. Its support for multiple text selection and multiple cursors makes certain quick edits, like making a bunch of lines a bullet list in Markdown, a snap; it’s actually kind of mind blowing when you get used to it. Lastly, I=its find and replace functionality is incredibly powerful as well, considering it supports regular expressions.

I have found no compelling reason to switch it out for a newer, shiner app—which is the whole point of having a simple productivity system in the first place.

I should say, though, that I do use Editorial or Ulysses on my iPad as a sidekick text editor quite frequently. I started to do so for a non-software related reason: my work machine’s mechanical keyboard is so loud that it bothers people on conference calls, while my iPad’s keyboard—the Apple Magic Keyboard—is so quiet that my phone does not pick it up. Those iOS apps are fantastic, but they are not vital to my Plaintext Productivity system.

My task list

I still use todo.txt for my work task list. Since I wrote Plaintext Productivity, I contributed a ton of patches to my favorite Windows todo.txt app: todotxt.net. I contributed multiple task selection and editing, and a lot of other things. I went on to write Mac and iOS todo.txt apps, SwiftoDo Desktop and SwiftoDo for iOS. I tend to use SwiftoDo for iOS most of the time, and revert to todotxt.net only when I don’t want to context-switch away from my PC to my iPad or iPhone. My todo.txt file is synced via Dropbox between all these apps, so it doesn’t really matter which app I use at any given moment.

Todo.txt is the best system for me because my work, and my GTD-inspired way of looking at my work, tends to present itself as a large number of tasks that get picked up, dropped, and re-prioritized frequently. I have started to dabble with TaskPaper for some of my planning needs, either in my daily work journaling, or when I have a self-directed project to plan, such as drafting a proposal or creating a software-based audit tool. TaskPaper is interesting, but I do too much sorting and filtering of tasks throughout the day for it to supplant todo.txt as my main task list system.

I don’t keep track of every task in my life in todo.txt, however. I prefer to keep my personal tasks separate from my work ones, mainly because I find having them commingled with work tasks distracts me from my work. Therefore, I keep my personal tasks in Reminders, which has had solid Siri support and cross-Apple-device syncing since 2011, and has only gotten better since then. I have changed a lot about how I managed non-work tasks since 2013, but those fall outside my Plaintext Productivity system.

Filing and searching

I still use the same filing system, too, and have been consistently happy with it. While I believe that you should rely on search rather than elaborate folder structures for finding what you need to, Windows Search still is not great. Despite its weaknesses, and the frustrations those weaknesses sometimes cause, I still get by with it.

Hardware and other things

I also wrote about hardware and other things in Plaintext Productivity. Since 2013, I have had the fortune to upgrade my keyboard to a 87-key mechanical keyboard with Cherry MX Blue switches. I really like the clicky-clacky keyboard switches and the keyboard’s smaller size, which I credit with helping eliminate repetitive stress injuries in my wrists. I also made things easier on my eyes by upgrading my display from two 1080p monitors to one, much bigger, 4K display. Crisper text has reduced eyestrain and has made me much happier, though Windows has had, and still has, awful and inconsistent high-DPI support. I don’t miss having two screens at all, actually. I can tile two to four windows on screen, and use the virtual desktop feature that premiered in Windows 10, to get most of the benefits that multiple monitors afforded me in the past.

The future of plaintext productivity

I have never used the same productivity system for so long. It has been solid and reliable for me for years now, and required no real tweaks worth mentioning when upgrading from Windows XP to Windows 7 to Windows 10. I see no obvious need to replace or upgrade my system in the near future, either. Maybe someday, when everything is in virtual reality or something—but maybe not even then.

If you are interested in streamlining your Windows workflows, and discovering a productivity system that really lasts, I encourage you to check out my Plaintext Productivity guide.

Instant Pot Salsa Chicken Recipe

I’m posting this for the benefit of Traci on Micro.blog.

This is a simple, lazy recipe for the Instant Pot. It isn’t entirely original, but it is extremely useful, and produces a result that everyone in my family will eat, which is no small feat.

I don’t measure anything. If I don’t have salsa, I dump in tomato sauce or even just water; the result is more bland, but still edible, and it can be shredded and mixed with barbecue sauce if desired. I make this in the morning or at lunchtime and let it stay on Warm for hours and hours until dinnertime. I find the taste of chicken thighs improves after a couple hours on the Instant Pot’s Warm setting.

Ingredients

  • 6 chicken thighs
  • 1 cup mild or medium salsa (eyeballed)
  • 1/4 cup water (eyeballed)
  • 2 large pinches kosher salt
  • 2 tbsp olive oil

Directions

  1. Oil bottom of Instant Pot.
  2. Coat bottom of Instant Pot with 1 pinch of kosher salt.
  3. Add chicken thighs in one layer
  4. Season top of chicken thighs with 1 pinch of kosher salt.
  5. Cover with salsa. Add water if salsa is not very liquid.
  6. Lid the Instant Pot and cook under high pressure for 20 minutes.
  7. Allow pressure to release naturally. The Instant Pot will automatically switch to its Warm setting. Keep the chicken thighs on the Warm setting as long as you would like. The chicken tastes better after several hours on Warm.

Picking a great writing font

One thing to do when you’re supposed to be writing is to fuss about your writing environment.

Not wasting time

Choosing the perfect writing font is a classic way to procrastinate—but it is not a waste of time. Fonts are important. A good font is not only highly legible, it also conveys a subliminal emotional effect on the reader. Naturally, it follows that it will also have similar effects on the writer. A good font will make you feel better while you are writing—maybe because you can read it more easily, or because you find elements of it, its curves or serifs, aesthetically pleasing. Whatever the reason, picking a font that is pleasing can have a profound effect on your writing.

What makes a good writing font?

For me, as a writer and programmer who began typing text on a computer in the 1980s, I gravitate toward monospaced fonts. Every character in a monospaced font has the same width. This is useful in programming or for data files, because, in those uses, you often want to align columns of text. It is not useful at all in typesetting books, of course; text laid out in monospace fonts looks primitive and wide-open. Primitive and wide-open, however, are perfect attributes for text that I am writing, breaking apart, moving around, and recombining. Writing in monospaced fonts is, on a subconscious level, freeing. It helps me feel like nothing in my text is set in stone.

Considerations

Whether the font is monospaced or proportional is only part of what is important. Other things matter, too: the shapes of the characters; whether they have serifs or not; whether some look identical to others (l vs. 1, or O vs. 0, for example); and so on.

Beyond that, some fonts render better on screen than others. For example, Verdana and Georgia were commissioned by Microsoft specifically to be look good, clear, and legible on screens, rather than on paper. This was revolutionary at the time, as was their free-to-use licensing. Consequently, these two fonts were adopted almost everywhere on the web for a while. Georgia is still one of the eight font options in Apple’s iBooks ebook reader.

Your particular display and operating system have a lot to do with what font looks good. In general, displays are much higher resolution and much higher quality now than when Verdana and Consolas were invented. As you might expect, this means that all all scalable fonts look better on modern, high-resolution displays. Still, some fonts will look much sharper than others on some displays. For example, on my Dell 27” 4K display for my work machine, a Windows 10 laptop, Consolas looks the best for the terminal and any coding I am doing, and Sax Mono looks better for writing actual documents. These fonts don’t offer similar advantages to me on my Mac or on iOS, however. They look fine, but they really pop for me on my work machine.

My favorite writing fonts over the years

There are tons of monospaced fonts available. Here are a handful that I have used over the years, with the platform I used them on in parentheses. I recommend trying them in your text editor, especially the newer ones listed at the bottom.

  1. Monaco (Mac)
  2. Menlo (Mac)
  3. Consolas (Windows)
  4. Source Code Pro (Windows)
  5. Droid Sans Mono (Windows, Android)
  6. Sax Mono (Windows)
  7. IBM’s Plex (Mac, iOS, Windows)
  8. iA Writer Duospace (Mac, iOS)

These are listed in the order in which I have adopted them. I tend to use only a few at a time, depending on which one looks best on my hardware and software at the moment. Below, I highlight two of my favorite, very much related, fonts for writing these days: Plex and iA Writer Duospace.

IBM’s Plex

IBM released Plex, an open source font that will be used in all of IBM’s published materials going forward, in late 2017. It isn’t the only open source font that’s free for anyone to download and use, but it is a really good one. Plex Mono, its monospaced variant, looks fantastic on my iPhone, iPad, and Mac. Its edges are crisp, and the stroke has a consistent width; it looks like the lines fit just right in the pixel grid that makes up the screen.

iA Writer Duospace

The iOS development company iA took IBM’s Plex Mono and tweaked it a little bit to make it even better, in their opinion, for writing. They kept the font monospaced except for M’s and W’s. It’s a pretty simple change, but a lot of thought went into it. iA Writer’s article about this process is absolutely fascinating—I highly recommend reading the whole thing.

The resultant font, iA Writer Duospace, looks great on my MacBook Pro. I prefer Plex Mono on my iPad and iPhone, though. There is something about the wider W and M that looks different in the two platforms. It could just be that my iOS screens are a lot smaller, and width is at a greater premium. It could also just be that I prefer my letters to line up vertically, especially when my text is constrained to a narrow column.

Perfect, for now

For now, I am very happy writing in Plex and iA Writer Duo on my Apple devices. I still happily use SaxMono and Consolas on the PC for writing notes and coding, though Plex Mono is starting to creep into use for my todo.txt file and in other places. Every year or two I look for something better, but I probably won’t change from these four main fonts until I get new hardware, which could change how everything is rendered, but that is probably a long way off.

Things I wish I could stop doing, but probably can’t

The beginning of the year is a time for setting goals. I have set some goals, and may post them here later. This list, however, represents my anti-goals—my to-don’t list, if you will.

  1. Lamenting failures rather than celebrating successes
  2. Being more interested in process than product
  3. Talking myself out of things
  4. Planning a project, rather than starting it
  5. Drafting blog posts, but never finishing them
  6. Letting important things pile up
  7. Not letting unimportant things go

These are my bad habits and bugbears, the blocks in my mind that frustrate me and prevent me from achieving my full potential.

These are the vampires that I have let in. They are no longer welcome.

Top posts of 2017

I started this blog in the summer, and since then I have published 30 posts, including this one. As far as output goes, I have met my goal, and I am happy with that.

Most popular posts

In the spirit of publishing year-end best-of lists, here are my top five most popular posts from 2017:

  1. Ulysses, a peerless writing tool, a short essay about my favorite writing software. I love good software, and think way too much about what makes productivity software, well, more productive.
  2. Choosing an iPad Pro Keyboard, in which I compare three of the main keyboards iPad users like me might be considering.
  3. Comparing todo.txt and TaskPaper formats, which are two plaintext task list formats. I love plaintext, love productivity software, and love not having lock-in with proprietary software vendors. I have been using both formats for different planning and task management tasks at work all year.
  4. Three ways to create nested projects in todo.txt, which addresses a common problem with the todo.txt format.
  5. Contexts in Getting Things Done, in which I describe the challenges I faced dealing with contexts in the GTD system.

These posts reflect some of my main interests: productivity software and systems, and Apple hardware. I have also written a little bit about Android, the Essential Phone, and parts of the free and open web that interest me.

Thoughts on the writing process

One thing that I have learned this year, from writing regularly again, is how much work it can be to complete a blog post. I have a half-dozen incomplete blog post drafts in my Ulysses library at any given moment. Shaping them into something worth reading is a lot of work—work that I don’t often complete as quickly as I would like. Even a simple 500-word post has to be written and re-written three or four times before I think it is worth publishing.

The writing process is valuable to me, though. Writing is a lot different than analyzing data (my day job) or writing code (my nighttime hobby). Writing, re-writing, and revising help me think and help me focus in ways that my more mathematically-focused activities do not. Plus, it feels good to communicate to the world, and to own all the content I produce and publish it on my own platform, under my own name.

The future

I plan to blog regularly in 2018, both on this site and on mjdescy.micro.blog. I have even set up regularly scheduled reminders (Apple Reminders, naturally) to help keep me on track. Thanks for reading.

Micro Blog

I started a micro blog at mjdescy.micro.blog this week. It is not to replace this blog, but to supplement it with a more frequently updated stream of short comments and asides about my life, or about news items that directly affect my life in some way. I want it to be like Twitter was for me back when I first joined it: a stream of consciousness, and a window into my life. My plan is to keep this blog (my macro-blog?) free of micro blog posts and life blogging, and more focused on longer articles, bigger ideas, and more complete thoughts—as it has been from the very start.

Drafts for iOS

Drafts is a tinkerer’s DIY dream of a text editor. It nails the basics, and allows you to customize its editor and its tag and folder system to fit your specific needs—it just takes a little time (and, maybe, some JavaScript skills, for some things) to do so.

Drafts is where text begins

Drafts, by Agile Tortoise, isn’t exactly an unknown app. On the contrary, it is one of the crown jewels of the iOS platform. It is one of the few apps with an in-app purchase tip jar that I actually threw money in—a few times, actually. Drafts makes my life simpler, in little ways, every day. Like one of my other favorite writing apps, Ulysses, it is a pleasure to use.

Drafts is primarily meant for quick text entry, and then pushing that text to another app for processing or storage. For example, I type most calendar entries and Google searches in Drafts (which is in my home screen toolbar) and, in two taps, open them for processing in Fantastical or Safari (which are not in my toolbar). Drafts 4, which has been out quite a while now, expands on that basic idea, and delivers a very useful utility and a top-notch text editor.

Not just for automation—for writing!

Drafts is already well known for its automation capabilities. It is great for drafting a tweet and posting it to Twitter (either natively or via another app), or for writing out a calendar entry and pushing it to Fantastical or Calendars 5 for parsing. What it is not well known for—but should be—is that it is the most customizable text editor on iOS. Editorial has long held that crown, thanks to its its support of snippets and extensibility with Python scripts. Drafts, however, outdoes Editorial when it comes to customizing the editor itself, which has a profound effect on writing experience.

In Drafts, actions can change the text your are writing, send some or all of it to another app, turn on/off night mode within the app, and so on. You can download actions from the developer’s extensive library, of, if you are a bit of a programmer, you can them yourself in JavaScript, from within the app. You can assign these actions to the main menu, which is accessible from the top-right icon, or from a swipe to the left. That’s the basic stuff. You can also assign these actions to a custom toolbar that is displayed over the keyboard. Even better, for hardware keyboard users, you can assign your own hardware keyboard shortcuts to these actions, too. No other iOS app that I use does this!

I use Drafts on my iPad primarily for writing notes, such as when I get a phone call or am in a meeting. I use my custom toolbar buttons to input today’s date, paste text, format headings and lists in Markdown, send various lines (text selections) to my todo.txt file (via Dropbox), and so on. At the end of my writing session, I send the entire note to Dropbox for storage.

Notes don’t have to be exported, however. They can stay in Drafts and sync to all your other iOS devices via iCloud. You can also organize them there. There are three basic folders—Inbox, Archive, and Trash—to put notes into. You can flag notes for future retrieval, and filter them them by folder, flag status, and keywords (search terms within the note text) into custom “folders” or saved searches as well. I have not switched over to using Drafts as a full-fledged notes app (most of my drafts get automatically deleted after 30 days in the Trash folder), but I am thinking about it.

Drafts in the future

Drafts 4 has been around for a while now. Drafts 5 is coming, someday, with even more features: TaskPaper editing is a feature that I am looking forward to. I expect the pricing model to change from paid upfront to a subscription; I will be happy to pay for it, as a valuable companion to Ulysses for writing, and a valuable sidekick to practically every other app in the iOS ecosystem.

What I want is Twitter that isn’t Twitter

I love Twitter. So much information and commentary is shared there, so quickly, that it is a vital source for “what is going on on the Internet today”. At the same time, I hate Twitter, for all the bad behavior performed on the platform that Twitter, the company, tolerates. I’m not alone. A lot of people I follow feel the same way. I see tweets like this almost every day:

Brad DeLong: “I wish there was a network like twitter, but not, you know, actually Twitter”

 

The thing is, practically since Twitter’s inception, alternatives did exist. I know. I used them: Identi.ca, StatusNet (the successor to Identi.ca), Pump.io (the successor to StatusNet), and App.net (a for-fee Twitter that got a lot of press but not so many users). And, I abandoned them and went back to Twitter, despite its flaws. So did everybody else.

Why is Twitter so sticky, and nothing else is?

What makes Twitter is valuable not what it does—microblogging is relatively easy to implement these days—but who is on it: Famous people! Intellectuals! Politicians! Journalists! These people and many more are not only publishing there, but reading there, too. Communication with, and between, influential people there can be two-way, and is usually in public, which is fascinating to read and unlike any other communications platform that had come before it. Twitter can amplify the voice of the non-famous and non-published people, too—the under-represented—which is often great.

Why is Twitter described as a cesspool?

Sometimes, though, amplifying under-represented voices is not great. Some voices are under-represented because they are malicious: Racists! Nazis! Liars! Sexist doxxers! Spammers! Russian bots! Malicious people have unique incentives to exploit and abuse a communications platform like Twitter. First, simply having a medium and a platform to spread their message is unique to them, because these people have been barred or banned elsewhere from spreading their message. Second, access to this new platform may be fleeting, because they could be banned there, too, for the same reasons they have been banned elsewhere. Third, people who want to spread malice are not the type of people who are concerned with preserving the health of the platform’s community, or the platform’s reputation in the wider world. Therefore, they can destroy the platform in the process of spreading their message.

Why can’t Twitter fix this?

The world is too complex to separate people, or Twitter users, into good and bad actors. What is unpopular or under-represented today may be celebrated tomorrow; it may be true and worth spreading today. Understandably, Twitter doesn’t want to choose who gets to speak on their platform. Therefore, they tolerate hate speech on their platform to a degree that makes some of their users angry. It puts the company in a difficult position when hate speech is broadcast (retweeted) by the President of the United States, as it was this week.

I understand Twitter’s problems as a company. It needs eyeballs on it to sell ads. Controversy on the platform, and the sheer number of active users (whether they are real people or bots), lead to greater traffic, greater revenue, and greater return on investment for their investors—at least in the short run. In the long run, however, poisonous speech on the platform poisons the platform.

What to do about it, as a Twitter user?

Basically, it is hard to see how, as users, we can improve Twitter. Twitter, the company, owns the platform. Consequently, it has the sole power to fix its flaws. Improvements to blocking and reporting abuse that Twitter has implemented have not satisfied the users who need them the most.

Moving away from Twitter entirely, onto another, similar platform, can work for small communities who primarily wish to communicate amongst themselves. It is unlikely, however, that a critical mass of influential users—the celebrities, journalists, etc., who make the platform valuable—will move to a different platform at this point. Without those users, another platform, however superior from a technical or community management standpoint, would not have as much value.

As a Twitter user, you really have two choices now: live with the abusive users, and report and block them as well as you can; or, if Twitter abuse is bothering you enough (or worse, threatening to your safety), stop using Twitter entirely. That is a sad conclusion to make, but I think it is realistic. Twitter’s ad-based model, need to generate both traffic and return on investment to satisfy its shareholders are, in the short run, at odds with its stated goal to improve safety, and therefore community, on its platform.

Fortunately, there are other ways to write content on the internet for free, such as WordPress. The problem is, you may never achieve the same reach with these other platforms as you would with Twitter. That is why I am sticking with Twitter myself. From a moralistic point of view, I would love to ditch it for something else. Despite that feeling, I get enough value from Twitter to keep using it, despite the sick-to-my-stomach feeling the Twitterverse gives me some days.