CalDescent bcc89adb5f Removed "peerAddress" from ArbitraryDataFileListMessage (introduced in recent commit) ...

It's best that the source peer's address isn't exposed to the requesting peer. The relay peer can keep track of this mapping itself.

The only real issue with this approach is that we can't use data from ArbitraryDataFileListMessage to update our ArbitraryPeers data, because we can't distinguish between relay peers and hosting peers. But this isn't something we currently do anyway, as we have the ARBITRARY_SIGNATURES message type to take care of updating ArbitraryPeers mappings.

2021-12-15 11:40:54 +00:00

..

main

Removed "peerAddress" from ArbitraryDataFileListMessage (introduced in recent commit)

2021-12-15 11:40:54 +00:00

test

Simplified lists feature to be referenced by a single name, instead of the confusing "category" and "resourceName" properties.

2021-12-10 11:33:26 +00:00