List traffic
in [PgSql]
|
Prev: Patch for PKST timezone
Next: [HACKERS] SHARE locks vs. DELETE in SERIALIZABLE mode (Was: Partitioning/inherited tables vs FKs)
From: Alvaro Herrera on 13 May 2010 16:53 Excerpts from Yeb Havinga's message of jue may 13 15:06:53 -0400 2010: > Now I made a new gmail account, subscribed to all lists with some volume > and let it all message per message come into the inbox. Together with > thunderbird/imap this works quite nicely. With filters it's possible to > tag interesting messages (like does the To: contain my email? -> tag it > so it becomes green). Now I only need to view unread mails, (by thread > or date), read some messages and then ctrl-shift-c - all read. > > My $0.02 - I like the whole 'don't sort, search' (or how did they call > it?) just let the inbox fill up, google is fast enough. What would be > really interesting is to have some extra 'tags/headers' added to the > emails (document classification with e.g. self organizing map/kohonen), > so my local filters could make labels based on that, instead of perhaps > badly spelled keywords in subjects or message body. Yeah, this approach is interesting. A few days ago I started using Sup ( http://sup.rubyforge.org/ ) to manage my email, and after a rather lengthy warm-up process, I find it a lot more comfortable than Mutt (or anything else I've tried earlier, for that matter). I particularly like the multiple buffer approach, avoiding the need for switching between several Mutt instances, one for each mailbox. So it's almost like gmail: you get fast search, labelling, and a thread-based approach rather than message-based. As with gmail, you can "mute" threads that are not interesting to you, so that if any email arrives later to that thread, you will not see it unless you actively look for it. An old (unmuted) thread receiving a new message jumps back at the top of the list; and you can dismiss stuff as "archived" with a single keystroke, and it will stop polluting your immediate environment, but you can search for it. And it's pretty *fast* with searches (uses Xapian as backend). It's clearly a programmer's MUA -- if you want automatic labelling, you better be prepared to write some Ruby code. I have already written some simple rules that get me the trivial labels for pgsql lists and such; I have also ported the Perl moderation script I used, and the main advantage is that it's a tad faster (though I spent a lot more time writing that function than I'll ever save actually doing moderation -- but hey, I managed to learn some Ruby in the process). It is rather immature though, so I can't recommend it unless you're prepared to deal with that. -- -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: "Marc G. Fournier" on 13 May 2010 17:07 On Thu, 13 May 2010, Alvaro Herrera wrote: > Excerpts from Yeb Havinga's message of jue may 13 15:06:53 -0400 2010: > >> My $0.02 - I like the whole 'don't sort, search' (or how did they call >> it?) just let the inbox fill up, google is fast enough. What would be >> really interesting is to have some extra 'tags/headers' added to the >> emails (document classification with e.g. self organizing map/kohonen), >> so my local filters could make labels based on that, instead of perhaps >> badly spelled keywords in subjects or message body. I missed this when I read it the first time .. all list email does have an X-Mailing-List header added so that you can label based on list itself ... is that what you mean, or are you thinking of something else entirely? ---- Marc G. Fournier Hub.Org Hosting Solutions S.A. scrappy(a)hub.org http://www.hub.org Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy(a)hub.org -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Tom Lane on 13 May 2010 17:19 "Marc G. Fournier" <scrappy(a)hub.org> writes: > On Thu, 13 May 2010, Magnus Hagander wrote: >> We tried that with pgsql-hackers-win32 and iirc also >> pgsql-hackers-pitr, and it was a big failure... > But, we are doing that now with pgsql-cluster-hackers and it looks to be > working quite well from what I can see ... Is it? If they want someplace where the majority of hackers won't see the discussion, maybe, but I am not sure that's not counterproductive. Ideas developed by a small group may or may not survive exposure when they reach this list. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Dimitri Fontaine on 13 May 2010 17:29 Alvaro Herrera <alvherre(a)alvh.no-ip.org> writes: > Excerpts from Yeb Havinga's message of jue may 13 15:06:53 -0400 2010: > >> Now I made a new gmail account > > Yeah, this approach is interesting. A few days ago I started using Sup > ( http://sup.rubyforge.org/ ) to manage my email Feature wise, I think gnus offers more than the two approaches combined. Speed wise some people use it with some indexing solution, I'm not finding the need yet. And yes, to handle our lists traffic you must have a MUA made for it. That's the reason why I switched, and it's working great here. Regards, -- dim -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: "Marc G. Fournier" on 13 May 2010 18:13
On Thu, 13 May 2010, Tom Lane wrote: > "Marc G. Fournier" <scrappy(a)hub.org> writes: >> On Thu, 13 May 2010, Magnus Hagander wrote: >>> We tried that with pgsql-hackers-win32 and iirc also >>> pgsql-hackers-pitr, and it was a big failure... > >> But, we are doing that now with pgsql-cluster-hackers and it looks to be >> working quite well from what I can see ... > > Is it? If they want someplace where the majority of hackers won't see > the discussion, maybe, but I am not sure that's not counterproductive. > Ideas developed by a small group may or may not survive exposure when > they reach this list. But that, IMHO, is the point of the smaller list ... it allows the group on that list to hash out their ideas, and, hopefully, deal with both arguments and counter arguments so that when presented to the larger group, they would then have a more cohesive arg for their ideas ... Marc G. Fournier Hub.Org Hosting Solutions S.A. scrappy(a)hub.org http://www.hub.org Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy(a)hub.org -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |