Amiga.org

Amiga computer related discussion => Amiga Marketplace => Topic started by: weirdami on April 27, 2004, 12:26:54 AM

Title: geocites vs sales pictures
Post by: weirdami on April 27, 2004, 12:26:54 AM
You think Geocities would get mad if I made a website just for storing all the pictures I have of the cables I'm going to sell? If I do the amibench thing, I figure I could Geocities the pics or even make a cheesy "here's a picture of X cable" page so people could gander what I'm hocking.

Or, should I just upload 40+ jpegs (~25KB each) to the AO picture gallery?

I'm still in the process of picturing the hardware I'm going to sell, too. A3000UX case w/ for-parts mobo, working A1000 with cosmetic difficulties, several A1000 RAM expansions 256KB-2MB, external HD boxes, old fashioned Amiga mice, etc.

Got all sorts of in-box software, too. Got some game boxes/documentation without disks, as well. :-)

Any help pricing old and NOS type cables also appreciated.
Title: Re: geocites vs sales pictures
Post by: cecilia on April 27, 2004, 12:47:12 AM
Quote
You think Geocities would get mad if I made a website just for storing all the pictures I have of the cables I'm going to sell?
no. if all you are doing is showing pics, they don't care.
most of my site is pics as well.
but i linked to paypal which is on another (paided) site.

what yahoo won't let you do is hotlink pics. in other words, you have to make a web page on the yahoo site which has the pics in it.
Title: Re: geocites vs sales pictures
Post by: Argo on April 27, 2004, 01:13:03 AM
Shouldn't be a problem. Though you'll probably be hit by their "Bandwith Limit Reached, Try Back Later" message.
Title: Re: geocites vs sales pictures
Post by: Ilwrath on April 27, 2004, 01:40:57 AM
Just make sure you can link to the page with the pictures cleanly.  IIRC, just linking directly to a picture stored on Geocities will fail.  (ie, only pages located in your directory on their server can be the referrer for images located in your directory.)

Other than that, and a possible 'terms of service' violation, it shouldn't be a problem.