Ok everyone I know the character limit is longer here, but I am a creature of Twitter and thus uncomfortable with boosting posts that occupy more than one phone-screen of my followers’ timeline. Even great posts.
@matthew_d_green FWIW my client truncates long posts with a “click to read more” option, so you’re not filling up my screen if you do boost the longer posts.
@TindrasGrove @matthew_d_green would be nice if it's integrated into the user preference section of server , so all clients can implement common good behaviour (probably one good default at instance level too which can be overridden by user at profile level if they want to see longer ones)
@flawed @TindrasGrove @matthew_d_green
IMO that'd be rather terrible, because it would force all the clients to either ignore these preferences or conform to the idea of what preferences even make any sense that the server author had. (For example, how should this preference be understood by a client that shows a threaded view?)
Granted, there are a few such preferences that can be expressed in terms that are very client-intependent (e.g. "should the client require explicit user action before showing an image"), though these also suffer from that problem (it would make a lot of sense to have a client that allows the user to specify an expression that determines whether an image is shown immediately).
