The week we’ve been laser focused on eliminating remaining niggles. We’re not seeing any data loss but there are some random upload and download failures requiring multiple retries. Fixes have been identified and are being tested.
There’s a new release out with lots of fixes, including one that will enable with emissions for people running nodes with a port forwarding configuration. We’ve gone some way to nailing failed downloads, but there’s still a bit to do on that. Essentially we are doing away with relays which were causing problems. The --relay
flag is deprecated so please upgrade your nodes asap. Clients are unaffected.
We’ve also kicked off an internal hackathon to develop a team-built app to showcase the network and assist partners and communities to use it from a central provider within the organisation, such as a single wallet for many people to use. This marks our transition from R&D to a features and products team. It’s so great to have got here and the team is super-energised!
On Impossible Futures, participants are now deploying to the network and preparing their projects for voting, which will begin next week. We’re also assembling the community judging panel ready to assess and score the apps. The community judging panel will account for 40% of the overall score for the top three prizes.
A way out of this M.A.D.-ness
Jim has put out another cracking video demonstrating the disadvantages of centralisation. This time it’s about how data centres are prime targets in times of war and introduces the countervailing concept of Mutually Assured Data. Make sure you subscribe to our YouTube channel.
Community doings
@riddim upgraded his Friends
messenger app to include dweb
attribution, routes upgrade and larger avatar pics.
Riddim also helped @happybeing with a bug fix for dweb
that affected uploads. Dweb
is now on V0.10.4
@zettawatt is mirroring Project Gutenberg to his local machine with plans to upload all the files and plug the metadata into Colony
for searching and management.
And @oetying unveiled a slimmed down MVP of Ryyn
, his backup project .
General progress
@chriso has been chiselling away at the latest release knocking off the rough bits.
@anselme has been working on data streaming support to allow for big file uploads in a way that’s backward-compatible.
Ermine continues working on fixing the issues with upgrading on metric service over RPC.
Lajos has been studying the signature scheme in the Safe ERC4337 module and trying to implement a valid signing method using Externally Owned Accounts (EOAs) for the smart account.
@mick.vandijke created tasks for the internal hackathon, added back-end offline detection and reconnect UI, and worked on an extensive Admin dashboard which is almost done.
@qi_ma has been checking out the release candidate and also fixed a couple of bugs to do with home nodes being unavailable to clients despite being able to connect to other peers. He also reviewed the data streaming work, which required some changes to self encryption. This is something @dirvine has been working on.
@roland has been on the hackathon, in particular Dockerising the components we are working on for our app.
Meanwhile @vphongph worked on the Python API, issuing a PR for implementing Postgres DB using SQLx, the Rust SQL toolkit. We can now store the auth tokens to the database for validation and also the uploaded file data!
Finally, @shu added additional functionality to ELK and Telegraf side so data in ELK can now be specifically targeted to be deleted. Previously we were running out of disk space when using verbose logging.