Guest wrote:dane wrote:A Usenet server array isn't something purchased and deployed, it's a platform that must be built. [ ... ]
May I prevail upon you to expand on this a bit? I'm conceptualizing an NNTP server as a machine with a few TB of spindles that sits in a rack and more or less looks after itself. I'm not grokking what you mean when you say, "platform."
My 2 cents on Usenet being a platform are:
- Peering with other news providers. You must establish relationships with other platforms to send/receive messages and for what hierarchies you exchange with each other. For example one peer may agree to send you everything from a particular sub, like sci.* and not for others. It's a complex set of relationships that dictates what messages you will and won't receive from other peers. It's a complex, distributed, server-to-server type of network.
- Retention. A few TB of storage could be a huge understatement. Depending on your retention period and subs, this can be in the petabytes. Even consider text only, with a hypothetical 30 MB of news per day to be retained for a period of 1 year (low) would require over 10 TB of storage (just for the content itself - not to mention filesystem overhead etc).
- Network bandwidth. You have to consider (even with a small number of users) the fact that a handful of people may pop on at the same time every couple of weeks and download a huge amount of content. If you serve media content in alt.bin imagine a few users on high speed connections trying to download a movie at the same time. They can either get their content quickly (requires a large amount of bandwidth) or it can take forever, resulting in a low quality of service.
There actually quite a bit of info at
https://en.wikipedia.org/wiki/Usenet
Hope that helps.