Writing

There are 44 posts filed in Writing (this is page 1 of 5).

The topic of text boxes

Recently, in another post on the subject of textcasting, Dave Winer made a comment about text boxes:

Every time you see a tiny little textbox that’s a sure clue they’re trying to own you, and hoping you don’t notice.

http://scripting.com/2024/02/01.html#a154043

I think this is a reach. In my opinion, the simplest reason to use a text box for text entry is that users are used to it and it is easy to implement (using Occam’s Razor here). Another explanation is that it is use of prior art, as Dave Winer has written about before (see here, here, and here). No sinister plan to “own” anyone here. Could text editors be better/have more features? Sure they could! Could writing apps cooperate with each other and have APIs? Sure they could! Should people be demanding these things? Sure…maybe….or maybe they could make those things happen…or maybe they could submit a feature request….

If the software is open source (Mastodon et al), someone could make their own changes. If the software is a service provided by a company that does not charge for the service (hmmm…Twitter, Facebook, Threads, Bluesky come to mind), it seems more difficult for users to request features and drive changes. If a group of users REALLLY wanted something and no other app seemed interested, maybe they could create their own product (thinking Kickstarter here). To me, it comes down to this: how bad do you want this?

Finally, another take on this sentence comes from Ken Smith:

Ken Smith comment on Dave Winer’s “text box” statement.

Based on Ken’s comment, I take this as “any antisocial behavior” in the blank – racism, anti-Semitism, discrimination, manipulation…the list can go on and on as Ken points out. This Quora thread has some good points about someone trying to “own” someone.

James Gallagher: The what, why, how formula of technical writing – “These three questions allow me to evaluate the extent to which my writing and the writing of others follows through on its stated goals.”. The post gives examples of each question – nice!

Colin Walker points to Misu talking about writing consistently, and I love this quote from Colin: “if you don’t do the things you want to get better at then you never will and there’s no point moaning about it.”. I also needed to hear that!

James’ Coffee Blog: Advent of Technical Writing – a series of posts on the topic of technical writing, published in December 2023, lots of good nuts-and-bolts writing advice.

Thoughts on POSSE and Textcasting

A number of people have posted recently on the subject of POSSE (Dave Winer, Tantek Celik, The Verge, and Bix Fronkonis). POSSE is an acronym for Publish On (your own) Site, Syndicate Elsewhere. Dave Winer has also been talking about Textcasting, where he proposes that blogging/social media tools support a common set of features. Dave Winer also talks about “Two-Way RSS”, which I think means that a tool can generate RSS feeds and can use RSS feeds as an input to posts within the tool. I would like to explore these ideas further in the next few paragraphs.

Recently, I got the impression that a Textcasting use case is to allow a user to write in their tool/platform, and have that output be accepted on other platforms as “first-class posts”. What I mean by that is the post appears on the other platform to have been written by the user using the platform’s own tools. Now, a number of platforms don’t support all the features in the Textcasting spec, so even if the other platform accepts input from the user’s platform, it may not represent the text as it appeared in the original platform. In this instance, I might call that a “second-class post”. It may have all the text from the original user platform, but not the styling, or links, or an enclosure.

So, it seems to me that the target of Textcasting is to get Threads/Bluesky/Mastodon/Twitter/Facebook to support the Textcasting feature set (which I assume they don’t, or at least not equally). In each of these cases, the user must have an account on those platforms, so they have an identity and the platform can recognize who is posting. Dave Winer mentions that other blogging tools that support peering for the Textcasting feature set is WordPress and micro.blog. Again, both of these tools require a user account, same as the social media tools listed above, for the same reasons.

What about people who just want to post on your own site? Go ahead – nothing stopping you! For people that want their message to go further, we shall have to wait and see if those platforms are open to change. For open source platforms (Mastodon), someone could make changes in a Mastodon version to support Textcasting. The other aspect of the social media platforms, to me, is that they are social. If you are a writer that wants to have interaction with your readers, and your readers are on those platforms, it makes sense to “get your message out there”.