@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.
@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.
xn–dw9h.social is taken :-(
@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!
The keys that have some use would be nick, url/feedurl, avatar, lang
@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
Hmm on mobile it shows as the text :poop: and not 💩
Maybe the mobile version has text emoji substitution like slack/discord does?
ip or ifconfig, fear now! You can view the network topology of the Kernel by just doing:
Related bookmark: https://command-not-found.com/
@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
@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
lextwt branch. There's a noticeable ~2x increase in CPU usage across the board since I deployed this at ~16.30pm (AEST).
@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 ¯\_(ツ)_/¯
Are you able to coax your webserver to add the charset to the content type header? Browsers are having a hard time thinking you are sending latin-1
content-type: text/plain; charset=utf-8
@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 ¯\_(ツ)_/¯
@hxii@0xff.nu Recursion is the best recursion!
@hxii@0xff.nu There is another twter that uses !<wikiword wikiaddr> or !wikiword for their wiki intigrations.
@lyse@lyse.isobeef.org @prologic@twtxt.net @vain@www.uninformativ.de A penny saved is a penny depreciating at a rate of 1.4% per annum.
@lyse@lyse.isobeef.org @prologic@twtxt.net I think lex will do that too currently. Should be able to lock that down.
@lyse@lyse.isobeef.org (#ezmdswq) Looks good for me!
@thewismit@blog.thewismit.com @prologic@twtxt.net I too wonder about this.
@prologic@twtxt.net @thewismit@blog.thewismit.com () possible, or a pod following any feeds it finds, if any one follows or not. So it has more twts cached
@prologic@twtxt.net () Should be ready to merge with lex as opt-in option. Need more eyes on it and some clean up.
@prologic@twtxt.net @thewismit@blog.thewismit.com () Ya I get that error a lot. I mostly use the web on mobile as a result.
@prologic@twtxt.net i think i finally suss’d out my hash issue.. now to figure out why im losing avatars on restart.
@prologic@twtxt.net @thewismit not sure.. im using Caddy instead of nginix
@prologic@twtxt.net lol.. sorry about the spam
@xuu@txt.sour.is @prologic@twtxt.net (#6jkpxzq) hmm from what i can tell its parsing ok.. something got broken in the markdown conversion…
@prologic@twtxt.net hmm this line seems to be tricky to parse. will need to look into it.
@prologic@twtxt.net test. Running new parser on txt.sour.is. :D
@prologic@twtxt.net that would be an interesting idea. I think your current spec of using an SMTP proto is probably best for DM.
but having a federation of IRC servers would be interesting for realtime twt propagation.
@prologic@twtxt.net the meta info on the top I added manually. it’s following what I have seen from some other twtxt feeds. the new parser will read them.
@prologic@twtxt.net Veri soon. I have a experimental runflag that I am just about to deploy to my node. I have a few show stoppers holding me back.