Posts

Showing posts from November, 2022

Some people don't think other people should be allowed to have opinions

Image
At least the last "Friend of Colleton" to  attack my candidacy  made an effort to make an argument--albeit one that was not supported by the facts. Here's a new email that's simply an  ad hominem attack :   I just finished that delusional megalomaniac Chad King “fake news” essay on why he wants to be The King of Colleton.  What a nightmare that he managed to find enough signatures, including his wife’s which is illegal as anyone who is an expert  in Governance as he is knows it is one per household. The worst, and there were many that must have Keith screaming, is his blog Colleton Skeptic.  My plan in response is to start my own blog entitled Colleton Scrumptious which will illuminate on a daily basis all the various ways I love living here, how grateful I am for the natural beauty and security, how I treasure my house, and my phenomenal friends including those who sacrifice their time and energy to keep the Chad Kings in check.   Dede Just ...

A reasonable question

One of the features of a Blog is that people who want to remain anonymous can pose questions to insure that the Owners understand the facts before they vote. Yesterday, an anonymous person made the following comment: Hey, as long as people are questioning DOL coverage let’s be reminded CK you ran governance, and made no strides on the seawall. Zero. And the you helped with the EDC contract that has contributed to our density concerns. Easy to be on the sidelines right? Why will you be a better BOD member now … how will you add value and be effective? Here is my response to this question. Seawall : The J-Lot and M-Lot seawalls were built in the 1990s and the Phase II seawall was built in the 2000s. For whatever reason, the seawall was a low visibility issue until Hurricane Matthew in October 2016. Matthew damaged parts of the seawall and the issue became more visible. Management, the Board and the seawall lots owners discussed the issue during 2017 and 2018, but little was done...