Loki

, Weekly Dev Update #102

Weekly Dev Update #102

Hey Y’all, 

This week we continued our work refactoring Session to improve multi-device, message sending reliability, and friend request logic. Our focus has been on Android, which is nearly finished, and Desktop, which is just getting started. The Lokinet team continued working on performance improvements, exit node support, and internode performance testing. Finally, the Loki Core team continued its work on merging in relevant upstream commits from Monero.

Loki Core


Lokinet

If you’re on our Discord you can catch Jeff, the lead developer of LLARP, live streaming as he codes at https://www.twitch.tv/uguu25519. He typically streams on Tuesday mornings, 9am – 12pm Eastern (US) time.

What went on last week with Lokinet: This past week in Lokinet saw us continue with performance fixes, more work on adding exit support via SNApps, the beginnings of a framework to report and act on peer router performance, and numerous improvements to our continuous integration testing framework.

The statistics and testing framework will allow us to have routers report (via their lokid) on other routers so that we can start detecting and penalizing Service Nodes that do not have a properly running lokinet router. Our initial plan for 0.8 is to enforce a few basic checks and collect various additional bandwidth statistics to be enabled later after we see how well they work.

The SNApp-based exit work is aimed at allowing anyone to set up an exit node on a SNApp (instead of only on service node routers) so that exit nodes can be decoupled from the snode itself. This will allow more flexibility in terms of exits: for example, Service Node operators would be able to set up an exit node on a different host (or different hosting provider) that is more suitable for exit node traffic than their service node itself.

Lokinet PR Activity:


Session

Session iOS 

Session Android

Session Push Notifications Server 

Session Wiki 

Session Desktop 

Thanks,  

Kee 

Leave a Comment

Your email address will not be published. Required fields are marked *