(#wql4w5q) @prologic@twtxt.net I don’t think the solution proposed there is a good one, and here are my reasons.

1. The specification says quite clearly, “The file must be encoded with UTF-8”. If an old piece of software can’t handle UTF-8, it can’t produce a valid twtxt feed at all.

2. I believe the intention behind this solution is to make it render in an acceptable fashion in clients that don’t support the convention, but I think it’s the opposite in reality. Separating posts like that could make it very frustrating to read in a feed. I would much rather have nothing or a replacement character separating logical lines.

3. I think it interferes quite heavily with human readability for the same reason. When reading a twtxt feed, it’s helpful to know that each line with a timestamp represents one post.