@(frogorbits.com) @niplav@niplav.github.io “I sign a lot less stuff these days now that my phone can pretend to be a credit card. Also: an impostor with a quantum computer can’t pretend to sign documents on my behalf…” -> It’s good that pen signatures are completely unfakeable. They’re unbelievably reliable. We can’t just copy & photoshop around the edges. Better worry about those definitely-soon-to-exist quantum computers that might crack cryptography.

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

@prologic@twtxt.net Twtxt.net’s privacy policy says you store emails, /register disagrees. Which is true?

@adi@twtxt.net “I usually seen the opposite. Women are more interested in longevity and happy that studies show that they live more than men.” -> I probably could have been clearer: It seems to me that women are on average much less interested in life-extension (methods beyond usual health advice such as the old “exercise, eat vegetables”) than men. This might just be founder/sampling bias (life extension comes out of the relatively male dominated libertarian/techno-optimist cluster). Actually, maybe there’s just a variance thing here: median man cares less about his longevity than the median woman, but the variance for men is higher.

@jlj@twt.nfld.uk “A good read: Why I find longtermism hard – […]” -> Interesting! I don’t particularly share that emotional intuition (although my bias probably cuts the other way: I am more moved by interesting projects, and more interesting problems probably also less neglected)–I generally find most problems other people find salient not very moving at all (although probably equally strongly moved by extremely near suffering compared to other people, but with a stronger emotional distance discount). EA makes sense in a very different way to me (phenomenologically, probably closest to philosophical high valence states it evokes).

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.

@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

@prologic@twtxt.net Vim, and it’s really not that awful.

@prologic@twtxt.net 36 characters left makes it rough.

@darch@twtxt.net Just inline images, they wrap like text.

@adi@twtxt.net I can’t find it now, keep an eye out for it.

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

@jlj@twt.nfld.uk “Anyone running Urbit? Thinking about having a play with a comet. ☄🌒” -> Just as @movq@www.uninformativ.de has problems with his reading queue, I have problems with my “things to explore” queue. I even bought a planet a while back, but haven’t had time to dive into the extradimensional madness of the urbit system. Subjective impressions & reviews highly anticipated!

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