• A notice about Rule 3 regarding sites hosting pirated/unauthorized content has been made. Please see here for details.
  • Staff is working to deal with the problem of synonymous tags. See here for more information and to suggest tag mergers.
  • QQ will have forum downtime on October 21, starting at 10:00 AM Eastern time, for software updates.
  • 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.

About the Forum Downtime

Last edited:
I just wish that it would be telegraphed that posting would be impossible from 1:30am to 10am before the update. THAT was a nasty surprise.
That was accidental collateral of a temporary protective measure, not deliberate, so giving advanced warning wasn't really possible.
 
I don't think we use node.js, do we?


Node.js Brotli decoder out-of-bounds write permits remote code execution (CVE-2026-111497) - (high)

A flaw in Node.js can cause Node.js Brotli decoder out-of-bounds write permits remote code execution.

This vulnerability affects Node.js 26.x, 24.x, and 22.x.

Thank you, to mcollina for reporting this vulnerability and thank you aduh95 for fixing it.
 
That was accidental collateral of a temporary protective measure, not deliberate, so giving advanced warning wasn't really possible.

I thought I'd gotten banned/infracted until I saw everyone else had stopped posting as well.

Just glad they were on top of the issue, sounds like there's still a lot of places which need to get their security patched.

AO3 has patched their stuff as well, in case anyone is wondering.
 
Last edited:
PHP's core code is what you get when somebody in the early 90s fuses together some C and Perl and calls it Personal Home Page.
This language was never built to run anything remotely scalable.

I am very, very glad I dirtched the one NextCloud server I have running in favor of Syncthing.
 
Last edited:

Users who are viewing this thread

Back
Top