Sorry about the Panthers.
I will release the sourcecode for the desktop client tonight. I will put it on github (sorry to anyone who prefer other places), but the reason is that I do not want my own git to be open for public. So I’ll put it on github where I have all my other public projects. I have to write the readme, then add some info on the login page (link to source etc), then it’s ready to release with the current features. I then hope others will give it a try and use it if they want :) I also have many other features I need to implement, but all the main features that makes it usable has been implemented, so I’m very pleased with it (And I use it all the time now).
I played around with parsers. This time I experimented with parser combinators for twt message text tokenization. Basically, extract mentions, subjects, URLs, media and regular text. It’s kinda nice, although my solution is not completely elegant, I have to say. Especially my communication protocol between different steps for intermediate results is really ugly. Not sure about performance, I reckon a hand-written state machine parser would be quite a bit faster. I need to write a second parser and then benchmark them.
lexer.go and newparser.go resemble the parser combinators: https://git.isobeef.org/lyse/tt2/-/commit/4d481acad0213771fe5804917576388f51c340c0 It’s far from finished yet.
The first attempt in parser.go doesn’t work as my backtracking is not accounted for, I noticed only later, that I have to do that. With twt message texts there is no real error in parsing. Just regular text as a “fallback”. So it works a bit differently than parsing a real language. No error reporting required, except maybe for debugging. My goal was to port my Python code as closely as possible. But then the runes in the string gave me a bit of a headache, so I thought I just build myself a nice reader abstraction. When I noticed the missing backtracking, I then decided to give parser combinators a try instead of improving on my look ahead reader. It only later occurred to me, that I could have just used a rune slice instead of a string. With that, porting the Python code should have been straightforward.
Yeah, all this doesn’t probably make sense, unless you look at the code. And even then, you have to learn the ropes a bit. Sorry for the noise. :-)
*sorry: connection
“sorry dude, you have vingean uncertainty over the EA community”
Sorry, not a big conspiracy fan. I don’t like conspiracy theories.
@darch@neotxt.dk @prologic@twtxt.net thanks for looking into this, and sorry for not getting back to you on it sooner (busy week)..
Last-Modified
header for your feed, so the official twtxt client complains not to cache it. I just fixed that, so that tt shows your feed (of course no progress has been made in the meantime). And the Date
header of your server seems to be quite funny, too. ;-)
@lyse@lyse.isobeef.org, hey, thank you! :-) Yeah, I am abusing the headers on ferengi.one, sorry about that. Will change it. You know, because Lyse.
@quark@ferengi.one Fixed the “Enter” key issue, sorry about that. I’m dumb 🤦♂️ Also I hate Javascript! 🤬
@prologic@twtxt.net sorry about the spelling mistakes. English is my third language.
Also I didn’t mean to question the vision as such.
Just ment a mobile up that pulls in files directly from the users follow list would line up better with the idea of decentralizing personal data. Since not everyone will be running a pod, but most everyone can have a public facing folder. Specially now with services like Skynet coming online.
Sorry hope I didn’t offend you too much.
Sorry if anyone saw my last Yarn here… I deleted it, I was wrong. Looks like everything is encrypted attachments phew but my other concerns above still stand.
@movq@www.uninformativ.de, is removing the hash from the body of the twt on the TODO? I read it, but I am unsure if it is there already, or not. 🙈 Sorry if it is, and I failed to spot it!
@fastidious@arrakis.netbros.com sorry. the fix was around having a mention in parenthesis like (yo @prologic@twtxt.net)
@adi@f.adi.onl Ugh sorry for not replying. If the file list is dynamic, usually you use something like autoconf to generate the Makefile. I’ve also used wildcards in the past and that works okay. You should be able to use shell commands to populate the file list.
Now talking about HomePod Mini. Not interested, sorry.
@movq@www.uninformativ.de
Sorry! 🙈
@prologic@twtxt.net I knew you were short sided from day one I saw Yarn. On desktop everything is huge, and I assumed it was to cater short-sightedness. Also, you have enabled underlines on buttons on iOS, bold and bigger fonts, etc., so that was also a give away. Sorry if I digress, but, glasses wouldn’t help? I have to wear mine all the time, otherwise I am also near blind myself!
@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.
sorry for the twtstorm o.o
@prologic@twtxt.net lol.. sorry about the spam
I just built a poc search engine / crawler for Twtxt. I managed to crawl this pod (twtxt.net) and a couple of others (sorry @etux@twt.u53.us and @xuu@txt.sour.is I used your pods in the tests too!). So far so good. I might keep going with this and see what happens 😀
Sorry but I do not have it in me to start 2021 with any optimism
Short Notice: Appearing on Millenniyule TONIGHT at 7PM New York Time
Sorry for the short notice, I’ve been busy for the holidays, but I’ve been asked to be interviewed on Millenniyule in less than two hours from when I’m posting this. I’m scheduled for 7PM to as late as 9PM New York time.
The livestream will be on this channel (i.e. not my own due to bandwidth issues).
If you miss it, you can get it [at the bottom of this playlist](https://www.youtube.com/ … ⌘ Read more
@lucidiot@tilde.town haha oops! sorry about that. It’s fixed now.
@Leo@www.gkbrk.com Sorry to disappoint. I think I have Finger running on my Raspberrypi but didn’t make it public.
@kas@enotty.dk Sorry I never replied. Haven’t quite gotten up to speed, here, but investigating the blog issue and twistnik!
@mdom@domgoergen.com The last tweet regarding #txtnish should point at you not @kas@enotty.dk Sorry. 😔
@freemor@freemor.homelinux.net What ‘tweet alias’?
I’m so sorry to all twtxters for all the changes that my twtxt file is getting
@mox@tilde.town Sorry had no time yesterday and today I’m also busy but maybe I find the time to dig in my configs.
/meta @ckipp@chronica.xyz Ok, I figured it out, sorry :) I entered my local time manually and forgot it’s supposed to be UTC, so my posts were in the future.
@kas@enotty.dk Sorry, i haven’t tested the build-script, should be fixed now #termpub
@kas@enotty.dk Sorry, i haven’t tested the build-script, should be fixed now #termpub
Stick To The Script!!! [SORRY TO BOTHER YOU film analysis] - YouTube https://www.youtube.com/watch?v=UGnQLgpaupU
I regret to inform everybody that Data Privacy Day was actually last Monday. We all missed it. Sorry. Honorary Data Privacy Day every Monday for the next 2 years to make up for it, kay?
I reduced (sorry (not sorry)) an entire blog post into my previous twtxt post and I’m not sure if I should be happy or not. It might’ve been a perfectly adequate blog post.
Love it we have a “contract” developer but he is not in the right group to push commits to the code repo. When I suggested that he be added to the right group one of the other developers was like that will give him access to everything. I’m sorry but what is everything? It’s not like he can pull from any of the repos as it is. Right now he just can’t commit.
Sorry, but we can’t fantasize our way out of this mess https://amp.fastcompany.com/90247038/sorry-but-we-cant-fantasize-our-way-out-of-this-mess
Read some excepts from a book I randomly found yesterday. While the writing was a little dry, I thought it could be an interesting read. However when I looked on Amazon, found out the book was 80 USD. I’m sorry but it was not that interesting.
Im sorry twtxt, I dont mean to ignore you… things are fine here, except my brain is made of snail poop
iOS autotweet test #sorry
“In the World of Film, We’ve Edited out All Rebellion” https://jacobinmag.com/2018/08/sorry-to-bother-you-boots-riley-interview
@71m@timmorgan.org If your nick is mentioned with @ (i forgot yesterday, sorry) most clients should highlight it in your timeline if you are following the person mentioning you.
Sorry, for being quite noisy now but it is really fun using #twtxt over #xmpp, am very proud it somehow works even when I’m no programmer.
@durcheinandr@durcheinandr.de Sorry, no idea then. I have a ticker with news agencies like dpa, afp etc. at work but that’s more like a firehose.
@durcheinandr@durcheinandr.de Sorry, no idea then. I have a ticker with news agencies like dpa, afp etc. at work but that’s more like a firehose.
@trevor@destroyed.today, @tx@0x1A4.1337.cx Sorry, too many new users! :) @tx@0x1A4.1337.cx suggested printing the messages to stdout.
@trevor@destroyed.today, @tx@0x1A4.1337.cx Sorry, too many new users! :) @tx@0x1A4.1337.cx suggested printing the messages to stdout.
Yeah, sorry, i meant epoch, which doesn’t count leap seconds.
Yeah, sorry, i meant epoch, which doesn’t count leap seconds.
You can find my twtxt feed at https://domgoergen.com/twtxt/mdom.txt Sorry for the trouble!
You can find my twtxt feed at https://domgoergen.com/twtxt/mdom.txt Sorry for the trouble!
Just added a search field for users and tweets at https://roster.twtxt.org And sorry for just tweeting about new features…
Just added a search field for users and tweets at https://roster.twtxt.org And sorry for just tweeting about new features…
@dracoblue@dracoblue.net Sorry, but what tweet are you referring to? I have no idea what sounds great… We need a way to reference tweets!
@dracoblue@dracoblue.net Sorry, but what tweet are you referring to? I have no idea what sounds great… We need a way to reference tweets!
@quite@lublin.se Ah sorry, should have checked the commit. #twet is officially the first twtxt client with colors! :)
@quite@lublin.se Ah sorry, should have checked the commit. #twet is officially the first twtxt client with colors! :)
As german speaker i missed the unintended meaning of txtwat. Sorry, if anybody was offended. The project is now called txtnix.
As german speaker i missed the unintended meaning of txtwat. Sorry, if anybody was offended. The project is now called txtnix.