Get daemon/content exchange protocol working within local network

Nobody has claimed this yet.

Till now A LOT of colleges(in India at least) use a local network data/content sharing client called DC\++. For using DC++ 1 person needs to create a server(e.g. ptokaX), give that server address to everyone and run the client(e.g. DC\++) as well, whereas all the others have to download the client(which didn't work across OSes mostly).
But this problem can be solved with a the lbry daemon as it has both a server and a client, and we have our own peer finding protocol, with which people won't have to go around sharing their IP addresses and give out an updated one(when DHCP recycles the IPs) and people can still access shared content.
People needed to use DC++ because of data usage restrictions(like 2 GB/day). The functionality of which can be replaced by the lbry protocol.

Note: _This was a quick draft of the issue based on the discussion during the planning meeting. This will be actively updated to be more well defined_

The issue is a draft and names no files or tests. Start by tracing the daemon, client, and peer-finding protocol components, then define the local-network exchange behavior and cross-platform scope; done should mean peers can discover one another and share content locally without manually exchanging changing IP addresses.

Written by the indexing model from the issue text.