I am a member in good standing, and this is a member initative. Here's the proposal: members will be provided with the capability to retrieve E-mail on Grex remotely.22 responses total.
According to Steve', this would be an inducement to potential members. I endorse taking this proposal to vote.
This would have some interesting consequences for Grex. It might bring in more members, but it would also be a burden on Grex, and would cost bandwidth. I believe we get 50G of traffic a month for our current payment, so if we went above that I think we'd be looking at another $50/mo for another 50G. I'm not 100% sure of those numbers, but they're in the right ballpark.
I doubt allowing members to POP their mail would use up a significant amount of bandwidth, but if this proposal passes, Grex's staff would be able to monitor usage and restrict it if necessary so that Cyberspace Communications doesn't get hit with an extra charge.
And then halt the ability to POP for the rest of the month? That sounds like a good way to get folks mad at us.
There might be cases where that's necessary, but I'm sure there are less severe restrictions that could be applied.
If you're reading mail on Grex and you're not seated at the console you are already reading it remotely.
Mike, many E-mail programs (Outlook Express, for example) retrieve E-mail by making a connection to a remote server and downloading stored messages to the user's computer for reading. Grex currently doesn't allow users to read their mail remotely in this way, and that's what I'm proposing we enable.
Instead of POP, why not allow IMAP? I believe IMAP would be less bandwidth intensive.
Proposals to provide extra benefits to members are not in line with the philosophy Grex was founded on. The outbound-access/membership link is a messy historical accident and not a model we should return to.
Re #6,7: David - Mike is pointing out that your proposal is poorly worded.
Re. 10: And I was pointing out he was wrong.
Regarding #2; I no longer by the resource/burden argument: grex has resources to spare since moving to the PC platform and into colo. Before suggesting that allowing POP access (for the only 1000 or so users who actually use grex for email) is going to swamp our network connection, I'd like to see some numbers. Regarding #8; Yes and no. IMAP provides facilities for retrieving parts of messages, whereas POP isn't so great at this (or generally isn't used in that way), but typically, mail remains on the server, and at the end of the day, to get the entire contents of the message, no matter how you access it (via POP, IMAP, or an MUA on grex itself) you're still sending largely the same bits over the wire. Of course, if you're working with lots of attachments, it may many some difference since the protocols one would typically use to download binary attachments are somewhat more efficient than the encodings used in email messages themselves. Regarding #11; No, it's not that well worded. Why make enemies by quibbling over language, when you're actually making a decent proposal?
I remember when Grex ran USENET for members and it was a pretty nice feature. Now, certain staff/members don't even want to allow POP3? Absurd.
re. 12: okay, i give up! The official wording of the proposal is now the following: Grex shall allow members of Cyberspace Communications Inc. to access their E-mail via the Post Office Protocol or the Internet Message Access Protocol.
Another argument in opposition: Grex should not be making its mail service more attractive while there are still basic stability problems and multi-day downtimes. Essentially this proposal says Grex should move to more of a fee-for-service model, at a point where our service reliability is not too good.
I agree. I think proposals should be better focused on soliciting staff volunteers that know how to patch systems.
That is a good idea.
I don't think we should patch. We should move to a more stable platform. OpenBSD ain't it. FreeBSD is. I really wish, in retrospect, that I'd pushed harder for FreeBSD.
I think Grex should be a flat YABB cgi script running on some 3rd party ISP's web service.
That's one possible future path. However, my strong belief is that online communities are intimately wedded to their software interface, and if you make radical changes to that, the old community breaks up and you have to start over. I don't believe you take away the open-Unix model and continue to have this Grex community.
This community needs a health & hygiene program.
This town needs an enema.
You have several choices: