Warning: getdate() [function.getdate]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 155

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 156

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'GMT/0.0/no DST' instead in /home/notgoo73/public_html/rss.php on line 198

Warning: Cannot modify header information - headers already sent by (output started at /home/notgoo73/public_html/rss.php:155) in /home/notgoo73/public_html/rss.php on line 220
http://www.notgoodenough.org:/index.php Opticon RSS Feeds Consumer website www.NotGoodEnough.org en-au Mon, 04 Apr 2016 02:20:27 GMT http://www.notgoodenough.org:/viewtopic.php?f=113&t=42706 rambotrader Wed, 07 Oct 2015 08:41:07 GMT http://www.notgoodenough.org:/viewtopic.php?f=113&t=42421 computerflyer Tue, 12 May 2015 10:13:16 GMT http://www.notgoodenough.org:/viewtopic.php?f=113&t=41839 Nomad44 Wed, 17 Dec 2014 20:51:32 GMT http://www.notgoodenough.org:/viewtopic.php?f=113&t=42265 Lloyd61 Fri, 17 Oct 2014 06:33:02 GMT http://www.notgoodenough.org:/viewtopic.php?f=113&t=42215 tekcop Fri, 15 Aug 2014 06:33:11 GMT http://www.notgoodenough.org:/viewtopic.php?f=113&t=42174 MosMad Mon, 04 Aug 2014 06:47:45 GMT http://www.notgoodenough.org:/viewtopic.php?f=113&t=42137 computerflyer Wed, 16 Jul 2014 21:53:57 GMT http://www.notgoodenough.org:/viewtopic.php?f=113&t=42137 furious bird Wed, 16 Jul 2014 13:01:43 GMT http://www.notgoodenough.org:/viewtopic.php?f=113&t=42121 BrizJH Fri, 11 Jul 2014 22:57:19 GMT http://www.notgoodenough.org:/viewtopic.php?f=113&t=42120 computerflyer Fri, 11 Jul 2014 22:02:11 GMT http://www.notgoodenough.org:/viewtopic.php?f=113&t=42120 BrizJH Fri, 11 Jul 2014 10:41:35 GMT they refuse to abide be Australian law. eGlobal Digital Cameras appears to be a HK company and you have effectively done business in HK not Australia. There is thus no requirement for them to comply with Australian law. You could try going after them via HK regulators, but good luck on that! See http://www.consumer.org.hk/website/ws_en/ for an intro. Noting the company specifies warranties are house warranties not manufacturers warranties and you may have to send a faulty product to "either HK or Australia" as instructed, they are all red flags IMO. Always consider the recourse you may have, and the costs of warranty postage should the need arise prior to doing business with an offshore "super discount" operation. Good luck getting a refund from Visa.]]> http://www.notgoodenough.org:/viewtopic.php?f=113&t=41950 computerflyer Sat, 12 Apr 2014 23:14:11 GMT http://www.notgoodenough.org:/viewtopic.php?f=113&t=41950 patrick80 Sat, 12 Apr 2014 05:07:29 GMT http://www.notgoodenough.org:/viewtopic.php?f=113&t=41930 daisy1251 Tue, 18 Mar 2014 10:11:22 GMT http://www.notgoodenough.org:/viewtopic.php?f=113&t=41905 Kuzzo Fri, 28 Feb 2014 07:48:45 GMT quick to take the money from my account I hope you mean credit card. Your next email to the company should be a refund request for non-delivery. Send the email with the "read receipt" option set. Their email system might ignore that, but if it is honoured and you receive one, it is proof of email delivery. If their system has an automatic acknowledgement that serves the purpose. also. Assuming neither a refund nor goods are forthcoming, contact your credit card issuer for a charge back for non-delivery of goods. They will ask if you tried to resolve it with the merchant. Your email records will demonstrate you did and were unsuccessful. There is a time limit to asking for a charge back, usually 60 days but sometimes 90. Some companies will appear to be helpful until the 60 days expire and then ignore you. Even if they promise a refund, if you do not receive it in the 60 days lodge the charge back claim. Good luck with resolution.]]> http://www.notgoodenough.org:/viewtopic.php?f=113&t=41897 computerflyer Sat, 22 Feb 2014 00:41:09 GMT http://www.notgoodenough.org:/viewtopic.php?f=113&t=41897 mloricha Fri, 21 Feb 2014 07:39:43 GMT depot and a phone call made to my mobile phone, so I can arrange to collect it." After about 30 emails, I have (reluctantly) provided a street address, in the full knowledge that the courier will not deliver here (I have over 15 years of experience to back up this assertion) and that, as we both work at locations that change from day to day, and week to week, I cannot give a "work" address for delivery, as I cannot guarantee to be at that address on the day of delivery. Kogan suggested that I get the local PO to "sign for the delivery on your behalf" but that would be tantamount to expecting the PO staff to accept responsibility for the delivery if (in very few cases, to be sure, but still enough to be concerned about) the item proved to be faulty/damaged on delivery. I am quite happy to accept a delay, I am quite happy to go out of my way to ensure that I (and I alone) sign for the delivery, so that I can inspect the packaging and satisfy myself that it is complete. FFS!! Not everyone lives in a city, and has a street address where there is ALWAYS someone present to accept delivery! Get with the program, Kogan! The 20th Century awaits!]]> http://www.notgoodenough.org:/viewtopic.php?f=113&t=41875 JA2340 Sat, 08 Feb 2014 09:43:00 GMT :)]]> http://www.notgoodenough.org:/viewtopic.php?f=113&t=41839 nm40 Sat, 28 Dec 2013 03:54:46 GMT http://www.notgoodenough.org:/viewtopic.php?f=113&t=41819 jpcw Wed, 20 Nov 2013 07:18:35 GMT