As someone who wrote their own "Quote of the Day" server [1] I will agree that the QOTD protocol (RFC-865/STD-23) is simple, but not quite the "ridiculously eas

As someone who wrote their own "Quote of the Day" server [1] I will agree that the QOTD protocol (RFC-865/STD-23) is simple, but not quite the "ridiculously easy" as you put it. Let's assume we have something like that. The code for the service itself is pretty simple (listen for a connection to TCP port 17, send a quote, close the connection) so there shouldn't be that many updates for the QOTD program. But can the user add new quotes? If so, how secure it is? Can that be exploited? How often should the quote be changed? Every request? Once a day? Something in between? How is it configured? Do you need to document DNS settings? Are there mitigations to keep a client from swamping the service with requests? [2] Are requests logged (say, to monitor bandwidth usage or to see how popular a service it is)? Where? How long? Nothing is ever "easy." [1] qotd.conman.org [2] Not a problem I've had yet.