Thanks, although, the changelog is not something I view as grunt work.
As long as I have the kind of ownership I do now over the release process, I will be continuing to curate it to the best of my ability. It’s not going to be just AI-generated text (though I did get some help from Claude Code to identify some changes and provide some scaffolding) or a lazy mish-mash, wiki-style document where everyone dumps in some text from stuff they’ve been working on. I want it to be readable and cohesive.
Can you say if all clients will benefit from all the CLN changes, such as batching, or does this depend on which APIs are used when uploading? So for example for client apps using dir_content_upload_public() / file_content_upload_public() etc.
My apologies - after having read through it, this is LOT more than grunt-work.
This, in particular, was very encouraging
There should be further improvements coming for the next release. In particular we are waiting on a
new libp2p release which will have a feature contributed by us that should further improve
performance. We’ve been told by the libp2p team that this release is now forthcoming.
Nice to see Autonomit feeding back into and improving other projects
They are apparently releasing tomorrow. You can see some correspondence on that here.
Qi contributed something for the request and response model that should be a big benefit to us, but the problem was libp2p have a very infrequent release cycle, or at least that’s what we thought. It turns out they generally will do a release if they are prompted by their users.
It was in jest of course and I understand the issues, with such a situation with Autonomi and the consequences of a failed update on the network. Maybe I should have just not taken the opportunity to inject some humorous sarcasm.
Yea I read the dev update too. But you’re speculating and I didn’t ask you, I asked a dev who would actually know what their plans are.
So for example, they could have potential plans to bring in to the node codebase the part of the code they can use, or some other hybrid. Of course all of this noise could have been avoided if you didn’t speak up about something you’d have no way of knowing FFS.
And of course there is always ongoing development in how to improve the networking side of things. But you are right, its for the client, no need for clarification since they tell us plainly and earlier announcements even say that the client and nodes are taking different paths in this area so nodes can have their networking and clients have theirs without the need for conditional compiling and maintenance in a combined library
In addition to these fixes, the latest version of Autonomi also features client light networking (CLN). In case you need a reminder, CLN represents a significant code cull replacing 12k lines of code with a minimalistic 2.3k lines that the client can use. It’s huge code simplification client-side that should lead to significant performance and maintainability improvements. It also allows us to refactor node networking without having to worry about the client as both are separate.
