[Groop]Re: Groop digest, attached Photos
Groopunk@aol.com
Groopunk@aol.com
Fri, 14 Feb 2003 11:53:46 EST
--part1_144.a99f00a.2b7e791a_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
>
> >> 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
>
Yeah, all, I apologize for sending the pics. As I am a new member to this
Groop, yet longtime fan of Groo, I was unaware of this "No-attachments"
policy. Unfortunately, I don't have a website... yet... where I can post
such images as our sexy carrot and so, upon seeing that others did not get a
chance to glimpse the veggie, well... I just wanted to spread the awesome
sight. That's all, sorry. I feel like I've created waves here. Maybe I
should return to the lurking. Lurking. Lurking. Lurking....
-s-e-t-h-
--part1_144.a99f00a.2b7e791a_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
<HTML><FONT FACE=3Darial,helvetica><FONT SIZE=3D2 FAMILY=3D"SANSSERIF" FACE=
=3D"Arial" LANG=3D"0"><BR>
<BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT=
: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px"><BR>
<BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT=
: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Please don't attach photos to m=
sgs sent to the Groop. I don't know about <BR>
the rest of you, but photos do NOT come thru here. All I get as part of my <=
BR>
digest is a huge unreadable block of letters and numbers. No photo. If you <=
BR>
want to send us a pic, please please put it on a webpage somewhere and send=20=
<BR>
us a link. <BR>
</FONT><FONT COLOR=3D"#000000" style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D3=
FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=3D"0"></BLOCKQUOTE><BR>
</FONT><FONT COLOR=3D"#000000" style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D2=
FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=3D"0"><BR>
--------------------->I understand that it is regular policy to not send=20=
attachment, in part for the reason you state. I got no problem with th=
at. 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 re=
quest for a link to the pic and 2) a notice that the link was no longer vali=
d. Your suggestion of putting something on a web page might not work.&=
nbsp; For example, had I been the one with the pic, I would have been=20=
unable to put it on a web page. Another alternative would have been fo=
r the person to send it to me individually, and made a general announcement=20=
to the groop that the pic could be sent to whoever wanted it. That mig=
ht 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=20=
think one of the two latter options would be best. But I don't know mu=
ch. <BR>
<BR>
Later, <BR>
A <BR>
</FONT><FONT COLOR=3D"#000000" style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D3=
FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=3D"0"></BLOCKQUOTE><BR>
<BR>
</FONT><FONT COLOR=3D"#000000" style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D2=
FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=3D"0">Yeah, all, I apologize for s=
ending the pics. As I am a new member to this Groop, yet longtime fan=20=
of Groo, I was unaware of this "No-attachments" policy. Un=
fortunately, I don't have a website... yet... where I can post such images a=
s our sexy carrot and so, upon seeing that others did not get a chance to gl=
impse the veggie, well... I just wanted to spread the awesome sight. T=
hat's all, sorry. I feel like I've created waves here. Maybe I s=
hould return to the lurking. Lurking. Lurking. Lurking....=
<BR>
<BR>
-s-e-t-h-
</FONT></HTML>
--part1_144.a99f00a.2b7e791a_boundary--