Improve rendering in text mode browsers

[faelys]

Hello,

my usual browser is w3m, and Twitter used to be a wonderful website with it, but that died with the old UI, so I tried nitter instead, which is already much better than the official mobile fallback.

I understand I'm part of a negligible minority which should have finished extinction already, but if you could just make a few little changes to nitter UI it would make a huge difference for me:

• put parent twits in li elements inside a HTML list (ol or ul);
• keep the current twit outside of list, to make it stand out;
• put in child thread in a li element, containing a new list for of twit in the thread;
• make an obvious distinction between embedded video and embedded picture, to prevent the confusion between the preview image of a video and an embedded picture (the old twitter UI did this by having img elements only for embedded pictures, so a pic.twitter.com link at the end of the twit without img meant a video was embedded; in nitter I saw an Enable hls button on video but I don't know whether it's always the case).

I saved some old twitter UI HTML files left in my browser memory, I can provide them or HTML samples or screenshots if that helps.

I would be really happy if someone familiar with the HTML could make these changes; if not I will try to come up with a patch, but I'm not entirely confident in my ability to change HTML without breaking the graphical UI.

Thanks in advance.

[Kaleidosium]

If Zed can't do it, then EasyChirp might be for you, it's mostly text-based, and unlike Nitter, it's an actual twitter client, which seems to me what you're looking for.

[faelys]

Thanks a lot for making me discover EasyChirp, but I will look further into it later.

However to clarify, my usual twitter client is Bitlbee used in text mode through irssi, which covers most of my needs, and youtube-dl handles pictures and videos from pic.twitter.com links.

I needed the old twitter UI (now replaced by nitter) only to browse twitter links shared through other means, and to browse threads around a given twit, since bitlbee does not provide such reading features. Such usage seemed to fall within nitter feature perimeter.