frigginglorious has quit [Ping timeout: 265 seconds]
frigginglorious1 is now known as frigginglorious
_whitelogger has joined #qaul.net
frigginglorious has quit [Read error: Connection reset by peer]
_whitelogger has joined #qaul.net
frigginglorious has joined #qaul.net
Degi has quit [Ping timeout: 272 seconds]
Degi has joined #qaul.net
_whitelogger has joined #qaul.net
infoverload has quit [Ping timeout: 260 seconds]
infoverload has joined #qaul.net
frigginglorious has quit [Ping timeout: 240 seconds]
link2xt has quit [Quit: WeeChat 2.6]
link2xt has joined #qaul.net
frigginglorious has joined #qaul.net
_whitelogger has joined #qaul.net
<spacekookie>
noracodes: I would be very interested in seeing how you could apply a pubkey based web-of-trust on Ratman
<spacekookie>
Did you have a look at the async branch and some of the structure changes in the routing core? I think the modularity makes it easier to understand now, but it's still largely missing
<noracodes>
I'm reading through it on and off
<noracodes>
Today is a bit hectic because I'm just starting the semester
<spacekookie>
Yea cool, just ping me if you have questions about anything
<noracodes>
Thanks!
<noracodes>
Something we talked about in the meeting that I'm not sure I understand: how does the router resolve situations where the same peer is accessible over multiple netmods?
<spacekookie>
At the moment it doesn't, but basicaly we need to keep quality mentrics for announcement frames that get sent
<spacekookie>
So, basically we keep a journal of announcements, and if they were delivered twice. Then we can very passively use that as a metric to switch to a connection that's consistently faster
<spacekookie>
On the other hand we could do more active tracking for TTLs
<noracodes>
That makes sense! I think active analysis using probe packets and TTLs is a good goal but likely not critical at the moment