@dave@davebucklin.com bingo!

@kas@enotty.dk I’m not currently using a handrolled client, but I’ve started a couple.

@kas@enotty.dk Yes, I know I am!

@benaiah@benaiah.me sounds a lot like why many years ago, I went with Drupal for a simple Blogging site vs Wordpress. WP was easier but Drupal allowed me as an admin to not have any filters. Which allowed me to put raw HTML in the posts to control certian that I was doing at the time

@nblade@nblade.sdf.org I could probably put something together, but I went this route originally because existing generators felt like they took too much control from me over the exact output. I want very small, static pages I can throw behind nginx, and I want to know exactly what the contents are. My current mess of spaghetti Racket is getting hairy since I’m halfway through an unfinished rewrite I started a while ago and forgot about, but at least I know exactly what it’s doing.

@benaiah@benaiah.me That is a tough call. I guess it depends on if you can find something off the shelf that will meet your needs or not.

@leveck@leveck.us welcome to twtxt!

@tfurrows@grex.org It is certainly not polished but I have made a good start on that php CLI

@mdom@domgoergen.com I get the error: awk: extra ] at source line 35

@benaiah@benaiah.me Thanks I am just fooling around at the moment.

@nblade@nblade.sdf.org welcome!

@pete@petedeas.co.uk that’s a clever solution; I’ll have to set up something like that.

@mdom@domgoergen.comI’m not sure I know how to reply properly with it. I handeded edit this to be right.

@mdom@domgoergen.com I am playing with the txtnish client, all the systems I have available are running an old version of Python

I tried to add myself to the Git repos for the twtxt users but I think all I did was create a fork that will not be merged

@tdemin@tdemin.github.io good points, though another that I’ve noticed is that it’s difficult to tell who in your network is actually reachable with your tweets. My HTTPS cert went unupdated for a brief while and now I have no idea who is still following me since I got it working again, so it’s difficult to tell where I can really have a conversation. A centralized service can tell who’s following who, but that’s basically impossible in twtxt.

I think this week I’ll look at a bare bone PHP CLI for a twtxt client. Just for fun mind you

@freemor@freemor.homelinux.net that would assume that someone is looking at crawler logs. That is not a given in this day and age…

@quite@lublin.se there is also a unicode symbol in there, maybe that?

@quite@lublin.se oh, txtnish url did that. I guess a pipe symbol does that to you?

@quite@lublin.se which line?

@mdom@domgoergen.com, I have got a smallish patch for you on GH. Maybe it helps others too.

@c-keen@pestilenz.org welcome!

@pete@petedeas.co.uk have you tried the plan9port of awk? Should be close to the original

thanks @pete@petedeas.co.uk. This probably means I should write my yearly blog post ;)

@kas@enotty.dk yes please!

@freemor@freemor.homelinux.net @kas@enotty.dk #twtxt’s quietness is actually something I enjoy about it. I care a lot more about signal-to-noise ratio than I care about the regular activity. It’s also a really fun thing to write clients for to play around with new libraries or languages.

@tdemin@tdemin.github.io too busy working on a twtxt client to tweet on twtxt

@kas@enotty.dk my bad - I’ve been developing a twtxt client, hence the frequent requests. I’m switching it over to use a fs cache for testing so I’m not hitting the twtxt files so much.

/me is finally working on a twtxt client

@quite@lublin.se the static site CMS? It’s open source: https://github.com/netlify/netlify-cms/

@phil@philmcclure.duckdns.org I actually just started a new job working on a frontend for Hugo (and other static site generators).

@quite@lublin.se that’s one of the approaches I was thinking of.

@kas@enotty.dk that sounds fair to me.

Additionally, there’s a lot that can be done by a client to reduce the network traffic and UI latency of twtxt without changing the protocol.

@mdom@domgoergen.com, @kas@enotty.dk re: metadata, I’m (obviously) in favor of my suggestion for metadata-in-comments, but I don’t think we should have comments in comments.

@mdom@domgoergen.com, @dave@davebucklin.com, @kas@enotty.dk I agree with the “no max length; show at least 140chars” idea.

I’m not working on bussard, I’m just IRC friends with @technomancy@technomancy.us and he expressed interest in making scheme available there.

@mdom@domgoergen.com mostly for fun, but once I have it working more it’ll get integrated into https://gitlab.com/technomancy/bussard.

Popular, finally. https://github.com/mdom/we-are-twtxt/ – Now exploring client options.

Just setting up my twtxt

@mdom@domgoergen.com @kas@enotty.dk thanks! I was checking access logs on nginx and noticed a bunch of 404s to my twtxt url, so I decided to pick it back up.

Think I’ll try out twtxt again for while…

How should metadata about a twtxt feed be stored? Weigh in @ https://github.com/buckket/twtxt/issues/48

part 3: make ‘tf’ run ‘twtxt follow “$@”’

part 2: make ‘tw’ run ‘twtxt tweet “$@”’

twtxt-able twtxt helper scripts, part 1: make ‘tt’ run ‘twtxt timeline -l 1000 | less’

I find the wide variety of ways people are deploying twtxt pretty fascinating

Been thinking about writing a twtxt-AAS provider.