I don't know why you set the MTU to a lower value... What I do know, is that I've set it to 65535; my machine now transmits 64KB instead of just 1.5KB (per packet)... Can you imagine what would happen if I set this to UInt32.MaxValue...?
Its generally a terrible idea to increase UDP MTU. There's no reliable reassembly in UDP. If you miss a single packet (out of say 1000) then all are simply discarded silently.
In fact, some versions of Linux didn't do UDP reassembly properly until a year ago (was a topic here on HN). Reordered UDP wasn't dealt with properly if I recall.
There are routers that drop UDP for any reason or no reason. And so on. So UDP is the red-headed stepchild of protocols, with little testing going on and lots of issues.
I recommend putting a protocol on top of any UDP transfer you code, and never increasing the MTU.
The UDP packet, and what goes out on the wire, are different things. IP-over-Ethernet for instance does not send out data in units larger than 1500 bytes; often smaller over WiFi. So UDP packets larger than 1500 bytes will be divided up, and reassembled on the receive end.
"To answer the question that at least a few dozen of you are looking for: Mailman 3 will not, by default, send you a monthly reminder that includes your password in plain text. In fact, it can't; Mailman 3 hashes passwords before storing them."
As I understand it from the write-up (and a brief look at the source seems to confirm that), Mailman 3.0 does encrypt passwords by default and does not mail them out any longer.
It is stored in unicode because that's what passlib hash algorithms return, not because there's an underlying plaintext representation.
2. "Show HN" shouldn't be a place to introduce startups and other "real world" projects.
Let's face it, a typical HN user is a programmer wanting to read something technical.
He will not take time to understand/appreciate your non-technical startup. What you can get at most is a snarky comment, but almost all will just ignore it.
