Searching txt.sour.is

Twts matching #sorry
Sort by: Newest, Oldest, Most Relevant

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

⤋ Read More

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. :-)

⤋ Read More
In-reply-to » Welcome back, @quark! Your web server doesn't send back a 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.

⤋ Read More
In-reply-to » @tamer We're not trying to compete with anything... If you've read About Yarn.social -- In a nutshell I want to create an open, transparent social platform that respect's folks privacy and freedoms. It must also be easy to use and down-to-earth where human interactions actually matter. None of this rubbish of manipulating what you see, driving up engagement numbers to serve your advertisers and all that garbage

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

⤋ Read More

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

⤋ Read More
In-reply-to » Apple Event for 18 October 2021, 10:00 PDT, 13:00 EDT begins. Commentary will stream as replies to this twt. I might miss things here and there, as I will also be on a work meeting from 13:00 to 14:00 EDT.

Now talking about HomePod Mini. Not interested, sorry.

⤋ Read More

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

⤋ Read More

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

⤋ Read More

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?

⤋ Read More

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.

⤋ Read More

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.

⤋ Read More