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.
@kas@enotty.dk, @david@post.aldebaran.uberspace.de As long as I can still upload my hand edited twtfile on any webserver and someone can follow me, twtxt hasn’t lost its way. :)
@kas@enotty.dk Great Idea! I wouldn’t worry about the file size. Content-Encoding gzip should get you a very good compression rate.
\me wonders if there’s something useful we can do with the referer header. We can put our own twturl there like in the user agent field?
Or we can use it to refback. Every time you mention somebody you send a HEAD with your twturl in the referer to her adddress. Any ideas?
@kdave@kdave.github.io I don’t see anything at all. So either my font has an empty glyph for that codepoint or i’m stripping it. Will investigate.
All fonts I tried are either ugly or the unicode glyphs are so small that they become unreadable. #fonts
@kas@enotty.dk What are you recommending? I usually prefer Terminus.
My code worked in test, still worked in integration and failed in prod after 4 hours with no complains. Oh my.
@kas@enotty.dk The moon or do you have another favourite glyph? And please with codepoint, my font doesn’t handle all the fancy stuff you throw at it.
Come on coveralls.io! Show me my new badge! Nothing more depressing that working on your coverage and your new shiny badge won’t update :)
@kas@enotty.dk The only thing stopping me from implementing webmentions by myself is RFC 5988. Crazy stuff…
Slow day for #txtnix. Just some documentation for plugins and fighting to get the test coverage back up to 85%.
@dracoblue@dracoblue.net It all comes back to #48 … :)
@kdave@kdave.github.io The last commit will check for the environment variable TXTNIX_CONFIG_DIR but this won’t help if i move following to a state file.
I could just fall back to twtxt’s config if i can’t find a config directory for txtnix…
@kdave@kdave.github.io I have no strong opinion about different configs fot #txtnix and #twtxt, but @david@post.aldebaran.uberspace.de had compatibiliy issues with quoting.
@kdave@kdave.github.io Ah, okay, i misunderstood you there… :) Would you be okay with following moving to the state file?
And INI is a weird format for sharing config. Even in perl one library can’t parse the result of the other. :/ Maybe TOML?
@kdave@kdave.github.io I had a race condition btw 2 txtnix processes. The obvious solution is to flock, but then config edit will flock for too long.
This would allow to add comments, preserves whitespace and ordering. And no process will be writing in your file while you’re editing it.
But what to do with following? Are you hand editing it? Would it be okay to move the section to the state file?
/me is pondering if there should be two configuration files. One with normale configuration data and one with the state.
@larry@lhyn.es Damn, twitch is also already used … we’re too late! Maybe we should concentrate on the txt part and just call them texts.
That’s also an established term but language is a crowded space… :)
#txtnix now uses it’s own configuration file ~/.config/txtnix/config after @david@post.aldebaran.uberspace.de discovered some incompatibilities.
@dracoblue@dracoblue.net #txtnix does now expand /me to @mdom@mdom.github.io. I’m not sold on the syntax though, my brain is trying to find the referenced mention.
Find words for twt: perl -lane ‘$line=$_;s/[aeoui]//g;print $line if /twt/i’ /usr/share/dict/words – I like twitch… :)
The smell of waffles is in the air.
#txtnix new subcommand will dump all available metadata for a feed. Until a decision is made it uses my // suggestion.
Otherwise i have not much time to code, daugther and friends intervene… :)
@reednj@reednj.com Is twtxt-dir removing exclamation marks after mentions?
Hello, @raur@raur.nfshost.com! Can i ask how you found #twtxt?
// follow raur http://raur.nfshost.com/twtxt.txt
Until there’s documentation: You need at least a empty section header like [LinkBack] to activate it. I’ll probaby require active = 1 later
@kas@enotty.dk You mean, you want to link a url in one of your twets and then send a webmention?
We would have to write a new plugin for that. Which sounds fun… Do you have a have a receiver we can play with?
Big changes for #txtnix: The last commits added a basic plugin system. There are currently just three plugins:
LinkBack can post your twturl to an url every time you mention someone as long as the user has a // linkback $url in her feed.
ShellExec takes over the work from the current hooks and should work without any further configuration.
And GistStore will upload yout twtfile to gist when you provide it with your username and password or access token.
@kas@enotty.dk is on fire. Great links, thanks! MovieSwap seems just crazy enough to succeed.
@mdom@mdom.github.io needs to move to copenhagen. I lived in Reformert Kirke for few weeks and loved Copenhagen!
@krt@krt.marmaro.de Hi there, welcome to #twtxt! We sure get a lot of comparisons with #finger…
// follow krt http://krt.marmaro.de/twtxt.txt
@kas@enotty.dk So the first hex string is the private key and the second a public key of a recipient?
But how do i generate my public key from my private? And shouldn’t iI be worried that my private key can be seen with ps? Still confused.
@quite@lublin.se Heh, I like twet twet! #twet
@kas@enotty.dk That’s what i’m using. But shouldn’t i be able to generate keys to communicate with other users? How could i encrypt a message for you?
@kas@enotty.dk, @kdave@kdave.github.io I don’t get it. How do i generate keys for #saltpack? Do i need #keybase to use it?
#txtnix displays relative dates when setting time_format to “relative”.