@prologic@twtxt.net hmm this line seems to be tricky to parse. will need to look into it.

@prologic@twtxt.net test. Running new parser on txt.sour.is. :D

FOLLOW: @twtxt@txt.sour.is from @xuu@txt.sour.is using twtxt/0.1.0@6987434

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

@prologic it seem to work just fine for the most part. http://darch.dk/twtxt.txt for refernce

FOLLOW: @xuu@txt.sour.is from @asdf@::1 using twtxt/0.1.0@90d1c09

@prologic@twtxt.net that would be an interesting idea. I think your current spec of using an SMTP proto is probably best for DM.

but having a federation of IRC servers would be interesting for realtime twt propagation.

@prologic@twtxt.net the meta info on the top I added manually. it’s following what I have seen from some other twtxt feeds. the new parser will read them.

@prologic@twtxt.net Veri soon. I have a experimental runflag that I am just about to deploy to my node. I have a few show stoppers holding me back.

@prologic@twtxt.net Wow! Really interesting perspective! Thanks for sharing. :-)

@prologic@twtxt.net Wow! Really interesting perspective! Thanks for sharing. :-)

Woohoo, #phpub2twtxt - my php interface for publishing to my selfhosted twtxt.txt is now online at GitHub

Well this looks interesting: https://github.com/jointwt/twtxt

@lucidiot@tilde.town “nuclear realtor” I like this twtxt. [meta: I guess I’ll often just reply with “I like this” or , although perhaps liking could be a primitive. I’ll do it rarely enough to not clutter my timeline tho]

@niplav@niplav.github.io Re: selection pressure against meditation: go on…

@niplav@niplav.github.io Re: not guaranteed to see it: I wouldn’t have bothered waving hi across the Internet if I hadn’t gotten bored one day and grepped my webserver logs for twtxt users.

@prologic@twtxt.net I see Consul service mesh everywhere these days, X-D thanks to a 180 career change and major upskill.

@prologic@twtxt.net I see Consul service mesh everywhere these days, X-D thanks to a 180 career change and major upskill.

@prologic@twtxt.net Really helpful context: was definitely over-engineering. Cheers!

@prologic@twtxt.net Really helpful context: was definitely over-engineering. Cheers!

@prologic@twtxt.net The favicon in particular! :-)

@prologic@twtxt.net The favicon in particular! :-)

FOLLOW: @xuu@txt.sour.is from @jlj@ctrl-c.club using twtxt/1.2.3

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

@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

@niplav@niplav.github.io Re: rats: YOU ARE NOT ALONE