The reason I ask is that recently, there was a weekend where Ravishment University appeared to be unavailable, behind what I believe was a 503 error.

This week, up to and including now, clicking on Ravishu comes with a warning that it cannot be accessed through an HTTPS (secure) link, and that passwords or other information may be stolen. This was not the case prior.

I don't know if others are having similar experiences, or if it's a local phenomenon, but I'm somewhat concerned with the possibility that, say, some neo-puritanical jackass is attempting to do dirty to the board and/or its members. I'm hoping someone who knows something of the matter can fill me in and perhaps (if warranted) reassure me that all is well.

[Army of One]

That has been the case in the past, and indeed, our submission rules were changed to only allow stories containing subjects 18 and older as a result of this. Right now, Eljorn and Lois are the pair who know what happened, so it's best to wait for them to respond.

[Eljorn]

There are two situations that you've brought up, the first being the 503 error and the second being the https issue.

A 503 error is a server-side error and is not the same as having the account suspended.  While I don't know the actual particulars, what appears to have happened is that either the webserver went down or hung.  I notified Lois of the issue and after a day or two we were back online.  This was probably an issue with one the web hosting webserver(s).

Let me again state that this was NOT the same situation as when our account was suspended.  In that case a quasi-governmental agency in Germany sent a report indicating that we had underage written content (based on German law) and web hosting company decided to suspend our account.  That is what led to the new rule that individuals in stories needed to be 18+ in age. 

Regarding the https issue.  When we upgraded our base software the database administrator also created an SSL certificate that allowed for https: connections.  That certificate has since expired which is why https connections are no longer working.  In the past I've spoken with Lois re: https and her feeling is that it's an added expense, which she and only a few other contribute, and since we're NOT in the business of collecting dues or engaging in any other financial transactions, https isn't necessary.

I'll bring up the subject again.

I hope this clears up the situation, if not, let me know.

Regrds.
--
Eljorn

I think my bigger concern with the 503 error was that RU might have undergone something like a Denial Of Service attack. Combined with the timing of HTTPS no longer working, my mind starts to devise nefarious hackers "spoofing" RU with the attention of doxxing accounts, stealing IP addresses, and the like.

I'm glad to hear that is just my paranoia talking. Thank you for taking the time to fill me in.