FOLLOW: @twtxt@txt.sour.is from @xandkar@xandkar.net using tt/0.19.1
”@niplav (#kfgri5a) There are no expectations when you’re honest. Expectations and honesty don’t mix.” -> I honestly wasn’t expecting that answer :)
FOLLOW: @xuu@txt.sour.is from @reednj@twtxt.xyz using twtxt/1.1
FOLLOW: @xuu@txt.sour.is from @xandkar@xandkar.net using tt/0.19.1
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.
@jlj@twt.nfld.uk “@niplav (#xvbnyma) Fascinating. :-) Suspect #RMS would have a violent physical reaction – accompanied by some salty language – after even a moment’s contemplation of life under such complicity. :-D” -> He is a very unreasonable man <3
@alip@dev.exherbo.org “We are calling for Richard M. Stallman to be removed from all leadership positions, including the GNU Project. https://rms-open-letter.github.io/” highly contextual/simulacrous memeplexes exclude high-variance impact neuroatypicals, nobody thinks about incentives?
FOLLOW: @xuu@txt.sour.is from @xandkar@xandkar.net using tt/0.15.0
Found a PGP signed twtxt feed. I’ve been thinking about this, I wonder how many clients it breaks. https://domgoergen.com/twtxt/mdom.txt
/twtxt.html, at 12.9KB, is now the largest HTML document on https://mckinley.cc/.
@adi@twtxt.net I am not. :-)
FOLLOW: @xuu@txt.sour.is from @codebalion@twtxt.prismdragon.net using txtnix/0.07
@(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.
FOLLOW: @xuu@txt.sour.is from @reednj@twtxt.xyz using twtxt/1.1
@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/
↳
In-reply-to
»
My finger server now includes the last post from tw that doesn't have a subject. 'finger a@9srv.net'
⤋ Read More
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.