Jason Rhinelander
Jason Rhinelander
Currently routers are spending quite a bit of time gossiping RCs (if you turn on debug-level logging you get spammed relentlessly). I think this is because mainnet connectivity is quite...
Currently our path handover logic when everything is working smoothly is to use an introset (which has a lifetime of 20min) until we are within the publish interval (5 mins),...
We're currently using std::chrono::duration types for both durations *and* timestamps (in the latter case we interpret as unix times). This is a bit icky, and was a result of converting...
All too often linux users install lokinet and it "doesn't work" because they are using god knows what for DNS. We need to fix this for as many of the...
Mac users have been trained by Apple to drag something to the trash to uninstall the app. However Mac users don't allow the app (AFAIK) to hook into that to...
On one team member's mac Lokinet fails to work; some of the lines in the log suggests that it may not have properly found the default route. [stdout.txt](https://github.com/loki-project/loki-network/files/5537417/stdout.txt)
Kee had an issue where installing Lokinet wasn't working (lokinet couldn't start). On investigation, he had some lokinet process running (probably from an old version) that had to be `kill...
Clients can potentially hang onto an RC for a long time, which may no longer be valid, but the client currently has no way to learn about that expiry. This...
A couple times in the last day I've been unable to reach blocks.loki. Lokinet reports, over and over: ``` [+1m03.915s] service/hidden_service_address_lookup.cpp:41 found result for kcpyawm9se7trdbzncimdi5t7st4p5mh9i1mg7gkpuubi4k4ku1y.loki [+1m04.091s] service/hidden_service_address_lookup.cpp:41 found result for...
Currently lokinet uses `llarp_time_t` (which is milliseconds) everywhere for times. Part of the justification was that it makes serialization easier, but conversely it makes other parts of the code a...