Work Project Note : Trying to redo server side logic on the client side sucks.

Re: support for other protocols, it seems like twtxt would be pretty easily adapted to work over the p2p file network DAT, though it’d need client support for DAT or some way to follow people via files and sync in the background, which might be simpler for clients to support but would still require changes to most clients.

@tfurrows@grex.org It is neat. Although it did require to recode a little bit of my kitbashed client LOL

@freemor@freemor.homelinux.net I’m cheating geting @mekon@sdf.org file by using my own kitbashed php CLI client I am playing around with

Had to update my client to use CURL so I could get @mekon@sdf.org twtxt file via gopher

@tfurrows@grex.org just saw your one reply. Yes the client does have a way to sync with the we_are_twtxt list. So far the biggest issue with the PHP CLI client is that it takes a long time to poll all the sites

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

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

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 @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

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.