Hi all, I posted this on the African violet forum today. I decided post it here too. ---------------------------------------------------------------------- Because I have been hearing conflicting opinions of what iVillage claims to have proprietary rights over I decided to look over the document a little closer. I should have done this sooner before posting an opinion. I'm no lawyer, so don't consider my interpretation of the copyright statement to be the final word. When looking at 7. Rights of Content paragraph 2, I also see no reference to iVillage laying claim to the link to any picture. And, that makes sense. If one posts a picture, it becomes a physical part of the forum. A link to it picture would not be a part of the forum and could be in some ways construed as a footnote or reference. It is sort of the same if I were to post a picture belonging to someone else, without their permission, I would be in violation of copyright laws. However, if I post a URL, where this picture resides, I have not violated copyright laws, because I have shown the owner of the picture. Another concern that people have had, in this same paragraph, is of iVillage having proprietary rights of the content of one's personal web page. People are concerned that if one were to link to his or her web page or web site that iVillage would lay claim to that also. After looking at the wording it seems to me that one's personal web site is really our member page. I came to that conclusion because in the first line it does say, ' By submitting content, which shall include your member name, to any "public area" of the Garden Web network, including, but not limited to, the forums and your personal web site, exchange page or journal...'. The use of the term web site for our member page is very confusing. Nowhere else on Garden Web is our member page referred to as our web site. I think it's OK for iVillage to have a legal document that spells things out in legalese. But I think that it would be a good idea if there was a place where this was spelled out in layman's terms. I really don't understand why iVillage doesn't respond to some of the threads in the suggestions and comments forum. When these interpretations and rumors start it is best to address the problems immediately so that people don't get upset and spend considerable time dwelling on them. There are people who have decided to leave G. W. because of what may be false interpretations on their part. I don't know. I like Garden Web a lot. I think it's one of the best message boards out there and I want to continue to be a part of it. Larry

The short story? Upload your photos to photobucket using the "800 by 600" pixel upload option. Done. You'll get a small file size but a photo that will display well. To answer your questions, here's the long story. And I'm not kidding. It's long. Way too long: "What I'm also trying to understand is the whole process: I take a picture with my 6.1 Kodak camera. The picture size is therefore________" Your file size depends on the settings on your camera at which you are taking photos. Most cameras offer a couple of choices, like "Image Quality: FINE/NORMAL/BASIC" and/or "Image size: LARGE/MEDIUM/SMALL". Those choices will define the amount of jpeg compression that your photo undergoes and thus they will define the size of the file that comes out of your camera. Generically a 6MP camera is probably putting out jpeg photos in the 2-3MB range. "Jpeg" is a compression program. It's a program that reduces the MB file size of the program by discarding redundant pixel color information from the photo's file for similar-colored pixels in the photo. It does not get rid of or discard any pixels. It just "averages" out red/ green/blue information assigned to similar colored pixels. jpeg looks at the photo's individual pixel information and says "these reddish pixels that are next to each other in this photo are so close in color, I'm going to consider them the exact same color". So it keeps the R/G/B information for one of the pixels, discards the RGB info for the other two, and assigns that saved RGB info to all three pixels. That allows your file to be smaller without destroying the overall visual integrity of the photo when you view it. If a file were to be over-compressed...too much information thrown away...then it can get ugly looking, very blocky. "When I upload it to Photobucket it remains 6.1 or do they change it as they "store it"__________" Using the default settings on PB it'll be uploaded as a small file. A MUCH SMALLER file. You've discovered the "Customize Your Upload Options" and you can use that to get a larger and more usable file size uploaded to your PB account. More about that later. "Of course talking about a picture in terms of 800x600 vs MB is confusing. " Your photo is made up of little dots, or to simplify, "pixels". If you have a photo that is "800 by 600", that's 800 pixels or dots wide by 600 pixels/dots tall. That's how "big" your photo appears. 800 dots wide. 600 dots tall. Each of those dots or pixels is a color, all those little colored dots together make up the photo. If each of those pixels is a different color, then the file size (the "MB" or "KB") will be large because the file has to store red/green/blue information for each and every one of those tiny pixels. If you take a photo of a piece of red paper, then theoretically the photo's jpeg file size will be smaller because so many of the pixels will be the same red color. The file doesn't have to "remember" as much red/green/blue information even though the number of pixels in the photo is the same. So if you take your glorious 6MP photo that's 3000 by 2000 pixels and upload it to Photobucket at the 320 by 240 pixel option, PB is going to throw way a lot of pixels. You uploaded a detailed file with 3000 times 2000, or 6 million pixels, and Photobucket is going to throw away and discard over 5.9 million of them! Gone forever! It'll display that photo small, 320 pixels by 240 pixels, so to the eye it will still look okay at that small size. But if you try to blow up or magnify the photo, pixels will have to be created to fill in the "holes", and the color information for those created pixels will be guessed at based upon what the neighboring pixels look like. You'll end up with a blocky looking photo. So the picture can have a physical size defined in terms of how many dots or pixels make up the picture. 3000 x 2000, 800 x 600, 320 x 240, etc. The pixels define how big or small the picture will be represented on your computer monitor or on a piece of paper when printed out. The photo file size, in MB or KB, is how much information is assigned to remember the color information of the pixels that make up the photo. 6MP is a large photo and will take longer to upload than a 1MP file. It's how much space the photo will take up n your computer's hard drive. I'm going to run you through a few examples, I hope this helps to clarify: I have a 2MB photo on my computer. I just uploaded it to photobucket, during the upload photobucket automatically reduced the file size from 2MB down to 38kb. Ouch! It reduced the pixel size (or the number of "dots" that make up the photo) from 3341 x 2217 (3341 pixels wide by 2217 pixels tall) to 310 x 212. That was done using the default upload setting of 320 by 240. This file is tiny, only 38kb, so it'll upload fast. But the small file can limit the quality of the photo seen by the viewer. Here is the quality of the 320 by 240 photo: By adding a "Width=" designator to the HTML code, I can make your browser display the photo larger. Previously it showed at 320 pixels wide, because that's it's size of the photobucket file. I'll add "Width=800" to make it display 800 pixels wide. Again, it's a 38kb file size, 319 x 212 photo that's being forced to display 800 pixels wide. Where did the extra pixels come from? They were made up, their color information copied from neighboring pixels in the photo's file. Since they had to be guessed at, the photo looks blocky due to the groupings of exactly-colored pixels all clumped next to one another: The photo shows larger, but it's blockier. Now going into photobucket's upload settings I chose "Best possible quality (while staying 1mb or less)". A large file size...but not ridiculous. Photobucket uploaded my same original 2MB, 3342 x 2217 pixel photo as a 745kb file that is 2301 pixels wide by 1527 pixels tall. At 745kb it's a large file size so it'll upload slower, but with all those pixels the resolution will be quite good. When I now have gardenweb show this new photo file at its native resolution, it looks like this: Since most people have their computer's screen displays set at 800-1200 pixels wide, this 2301 pixel wide photo causes you to have to scroll left/right to take it all in. It's not viewer friendly. So now I'll limit the photo by adding a "Width=800" to the html code and it'll show better. A better size, and with nice resolution: There actually is a point to this post, and it's this: Photobucket has an 800 by 600 upload selection. If you want a "bang for your buck" upload selection, use the 800 x 600 choice. Uploading my 2MB file using the 800 by 600 option gave me a 134kb file with pixel dimensions of 800 wide by 530 tall. A very manageable file size that will upload quickly, and a pixel size that will display nicely: Still awake? Not me. Zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz

I might have a obsession with organizing my spices... I hated where I stored my pans before. They were always a mess and unorganized... I have 2 drawers like this. YEA!!! Mucho better! Drinkie-poo? This was the one thing hubby and I disagreed on. He didn't think we needed the wine frig. I went with the beverage center instead to get him more on my side. Then purchased before he could say no.. LOL He just said last night that he liked it. SCORE one for momma! Also was excited to have a dish drawer! No need for the pegs. island plugs

cocomac20: In regards to the viking stuff... that hood was sent to me without the proper fitting filter inserts, and no railing to even place the inserts on. I tried and tried and tried to have the company fix the issue and send me new inserts. Eventually they did send some, but once again they weren't able to be installed due to there being no railing, and even if there was a railing they were the wrong size. At some point they just stopped responding to my requests. I had to have my lawyer draft a letterhead document threatening to sue them if they didn't fix the issue. Only after that they sent a tech out who measured the space and was able to install the proper items. The customer service is horrendous, especially considering how much I spent on their product. Also, the vent fan had an issue with a clicking sound on the vent top opening and hitting the side walls of the shaft (which I was told to place some weather stripping on to stop), but seriously why couldn't they have done that at the factory? Lastly, the time controller on it has just simply stopped operating, I didn't use it very often anyway since it was kind of confusing to begin with, but it's just one more item that makes me sour of their products. Thanks for the compliments on the video :)