
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.
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.
@prologic@twtxt.net :-D i consider myself subpar on UX outside of React, but can def give it a stab.
twtxt.net looks quite nice, but i wish it was designed to encourage an offline / async workflow
@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 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!
but if we kept things simple stupid I how would the poor little darlings in middle-management have a job? 😂
@xuu@txt.sour.is Speak of lang… Do you think we could detect the user’s lang by what they write? Probably just inspect a random subset?
@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 I know! it has 55 new emoji!! \u1F90C
💁♂️ If you’re ever on a UNIX machine of some kind without any useful networking utilities like ip or ifconfig, fear now! You can view the network topology of the Kernel by just doing:
cat /proc/net/fib_trie
@prologic@twtxt.net @jlj@twt.nfld.uk @thewismit@twtxt.psynergy.io https://gist.github.com/JonLundy/fb2a23c003be46c3a66e4b14e5971f13
@jlj@twt.nfld.uk @thewismit@twtxt.psynergy.io Custom Pod Logos are now available with PR 358 🎉 if you’d like to checkout this PR on your pods and recompile and let me know how it goes that would be swell 👌
@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
@thewismit@twtxt.psynergy.io @prologic@twtxt.net Yo. wrap that naked link in some <>’s https://fosstodon.org/@/105673078150704477
@prologic@twtxt.net deedum for android.
Kristall for OS X
Elaho for iOS
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