FOLLOW: @xuu@txt.sour.is from @codebalion@twtxt.prismdragon.net using txtnix/0.07
@tx@0x1A4.1337.cx Take a look at dns resolv times. This was a major pita with txtnix.
Publishing to #ipfs now works reliable in #txtnix. You can find me at /ipns/QmZxsWLdxMcpb34qXtDyFAVtUDDm9Fp2G24NSjS8fGWBWY/twtxt.txt
How to use #txtnix with tor: HTTPS_PROXY=socks://localhost:9050 txtnix timeline Or use the new variables http_proxy and https_proxy
I upload a version of #txtnix with that feature as soon as i have some time to clean up the code
#txtnix now depends on Net::DNS::Native for nonblocking dns request, this should solve the annoying request timeouts. Yay!
#txtnix would only unfollow urls with 410. Now you can set the variable unfollow_codes to list additional codes like 404 and 403.
#txtnix now has minimal support to add and publish files with IPFS. Subscriptions shouldn’t be too hard either.
#txtnix now accepts user templates. There’s an example on github for html output wich can be used by calling txtnix timline –template html
New plugin for #txtnix: Upload your twtfile to a ftp server. Hello FTP world! Now if someone would like ftp retrieval… :)
New feature for #txtnix: tweet via email. This tweet was written on my phone!
So, after weeks of neglecting my twtxt feed, i try to tweet more often. I think i was simply a little burnt out after roster and txtnix.
@kdave@kdave.github.io I fixed the connection timeouts with #txtnix. It seems i fetched to many urls concurrently, so now there’s a worker pool.
#txtnix and #roster now support the new metadata syntax ts#metadata. Now time will tell if somebody will use it.
@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.
#txtnix watch –alarm mention or –alarm tweet should ring the visual bell when something happens.
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.
@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?
Slow day for #txtnix. Just some documentation for plugins and fighting to get the test coverage back up to 85%.
I could just fall back to twtxt’s config if i can’t find a config directory for txtnix…
@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.
@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 I had a race condition btw 2 txtnix processes. The obvious solution is to flock, but then config edit will flock for too long.
#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.
#txtnix new subcommand will dump all available metadata for a feed. Until a decision is made it uses my // suggestion.
Big changes for #txtnix: The last commits added a basic plugin system. There are currently just three plugins:
#txtnix displays relative dates when setting time_format to “relative”.
Thanks @kdave@kdave.github.io for the new default colors. And colored hashtags are also a thing now. And text wrapping at 76 characters. #txtnix
You have to set use_color = 1 and display_format = pretty to get colorized output in #txtnix.
@quite@lublin.se Woah, we both implemented ANSI color support for #twet and #txtnix at the same time!
#txtnix now has a –pretty and –simple for the timeline and view subcommands and a config option display_format that defaults to simple.
If you want to try #txtnix, now is the time with the new installation guide https://github.com/mdom/txtnix#installation
If connected to a pipe #txtnix tweet will now read tweets from STDIN. Will it now be too easy to spam the #twtxt network? :)
#txtnix will now add a tenth of a second between tweets to enforce strict ordering between tweets.
#txtnix now calls an editor if you provide no argument to tweet. Every line in then tweeted as a seperate tweet.
#txtnix now has support for all registry endpoints, you can query tags, tweets, mentions and users.
@kdave@kdave.github.io Not that i endorse anything like that, but one could always just .
@kdave@kdave.github.io There’s an almost dependency-free version at https://mdom.github.io/txtnix.
txtnix v0.03 now has support for mentions via registries. Now, if just more users would use registries…
@kas@enotty.dk Just put <|formail -x subject | sed ’s/ tweet //’ | xargs txtnix tweet in your procmailrc and send mails with the subject: tweet msg.
First release of txtnix should be hitting cpan any minute now.
@kas@enotty.dk It’s xargs -n1 txtnix tweet on steroids!
New version of txtnix. I would be happy if anybody could test the no-dependency script at http://mdom.github.io/txtnix.
My one daily hour of programming was spent today with writing tests for txtnix. So tired now …
As german speaker i missed the unintended meaning of txtwat. Sorry, if anybody was offended. The project is now called txtnix.