Ryan Ashbrook

This should be fixed now. A couple days ago, Google Tag Manager was enabled, however the the GTM Body Snippet simply had <noscript> in it, which was causing the issue.
I've adjusted that to <noscript></noscript>, which resolved the issue.
Note, this isn't likely correct - if you are using Google Tag Manager, then there is additional code that needs to be added there. Unfortunately, that code is unique, so I cannot add it myself. Only the administrator of the site, with access to GTM, can do that.

This should be fixed now.

This should be fixed for you now.

Yes, but this only controls cookies IPS4 itself sets (so anything prefixed with ips4_, or your prefix if you've changed it previously). Cookies from external sources will follow their own rules.
If you do this, make sure you use two dots as that's what allows the cookies to be read by subdomains:
define( 'COOKIE_DOMAIN', '.brfcs.com' );  

Are you using OAuth Tokens or just a REST API key? If you are using OAuth, then yes you still need to submit HTML with the request, however it will be parsed and sanitized according to the users permissions to remove anything malicious (excluding those with HTML posting permission - which should be no one other than groups like Administrators). This is ideal for applications that end users submit to directly, like a Desktop app in your case. OAuth also limits requests based on a users permission, so even if they can submit files to the API, they can still only submit to categories they have permission to post to.
If you're just using a REST API key, then it's assumed that the request is coming from a trusted source. This is for things only an administrator has complete control over (typically automated tasks).

The spam defense service already takes this into account.

ACP > Statistics > Activity > Reactions.

There hasn’t been upgrade code to disable third party apps and plugins in quite some time.
If you upgraded from a version prior to the PHP8 requirement, then yes, they would be automatically disabled to allow your community to work error free.

Sorry about that - can you please try now?

It looks like there was a temporary issue with your license - I have refreshed that, and your databases are back now.

This should be fixed now.

No, only MySQL is supported at this time.

You are missing your beginning and end delimiters. Try this:
/^(fa(-[0-9a-zA-Z]+)+)( (fa(-[0-9a-zA-Z]+)+)+)*$/i And then set Apply text formatter to Yes, and then set Formatting Option to All lower-case in case someone enters a valid Font Awesome icon class, but uppercase.

I believe key is a reserved keyword in MySQL. Try this.
\IPS\Db::i()->delete( 'core_tasks', array ('`key`=? AND app=?','steamCleanup','steam') )  

Yes, in your Admin CP > Community > Calendars, edit the calendar and set "Events must be approved?" to Yes.

This should be fixed on our end now.

It does not.

I've unlocked your account.

Unfortunately, from everything I can see, this is happening on Twitter's end. I'm not entirely sure there is much we can do for this right now.

This is a known issue, and we have a fix coming for it.

Classes using the trait can overload the method if the column name does not match - in this case, the trait is simply providing a default value.
Using mapped() would not work, because the "topic" column isn't actually included in the $databaseColumnMap property.

ACP > Members > Download Member List. Under Data to include, uncheck everything except Email address, and set "Member bulk mail subscription" to Currently subscribed.

Yes, I've just checked with other PWA's as well, and they also have the same issue, so this is a problem in iOS itself. The manifest only has two properties to define the name of the PWA (short_name for locations with limited space and name for anywhere else), and both are set.

If you can update your Admin CP details in your client area, I can check this for you. However, a 403 typically means that your host has Mod Security or some other firewall / security software in place that is blocking the request.
I would recommend contacting your host to see if this is the case and, if so, change the configuration to allow the request to go through properly.

We use the Rules settings under the Display Settings tab.