Just added a search field for users and tweets at https://roster.twtxt.org And sorry for just tweeting about new features…

Fun with data! The complete roster twtxt database can be downloaded at https://roster.twtxt.org/twtxt_20160405.sql.gz

There a new version of roster out: All links to nicks now point to a page with tweets by that user.

We probably should put that in the registry spec. I use /tweets/by/$twturl but /tweets?by=$twturl would probably be more correct.

@kas@enotty.dk aura akua sound a lot like a sentence from toki pona.

@dracoblue@dracoblue.net https://roster.twtxt.org now supports https and cors headers. And @all: every tag links to a page with all tagged tweets.

#txtnix and #roster now support the new metadata syntax ts#metadata. Now time will tell if somebody will use it.

Anybody wants to do a PR for twtxt?

And both are more liberal in parsing twtxt files: Any kind and amount of ws can now seperate timestamp and tweet.

Mike Duncan of “History of Rome” fame has another great podcast: http://www.revolutionspodcast.com/. I can really recommended it!

Do we really need to scale? How many people can you follow, read and respond to? And websockets could really help.

And we can support multiple transport mechanism and there’s no reason to not upload you twtxt to multiple backends.

I’m currenty fetching approx. 40MiB per day on roster.twtxt.org by requestion every ressource every 10 minutes.

@kas@enotty.dk I’m pretty sure i would never have tried twtxt if Zeronet had been a dependency. Though i definetely have to check zeronet!

@david@post.aldebaran.uberspace.de And i thought that was just a thing on the german wikipedia.

Or do you ask because you want to implement a client or server? I can probably write something up, it’s a very minimal api.

@mylesb Nice idea!

@kas@enotty.dk, @dracoblue@dracoblue.net You’re right we should really use robots.txt for twtxt registries. Maybe i even add this as a option to #txtnix.

@dracoblue@dracoblue.net I’m not sure if i’m ready to document the streaming interface, i’m still playing with different ideas.

@dracoblue@dracoblue.net Sorry, but what tweet are you referring to? I have no idea what sounds great… We need a way to reference tweets!

@krt@krt.marmaro.de I actually like it when tweets are short, but insisting on 140 characters and cutting the tweet is a little bit too strict.

@kas@enotty.dk It’s a cool game, i played it when it was featured on hn, but lost interest once i could venture outside.

What’s weird, normally you’d think this would be the point where it gets interesting.

Anybody has http://tools.ietf.org/html/rfc7033 running for twtxt? And what to use for rel? https://twtxt.org/twtfile?

A detailed document describing HTTP/2 ⌘ https://www.gitbook.com/book/bagder/http2-explained/details

Sometimes you just need the 20 additional characters… :)

#txtnix watch –alarm mention or –alarm tweet should ring the visual bell when something happens.

And as #roster is currently the only endpoint it’s for now the default endpoint for watch.

Great, i wanted to have cold Club Mate and now i have a frozen block of it.

Instead of fetching feeds every few minutes, ‘txtnix watch ws://url’ will listen to a websocket endpoint for new tweets.

Talking about scaling: #txtnix has a new feature since last night i haven’t talked about as i wanted to test it for a few hours first.

This would be a good use case for metadata. @kas@enotty.dk could ask clients to refetch less, eg with /refetch 10m

@krt@krt.marmaro.de Twice an hour would be really slow for a lively discussion. But i agree, 10 seconds is too often.

And as luck would have it, #roster provides a websocket stream on ws://roster.twtxt.org/stream. Have fun!

@kas@enotty.dk Good reminder, i really should add a url in my user-agent-string for roster.twtxt.org. Although it only fetches feeds every 600s.

@krt@krt.marmaro.de You can use more than 140 characters. It seems twtxt does not limit the number of characters to 140. Neither does txtnix. Twet?

Another sunday at the office. Alone. Only admin in the building. Wish me luck that nothing breaks.

Thanks @krt@krt.marmaro.de. Packaging is such a thankless but important job.

@quite@lublin.se Very cool!

@krt@krt.marmaro.de What are you working on?

@kas@enotty.dk,@ Are your twtfiles requested too often? Do you think we need a policy how often to request a twtfile?

http://roster.twtxt.org got a nicer layout, buttons and collapsed mentions tonight! #roster

@dracoblue@dracoblue.net Does your offer for subdomains on twtxt.org still stand? Could you point roster.twtxt.org to 46.101.199.168?

It’s running since last night, supports the twtxt registry api and crawls the feed for new urls. #roster

@soltempore Berlin is missing! How long is my day? Please tell me!

@kas@enotty.dk We had a short power fluctuation yesterday. Funny to see which machines die and which survive.

@dracoblue@dracoblue.net But apache eg can just use mtime,inode or size for the etag. No default way to compute md5 without a filter.

@dracoblue@dracoblue.net The problem is that my ini parser does not remove quotes around values and twtxt’s does. Another parser? Another format? sigh

The sun made it across the pacific! @david@post.aldebaran.uberspace.de @kas@enotty.dk

I think we sometimes forget that even with all the advanced web technologies, you can still share your ideas with a simple text file.