[47°09′47″S, 126°43′24″W] Transponder fixed

[47°09′57″S, 126°43′56″W] Transponder fixed

[47°09′59″S, 126°43′25″W] Transponder fixed

[47°09′35″S, 126°43′55″W] Dosimeter fixed

[47°09′36″S, 126°43′27″W] Dosimeter fixed

[47°09′21″S, 126°43′12″W] Transponder fixed

[47°09′21″S, 126°43′25″W] Dosimeter fixed

[47°09′09″S, 126°43′26″W] Dosimeter fixed

[47°09′32″S, 126°43′48″W] Dosimeter fixed

[47°09′20″S, 126°43′52″W] Transponder fixed

[47°09′32″S, 126°43′56″W] Dosimeter fixed

[47°09′38″S, 126°43′14″W] Transponder fixed

[47°09′11″S, 126°43′39″W] Transponder fixed

[47°09′04″S, 126°43′22″W] Dosimeter fixed

[47°09′21″S, 126°43′05″W] Dosimeter fixed

[47°09′24″S, 126°43′43″W] Transponder fixed

Also - the last thing I needed is sorted, how to get vs code to pick up the default.nix shell environment, there is a really nice addon for vs code that picks up what is in that file, and then set up the environment based on that, meaning I can now open the source, configure, compile and debug with vscode, this was the last piece that was missing. I will write a blog post on my website that explain what I learned, and how I fixed all these things, maybe it’ll help someone else to try NixOS for some development.

I was able to fix this now, by making a ‘default.nix’ file, and then you can open a shell that has all the stuff needed by simply typing ‘nix-shell’ in the root git directory. Pretty nice, I’m starting to enjoy this OS more and more.

Heh, I do not regret it anymore, I was able to create a flake.nix file that builds the desktop client on NixOS.
But I now found a bug with keyring access that I need to fix. but the client compiles and starts.
It does not open the keyring - so it hangs and waits and you need to kill it. On my previous machine the keyring got opened at login by another application.

[47°09′58″S, 126°43′16″W] Dosimeter fixed

[47°09′00″S, 126°43′51″W] Transponder fixed

[47°09′07″S, 126°43′05″W] Dosimeter fixed

productivity under anxiety is a repulsive fixed point (you might even feel worse the closer you get to what you should be doing)

[47°09′32″S, 126°43′54″W] Dosimeter fixed

How to fix a ReDoS
Code scanning detects ReDoS vulnerabilities automatically, but fixing them isn’t always easy. This blog post describes a 4-step strategy for fixing ReDoS bugs. ⌘ Read more

the next thing to fix is thread view, and the reply to.. feature (showing the text preview of the post the reply goes to).

[47°09′32″S, 126°43′04″W] Transponder fixed

[47°09′10″S, 126°43′48″W] Dosimeter fixed

[47°09′26″S, 126°43′59″W] Transponder fixed

[47°09′51″S, 126°43′27″W] Dosimeter fixed

Working on showing attached images in the desktop client, it worked on first try.
Now I need to fix the scale and alignment - but cool that it works already!

Image

[47°09′56″S, 126°43′48″W] Dosimeter fixed

[47°09′17″S, 126°43′07″W] Transponder fixed

Private vulnerability reporting now generally available
Open source maintainers and security researchers embrace a new best practice to report and fix vulnerabilities. ⌘ Read more

[47°09′21″S, 126°43′50″W] Dosimeter fixed

@funbreaker@twtxt.net no need to feel dumb. This is why testing is nice! That being said - ill make a fix for that too :) this is why I appreciate you taking the time to test, because we have now found many things to improve already 😀

@funbreaker@twtxt.net I tested now against twtxt with a account I created -it segfaulted if you had a / at the end of the server url.. My bad.. works if you remove the slash. I will fix it in the client so that it removes the slash if it’s in the server url.

[47°09′00″S, 126°43′15″W] Transponder fixed

@funbreaker@twtxt.net Also, did you compile rapidjson from source? Or install the package with your OS? I built the latest version and installed that - if the problem continues now after I fixed the error on my end - then that might be the cause.

@funbreaker@twtxt.net I have pushed a fix now to git, I now got rid of the error when I use it on my end. I will create a test account on twtxt later tonight (after dinner and all that) if needed. If you test the latest on your end before that - let me know :) And thanks for your patience.

@funbreaker@twtxt.net Ok, I saw that error here now as well - but it does not crash. I have put it in the issue tracker, I will fix it and let you know once I’ve tracked it down.

I’m not super a fan of using json. I feel we could still use text as the medium. Maybe a modified version to fix any weakness.

What if instead of signing each twt individually we generated a merkle tree using the twt hashes? Then a signature of the root hash. This would ensure the full stream of twts are intact with a minimal overhead. With the added bonus of helping clients identify missing twts when syncing/gossiping.

Have two endpoints. One as the webfinger to link profile details and avatar like you posted. And the signature for the merkleroot twt. And the other a pageable stream of twts. Or individual twts/merkle branch to incrementally access twt feeds.

@lyse@lyse.isobeef.org valid points and noted. 😀
It will improve shortly. I had not thought about quotes in password, so that was a nice catch that needs to be fixed.

The code for the desktop client is now public here: https://github.com/stig-atle/YarnDesktopClient , I will create tickets for the known things I need to fix and such later today.

@prologic@twtxt.net hehe, yeah! That’s the way to get things done - use it daily, fix everything that needs to be fixed :)

[47°09′01″S, 126°43′00″W] Dosimeter fixed

@lyse@lyse.isobeef.org Thank you! Yeah I fixed that now, short statuses got shifted, but that has been fixed. :)

One thing I need to also fix - is the way a reply is done, I need it to add the mentions as well, so that you can reply to a person more easily, instead of just the thread.

Moving my source to git today, I have just developed on a local copy until today.
I needed to move it before going too crazy with it. Starting the work on the timeline that I’ve mentioned.
Yesterday I ran out of time, but today I have some free time to work on things. Very pleased with the software already, I know I’ll use it all the time. So today I will work on refreshing the timeline, and then fix so that it’s a bit smarter then now, the class that holds the statuses will also contain the GUI elements for each status, that way I can more easily append new statuses into the timeline - instead of grabbing the whole timeline and rebuild all it’s gui each time it refreshes. I know what to do - so I do not expect it to take too long to fix.

Going out for a hike with the dog. Then I’ll code a bit later today.
Want to fix the timeline refresh, and then create one timeline for each timeline, and buttons to switch between them.

[47°09′55″S, 126°43′00″W] Dosimeter fixed

Got the gui to scale properly with the window now, was easy to fix… Looks much better already!

Image

@funbreaker@yn.vern.cc Hi! I have attached the current screenshot, as you see it’s not done yet, I need to add some things, but a lot of work is already done.
I will fix the remaining things and try to make it usable enough this week so that I can upload the source.
Need to add the remaining reply button, image loading and width of the text etc first.
I had that in the FLTK client, so I just need to add it to this new GTK gui.

Image

Here is what I had with FLTK
https://yarn.stigatle.no/twt/4nuoc7q

I did not have time to work on those things today, ran out of time. But I’ll resume tomorrow.

[47°09′52″S, 126°43′52″W] Transponder fixed

Time to get back at it, I want to fix so that when you hit ‘reply’ it will also add any mentioned user in the reply.

[47°09′23″S, 126°43′57″W] Dosimeter fixed

Timeline is cleaned up, so now I think I have that part sorted.
Next is to refactor a bit and then fix so that the timeline refreshes properly.
Once that is done I think I’ll clean it up and upload the source somewhere and create tickets for outstanding known issues. Most likely upload it to github and continue the work there.

Image

Also- refresh of the timeline needs to be fixed.

Okay, so back at it today. I want to start and fix the text where nick and url is included, strip that away from the text being shown, makes the statuses much more cleaner. Also need to get started on clickable url’s somehow.

Build a secure code mindset with the GitHub Secure Code Game
Writing secure code is as much of an art as writing functional code, and it is the only way to write quality code. Learn how our Secure Code Game can provide you with hands-on training to spot and fix security issues in your code so that you can build a secure code mindset. ⌘ Read more

[47°09′24″S, 126°43′44″W] Dosimeter fixed

[47°09′20″S, 126°43′52″W] Dosimeter fixed

Weekend is here :)
I want to create a frontpage for my website - https://stigatle.no , fix cmake script for the desktop client and compile it on debian. Other then that I’ll walk the dog as usual and spend quality time with my family. Going to be a great one :)

[47°09′10″S, 126°43′22″W] Dosimeter fixed

Okay, so I spent about one hour setting up cmake, fltk and libcurl for c++, got all that running now.
I still need to fix the cmake script a bit, but I have a working verison now with this.
I will now add the same curl stuff I had in rust in c++, then work on the gui and all that.
So I will drop rust, and go for c++ instead, much easier for me. Was worth a try in rust, but for now that’s not for me to be honest, I much faster and better in c++.

[47°09′59″S, 126°43′16″W] Transponder fixed

[47°09′59″S, 126°43′27″W] Dosimeter fixed

Lindypress Bug Fix
Just a brief note that for the past couple of days, you might’ve been unable to buy books on LindyPress.net if you are in the United States, Canada or Australia (which is a lot of you). This has now been fixed, so you can place your orders now!

The issue was that there was a silent API update that kept addresses from validating states and provinces. Note that if your order placed, it’s all okay, this is only for people for whom the site would not let place an order.
… ⌘ Read more

[47°09′05″S, 126°43′21″W] Transponder fixed

Okay one last time, then I’m going to bed, let’s hope this is the final bug that fixes Yarn/Twtxt <-> Activity Pub integration 😅

I should probably fix that

[47°09′38″S, 126°43′32″W] Dosimeter fixed

[47°09′55″S, 126°43′44″W] Dosimeter fixed

[47°09′50″S, 126°43′04″W] Transponder fixed

[47°09′06″S, 126°43′29″W] Dosimeter fixed

[47°09′00″S, 126°43′44″W] Transponder fixed

[47°09′30″S, 126°43′40″W] Transponder fixed

[47°09′35″S, 126°43′09″W] Dosimeter fixed

[47°09′16″S, 126°43′21″W] Dosimeter fixed

[47°09′02″S, 126°43′37″W] Transponder fixed

Finally back! My VPS’s main drive got toasted. I got a freshly installed VPS now, got yarn set up and working now, now I have to fix the rest of the stuff.
I’ve been using apache for many many years, but I had so many issues getting it set up today, so I switched to nginx, and that took me like 2 minutes.. So yeah - I’ll use nginx from now on.

[47°09′36″S, 126°43′50″W] Dosimeter fixed

[47°09′39″S, 126°43′46″W] Transponder fixed

[47°09′20″S, 126°43′49″W] Dosimeter fixed

[47°09′12″S, 126°43′33″W] Transponder fixed

[47°09′45″S, 126°43′59″W] Dosimeter fixed

Almost MIPS-only session today! Actually, I also briefly ran my PowrBook G4 and the Gemini PDA in attempt to fix my Pebble. But mostly the SGI O2 and the Indigo, too!

[47°09′34″S, 126°43′49″W] Dosimeter fixed

[47°09′38″S, 126°43′31″W] Dosimeter fixed

[47°09′55″S, 126°43′20″W] Dosimeter fixed

[47°09′03″S, 126°43′20″W] Dosimeter fixed

always something broken to fix, too

[47°09′51″S, 126°43′39″W] Transponder fixed

[47°09′13″S, 126°43′14″W] Dosimeter fixed

@prologic@twtxt.net git worked after upgrade. But I seem to have to reinstall go. I have not done that yet. I will see if I have time to fix that later tonight.

I have found the issue with this very subtle bug.. the cache was returning a slice that would be mutated. The mutation involved appending an item and then sorting. because the returned slice is just a pointer+length the sort would modify the same memory.

          CACHE         Returned slice          
original: [A B C D]     [A B C D]
add:      [A B C D] E   [A B C D E]
sort:     [E A B C] D   [A B C D E]

fix found here:
https://git.mills.io/yarnsocial/yarn/pulls/1072

** Occasional notes **
If they aren’t weekly, I guess they’re occasional?

3rd repair procedure to fix brain bleed was a success. I have a few more scans and follow ups, but, knock wood I think I’m through at this point.

I’ve spent about a week laying low and taking it easy navigating some wild pain, but that is subsiding now. I watched a bunch of stuff. It was a nice change of pace. I don’t typically watch much television or many movies. Stand outs (all things I revisited) include:

• Michael Clayton
  
• Point Break, the o … ⌘ Read more

[47°09′07″S, 126°43′53″W] Dosimeter fixed

Hmmm, after fixing my feeds to move the <author> from <entry>s to <feed>, Newsboat marked all old affected articles as unread. IDs were untouched, of course. Need to investigate that. Had something similar happen with another feed change I did some time ago. Can’t remember what that was, though.

@mckinley@twtxt.net Thank you! I didn’t even know about signing and encrypting XML documents. Right, RSS is a little bit messy.

Unfortunately, the autodiscovery document in one of your linked resources does not exist anymore. What annoys me in Atom is the distinction between <id> and <link>. I always want my URL also to be my ID, so I have to duplicate that – unnecessarily in my opinion.

Also, never found a good explanation why I should add <link rel="self" … /> to my feeds. I just do, but I don’t understand why. The W3C Feed Validation Service says:

[…] This value is important in a number of subscription scenarios where often times the feed aggregator only has access to the content of the feed and not the location from which the feed was fetched.

This just sounds like a very questionable bandaid to bad software architecture. Why would the feed parser need access to the feed URL at this stage? And if so, why not just pass down the input source? Just doesn’t make sense to me.

Also, I just noticed that I reference the http://purl.org/rss/1.0/modules/syndication/ namespace, but don’t use it in most of my feeds. Gotta fix that. Must have copied that from my yfav feed without paying attention what I’m doing.

Your article made me reread the Atom spec and I found out, that I can omit the <author> in the <entry> when I specify a global <author> at <feed> level. Awesome! Will do that as well and thus reduce the feed size.