# Discourse blocked my question
**URL:** https://discourse.cmake.org/t/discourse-blocked-my-question/5465
**Category:** Site Feedback
**Created:** [April 14, 2022, 9:41am UTC](https://discourse.cmake.org/t/discourse-blocked-my-question/5465 "2022-04-14T09:41:01Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@mschorm](https://discourse.cmake.org/u/mschorm)
#### Post date: [April 14, 2022, 9:41am UTC](https://discourse.cmake.org/t/discourse-blocked-my-question/5465/1 "2022-04-14T09:41:01Z")
I’ve just asked a long complicated question titled:
“ **CMake ‘-s’ argument - recent change in behaviour** ”
but the Discourse blocked it.
And I can´t post it again !! as it it “too similar to what I recently posted”.
I really need to discuss it - can you somehow unblock it?
The limit of 2 url per topic for new users is pretty dumb as well.
I must say my first impression of Discourse consist of deep frustration ☹
PS: sigh … also “Category can’t be blank”, but there is no category related to the Discourse forum. I guess “Site feedback” is the closest ?
---
### Author:  [@brad.king](https://discourse.cmake.org/u/brad.king)
#### Post date: [April 14, 2022, 2:34pm UTC](https://discourse.cmake.org/t/discourse-blocked-my-question/5465/2 "2022-04-14T14:34:43Z")
Your topic was in the moderator queue after being flagged by a Akismet. I’ve restored it:
> [@CMake '-s' argument - recent change in behaviour](https://discourse.cmake.org/t/5463):
>
> Hello, I am a maintainer of several packages that use CMake in the Fedora Linux. Recently, after the following commit: https://gitlab.kitware.com/cmake/cmake/-/merge\_requests/7001 and this release: cmake-3.23.0-0.1.rc2 the packages builds started to fail on CMake. I’ve reported a Bugzilla ticket in which I gathered my observations: [https://bugzilla.redhat.com/show\_bug.cgi?id=2057738](https://bugzilla.redhat.com/show_bug.cgi?id=2057738) The thing is I believe that the actual behavior differs from the intended behavior - I believe somewher…
> The limit of 2 url per topic for new users is pretty dumb as well.
It’s an anti-spam/search-engine-optimization feature of discourse.