My apologies to Micro.blog users following my feed – I had a comment spam problem arise and could not log in – I have fixed it…

My impressions of the current state of Drummer

I read some comments by Dave Winer on March 15th about users/development of Drummer and how he got little feedback on a feature and how he might go back to just writing software for himself. I also just finished listening to a podcast from March 16th where Dave Winer talks about the need for Drummer users to test new features, or “we can’t move”. As an early tester and user of Drummer, I would like to offer my perspective on these items.

I was one of the early testers of Dave Winer’s Drummer application. I was pretty active in the first month or two, but then I had a negative experience – getting deleted from the Drummer support repo for posting a link to a river of news of Drummer users using Drummer to create blogs. I understood the reason for the deletion (I wasn’t reporting any problem), but I felt the attitude was wrong. As I watched other Drummer users giving opinions on the product, instead of reporting problems, their comments would get deleted, usually after some negative back and forth with Dave Winer. I can understand having rules about participation in support forums, but this consistent pattern gave me the impression that Dave Winer did not want any other feedback except for problem reports on Drummer. To me, this behavior does not give the impression that someone is interested in other people’s opinions. Also, I think if someone is going to criticize others in public, be prepared to stand behind your comments. For people who followed the Drummer support repo, all of this back-and-forth was plain to see via the Github emails.

I spent some time working on developing outline renderer scripts, but got a dig (I think) for using the word “Drummer” in the title of my Github repo. That didn’t feel good. I had started work on integrating a presentation library with Drummer, but decided after that to hold off on investing more. I guess some people can include Drummer in their repo name, but not others.

The first major feature of Drummer to get traction was the Old School blogging tool. Many people gave it a try (including me (original blog and relocated blog when I had a overwrite problem) and there were lots of comments and problem reports. At first, these were welcomed, but within a short period of time, negativity returned. In addition, people posting about the tool or possible changes were deleted or got negative responses. I worked with another Drummer user to create a separate repo (awesome-drummer) to collect information on Drummer, and to provide a place where non-problem-report conversations could occur. Dave Winer created a separate repo called “RFC” – Request For Comments – where people could contribute ideas that could be developed further. There were some user posts there, but most initial posts were by Dave Winer, so it did not appear to have much uptake in terms of suggestions from users. Full disclosure – the awesome-drummer site did not take off either, but at least no one’s comments were deleted for being off-topic…

When Dave Winer rolled out the Daytona search engine, some reasonable initial comments were met with replies like “…people who won’t even read the fucking manual.”, but those “docs” were somewhat hidden in the first days of the release of Daytona. How does this behavior help build a community?

I have worked in software development for 37 years, primarily in small teams in the aerospace industry. If I or other team leads treated team members in the way other Drummer users have been treated in the Drummer development project, I believe they would go find some other project to work on. 

Frank McPherson sums it up well: “Developer yells at users, wonders why then users don’t participate in the development process.”

So how much activity is Drummer getting now? The small flood of users who tried use Old School for blogging have stopped. There are an average of five people who still post to their Old School blogs on a regular basis (from reading the Old School Drummers river of news). New items on the support repo have slowed. This could mean that Drummer is working great. To me, it says that many of the early Drummer users have moved on.

I am glad that Dave Winer made a choice to share Drummer with the world. I am using Drummer to write this blog post. I have a copy of Electric Drummer for Windows, for which I am happy. What I don’t have is a compelling reason to use Drummer. I don’t need another writing tool (strictly speaking), writing in outlines is fun but getting that text into something other than a blog post using the Drummer tool being hosted on someone else’s site is not straightforward (did I mention that the blog is hosted on someone else’s site?). I don’t have a lot of content that could be searched using Daytona, so that is not enticing. Markdown is not part of my workflow, so the work on that feature is not something I am interested in.

There are ways to add functionality through scripting, which is great. Several users did develop some independent features (WordPress integration, Gatsby integration, HTTPS proxy mapping, my outline renderer script), but these did not get much participation from other users. Still, their contributions are still present and available for use.

I get the comment that Dave Winer wants feedback on features. The work I did was a collaboration with two other Drummer users. However, the tone of the podcast comments and the blog post comes off to me as more “demanding” than “asking” or “requesting”. In the end, my impression of Drummer is that this is Dave Winer’s application, a logical outgrowth of his previous work on Frontier and the OPML Editor. It is his application to shape and grow. Other people may not share his vision or interest, but that should not be a roadblock for development, unless Dave lets it be a roadblock. Look at how other development tools have evolved/grown over the past 20 years – a tool scratches someone’s itch, gets some users, gets traction, interest grows, people start to talk about the tool itself, people start making contributions to the tool or environment. Perhaps it will take more time. Perhaps it will take a change in attitude. I don’t know, but I think there are at least two sides to this story.

(Cross-posted from my Drummer blog).

Some perspectives on the Ukraine War

Politico/Fiona Hill: ‘Yes, He Would’: Fiona Hill on Putin and Nukes

We are already, she said, in the middle of a third World War, whether we’ve fully grasped it or not.

“Ukraine has become the front line in a struggle, not just between democracies and autocracies but in a struggle for maintaining a rules-based system in which the things that countries want are not taken by force,” Hill said. “Every country in the world should be paying close attention to this.”

Reynolds: And then there’s the nuclear element. Many people have thought that we’d never see a large ground war in Europe or a direct confrontation between NATO and Russia, because it could quickly escalate into a nuclear conflict. How close are we getting to that?

Hill: Well, we’re right there. Basically, what President Putin has said quite explicitly in recent days is that if anybody interferes in Ukraine, they will be met with a response that they’ve “never had in [their] history.” And he has put Russia’s nuclear forces on high alert. So he’s making it very clear that nuclear is on the table.

NPR/Fresh Air: How Russia’s Invasion Of Ukraine Changes The World As We Know It – Anne Applebaum/The Atlantic

Journalist Anne Applebaum has been covering the war in Ukraine for The Atlantic. “I don’t think that we will ever again smugly assume that borders in Europe can’t be changed by force,” she says. We talk about why Putin takes Ukrainian democracy as a personal and political threat — and how Stalin created a famine to destroy the Ukrainian national movement in the 1930s.

Radio Open Source: Russian Invasion

The panic building around Ukraine is now a deadly modern war in Europe. Vladimir Putin at midweek unleashed a full-scale air-and-ground assault by Russia on Ukraine’s capital Kyiv, and many other points. It’s a compound global crisis as we put this program together. Collaborating with the Quincy Institute in a radio/podcast series we’re calling In Search of Monsters, we will get to some of the history behind the battle for Ukraine and the geo-politics around it. First, a hint of the pain all through it, with the writer Masha Gessen, an eminent activist with two passports, Russian and American. At home in two countries, outspoken in both, Masha reminds you that Vladimir Putin’s assault on Ukraine this week is a devastation to the hearts and hopes of millions.

Substack/Niccolo Soldo: “Fuck it!” Russia’s Final Break With The West – US-Russian joint tactical victory, European and Ukrainian defeat

Celebrations have been taking place in the self-declared Republics of Donetsk and Luhansk in what is almost universally recognized Ukraine. Having declared independence eight years ago, events have now forced Russia’s hand in which these two nascent entities are now recognized by Moscow, with all the protections that come with it. One cannot help but understand why these people are celebrating.

Another celebration is taking place in the USA. The State Department has achieved its main objective of seeing Nordstream 2 put on ice. American LNG producers are now popping champagne bottles as they can envision huge stacks of cash to be made by overcharging Europeans desperate for gas. The Military-Industrial Complex is chuffed as well, as the arms will continue to pour into Ukraine and into the NATO armies in its periphery.

Substack/Tenzer Strategics: This Is Our War: If We Don’t Fight It Now, We Will Lose It – Just Like All The Other Ones

In terms of defense, the fate of Ukraine is decisive not only for the people of that country, but for all those of Europe. There is a kind of security continuum between the NATO countries and Ukraine—and also Moldova and Georgia, and tomorrow Belarus. This security continuum is inseparable from our ideals of freedom and those of these countries.

The attack on Ukraine is an attack on every European country; every Ukrainian murdered by Putin’s regime is a murdered European—just as every Syrian child murdered by the same Putin was a direct attack on the humanity of which each of us is a custodian.

This is our war—and we know what it would mean to lose it in Ukraine. Our historical consciousness would be doomed to sink into ineptitude if we remain in the middle of the ford.

How to organize information for use

Ken Smith had two recent posts (“For the team” and “Or maybe not“), discussing the ideas of forming a community, collecting information on a topic, processing information as a group, and providing a summary of that information. I think the collection and processing tasks are attainable and occur on a regular basis. The task not being performed well is the curate/share/maintain steps.

As an example, I started collecting information on the topic of personal book lists in a Github repo. I provided a chronology of recent posts on the subject, collected tools and techniques, and also created some tools of my own. The recent Github repo for Drummer stuff would be another example, as well as other “awesome-fill-in-the-blank” sites on Github. A mega example of this is a tech guide put together by Stephen Downes on resources for creating an online community, class or conference. 

Perhaps the main thing is to start a “beach-head” of some sort where people can collaborate, then publicize and support that beach-head. Thoughts, anyone?

(cross-posted from my Drummer blog)

Creating A River of News from a Twitter List

I had noticed several people this week posting Twitter lists of people to follow for the Ukraine crisis (journalists/activists/subject matter experts). I know how to follow a Twitter list, but with the Twitter list comes all the other Twitter stuff (sponsored posts, other non-value added things). Since I had the tools available from creating other rivers of news (Old School Drummers, my own reading list and 1999.io bloggers) I followed this process to create a new river of news for following the Ukraine crisis (Politico’s Ukraine Reading List).

  • For each person in the Twitter list, copied their Twitter URL
  • Added an entry in a configuration JSON file (config.json) with the Twitter handle for each person and a RSS feed name based on the Twitter handle
  • Uploaded the config.json file to my instance of tweetsToRss (Node app for creating an RSS feed for a Twitter user timeline)
  • After 10 minutes, checked to see that the tweetsToRss app had created initial RSS feeds
  • After another 10 miniutes, checked to see that my cron job had started copying those RSS feeds to a web hosting location
  • Created a new text file (politicoUkraine.txt) with URLs for all of the RSS feeds, then added that text file to the lists folder in my River5 installation (RSS feed reader)
  • After 10 minutes, checked my River5 console and saw the tab showing those feeds in a River5 file format that I could use for displaying a public river of news
  • Used the files for the Old School Drummers river of news as a base to create the new river of news

If you are interested in more technical details, check out my book Set Up Your Own Platform, which includes a set of chapters on setting up a virtual server and step-by-step details on how to set up the tools to create and manage your own public news rivers.

I am really happy to read that a Windows version of Electric Drummer is in work!