@evil@enotty.dk What should i expect to happen with the last update? Looks okay here… :)
Does anybody has a good idea where to do some promotion for twtxt? A subreddit or online community i haven’t thought about?
I though about ix.io, any other good ideas?
#txtnish now reports about redirects or error codes on stderr.
Maybe it would be a good idea to point new users to reednj, we-are-twtxt or irc. Some set up a twtfile and aren’t sure about the next step.
Now that we can autofollow some feeds, the only thing missing for new users would be an easy way to upload some tweets.
I stumbled upon darebee.com in an unrelated hn thread and i’m really impressed, it’s a really easy follow regimen. Try the Totals program.
@freemor@freemor.homelinux.net Uh, i haven’t heard about yacy in years. Please keep us informed! I have to talk to our hardware guy, maybe we can run an instance at work.
@kas@enotty.dk Yeah, i know, it’s crazy, especially wp http://stackoverflow.com/questions/7996919/should-url-be-case-sensitive/17113291#17113291, let’s just use only lowercased urls!
@kas@enotty.dk The path starts with /Hund. Collapsing mentions is harder than i thought. #txtnish does now lowercase the hostname to handle 0x1A4.1337.cx vs 0x1a4.1337.cx in mentions.
Welcome to twtxt, @hund@raw.githubusercontent.com!
@tx@0x1A4.1337.cx Thanks!
@durcheinandr@durcheinandr.de Can you check with the newest version? This should be fixed in eb3665b.
@trevor@destroyed.today Looks great, do you have the syntax file uploaded somewhere?
@durcheinandr@durcheinandr.de. Thanks, fixed!
@durcheinandr@durcheinandr.de Sure, thanks for pointing out the problem. I’m very happy somebody is testing txtnish!
@kas@enotty.dk Interesting video, i just watched the first ten minutes and bookmarked it for later.
@tx@0x1A4.1337.cx I think there’s just a charset=utf-8 missing to see it correctly in the browser. It’s fine in a terminal.
@durcheinandr@durcheinandr.de, @freemor@freemor.homelinux.net Okay, following one self seems not so obvious as i thought. With commit 4b9b067 #txtnish displays the local twtfile.
@tx@0x1A4.1337.cx Nice! But i don’t get a UTF8 feed, for example https://twtxt.1337.cx/tazgezwitscher
@freemor@freemor.homelinux.net Thanks for the reference! How do you create your timeline? Would it help if you had access to the unformatted timeline? Before formatting it’s nick “t” url “t” props “t” unixtime “t” msg
But i should probably autofollow if twturl is set in the config file. What do you think?
@trevor@destroyed.today, @tx@0x1A4.1337.cx Sorry, too many new users! :) @tx@0x1A4.1337.cx suggested printing the messages to stdout.
The unix way: If you can’t decide, add a configuration option.
@kas@enotty.dk Shouldn’t i check [ -t 0 ] if i want to know if i can prompt?
@durcheinandr@durcheinandr.de, @freemor@freemor.homelinux.net It’s a feature, i want to see what the rest of the world sees. In case publishing fails.
I think i just add a configuration option stating if the users wants to be prompted or if it should happen automatically.
Or maybe i just print a message to stderr as @trevor@destroyed.today suggested.
How should #txtnish handle permanent redirects? Prompt the user to change url? But what if timeline is run in cron? A flag like -I for non-interactive? Mhh…
@trevor@destroyed.today, @quite@lublin.se I already ignore the scheme for collapsing mentions, I wonder if i should ignore www to. Probaby not… :)
txtnish should handle 301 and rewrite urls accordingly, then i can just redirect to my canonical url. #somuchtodo
Big improvement for #txtnish. It converts the timestamps to unixtime and displays relative dates!
Someone wants to write a vim syntax file for #twtxt? :)
And #txtnish is now on the one hand more lenient and tries to fix the feed, but if it can’t it will skip the misformed tweet.
@freemor@freemor.homelinux.net Ha! Thorsten Glaser is an old colleague of mine. Shared his office for three days before i switched to another client.
@kas@enotty.dk I’m practising, and it’s really easy, at least for the current year. Thanks! #doomsday
This will be configurable in the future but that’s enough coding for one night, time computation is weird.
The doomsday algorithm is cool. Do you already have it memorized?
@kas@enotty.dk But then we wouldn’t be a decentralized network anymore. Or do i misunderstand the nature of keybase?
@trevor@destroyed.today Yeah, we just talked this morning about that. There are clients (for example twet) that won’t be able to read signed files.
I would love to add metadata to the spec, but someone would have to hack it into twtxt #issue48 @buckket@buckket.org? :)
The current spec does not allow for clearsigned twtfiles. I just hoped for the best, but sure something broke… :)
Welcome to twtxt, @trevor@destroyed.today! Your timestamp looks like your’re using txtnish? :)
Starting an Internet Service Provider http://chrishacken.com/starting-an-internet-service-provider/
@kas@enotty.dk Yeah, we are currently relying on the fact that lines without tabs are skipped and gpg does not produce lines with a tab. I agree, that this is suboptimal.
But buckket’s last comment in https://github.com/buckket/twtxt/issues/48 seems to support that.
@freemor@freemor.homelinux.net Something like post_tweet_hook () { cp “$twtfile” /var/www/twtxt.txt; }