Re: [Mailman-Users] Efficient handling of cross-posting

Mikael Hansen writes: > So I enjoy the roster concept which is outlined. Still, it seems odd > to me that the list server software can adequately decide on the > process of eliminating duplicates. To me, the roster concept implies > that duplicates should not have been sent by list membe

Re: [Mailman-Users] Efficient handling of cross-posting

On Jan 28, 2008, at 15:40, Barry Warsaw wrote: > What this means is that in Mailman 3.0, there is knowledge of > subscriptions across mailing lists, so that we could do better cross- > posting, though this isn't implemented yet. For example, you could > say that the 'musicians' mailing list roste

Re: [Mailman-Users] Efficient handling of cross-posting

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jan 29, 2008, at 9:15 PM, Brad Knowles wrote: > I wouldn't say that I was channeling them. I would say that I'm > trying to do what I can to support them and to allow them to spend > what little time they have on their "real" work, as far as the >

Re: [Mailman-Users] Efficient handling of cross-posting

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jan 29, 2008, at 7:30 PM, Mikhail T. wrote: > Thank you, sir, for the encouragement, but I don't want my > hypothetical > contribution to live this way. I've contributed plenty to various > open- (and > closed-) source projects over the years (

Re: [Mailman-Users] Efficient handling of cross-posting

On 1/30/08, Stephen J. Turnbull wrote: > This is false. "Open source" means you can do what you like, and > Mailman actually will distribute it for you as a patch on the issue > tracker. Not quite. If he uploads his code as a patch to the tracker, we will most likely leave it there, and at

Re: [Mailman-Users] Efficient handling of cross-posting

On 1/29/08, Mikhail T. wrote: > As you may realize, I have no idea of the Mailman project hierarchy. Brad's > words sounded quite authoritative, and he was no contradicted in any > follow-ups... I'm not a core developer for the project. I'm just the current active postmaster/Internet mail sy

Re: [Mailman-Users] Efficient handling of cross-posting

On 1/29/08, Mikhail T. wrote: > May I suggest, you underestimate the importance of this feature? >Cross-posting > may often be justified from the end-user perspective, but is discouraged by > the admins exactly because it increases the archival-storage requirements... I've never once heard an

Re: [Mailman-Users] Efficient handling of cross-posting

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jan 29, 2008, at 12:17 PM, Mikhail T. wrote: > вівторок 29 січень 2008 12:05 по, Steve Burling Ви > написали: >> I love comments like this. If it "can't be too difficult...", I >> suggest >> you put on your Python programming hat, and get codi

Re: [Mailman-Users] Efficient handling of cross-posting

With regards to the Mailman project, Barry Warsaw is the only one who can give you the definitive answer as to whether or not this concept is or is not acceptable in principal. Mark Sapiro and Tokio Kikuchi may disagree with him, and if so it will be up to them to convince him that they are

Re: [Mailman-Users] Efficient handling of cross-posting

I was speaking in terms of the practical reality of a 100% unpaid all- volunteer project, like Mailman. There are simply way too many other things going on that are much higher priority. If you pay certain Mailman developers real money for such a feature, then it will get done. If you write s

Re: [Mailman-Users] Efficient handling of cross-posting

Google does not provide all the storage for all the content in question, although they may have a cache of it. -- Brad Knowles <[EMAIL PROTECTED]> Sent from my iPhone On Jan 29, 2008, at 1:21 AM, "Stephen J. Turnbull" <[EMAIL PROTECTED]> wrote: > Brad Knowles writes: > >> No search engine

Re: [Mailman-Users] Efficient handling of cross-posting

вівторок 29 січень 2008 05:24 по, Stephen J. Turnbull Ви написали: > This is false.  "Open source" means you can do what you like, and > Mailman actually will distribute it for you as a patch on the issue > tracker.  Many contributions have lived full life cycles that way. Thank you, sir, for the

Re: [Mailman-Users] Efficient handling of cross-posting

> Mikhail T. writes: > Whatever I code up will, naturally, need to be approved by the > project-maintainers. This is why securing their acceptance /in > principle/ is important before beginning the actual work. This is false. "Open source" means you can do what you like, and Mailman actua

Re: [Mailman-Users] Efficient handling of cross-posting

Mikhail T. sent the message below at 09:17 1/29/2008: >Whatever I code up will, naturally, need to be approved by the >project-maintainers. This is why securing their acceptance /in >principle/ is important before beginning the actual work. As long as >the official position remains:

Re: [Mailman-Users] Efficient handling of cross-posting

вівторок 29 січень 2008 12:05 по, Steve Burling Ви написали: > I love comments like this.  If it "can't be too difficult...", I suggest > you put on your Python programming hat, and get coding. Whatever I code up will, naturally, need to be approved by the project-maintainers. This is why securin

Re: [Mailman-Users] Efficient handling of cross-posting

--On January 29, 2008 11:09:21 AM -0500 "Mikhail T." <[EMAIL PROTECTED]> wrote: > I hope, you'll give the idea of "single instance storage" another > thought. There is already an option to archive in "Maildir" format. > Optionally storing hardlinks instead of copies of cross-posts can't be > to

Re: [Mailman-Users] Efficient handling of cross-posting

понеділок 28 січень 2008 08:05 по, Brad Knowles Ви написали: > We do not do a "single instance store" within the archiving system of > Mailman, and I can pretty much guarantee you that we never will. > That's not to say that this is necessarily a bad idea, but I think we > have much, much more imp

Re: [Mailman-Users] Efficient handling of cross-posting

Brad Knowles writes: > No search engine author in their right mind should ever consider > doing de-duplication on their own, although they might be willing to > provide that feature to customers who demand the option. Google does. -- Mailma

Re: [Mailman-Users] Efficient handling of cross-posting

Brad Knowles wrote: > >Most of the anti-duplication features can't be delivered until >Mailman3. The sister-list concept that Mark has introduced with >Mailman 2.1.10 is the best we're likely to be able to see for a long >time. Actually, Tokio deserves the credit for bringing the concept and

Re: [Mailman-Users] Efficient handling of cross-posting

On 1/28/08, Mikhail Teterin wrote: > Well, depending on the archival method, a message can appear in both, with > only a single copy of it being stored. This can be achived, for example, > using symbolic (or even hard) links. We do not do a "single instance store" within the archiving system o

Re: [Mailman-Users] Efficient handling of cross-posting

On 1/28/08, Mikhail T. wrote: > Yes, of course. But a single mailman installation hosting multiple mailing > lists already has the complete knowledge, does not it? Nope. All you have for each list knows is a bunch of e-mail addresses that are subscribed. When sending out a message that has

Re: [Mailman-Users] Efficient handling of cross-posting

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jan 28, 2008, at 5:16 PM, Mark Sapiro wrote: > The concept to be implemented in Mailman 3.0 is a separate user > database which has an entry per person with perhaps multiple email > addresses and various roles such as member of list1, owner of list

Re: [Mailman-Users] Efficient handling of cross-posting

Mikhail Teterin wrote: > >But I was referring to search-results only. Regardless of how the messages >are stored, if I type the search string and select several of the mailing >list archives to search through, the same message may appear in my search >results more than once. That duplication should

Re: [Mailman-Users] Efficient handling of cross-posting

Mikhail Teterin wrote: >Well, depending on the archival method, a message can appear in >both, with only a single copy of it being stored. This can be >achived, for example, using symbolic (or even hard) links. >Similarly, if a relational database is employed, the same message >can be referred

Re: [Mailman-Users] Efficient handling of cross-posting

понеділок 28 січень 2008 05:16 по, Mark Sapiro Ви написали: > > AFAIU, the message will appear in the search results multiple times -- > > once per mailing list. That is not justified -- the results should > > contain no repetitions... > > For as many people who feel as you do, I'll wager that ther

Re: [Mailman-Users] Efficient handling of cross-posting

Mikhail T. wrote: > >Yes, of course. But a single mailman installation hosting multiple mailing >lists already has the complete knowledge, does not it? See my reply to Brad's reply. >I think, this function is already here. When I first sent message to this >list, it bounced, because I was not

Re: [Mailman-Users] Efficient handling of cross-posting

понеділок 28 січень 2008 02:15 по, Brad Knowles Ви написали: > The elimination of duplicates being sent to individuals is something > that might be implemented in a future version of Mailman, but that > would require that each list have complete knowledge of who all the > overlapping subscribers ar

Re: [Mailman-Users] Efficient handling of cross-posting

Brad Knowles wrote: >On 1/28/08, Mikhail T. wrote: > >> Can our mailman installation be tweaked to eliminate all or some of the >> above >> undesirable effects? Thanks, > >Not without source-code level modifications, no. In Mailman 2.1.10, there is a new sibling lists feature that can be used

Re: [Mailman-Users] Efficient handling of cross-posting

On 1/28/08, Mikhail T. wrote: > Can our mailman installation be tweaked to eliminate all or some of the above > undesirable effects? Thanks, Not without source-code level modifications, no. The elimination of duplicates being sent to individuals is something that might be implemented in a fut

[Mailman-Users] Efficient handling of cross-posting

Hello! Our site uses mailman to host many mailing lists. Sometimes a person would find it necessary to post to several of the lists at once incurring irritation of the subscribers for the following reasons: 1. People subscribed to more than one list will get the same message multiple times