# Blue post notices ... really necessary?

**URL:** <https://meta.discourse.org/t/blue-post-notices-really-necessary/124192>\
**Category:** Feature\
**Tags:** post-notices\
**Created:** [July 28, 2019, 3:29pm UTC](https://meta.discourse.org/t/blue-post-notices-really-necessary/124192 "2019-07-28T15:29:29Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Tracey](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tracey/32/149153_2.png) [@Tracey](https://meta.discourse.org/u/Tracey)\
**Post date:** [July 28, 2019, 3:29pm UTC](https://meta.discourse.org/t/blue-post-notices-really-necessary/124192/1 "2019-07-28T15:29:29Z")

</div>

Anyone else find these blue banners announcing ones activity, very condescending, immature and annoying?  
Maybe even embarassing for the OP concerned! 🤷🏼‍♀️

> [@Watch out for double url encoding of SSO payload](https://meta.discourse.org/t/watch-out-for-double-url-encoding-of-sso-payload/124185):
>
> We’ve been having a ton of problems with our SSO implementation recently and after a lot of debug work found the issue. Some of our issues included: New users being unable to sign into the forums Existing users having 7 added to the end of their username when they signed in for the first time sso\_sync rejecting username changes It turns out this was all caused by double URL encoding our SSO payload. We were encoding it, putting it in the URL with the signature and encoding that again. As bas…

The Discourse forum does not need such childish improvisations!  
Just my opinion please feel free to comment, I know I will never add this feature to any of my forum groups.

---

_[View the full topic](https://meta.discourse.org/t/blue-post-notices-really-necessary/124192)._