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

@ionores@twtxt.net “Perseverance ! 👏🎉😀” <3

@adi@twtxt.net Thanks, man. I’ll take a look.

@prologic@twtxt.net Logs say it’s just you :)

@prologic@twtxt.net 36% of requests since I enabled logs

@golang_news @prologic@twtxt.net Woot!

@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).

@twtxt.net@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.

@jlj@twt.nfld.uk “@niplav (#4qeibma) Hadn’t heard of this; thanks for the tip! Been getting lost in your text reviews; the Benatar piece piqued my interest: I’d been reading a critique of his earlier work – in Overall’s Why Have Children? – that really wasn’t up to scratch. Now I’m reading about pure replicators, which is a new concept, to me. :-)” -> Nice :-) Looking over my text reviews, they’re not quite finished (especially the Benatar one), so take it with a grain of salt

@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.

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.

@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.

@prologic@twtxt.net :-D i consider myself subpar on UX outside of React, but can def give it a stab.

@prologic@twtxt.net we would want:

• a way to reply to the current thread. We have this.
  
• a way to reply to a specific twt. Need this. Maybe make all the replies start new conversations?
  
• check if twt is start of a conversation.. we kinda have this in the main feed with the conversation button. need to extend it for forked convs
  
• a way to inline first replies. maybe show one or two in the sub thread with a link to view.
  
• for convenience have a link to parent conv?

@xuu@txt.sour.is @prologic@twtxt.net see how it has a bar on the first level reply?

@xuu@txt.sour.is @prologic@twtxt.net we could show first level inline like twitter does. With links for deeper discussion.

@prologic@twtxt.net speaking of complexity.. How would checking twts for sub conversations complexify things?

@prologic@twtxt.net would that need a NLP library? The lang would be great for a search engine to find language prefs.

@prologic@twtxt.net @darch@twtxt.net Like with many things that live in a diaspora there will be many names for about the same thing. Just look at e-mail headers!

@vain@www.uninformativ.de I have seen it pop up on a few feeds around and adopted it into the new parser I built.

The format I have followed has been '# ' :whitespace: :key-name: :whitespace: '=' :whitespace: :value: keys can be repeated and accessed like an array of values.

@prologic@twtxt.net fixed.

@prologic@twtxt.net

@prologic@twtxt.net I know! it has 55 new emoji!! \u1F90C

@prologic@twtxt.net @jlj@twt.nfld.uk @thewismit@twtxt.psynergy.io https://gist.github.com/JonLundy/fb2a23c003be46c3a66e4b14e5971f13

@xuu@txt.sour.is @prologic@twtxt.net @thewismit@twtxt.psynergy.io ah.. probably a bug with the re parser. looks like i can do it without the <>’s with lex

https://fosstodon.org/@thewismit/105673078150704477

@thewismit@twtxt.psynergy.io @prologic@twtxt.net Yo. wrap that naked link in some <>’s https://fosstodon.org/@/105673078150704477

@iolfree@tilde.club “I just typed in ‘censorship’ on pinterest and that is also completely banned.” https://i.imgflip.com/1ppi4p.jpg

@prologic@twtxt.net deedum for android.

Kristall for OS X

Elaho for iOS

more here

though I can only vouch for the first two.

@thewismit@twtxt.psynergy.io @darch@twtxt.net @adi@twtxt.net @prologic@twtxt.net There is another: @hecanjog@hecanjog.com

@prologic@twtxt.net That is strange.. i wonder if there is another change that is causing it. Benchmarks are thinking the other way :|

BenchmarkAll/retwt-16                  1        4940172200 ns/op       587319376 B/op    2587159 allocs/op
BenchmarkAll/lextwt-16                 1         775764020 ns/op         9223088 B/op     197557 allocs/op
BenchmarkParse/retwt-16                1         591158277 ns/op        67539096 B/op     230841 allocs/op
BenchmarkParse/lextwt-16               1         716961837 ns/op         5450448 B/op     130290 allocs/op
BenchmarkOutput/retwt-html-16          1        8358103017 ns/op       918709168 B/op    4692292 allocs/op
BenchmarkOutput/lextwt-html-16         1         822033267 ns/op        14280112 B/op     261795 allocs/op
BenchmarkOutput/retwt-markdown-16      1        8114225415 ns/op       929928384 B/op    4693004 allocs/op
BenchmarkOutput/lextwt-markdown-16     1         806554306 ns/op        14332608 B/op     270905 allocs/op
BenchmarkOutput/retwt-text-16          1        8098215897 ns/op       923862192 B/op    4684739 allocs/op
BenchmarkOutput/lextwt-text-16         1         745064673 ns/op        12689784 B/op     252476 allocs/op
BenchmarkOutput/retwt-literal-16       1        4068799822 ns/op       409517880 B/op    2372471 allocs/op
BenchmarkOutput/lextwt-literal-16      1         754793627 ns/op         9834520 B/op     214931 allocs/op

@xuu@txt.sour.is @jlj@twt.nfld.uk @hxii@0xff.nu only if you look at the raw text file https://0xff.nu/blog.txt

@jlj@twt.nfld.uk oh dang the reply didnt add the reply. It was to @hxii@0xff.nu because Firefox shows his shruggy like ¯\_(ツ)_/¯

@prologic@twtxt.net @hxii@0xff.nu I’m certain that it is a markdown thing. Its that way on other markdown sites like Reddit. Because the underline is being escaped to prevent the underline style. Gotta double it up ¯\_(ツ)_/¯