@prologic@twtxt.net @adi@twtxt.net @jlj@twt.nfld.uk @readfog I too would love to see the “internal” package decrease and clearly defined / modular packages increase.

@prologic@twtxt.net I would to build a Chinese version, have you considered supporting different languages? I translated a README file.

Sure. I think search, if it’s going to exist, should be the client’s responsibility. But I also value the readability of the raw twtxt file a lot more than y’all do.

Playing around with #GLSL #shaders and webcam in #KodeLife

9rpi memex is coming along https://pub.sunshinegardens.org/xjix/twtxt/screens/clone-memex-done.png

Live coding #improviz

@adi@twtxt.net I am not. :-)

@adi@twtxt.net Some linux; how does one tell which?

peak aesthetic https://pub.sunshinegardens.org/xjix/twtxt/peak-aesthetic.jpeg

Twtxt is distributed like in the old school unix2unix copy days

@lyse@lyse.isobeef.org (#hut4mnq) I am so sorry for you. I left my Java job for Go. Though through “restructuring” its become a Python job.

I am very excited about this, and it seems like something the twtxt crowd might enjoy: https://anewsession.com/

Huh. In my feed, there is (correctly) a backslash before that . in the sed command, but twtxt.net is stripping it.

@lyse@lyse.isobeef.org What do you do at your day job?

@prologic@twtxt.net Bug in your profile links: it’s repeating a segment. For example, your face tries to get to https://twtxt.net/user/https://twtxt.net/user/prologic/twtxt.txt

@thewismit@twtxt.psynergy.io @jlj@twt.nfld.uk in old school terminal jargon the ^H means control H or the sequence used in some terminals to indicate backspace. The “joke” is that the term failed to interpret it correctly and you can see the partially typed word before they changed it.

WIP for a new branding and top-navn

@adi@twtxt.net @movq@www.uninformativ.de ah.. looks like you still follow movq as vain.

mm yeah newlines without unicode is much better https://github.com/jointwt/twtxt/issues/215

seems like the \u2028 approach breaks some clients, maybe i will try another way https://github.com/jointwt/twtxt/pull/166

this web discourse is pretty hilarious, time to stop checking twtxt.net tho XD i can just stick to my own subs ^^

@golang_news @prologic@twtxt.net Woot!

it would appear that twtxt puts me into the same domapine loop i would like to avoid this please.

@xuu@txt.sour.is Errors are gone! 👌

@xjix@xj-ix.luxe Saw your oldish note about wanting an offline/async twtxt workflow. Do you have something that works for you? My (very young!) client was designed with that in mind.

@prologic@twtxt.net Exactly, but that reduces the argument for URLs in the post. The client should figure out how to search based on the hashtag.

@bml@twtxt.net Yup, several. My favorite is RFC 1149, another that’s since been implemented. https://en.wikipedia.org/wiki/April_Fools%27_Day_Request_for_Comments

@prologic@twtxt.net You may be interested in https://github.com/u-root/u-root (I work with a contributor).

@bml@twtxt.net It was totally an April Fools’ joke; the IETF has a bunch of those. But! It has also been implemented. And 418 is my favorite error code.

I’m unclear if I’m going to do the twtxt.net discovery protocol; neither my web server nor Plan 9’s default capture agent strings. :-/

@prologic@twtxt.net @anth Sounds like a good idea. The hash to conv/search url should stay local to a pod.

@prologic@twtxt.net Looks like twtxt.net is already happy with it, so that’s good! I’m just going to aim for that.

My silly Plan 9 rc twtxt client now has a web page: http://txtpunk.com/tw/index.html

@prologic@twtxt.netFor example, this should work (no idea if it does).

@prologic@twtxt.netYes, I think tags should just be #foo, and let the client figure out searching if it cares.

@lyse@lyse.isobeef.org Yes, I often read the raw messages. But more to the point, the simplicity of the format is the bulk of the appeal.

@movq@www.uninformativ.de No argument that threading is an improvement. But I think (#hash) does that, and I think figuring out how to search should mostly be up to the client.

I don’t have any issue with the (foo) subjects, it’s the proliferation of the (foo url) tags. They’re just too long and ugly.

@prologic@twtxt.net yah I’ll get a fix out soonish

@darch@twtxt.net @prologic@twtxt.net Technically it should be at the start.. Though the parser doesn’t currently care where it is. Though that leads to artifacts like any random string inside perens becoming a subject.

Tutorial - Write a Shell in C • Stephen Brennan

cc @adi@twtxt.net

Hah… my silly twtxt client now has “stories” mode.☺

I don’t think I’m implementing twtxt.net-style hashtags (for now?). The “” is bad enough for nicks, but they just make the plain text unreadable.

@prologic@twtxt.net I’ve just never had it be a rewarding experience.

@prologic@twtxt.net rc, the Plan 9 shell.

@prologic@twtxt.net tricky.. punctuation is being grouped in with other text. i need to break up string tokens.

Hey @xuu@txt.sour.is another mention that didn’t render ☝️

@thewismit@twtxt.psynergy.io Hey! It’s easy. Just install the twt CLI with something like:

go get github.com/jointwt/twtxt/cmd/twt/...

Then use it in some hooks/scripts to post some content to your Pod.

@prologic@twtxt.net its the puny code for the yarn emoji. Though you would want the type-able version to redirect so its not hard to type on non mobile.