I was already pretty sure the existing code wouldn't work on big endian architectures, since I later learned the << and >> operators are meant to be consistent. Better to use the std lib when I can, anyway. I'd wanted to use them from the beginning, but stubbornly refused to do so until they were stabilized. Finally, they were stabilized in 1.32.

I'll have to convert the array slices to actual arrays before passing to from_be_bytes, but I would rather keep the current behavior where an Error is returned if the slice is the wrong length than use the "fallible conversion APIs" suggested by the official Rust documentation for these methods. (If the tag is malformed, an Error should be returned, end of story.)

This changes applies to the TryParse impls for BigIntPayload and IntPayload, and the Serialize impls for BigIntPayload, IntPayload, and IndexedSocketAddrPayload.

A cleanup method should be written to iterate through the LobbyList instance and remove any Lobby instances with a modified property older than some configured threshold (in minutes).

It should be executed regularly on its own thread in the Server instance, but I'm undecided if this should be in addition to the configured number of workers or at the expense of that configured number. (Put another way, I haven't decided if the total number of threads running on a Server should be config.workers or config.workers + 1.)

Whatever the case, the designated thread should sleep for around 30 seconds after each run of cleanup.

Avara was written before routers were common place, and the IP address it reports for the host is the host's LAN address, e.g. 192.168.1.7. Useless for a game tracker.

Somehow it needs to be replaced with the IP from which the "Hello" datagram originated... during Datagram parsing. Or maybe it makes more sense to make the swap when it is inserted into the LobbyList.