Problem with an author's site

A word from our sponsor:

Printer-friendly version

Author: 

There seems to be a problem with Samantha Michelle's Storysite (Samantha MD).
I have tried at least once a day for the last 10 days to view it looking for new stories and have not been able to.
A message appears that the server isn't responding.
I hope is all is well with Samantha and hopefully it is just a minor equipment problem.
And yes, I did see the newest part of her latest story was posted Friday.

Comments

I just tried

Patricia Marie Allen's picture

I just tried accessing her page here on BCTS and drew a blank, with only her name. I tried looking at my own and it came up just fine.

Hugs
Patricia

Happiness is being all dressed up and HAVING some place to go.
Semper in femineo gerunt

Wrong name

my user name here is "SamanthaMD"

Samantha

SmanthaMD

Patricia Marie Allen's picture

SamanthaMD is good... I wonder who Smantha Michelle is and how they only have a name listed on the "author search page" and an author page, but no content.

Hugs
Patricia

Happiness is being all dressed up and HAVING some place to go.
Semper in femineo gerunt

None

erin's picture

There is no Samantha Michelle. I'm not sure how the page got created, but it is the same person as SamanthaMD. :)

Hugs,
Erin

= Give everyone the benefit of the doubt because certainty is a fragile thing that can be shattered by one overlooked fact.

Not Exactly...

Samantha Michelle was an author on StorySite (one of my favorites, as it happens). About two years ago someone reportedly posted a couple of stories here under that name which turned out, apparently, to be plagiarized and got removed from the site almost immediately, so quickly that all I ever saw were the titles.

Eric

If anyone else is having problems

please send me a message and I will respond.
My site has been under attack recently so I've been a bit aggressive when it comes to blocking sites. I have a shell script that analyzes the web server logs and gives me a list of suspicious IP addresses. There are about 25 rules that are used to filter out the bad requests.
I might have been too aggressive so I'm willing to 'unlock' various IP addresses if they belong to genuine requests.

I had 3 DDOS attacks from AWS last week. As a result, I've blocked ALL the IP addresses that AWS has. I know that sending a request to their abuse email will go straight to the big bitbucket in the sky. So they can have my middle finger as thanks.
Samantha

Trying to Survive among the Thieves

BarbieLee's picture

Over thirty years ago I purchased my own domain name BarbieLee.com. Over ten years ago I parked it due to spammers using it as a return mail address. I was receiving a dozen or more hate mail everyday from people who got coned and of course whose name came up when they looked at the return address or looked up Barbie Lee. The return in their spam message was different from the click on this link for treasures and riches beyond measure such as you have won... [email protected] is a heck of a drawing card but I couldn't handle the hate mail. The site has been parked. My Domain Register sends me an email every now and then wanting to know if I'm still alive. It's registered in my name not some big ISP that registers names for people. Like the Domain Name provider register's the name so the person who wanted the name really doesn't own it. The individual or business loses the name if they move ISP providers. Don't send any email there as the domain is parked, your mail will bounce.

I'd really like to open it up again and sell my stories and novels but the scammers is a pain in the...
Hugs Sam, I wish you luck in your fight with the ass holes of the world.
Barb

Oklahoma born and raised cowgirl

Stealing a Domain

BarbieLee's picture

Have no idea how prevalent it is now but several years back domain name stealing was a big problem for many. They would sign in to their own domain to find it was no longer theirs. Stealing a domain name is or was fairly easy. The con would find the passwords to the domain the owner had installed. They would change the password and then alert the domain provider they had purchased the domain and register as the owner. There are several programs designed to search for passwords. Thus no one has to sit at the computer for days, weeks on end searching for passwords as all they need to do is point their program at a site and turn it lose.

There was a response to this and it became necessary to inform one's provider to NOT transfer ownership. It's called "client transfer ownership is prohibited". Actually it can be transferred but only with a lot of personal phone calls, notarized forms, etc. Applying for a super spy identity permit would probably be easier. Most people who buy and resell domains don't lock down the domain for that reason. However if one has a domain and plan on keeping it inform your provider, transfer is not permitted. Don't know if the theft of domains is as bad as it was but be safe. From what I read it's next to impossible to get one's domain back after it has been stolen. Court, lawyers, lots of money and tons of documented proof, may get it back. If the thief is overseas..., kiss it off. All this info is from twenty plus years ago. Maybe things have changed but don't count on it.
Barb

Oklahoma born and raised cowgirl

Domain transfers

Well, domain transfers are a lot safer and easier to manage nowadays (since about 10 to 15 years …).
Typically, your registrar locks down a domain, requiring you to unlock it for a transfer via their management web interface. Also, a lot of registries (this depends on which TLD you register your domain in) use authentication codes for a transfer that you can retrieve via their webinterface (or they get sent to your registered contact emails).
Thus someone would need to guess which registrar you used (not necessarily guessable from WHOIS data …), then guess your username (again, not guessable from WHOIS data) and try to break your password. Nowadays you normally lock out an account after a number of bad password entries (at least for several minutes), so brute forcing a password is impractical (would take years to centuries).
Yes, I handled that kind of procedures for a few thousand domains, not hard, but explaining the necessary procedures to a customer who just wants to sell pizza and tried to move domain from somewhere else to our services, was sometimes … interesting. ;-)