@prologic@twtxt.net lol. quitfacebook.org is still up. twt is set to be on more radars, though. ;-)

@prologic@twtxt.net sometimes I think it would be nice to have a XMPP instance. then I remember it’s all XML and I think “nah.”

I am constantly in awe that IRC remains the only realtime chat that isn’t unnecessarily complex. name another that can run chatops bot with just nc and sh?

The 140 character limit of the twtxt spec is annoying. I hope you got the essence of my previous post.

FOLLOW: @xuu@txt.sour.is from @adi@46.23.94.13 using twtxt/0.1.0@7098fcf

@prologic@twtxt.net Yeah, a completely-unsolicited surprise! :-) And, sweet! To IRC then!

@prologic@twtxt.net Yeah, a completely-unsolicited surprise! :-) And, sweet! To IRC then!

@adi@twtxt.net “@niplav What kind of thinking?” Leaning towards explicit abstract reasoning, though, if I would be pressed.

@adi@twtxt.net “@niplav What kind of thinking?” Nearly everything, I guess? More concretely: What falls into the category of whatever spans {deciding where to sit, deciding whether to blame someone else for something, catching a ball, picking a good career, proving a theorem}.

@prologic@twtxt.net @xuu@txt.sour.is Closer! Last bit to finish is a beast. FormatTwtFactory

@vain@www.uninformativ.dedd @lyse@lyse.isobeef.orgdd @prologic@twtxt.netdd Nope.. i have updated my gist to include the feeds listing. feeds.txt

@prologic@twtxt.net that seems to match my numbers. are you picking up the few gophers out there?

kinda makes me wonder about the ~300k you have cached. y’all got the library of alexandria over there.

FOLLOW: @stats@txt.sour.is from @xuu@txt.sour.is using twtxt/0.1.0@9d7b86c

@prologic@twtxt.net in theory shouldn’t need to let users add feeds.. if they get mentioned by a tracked feed they will get added automagically. on a pod it would just need to scan the twtxt feed to know about everyone.

@prologic@twtxt.net sounds about right. I tend to try to build my own before pulling in libs. learn more that way. I was looking at using it as a way to build my twt mirroring idea. and testing the lex parser with a wide ranging corpus to find edge cases. (the pgp signed feeds for one)

Well, my twtxt reader is a bit too simple; drops who actually wrote the message before it’s printed. 🤦🏻

@prologic@twtxt.net the add function just scans recursivley everything.. but the idea is to just add and any new mentions then have a cron to update all known feeds

@prologic@twtxt.net yeah it reads a seed file. I’m using mine. it scans for any mention links and then scans them recursively. it reads from http/s or gopher. i don’t have much of a db yet.. it just writes to disk the feed and checks modified dates.. but I will add a db that has hashs/mentions/subjects and such.

@prologic@twtxt.netd It is pretty basic, and depends on some local changes i am still working out on my branch.. https://gist.github.com/JonLundy/dc19028ec81eb4ad6af74c50255e7cee

@lyse@lyse.isobeef.org @prologic@twtxt.net very curious… i worked on a very similar track. i built a spider that will trace off any follows = comments and mentions from other users and came up with:

twters:  744
total:  52073

curl https://raw.githubusercontent.com/jointwt/we-are-twtxt/master/we-are-twtxt.txt | grep -v '^niplav ' | field 2 | xargs curl ^/dev/null | grep niplav here we go

@prologic@twtxt.net “What the hell does cartesianly mean?! 😳” Me inventing a new adjective for “there is only a one-way flow of information” ^^

Maybe I could write a script that trawls the we-are-twtxt list and notifies me when I’m mentioned–the name should be unique enough.

Disadvantage of twtxt: less incentives to reply to people since it’s not certain they’ll ever see it. My current solution to that is to follow everybody on the we-are-twtxt and only unfollow if they twt a lot of stuff I’m not interested in

@felixp7@twtxt.net “Yo, crypto-heads. Encrypted communication doesn’t protect your privacy. Laws …” I guess crypto-heads are often happy with acknowledging this, but also arguing that e.g. deniable crypto is a useful way out here (and, of course, just doing illegal stuff if it gets really rough).

FOLLOW: @xuu@txt.sour.is from @niplav@niplav.github.io using txtnish/0.2

Following with interest the developer activity regarding the twtxt spec at twtxt.net

Following with interest the developer activity regarding the twtxt spec at twtxt.net

apparently you can compose multi-line twtxt’s with txtnish but it won’t render them? maybe should patch it to support the line-break proposal here? https://dbohdan.com/wiki/twtxt-line-breaks

number of GET /twtxt.txt requests against my server, grepped from my nginx access logs: https://jb55.com/s/e75071f023eeaf90.txt

Okay, my #twtxt reader works-ish. Need to properly deal with timezones (and, um, maybe do any error checking).

I have a working model for the reader portion of what I want this twtxt client to do.

@prologic@twtxt.net I am trying to cut costs, so I deleted all my Digital Ocean droplets. For a month I will be using a free s390x VPS, so I needed to adapt some of my Docker images, scripts and configurations for that architecture. Also took another chance with Traefik Proxy, I ditched it long ago for nginx-proxy, but this time I made it work. #h5nn5tq

@prologic@twtxt.net I am trying to cut costs, so I deleted all my Digital Ocean droplets. For a month I will be using a free s390x VPS, so I needed to adapt some of my Docker images, scripts and configurations for that architecture. Also took another chance with Traefik Proxy, I ditched it long ago for nginx-proxy, but this time I made it work. #h5nn5tq

@vain@www.uninformativ.de the truth is, i never “got” or liked twitter. i think it’s way too noisy and a terrible way to have a conversation, what with the character limit and all. and then mastodon came along and i thought it would be different, but then it became too twitter-like. i get what you mean about twtxt and discoverability, that is one of its drawbacks.

@vain@www.uninformativ.de i don’t think mastodon is a good idea but then again i never really understood the twitter format and its appeal, so there’s that.

@prologic@twtxt.net that I do. lol. I am xuu on hackint.org and freenode

@prologic@twtxt.net sure. I don’t use signal much because I have to disclose my personal phone. Telegram? https://www.t.me/xypheri

@xuu@txt.sour.is @prologic@twtxt.net Your feed was great for catching edge cases ;)

@prologic@twtxt.net https://github.com/JonLundy/twtxt/tree/xuu/integrate-lextwt I made a stats command for the new parser that extracts a bunch of info about a twtxt file. run like: go run ./cmd/stats https://twtxt.net/user/prologic/twtxt.txt

FOLLOW: @xuu@txt.sour.is from @lyse@lyse.isobeef.org using twtxt/1.2.3

@prologic@twtxt.net yep!some of the lexer is directly copied from monkey-lang. love that book series.

@prologic@twtxt.net ah I need to add an edge case for naked urls with fragments.

@prologic@twtxt.net yep. it actually extracts everything at parse time. like mentions/tags/links/media. so they can be accessed and manipulated without additional parsing. it can then be output as MarkDown

@adi@twtxt.net @prologic@twtxt.net using regex. which can be a rather inexact science ;)

@prologic@twtxt.net kinda.. It can parse the twts into an AST.. but most of the formatting out expects a string to do regex over rather then the parsed AST. thats what i am working out next.

@prologic@twtxt.net as promised! https://github.com/JonLundy/twtxt/blob/xuu/integrate-lextwt/types/lextwt/lextwt_test.go#

the lexer is nearing completion.. the tough part left is rooting out all the formatting code.

the !zet I have written for my wiki is probably going to end up replacing what I’ve been using twtxt for these past few months. this means less spam here. you’re welcome.

@prologic@twtxt.netdd ooh I am adding that to my test suite

@prologic@twtxt.net @gareppa Tis fake.. that is the name of the tower in Die Hard. A movie that takes place on Christmas Eve. The actual name of the Nakatomi Plaza is the FOX Plaza.

@prologic@twtxt.net I agree, should have asked for help. Neither the bridge network nor any other bridge-based custom network allowed the containers to contact external servers, it might have been an iptables issue. #twflvza