Regarding my problem with some chars from @kas@enotty.dkdk: The txtnish output looks fine. As I don’t see anything in my program that could cause this I asked in the #golang #xmpp room. Let’s see if someone has a good idea.
@mdom@domgoergen.com is this a known #txtnish issue what happend with @kas@enotty.dk vs @kas@enotty.dkdk or again some weirdness in my stack?
@kas@enotty.dk that probably was #txtnish then.
@kas@enotty.dk What do you mean by ‘it’? Twtxt? Txtnish? For my bot I actually wanted this behavior when filtering for mentions to also find @mdosch., @mdosch, or (@mdosch). Maybe I should limit it to ignore only one symbol after the search term.
@kas@enotty.dk I don’t know. I will check what txtnish output in the terminal looks like. Right now I only access #twtxt via my #xmpp bot.
@mdosch@mdosch.de That’s weird, I just tested with #txtnish and I can see my posts there.
@leo@www.gkbrk.com Hmm, also #txtnish is not showing your posts. Maybe there is a bug.
@freemor@freemor.homelinux.net re:line. Well, maybe it’s just me ^^ at least it’s working fine with txtnish now :)
@freemor@freemor.homelinux.net Ok, switched to txtnish, and I can see your posts :)
@metamurks@www.metamurks.org: Also, maybe switch to my https url: https://codevoid.de/tw.txt - txtnish can deal with gopher, but it would always fetch the full file even when nothing has changed (gopher doesn’t support HEAD requests). So https might be faster.
txtnish seems nice i’m gonna try that instead
Happy new year! I will resume posting with txtnish again I guess.
@nblade@nblade.sdf.org The newest txtnish can show the users other users are following: txtnish following mdom (if mdom is my nick on your system)
@mdom@domgoergen.com That’s interesting. So does txtnish read that metadata? or would an end user just look at the file to see it? Is the meta data going to be the standard?
New feature for txtnish: After setting add_metadata to 1, txtnish will, uhm, add metadata to your twtfile. Currently i only add followings, client and your gpg fingerprint. See my file for an example.
@mdosch@mdosch.de: Yes, #txtnish uses curl and can therefore handle all curl supported protocols.
How do you follow tweets via gopher? Can #txtnish handle these?
This tweet was written on an iphone. (via http proxy to gopher to txtnish)
@mdom@domgoergen.com: I’m using txtnish on FreeBSD and I had to switch it to gawk (not sure why BSD awk fails) and disable color. Just fyi. I didn’t look into it any further.
fmt removed my escape sequences on openbsd. txtnish now defaults to fold -s, which makes even more sense as it is specified by posix.
txtnish people can follow me via gopher! @ gopher://codevoid.de/0/tw.txt
Damn, colors are not working on openbsd! #txtnish
@freemor@freemor.homelinux.net Somehow my #txtnish also always falls back to non-TLS URL for you 🤔
Increased the limit in my twtxt botconfig to 280. @mdom@domgoergen.com, is there actually a limit for #txtnish? Didn’t see a config for this.
@Leo it was a client problem it seems. #txtnish doesn’t crash.
@mdom@domgoergen.com if you can read this my bot works with #txtnish. :D
@mdom@domgoergen.com is there a way to prevent txtnish from inserting linebreaks within the tweet?
I think I’ll checkout #txtnish this weekend. It’s syntax should work with my bot ootb.
Still trying to get it working right tho. txtnish is great.
Maybe without a new command? txtnish follow mdom http://new_url.com would just work and add a alias? And unfollow http://new_url.com would remove it?
What do you think about adding aliases to txtnish’ follow file? So mentions could be collapsed for different urls of the same twtxt file?
Small feature for txtnish: You can now unfollow multiple accounts in one call, so i’m ready for the next stream of 404.
@tdemin@tdemin.github.ioThis is the good entry that happens after I hand edit. I am sure there is just a problem with my txtnish I get an odd awk error
@mdom@domgoergen.com I am playing with the txtnish client, all the systems I have available are running an old version of Python
@quite@lublin.se oh, txtnish url did that. I guess a pipe symbol does that to you?
So, what a month, a new home and a new daughter! And slightly less important, txtnish was featured on The Changelogs weekly newsletter.
And i liked @dave@davebucklin.com’s version so much, i copied his banner. Maybe i should create a empty twtfile with the banner in #txtnish quickstart :)
#txtnish supports exporting your timeline to html with –theme html since last night. See https://domgoergen.com/twtxt/timeline.html for an example.
The latest #txtnish will check the url key to change the twturl you’re following. Like an inline 304.
I shouldn’t use @foo in git commits https://github.com/mdom/txtnish/commit/42f9715b7d136393a2665566ee96b61bd1a20a87
New stuff in #txtnish: Better argument parser, automatic url rewriting for redirects and a new silly mode that let you share urls like @kas@enotty.dk
#txtnish now supports long options! It’s not easy to implement all cases, but it wasn’t as hard as i though it would be.
@kas@enotty.dk Yeah, i though about adding it for the future ncurses frontend. Maybe i could also add the urls as comment in txtnish reply.
#txtnish now accepts ws as seperator and timestamps without T
@phil@philmcclure.duckdns.org 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
What about benaiah first idea for #issue48? It would be easy to parse, looks very unixlike and doesn’t clash with the current syntax? I would implement it for txtnish, if it wouldn’t be the only implementation… :)
@freemor@freemor.homelinux.net Or we resort the timline to have the newest entries on top, then you could just request the first x bytes of every feed. But archiving is definitly the pragmatic solution. Get back to me if you want to have that in txtnish. Or maybe someone want to submit a PR?
#txtnish can send new tweets per mail to you with txtnish mail bob@example.com … the only missing step is to tweet via mail. #mobile
@tx@0x1A4.1337.cx Is you page publicly accessable? Maybe i should add exporting to html to #txtnish, seems like a thing many users wan to to?