I use ITT infrequently with my mechanical machines, but when I do it's pretty heavy.  I have a M15 geared for 60 WPM and a 28RO geared for 100, so I use both the 60 and 100 WPM circuits.  I also have two raspberry pis in my workshop in my basement, one for each speed and those run into FLDIGI for RTTY decoding also running on each pi.  those pis run 24/7, until Comcast does something to dump the audio feed and I then need to manually kickstart them.  I use VNC to connect to the pis over my home network, so that I can see the FLDIGI window on the pis from my office (upstairs).

I'm doing some AVR Arduino projects with TTY so I will often use the ITTY feed to test those as well.

Addressing your other question(s), my own preference is to leave the 100 WPM channel as a news feed, rather than moving it to auto start.

One change I'd like to see is for ITTY is to have the posted text to be filled out to 68 chars per line, mostly as a paper saving convenience.  One of the things I plan to add to my AVR code is a means to fill the line myself, but I think the right place to do that would be at the source, or within ITTY, so that all those printing with mechanical devices can save in the paper department.  This is mostly a nit, and not a heavy hitter.

Bottom line is that I'm very grateful to have ITTY available 24/7 for TTY testing (and pre pandemic demonstrations).  I'm also grateful to those who contribute content for transmission over ITTY.

73, Paul, ad7i

Central Coast of NJ