Skip to main content

Spotting photographic equipment scammers

  1. Go to nexttag or some other site and figure out the price range of the product
  2. Go to several different resellers and check the prices.
  3. Do a search with the reseller's name along with the phrase 'bait and switch'
  4. Find the product on amazon, adorama, ritzcamera and keh.com
If the
  1. Price of the product is much below (say 30%) the well know retailers' prices
  2. Accessories are correspondingly more costly
  3. Extended warranties are correspondingly more costly
  4. website sells the same product at a higher price and it looks like one is body only and the other is kit (but the website does not tell you)
Then be wary. They could be
  1. Trying to bait and switch you (sell you another product after saying out of stock)
  2. Trying to sell you over priced accessories and warranties to make up
  3. Selling a used or refurb kit as new
  4. Just plain old scam you - take your money and not deliver the product.
Labels:

Comments

  1. Helen OsterSeptember 27, 2009 at 6:46 AM

    Or you can simply search www.reselleratings.com, and check out the customer feedback and ratings.

    Sincerely

    Helen Oster
    Adorama Camera Customer Service Ambassador

    helen.oster@adoramacamera.com
    www.adorama.com

    ReplyDelete

Post a Comment

Popular posts from this blog

A note on Python's __exit__() and errors

Python's context managers are a very neat way of handling code that needs a teardown once you are done. Python objects have do have a destructor method ( __del__ ) called right before the last instance of the object is about to be destroyed. You can do a teardown there. However there is a lot of fine print to the __del__ method. A cleaner way of doing tear-downs is through Python's context manager , manifested as the with keyword. class CrushMe: def __init__(self): self.f = open('test.txt', 'w') def foo(self, a, b): self.f.write(str(a - b)) def __enter__(self): return self def __exit__(self, exc_type, exc_val, exc_tb): self.f.close() return True with CrushMe() as c: c.foo(2, 3) One thing that is important, and that got me just now, is error handling. I made the mistake of ignoring all those 'junk' arguments ( exc_type, exc_val, exc_tb ). I just skimmed the docs and what popped out is that you need to return True or...
Post a Comment
Read more

Remove field code from Word document

e.g. before submitting a MS, or hand manipulating some formatting because Word does things (like cross-references) so half-assed [from here ] Select all the text (CTRL-A) Press Ctrl+Shift+F9 Editing to remove anonymous comments that only contain thanks. I really appreciate the thanks, but it makes it harder to find comments that carry pertinent information. I'm also going to try and paste informative comments in the body of the post to make them easier to find.
24 comments
Read more

h5py and multiprocessing

The HDF5 format has been working awesome for me, but I ran into danger when I started to mix it with multiprocessing. It was the worst kind of danger: the intermittent error. Here are the dangers/issues in order of escalation (TL;DR is use a generator to feed data from your file into the child processes as they spawn. It's the easiest way. Read on for harder ways.) An h5py file handle can't be pickled and therefore can't be passed as an argument using pool.map() If you set the handle as a global and access it from the child processes you run the risk of racing which leads to corrupted reads. My personal runin was that my code sometimes ran fine but sometimes would complain that there are NaNs or Infinity in the data. This wasted some time tracking down. Other people have had this kind of problem [ 1 ]. Same problem if you pass the filename and have the different processes open individual instances of the file separately. The hard way to solve this problem is to sw...
Post a Comment
Read more