<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'><div style="text-align: left;">Hello everyone!<br>It has never been in my intention to upset anyone in the WLUG, by attaching that file. I was only thinking that it might help those who don't know about GPG and security, to understand it better. But i guess i have created an issue in doing that, which i am really sorry! No more attachments.<br><br>I apologise for all this. If you get into trouble, just tell them you got it from me.<br><br>Suntish.<br></div><hr id="stopSpelling">> Date: Mon, 20 Aug 2007 16:54:23 +0100<br>> From: drinky76@yahoo.com<br>> Subject: Re: [Wolves] Please Don't......<br>> To: wolves@mailman.lug.org.uk<br>> <br>> --- Alastair Battrick <al@aj8.org> wrote:<br>> <br>> > Dave Morley wrote:<br>> > > This is just a general reminder to please not post<br>> > links to content that<br>> > > is not free to view. It can come back to haunt us<br>> > through the lovely<br>> > > archiving system. If content is a tutorial on a<br>> > free website that is<br>> > > fine. But if content is not under a free to view<br>> > licensing like CC or<br>> > > GPL etc then Please Don't Do It.<br>> > <br>> > Why?<br>> <br>> There are 2 issues here.<br>> <br>> The first is that this PDF contains a copyright notice<br>> which states that the contents may not be reproduced<br>> or transmitted by any means including electronic,<br>> without the permission of the copyright owner and<br>> publisher.<br>> <br>> In short it's illegal. No Starch Press make many of<br>> their books available for download as PDF, but not for<br>> free. I doubt they'd take kindly to us passing them<br>> around. It should also be noted that we all now have a<br>> copy of this PDF on our PCs, unless you deleted it (be<br>> sure your mail client hasn't cached it).<br>> <br>> I'd hate to see them use some kind of DRM to protect<br>> their PDFs. I wouldn't like to explain to No Starch<br>> Press' lawyers how I got their copyrighted material<br>> either.<br>> <br>> The second, as Andy illustrated (being the sysadmin of<br>> the box that this list runs on), is that posting<br>> attachments means that the server has to deliver that<br>> attachment to all of the list members, including<br>> retries and bounces. Which, as he points out, created<br>> a 650MB spike in bandwidth usage, which none of us<br>> have paid for, but somebody has to. This is why<br>> Suntish posted it twice. The load on the server caused<br>> by the first one slowed the system down for every<br>> mailing list on the box (which is pretty much every<br>> LUG in the UK) and meant that it wasn't delivered<br>> promptly for anyone.<br>> <br>> In fairness, I'm pretty sure that Suntish had no idea<br>> that he would cause a problem.<br>> <br>> So, to summarise:<br>> <br>> 1) Don't post attachments to the list.<br>> 2) Don't post copyrighted material to the list.<br>> <br>> Please :)<br>> <br>> Ad<br>> <br>> -- <br>> <br>> http://blog.adamsweet.org/<br>> <br>> <br>> ___________________________________________________________ <br>> Want ideas for reducing your carbon footprint? Visit Yahoo! For Good http://uk.promotions.yahoo.com/forgood/environment.html<br>> <br>> _______________________________________________<br>> Wolves LUG mailing list<br>> Homepage: http://www.wolveslug.org.uk/<br>> Mailing list: Wolves@mailman.lug.org.uk<br>> Mailing list home: https://mailman.lug.org.uk/mailman/listinfo/wolves<br></body>
</html>