[Groop]Re: Groop digest, attached Photos

Fri, 14 Feb 2003 11:41:17 EST

--part1_12.2d1e44b7.2b7e762d_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 2/13/2003 6:40:56 PM Eastern Standard Time, 
rick@flyingbuffalo.com writes:

> Please don't attach photos to msgs sent to the Groop. I don't know about
> the rest of you, but photos do NOT come thru here. All I get as part of my
> digest is a huge unreadable block of letters and numbers. No photo. If you
> want to send us a pic, please please put it on a webpage somewhere and send
> us a link.
> 

--------------------->I understand that it is regular policy to not send 
attachment, in part for the reason you state.  I got no problem with that.  I 
think it a wise policy.  However, I forget who sent the pic (and thank you 
for doing so), but whoever sent the pic did so after 1) a request for a link 
to the pic and 2) a notice that the link was no longer valid.  Your 
suggestion of putting something on a web page might not work.  For example, 
had I been the one with the pic,  I would have been unable to put it on a web 
page.  Another alternative would have been for the person to send it to me 
individually, and made a general announcement to the groop that the pic could 
be sent to whoever wanted it.  That might not work either, as someone might 
be daunted from going to the added  burden of sending a bunch of individual 
e-mails.  A third alternative would be a bit of flexibility depending on 
specific circumstances.  I think one of the two latter options would be best. 
 But I don't know much.

Later,
A

--part1_12.2d1e44b7.2b7e762d_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<HTML>In a message dated 2/13/2=
003 6:40:56 PM Eastern Standard Time, rick@flyingbuffalo.com writes:
 
 
 <BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-=
LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Please don't attach photos=20=
to msgs sent to the Groop. I don't know about
 the rest of you, but photos do NOT come thru here. All I get as part of=20=
my
 digest is a huge unreadable block of letters and numbers. No photo. If y=
ou
 want to send us a pic, please please put it on a webpage somewhere and s=
end
 us a link.
 </BLOCKQUOTE>
 
 ---------------------&gt;I understand that it is regular policy to not s=
end attachment, in part for the reason you state. &nbsp;I got no problem wit=
h that. &nbsp;I think it a wise policy. &nbsp;However, I forget who sent the=
 pic (and thank you for doing so), but whoever sent the pic did so after 1)=20=
a request for a link to the pic and 2) a notice that the link was no longer=20=
valid. &nbsp;Your suggestion of putting something on a web page might not wo=
rk. &nbsp;For example, had I been the one with the pic, &nbsp;I would have b=
een unable to put it on a web page. &nbsp;Another alternative would have bee=
n for the person to send it to me individually, and made a general announcem=
ent to the groop that the pic could be sent to whoever wanted it. &nbsp;That=
 might not work either, as someone might be daunted from going to the added=20=
&nbsp;burden of sending a bunch of individual e-mails. &nbsp;A third alterna=
tive would be a bit of flexibility depending on specific circumstances. &nbs=
p;I think one of the two latter options would be best. &nbsp;But I don't kno=
w much.
 
 Later,
 A
 </HTML>

--part1_12.2d1e44b7.2b7e762d_boundary--