From: Rich Lane <rlane@club.cc.cmu.edu>
To: sup-devel@rubyforge.org
Subject: [sup-devel] RFC: Nuke remote sources
Date: Sun, 17 Jan 2010 10:50:44 -0800 [thread overview]
Message-ID: <1263754247-20979-1-git-send-email-rlane@club.cc.cmu.edu> (raw)
Every few days someone joins the IRC channel complaining of poor
performance or bugs with IMAP sources, and we have to tell them to use
offlineimap or fetchmail instead. This is embarrassing. There are likely
many more users who don't bother to ask on IRC and either unhappily
tolerate IMAP or give up on Sup.
Even with IMAP you still need to store a huge index on disk, so I can't
accept that you'd have enough space for that but not for the actual
messages. You still need to download every message to index it. Your
mails aren't any more secure from someone stealing your laptop. The same
arguments apply to mbox+ssh.
The benefit for me is that I won't have to deal with slow, blocking
sources when converting the UI to EventMachine.
If people agree that this change is a good idea, I assume William will
add a deprecation notice to master for 0.10 and merge this patchset to
next.
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next reply other threads:[~2010-01-17 18:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-17 18:50 Rich Lane [this message]
2010-01-17 18:50 ` [sup-devel] [PATCH 1/3] remove mbox+ssh source Rich Lane
2010-01-17 18:50 ` [sup-devel] [PATCH 2/3] remove imap source Rich Lane
2010-01-17 18:50 ` [sup-devel] [PATCH 3/3] simplify sup-add Rich Lane
2010-01-17 20:39 ` [sup-devel] RFC: Nuke remote sources William Morgan
2010-01-18 17:06 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1263754247-20979-1-git-send-email-rlane@club.cc.cmu.edu \
--to=rlane@club.cc.cmu.edu \
--cc=sup-devel@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox