Why aren't stories being posted?

[Britva415]

Some people swear by deleting the story, changing some minor thing, and resubmitting it.

The "changing some minor thing" part isn't necessary.

I'm not saying there aren't some people who do it, just that getting a new place in the review queue doesn't depend on making any change to the content.

 

[SmilingLez]

While I never claimed that Laurel fully reads any story, there is evidence that some level of human review does happen. One of those things is Notes to Admins. Sure, events that use a specific phrase to join can be handled with automation, but non-standardized requests that are honored clearly involved a human review. This is especially true of ones where those notes explains why a certain part of the story is going to trigger a flag erroneously.


Well, it's from 2022, but the Literotica account stated they use MySQL.


Except they are separate problems, and it's important to know which it is so you can actually fix what's broken. Sure, to the average user, broken is broken. However, to the mechanic, a blown engine and a broken driveshaft are very different things.

Also, once again, they're not running outdated MySQL on outdated Linux on thirty-year-old hardware.


Yes, bad code can put bad data in the database. However, that's true of brand new code as well as old code. Also, what you call stuck rows are simply rows unmatched by the query used. The problem might just as easily be an issue with the query criteria as the data itself. Unexpected combinations of data can cause this just as well as as unexpected data. I speak from experience when I say it's easy to AND when you should OR, or OR when you should AND.


No. It behaves unexpectedly, but quite predictably.


Maybe it doesn't make sense to you, but as somebody who actually supports web sites and the databases behind them, it makes a lot of sense to me. Actual data corruption and unexpected data are not the same thing. All those things you listed require only require faulty code to happen.

Unless that record is actually corrupted, the fact that a query doesn't return a record you want it to is a code problem. It might be the code that stored the data or the code that's querying for it (or both), but it's still a code issue. The code expecting different data is not a database issue. The database is storing what it was told to store just fine.

Agree to disagree. Your opinion is just as valid as mine. But the one thing we can agree on is Literotica is not fixing (and IMO do not care) whatever you want to call their errors - pending purgatory still exists and multiple notifications of new works still exist, along with other problems I'm sure.

 

[IWroteThis]

Agree to disagree.

Sure.

Your opinion is just as valid as mine.

Nope. Not even close. Sorry, but your comments demonstrate a lack of relevant education and experience that I have, making my opinion better informed.

But the one thing we can agree on is Literotica is not fixing (and IMO do not care) whatever you want to call their errors - pending purgatory still exists and multiple notifications of new works still exist, along with other problems I'm sure.

Wrong again. While they're not fixing them as fast nor in the order I would prefer, I do see some things getting fixed. I find the focus on new features over old bugs to be annoying, but the business model says they cater to readers before writers.

I also have to acknowledge that writing new code can be quicker, easier, and more fun that trying to track down and fix bugs in old code. I know, because I'm still running code I wrote over twenty years ago, and I'm also running code I wrote since then. Also, bugs in the code you're looking at are a lot easier to find than bugs in other code that is just exposed by the code you're looking at.

 

[SmilingLez]

Sure.


Nope. Not even close. Sorry, but your comments demonstrate a lack of relevant education and experience that I have, making my opinion better informed.


Wrong again. While they're not fixing them as fast nor in the order I would prefer, I do see some things getting fixed. I find the focus on new features over old bugs to be annoying, but the business model says they cater to readers before writers.

I also have to acknowledge that writing new code can be quicker, easier, and more fun that trying to track down and fix bugs in old code. I know, because I'm still running code I wrote over twenty years ago, and I'm also running code I wrote since then. Also, bugs in the code you're looking at are a lot easier to find than bugs in other code that is just exposed by the code you're looking at.

Pray tell O wise one, with insider knowledge, what bugs are (permanently) fixed?

And using your immense internal knowledge base, O wise one, tell me why the last five stories of mine (every single damn one of literotica's rules for submission have been obeyed) have been/ are in pending purgatory?

 

[123z]

It's now been 5 weeks since my story has been in pending. I sent a message to laurel but as usual got no reply. Since them I submitted part 3 of the story already pending and that has been pending for over a week. Very frustrating.

 

[SmilingLez]

It's now been 5 weeks since my story has been in pending. I sent a message to laurel but as usual got no reply. Since them I submitted part 3 of the story already pending and that has been pending for over a week. Very frustrating.

I submitted it as a bug and came up with a possible fix. Check the lit tech support forum. I finally deleted two of my non-erotic science fiction flash fiction stories and posted them elsewhere. Now I have four stories in pending purgatory