@tx@0x1A4.1337.cx Is you page publicly accessable? Maybe i should add exporting to html to #txtnish, seems like a thing many users wan to to?

Behold! color_nick=“red on_yellow blink” is now a thing! #txtnish

#txtnish now requests gzipped pages if possible and you can call timeline with a single url to view the twtfile of someone you don’t follow.

@dave@davebucklin.com It’s probably https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195792, should be fixed for #txtnish

@dave@davebucklin.com Welcome to twtxt, i take a look at txtnish on mac os x, should be easy to fix

Okay, i dumped the wget backend from #txtnish, curl works better and providing the same interface with both was hard.

@kas@enotty.dk Ah, #txtnish just dumps the latin-1 on your terminal. Not sure what i should do about that, but it’s probably okay. But it’s a good idea to test that!

#txtnish now reports about redirects or error codes on stderr.

@kas@enotty.dk The path starts with /Hund. Collapsing mentions is harder than i thought. #txtnish does now lowercase the hostname to handle 0x1A4.1337.cx vs 0x1a4.1337.cx in mentions.

@durcheinandr@durcheinandr.de Sure, thanks for pointing out the problem. I’m very happy somebody is testing txtnish!

@durcheinandr@durcheinandr.de, @freemor@freemor.homelinux.net Okay, following one self seems not so obvious as i thought. With commit 4b9b067 #txtnish displays the local twtfile.

How should #txtnish handle permanent redirects? Prompt the user to change url? But what if timeline is run in cron? A flag like -I for non-interactive? Mhh…

txtnish should handle 301 and rewrite urls accordingly, then i can just redirect to my canonical url. #somuchtodo

And #txtnish is now on the one hand more lenient and tries to fix the feed, but if it can’t it will skip the misformed tweet.

Big improvement for #txtnish. It converts the timestamps to unixtime and displays relative dates!

Welcome to twtxt, @trevor@destroyed.today! Your timestamp looks like your’re using txtnish? :)

@tx@0x1A4.1337.cx Reusing twtxt config is probably the easiest way for new clients. Although i’m really happy that i can now use comments in txtnish… :)

@freemor@freemor.homelinux.net Can you check with sh -x? Do you use gpg_sign? This will create a new file in a temp dir. https://github.com/mdom/txtnish#sign_twtfile Maybe you upload your twtfile and not the tempfile?

#txtnish is still on the start page of hn! https://news.ycombinator.com/item?id=13742949

So, last #txtnish update for today: It supports subscribing to ipns:// and can publish your twtfile to ipfs. puh

Signing the twtfile with pgp is now built into #txtnish. I hopy my #txtnish accouncement are not annoying anyone?

#txtnish supports ftp and scp upload and prompts users about it in quickstart.

#txtnish now ask the user in quickstart if she wants to import we-are-twtxt.

#txtnish quickstart will import your twtxt followings and some of your configuration.

I just pushed a commit that shows gpg and tls in the user interface. Check the example config how to sign your twtfile. #txtnish

If you don’t have wget, #txtnish can also use curl via http_backend=curl

#txtnish has a reply subcommand that opens a editor with your outcommented timeline. Every non empty, not commented line will be tweeted.

Hello from #txtnish, a new twtxt client with minimal dependencies: posix tools, wget and xargs with -P: https://github.com/mdom/txtnish