The site has now migrated to Xenforo 2. If you see any issues with the forum operation, please post them in the feedback thread.
Due to issues with external spam filters, QQ is currently unable to send any mail to Microsoft E-mail addresses. This includes any account at live.com, hotmail.com or msn.com.
Signing up to the forum with one of these addresses will result in your verification E-mail never arriving. For best results, please use a different E-mail provider for your QQ address.
For prospective new members, a word of warning: don't use common names like Dennis, Simon, or Kenny if you decide to create an account. Spammers have used them all before you and gotten those names flagged in the anti-spam databases. Your account registration will be rejected because of it.
Since it has happened MULTIPLE times now, I want to be very clear about this. You do not get to abandon an account and create a new one. You do not get to pass an account to someone else and create a new one. If you do so anyway, you will be banned for creating sockpuppets.
Due to the actions of particularly persistent spammers and trolls, we will be banning disposable email addresses from today onward.
The rules regarding NSFW links have been updated. See here for details.
@ziggy, you have been warned multiple times to drop this issue. Instead, you decided to drag it out into the public forum. We are not addressing this further, and ignoring staff warnings will get you a week off the site.
For the benefit of public readers, this post is a continuation of a...
Someone up-thread suggested Privacy Badger. I just tried it with uBlock Origin, basically the standard; it doesn't block it by default, but you can add the custom filter:
||tiktok.com^$3p
Note that uBlock Origin, and maybe others, might have problems in Chrome due to the upcoming Manifest v3...
Huh.
I had not really realized that the server now supported Tiktok embeds. Unfortunately, this functionality comes from an addon that supports a wide variety of media sites, and there isn't an easy way to select them on or off one by one.
I currently rate the probability of malicious software...
Regarding the original question, the rule issue here is primarily under Rule 1. Under Rule 1, it's a violation to attack or insult users for their tastes in fiction. Likewise, we also don't allow people to insult everyone who likes a given kink or genre.
When the topic shifts to RL concerns...
Wayback Machine, and other similar public archivers, cannot see QQ NSFW pages at all. This is a natural consequence of those pages needing a login to view.
If you want to archive stories, you can use FanFicFare or similar, which let you use your own username and password.
I've been away from computers for a few days, but now getting back to look into this.
I am no longer seeing the problem, and I don't see any issue on the server end. We've had lag spikes like this before, usually for mysterious reasons. However, this one was worse and lasted longer than usual...
There's a fair amount of leeway granted to people in-thread playing along with the story. In most reasonable cases there won't be an issue.
Assuming there is an issue, the way forward is to heed mod warnings and make a good-faith effort to resolve it. We will issue warnings before taking more...
I've turned off the media auto-embed for the moment. This means the only way to trigger that is to type out the full invocation, e.g. <url>, which is a bit of a pain. I'll look into finding a better way to do that later.
Is one of the two scrollbars the whole-window scrollbar? I just shrank my window down to very narrow, and the alert box scrollbar ends up right next to the one for the window as a whole.
The functionality of the textbox specifically should be almost entirely possible to bring in. The old QQ textbox was (an older version of) TinyMCE, so the differences are fairly minor.
The functionality of the rest of the forum is harder to duplicate.
The plan is to update the current TinyMCE implementation to duplicate all the functionality of the XF1 editor. This will take a little while, because I have about two dozen things to fix otherwise.
I've found the issue here. Those posts include some syntactically invalid BBcode; on the old site implementation, they coincidentally worked (or rather, were ignored and the subsequent element worked), whereas on the new one they coincidentally fail and mangle some of the surrounding text.
I...