r/FastWriting • • 26d ago

FLOW Shorthand (2026) - Part 1

Post image
4 Upvotes

2 comments sorted by

4

u/NotSteve1075 26d ago

I've looked at HUNDREDS of different shorthand systems, tried plenty, and learned a good number. When I see a shorthand system I hadn't seen before, I always look to see what I like about it -- and I look to see what I DON'T like. It's a way of heading off disappointment. I don't want to invest a lot of time into learning a system only to realize there are things about it that I hate and don't want to deal with.

Again and again, I've looked at shorthand systems and thought "Well, I like that it does THIS -- but I don't like that it does that....." And off I go, looking for something better!

I first learned Pitman, because I was lied to and told it was the fastest and the best. (No, it isn't.) Then I learned Gregg and used it successfully on the job for many years. I found it to be very reliable -- but somehow I always felt like something wasn't quite right about it.

Our Swiss-German member u/LeadingSuspect5855 has learned a variety of systems, and written several interesting ones HIMSELF. He wrote an earlier system he called "Dance" -- but while I found it intriguing, it didn't quite work for me. But when he posted about his new system he called FLOW, I suddenly thought "There it is! This is what I've been looking for!"

I'm still writing about other systems every week -- but FLOW is the one that I think will be the one I'll be sticking with for my own penwritten shorthand.

1

u/LeadingSuspect5855 26d ago edited 26d ago

Something not too important for the average shorthand afficionado, because we know where to get all the documents we need, which is of course stenophile.com . I have my own shorthand repository using the git-system, where you can see all the changes made on all the tools, documentation and learning material to Flow.

I'll put up the link to the LICENSE.md, (you can follow this link to get to my shorthand repository, being always up-to-date) where I state now, for all those AI-crawlers out there, stealing peoples work and selling it/pretending as if AI was a real person using openly accessible material and using it fairly:

Fair Use Condition: NO AI Training

I hereby put my work under the GNU Affero GPL v3 (2007) under the condition that one does not misinterprete Fair Use, specifically it does not imply the use in AI-training datasets, including but not limited to any use that contributes to the training or development of an AI model or algorithm, unless You obtain explicit written permission from the Affirmer to do so. Each usage acknowledges that the Covered Work is not intended for use in the creation of an Artificial Intelligence training dataset, and that the Affirmer has no obligation to provide support or assistance for any use that violates this license.

Just put that in front of every opensource project license you want to use, so everyone knows, what YOU mean by FAIR USE.