Is this an on-topic Question and a valid Community Wiki?

Question

Related Question: https://wordpress.stackexchange.com/q/58214/12615

The background and motivation are exposed in the Q.
But for further clarification: 5G Blacklist is an HTAccess tool that acts as a Firewall to any platform operating in Apache (in my limited understanding).

Having it installed, I found specific Directives that are incompatible with WordPress.

Is WordPress StackExchange a valid venue to catalog such incompatibilities?

[edit]
Or better yet, can the related Q be modified/adapted to be fit?
(as it increasingly seems not to be...)

[edit 2]
Copy of the original Q, which self-destructed before being shut-down :)

The intention of this Question is to catalog the directives of the Perishable Press 5G Blacklist that may break or provoke malfunctions in WordPress core and plugins.

What it does

The 5G Blacklist is a simple, flexible blacklist that checks all URI requests against a series of carefully constructed HTAccess directives. This happens quietly behind the scenes at the server level, saving resources for stuff like PHP and MySQL for all blocked requests.

How it works

Blacklists can block just about any part of a request: IP, user agent, request string, query string, referrer, and everything in between. But IP addresses change constantly, and user agents and referrers are easily spoofed. As discussed, request strings yield the best results: greater protection with fewer false positives.

The 5G works beautifully with WordPress¹, and should help any site conserve bandwidth and server resources while protecting against malicious activity.

^{1 Editor note: my emphasis}

Reports are being made in the page comments, but, IMHO, that's not the best venue to search and track incompatibilities that such a nice tool may have with WordPress, as this Stack is.

Answer 1

This doesn't seem like a fitting use of the site to me. It's a little too vague what is being accomplished.

• Fixing the list? Would be better as bug report to original developer.

• Enumerating problems with it? Enumerating badness is simply not productive.