A new service is coming online, and I want Drummer users to be the first to have a chance to try it out.#
For people who were part of the initial test group this will be familiar. It was initially developed inside Drummer, but I figured out that it would work better if it ran on a server, so I punted on the feature, to get back to it after the product shipped.#
If you write in an outliner, and use Twitter, now you can have all your original tweets (not RTs) in a calendar-structured outline, that updates on its own. #
This means if you're out and about and get an idea you want to include in your writing, just write a tweet, and when you get back it'll be in Drummer.#
No. It's for anyone with an OPML-compatible outliner, which for now effectively means Drummer. But I want to this to be open to all, the same way RSS feeds are open to all. You didn't have to use Radio UserLand to read feeds when RSS was booting up, and the same thing is true of OPML today.#
Post something to Twitter to get things started. Wait a few minutes. #
On the home page there will be a link to your OPML file, grab the link, switch into Drummer and enter the address into the Open URL command in the File menu.#
Next time you tweet, after as much as three minutes (that's the interval between checks, it may go up over time as more people use the service) the tweet should show up in the outline on GitHub, and in Drummer. #
There are still a few things I want to add to this, but the service is fairly complete. I think it works. But in case it doesn't or if you just want to ask questions about the design, or what it can be used for, I started a thread on the Support site. #
The next problem I want to tackle, left over from before shipping, is making Drummer able to recognize that there's a copy of itself running on another machine, and sending it message to turn itself off, so as to avoid version problems. #
I've got new code in the server that sends a "goodnight" message to such extraneous copies of Drummer. To be clear, not just on the same machine (as it currently works) -- no matter where it is. #
Also I want it to do something more appropriate than switching to the About Drummer page from the docs. I think I figured out how to do that too.#
This is a tricky corner-turn. If for some reason it doesn't work properly, and of course Murphy's Law says that it won't, mayhem could result and that would suck. #
So here's the deal, if you want to help validate this, let me know by responding to this item, and in a couple of days we can start testing this functionality. Once it appears to work properly, then I can "arm" the feature. But I want to be extra-extra careful with this fix. #
A new service is coming online, and I want Drummer users to be the first to have a chance to try it out.#
For people who were part of the initial test group this will be familiar. It was initially developed inside Drummer, but I figured out that it would work better if it ran on a server, so I punted on the feature, to get back to it after the product shipped.#
If you write in an outliner, and use Twitter, now you can have all your original tweets (not RTs) in a calendar-structured outline, that updates on its own. #
This means if you're out and about and get an idea you want to include in your writing, just write a tweet, and when you get back it'll be in Drummer.#
No. It's for anyone with an OPML-compatible outliner, which for now effectively means Drummer. But I want to this to be open to all, the same way RSS feeds are open to all. You didn't have to use Radio UserLand to read feeds when RSS was booting up, and the same thing is true of OPML today.#
Post something to Twitter to get things started. Wait a few minutes. #
On the home page there will be a link to your OPML file, grab the link, switch into Drummer and enter the address into the Open URL command in the File menu.#
Next time you tweet, after as much as three minutes (that's the interval between checks, it may go up over time as more people use the service) the tweet should show up in the outline on GitHub, and in Drummer. #
There are still a few things I want to add to this, but the service is fairly complete. I think it works. But in case it doesn't or if you just want to ask questions about the design, or what it can be used for, I started a thread on the Support site. #
The next problem I want to tackle, left over from before shipping, is making Drummer able to recognize that there's a copy of itself running on another machine, and sending it message to turn itself off, so as to avoid version problems. #
I've got new code in the server that sends a "goodnight" message to such extraneous copies of Drummer. To be clear, not just on the same machine (as it currently works) -- no matter where it is. #
Also I want it to do something more appropriate than switching to the About Drummer page from the docs. I think I figured out how to do that too.#
This is a tricky corner-turn. If for some reason it doesn't work properly, and of course Murphy's Law says that it won't, mayhem could result and that would suck. #
So here's the deal, if you want to help validate this, let me know by responding to this item, and in a couple of days we can start testing this functionality. Once it appears to work properly, then I can "arm" the feature. But I want to be extra-extra careful with this fix. #
Copyright 2021, Dave Winer.
Last update: Sunday December 19, 2021; 9:48 AM EST.