Weekly Dev Update #88
Hey Y’all,
Last week we continued patching Session bugs related to message sending and multi-device, which culminated in a new round of cross-platform Session client releases. The Loki Core team merged the first parts of LNS, which is slated for release in about a month. The Lokinet team continued working on Lokinet 0.7.0, with the aim that 0.7.0 will be ready in time for the aforementioned Loki Core release.
Loki Core
Allow for multi-year registrations for .loki LNS names
Implement LNS name blinding so that names are not exposed by default
Fix unit tests
Create default address for sweep_all command
https://github.com/loki-project/loki-core/pull/1031
(Thanks to a community dev, Darcys22, for this one!)
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: we launched the bulk of the Lokinet changes (publishing updates, introset blinding, and RC propagation via gossiping) onto the Loki testnet this week. We still have one remaining issue to track down, involving how clients handle introset expiries and handover to updated introsets, but that is the final core Lokinet issue for 0.7.0.
PR Activity:
Make introset publishing optional; a client that doesn’t publish introsets can still reach other .loki addresses, but isn’t reachable itself –
Make public DNS CNAME records that point to .loki functional (so that you could make loki.example.com point to a .loki address and have it do the right thing when resolved on a machine with a running lokinet client) –
Don’t prematurely clear introsets –
Redesign DHT publishing to be more redundant –
Converted bundled libraries to upstream submodules for easier maintenance/updates (and updated them to the latest versions) –
Add key updating tests to test suite –
Don’t try to re-establish inbound connections back to their source; instead let the inbound connection worry about reestablishing if it wants –
RC gossiping – this makes routers advertise each other to the Lokinet network once per hour (like lokid does with uptime proofs) rather than relying on random exploration to find everything –
Don’t limit the queue size for direct SN-to-SN DHT messages –
More updates for Windows builds –
Reduce redundant traffic between SNs –
Session
Session iOS
Begin work on light mode
Improve closed group functionality, allow users to add friends to existing closed groups, kick members and change group names
Fix session resets
Fix profile picture issues
Fix a new round of multi-device issues caused by sealed sender integration
Improve error handling and remove the Loki news RSS channel by default
Resubmit a device token periodically (for push notifications)
Session Android
Fix session resets
Handle clock out of sync issue that was causing message failure
Refactorisation of multi-device code
Add file size limits
Remove auth tokens being sent as part of file uploads
Session Desktop
Fix check to see if the user has pre-esablished keys
Button gradient fixes
Disable section event in message details view
Improvement for TTL slider
Remove filter request button
Group update fixes
Release note fixes
Adjust min size to allow low resolution screens to see Session
Hide notifcation settings in open groups
Add animations
Fix aspects of message selection
UI fixes
Error when file too large
Allow user to select text in messages
Alter disappearing messages menus
Fix button overflow
Refactor session resets
Various logging improvments
Closed chats UI re-arrangement
Support new nodejs version
Modal blurring a style improvements
Friend requests for background messages
Polling fixes from open groups
Multi device fixes
Loki MQ
Loki MQ is a communications layer for various components that allows more efficient and reliable communication. It is an enhancement of the “quorumnet” code added in Lokid 6.x, which is currently used for SN-to-SN communication for Blink transactions, and also for Service Node deregistration voting, with various additions to support using it for Service Node proxying and other communication channels between various loki components (e.g. Session-to-storage server; storage-server-to-storage-server; wallet-to-node; etc.).
Minor bug fixes
WIP – minor redesign of non-SN client-server connection handling so that lokimq can be better used for ordinary RPC connections.
Thanks,
Kee
You've got mail!
Sign up to our newsletter to keep up to date with everything Oxen.