showing replies to @phil
@phil I gave up on waiting for gitly.io sources
@phil I gave up on waiting for gitly.io sources
@phil what was it supposed to be?
@phil thanks, Syncthing seems to be suitable for synchronization. Bookmarked.
@phil The real spec is more like this - any line that starts with a timestamp is a tweet. They don't have the be in order. The timestamp is some type of iso8601 cc: @mdom
@phil (re: spec) yeah that spec was too restrictive, you can't do much with it cc: @mdom
@phil We all just decided to ignore that... :)
@phil We all just decided to ignore that... :)
@phil (re: #twtxt specs) Do you mean the comments? They're sort of a de facto standard. Or the length of some of my statuses? I have chosen to completely ignore the ‘up to 140 characters’ recommendation. So, ...
@phil the author should automate the delay
@phil the author should automate the delay
@phil #twtxt format specification ⌘ https://twtxt.readthedocs.io/en/latest/user/twtxtfile.html#format-specification
@phil thanks for that!
@phil (re: gitly) website changed from april 10 to april 2017
@phil (re: gitly) website changed from april 10 to april 2017
@phil Cute.. We definitely need more time traveling jokes :)
@phil Oh yes, running my own mail server Viagra and other pharma spam is a big thing.. tho fairly trivial to block
@phil LOL... :D
@phil, @durcheinandr: If you want a browser that acts like vim - try: https://www.uzbl.org/ I love it.
@phil you have surf from suckless.org
@phil #Qutebroser, #Xombrero, #Vimperator, for vim like browsers
@phil (re: vim, browser) There are a few browser plugins which try to accomplish this. As you use X there is no need for LeftRelease in (neo)vimrc - see :help mouse
@phil (re: copypaste) neat trick, but needs mouse ;-)
@phil (re: pneumonoultramicroscopicsilicovolcanoconiosis) that would be a shitty password :)
@phil (re: pneumonoultramicroscopicsilicovolcanoconiosis) that would be a shitty password :)
@phil I actually _just_ started a new job working on a frontend for Hugo (and other static site generators).
@phil, i mostly check @freemor timeline. Less bots. How often do you update, @freemor?
@phil, There is basically just one real aggregator and that's reednj. And it doesn't even collapse before cutting off the tweet.
@phil, i mostly check @freemor timeline. Less bots. How often do you update, @freemor?
@phil, There is basically just one real aggregator and that's reednj. And it doesn't even collapse before cutting off the tweet.
@phil I can't imagine a simpler time format than rfc3339. I would be fine with just using utc or unix time, but i don't think most people could write that without a client... :)
@phil I don't just throw away lines i can't parse, but try to fix as many errors as possible. But eventually you have to give up. https://github.com/mdom/txtnish/blob/master/bin/txtnish#L368
@phil I can't imagine a simpler time format than rfc3339. I would be fine with just using utc or unix time, but i don't think most people could write that without a client... :)
@phil I don't just throw away lines i can't parse, but try to fix as many errors as possible. But eventually you have to give up. https://github.com/mdom/txtnish/blob/master/bin/txtnish#L368
@phil (re: aggregators) I'm unsure, I don't use the aggregators. The sooner the 140 char limit is removed from [the specs](https://twtxt.readthedocs.io/en/latest/user/twtxtfile.html#format-specification), the...
@phil IMHO, the 140 char limit ought to be ignored and people should instead remember that this is a microblogging system.
@phil ah, actually that's the www, that causes trouble, scheme is ignored
@phil please use mdom's https URL
It seems @phil is not listening; neither can we fully read what he is saying. :(
@phil ah, actually that's the www, that causes trouble, scheme is ignored
@phil please use mdom's https URL
@phil I use a roll-your-own client for #twtxt and I have decided to throw away lines that doesn't start with a timestamp that the dateutils module understands. Other clients can do as they please.
@phil In order [for Python] to parse timestamps with leap seconds, you'd almost have to parse any time stamp “manually”. It's definitely a bug in Python, not in the timestamp.
@phil I can't read all your arguments since your client cuts off everything after the 140th character.
@phil RFC3339 is a subset of ISO8601, your timestamps are fine. We're not using 8601 as it's crazy complicated to parse: 2009-W01-1 is a valid represenation for Monday 29 December 2008.
@phil You mean the leap second in evil.txt? It's expected to break clients ... :) You can just skip lines that you can't parse. Although it's a valid date according to rfc3339. Maybe file a bug against coreuti...
@phil RFC3339 is a subset of ISO8601, your timestamps are fine. We're not using 8601 as it's crazy complicated to parse: 2009-W01-1 is a valid represenation for Monday 29 December 2008.
@phil You mean the leap second in evil.txt? It's expected to break clients ... :) You can just skip lines that you can't parse. Although it's a valid date according to rfc3339. Maybe file a bug against coreuti...
@phil Can i add you the we-are-twtxt? And how does the telegram bit works? Never used telegram before ... can you chat it up and it will post to twtxt?
@phil Can i add you the we-are-twtxt? And how does the telegram bit works? Never used telegram before ... can you chat it up and it will post to twtxt?
@phil this can work as a fallback but rdr extract the content and leaves out menus etc.
@phil this can work as a fallback but rdr extract the content and leaves out menus etc.
I managed to autocollapse mentions in the timeline view (e.g. @<phil> instead of @<phil htt p://doman.tld/twtxt.txt>)
@phil If you install termux (https://termux.com/) you can run twtxt on Android. I'm doing so right now.