Klaus Alexander Seistrup

GPLv3+

This is _way_ better than before: I don't notice any chunks. However, the output in mtm is noticeably slower than in a plain terminal. ```sh $ # Without mtm $...

@deadpixi it is still noticeably slower than a plain terminal emulation. It's not a big problem, but I thought you should know. The chunked output is gone and that's good.

@kitchen it's a pity `NAPTR` records are so uncommon, or you could do, e.g.: ``` somebody.example.com. 3600 IN NAPTR 100 100 "u" "E2U+twtxt:Personal" "!^.*$!https://example.com/twtxt.txt!" . ``` corresponding to the `twtxt`...

@kitchen it's the semantically korrekt RR type, that's right, and the format is just awful. So perhaps we should just be thankful that not all DNS providers support this exotic...

One way of increasing discoverability could be to include `twtxt.txt` URL and `@username` in the HTTP `User-Agent`string, e.g.: ``` txt twtxt/1.2.3 (+https://example.com/twtxt.txt; @somebody) ``` This way at least people who...

There is nothing that prevents a twt'er from announcing their stream in a NAPTR record, and I'm all for the idea (although my own DNS provider doesn't support that record...

@quite, good point! A cup of :coffee: later I am thinking if [`/humans.txt`](http://humanstxt.org/) could be a place to put information about a twtxt stream. Another possibility is to put a...

Just a side note: as an experiment I put my twtxt URLs in the `/humans.txt` file on my website and I decided to use the mention format: ``` txt TwTxt...

@timofurrer, of couse. `/humans.txt` is a free-form file meant for human consumption.