I’m not a fan of new badges being turned on by default.
We don’t use most of the native Discourse badges so I have them turned off, but there was an awkward situation just now when someone received this:
I knew nothing about it and his ‘um, wow, thanks’ response was a bit awkward.
I think it’s an awesome initiative and will go down well in lots of communities, but it’s not something that we’ll use and I don’t think it should be enabled by default – at least not without notifying the CM.
Discourse changes all the time. I like to think I keep abreast of things by spending a lot of time reading here. But I understand that most don’t have that luxury.
At one time I considered trying to write a plugin that compared an existing site_settings.yml against the newer file, but it’s still on my “maybe someday” todo list.
Do you think something like that would be adequate to prevent most serious gotchas?
i.e. These Settings are new - be aware!
It would be helpful for me, yes.
I remember having a convo with someone about this a while back. I’d love it if Discourse had a What’s New / News widget on Dashboard like WP does.
I think the easiest to implement would be a link to “commits since your version”.
But I don’t see that as being the most user friendly. Kind of like sending a newbie to a W3C RFC. Everything needed is there, but can it be digested?
I guess we could petition the Discourse team to use descriptive commit tags so they could be filtered.
But I’m thinking changes in the site_settings.yml file would catch most things that would be important to forum users.
That already exists
And on the upgrade page
However, if you are hosted by Discourse (and I believe @hawk is), they sort of handle upgrading you… so you still might not get a chance to see what changed.
Out of curiosity @hawk, do you have all badges disabled or just a select number of them? As I know there is a global setting for ALL badges, setting is enable badges
Hmm if badges were disabled globally this is a bug. But I don’t think you disabled badges globally? You should disable badges globally if you don’t want badges.
Otherwise this is very much by design.
I think there is merit for a badge system is on but no stock badges are enabled by default, mode, but it is a rather rare use case
My personal preference would be that new badges (and other such changes) be preffed off by default, but that when an admin/leader logs in after the update, they have the option to enable them.
As an alternative, could it perhaps be that the preferences become available a week or so before the functionality (with a “what’s changing” notice), so that admins have the opportunity to pre-emptively disable them? I’d be happy if this was a way to set preferences by typing in a key (like Firefox’s about:config), and these were communicated via email (or announcement here) ahead of the release.
Would there be merit in something like this?
In that scenario, do users ever advance through trust levels automatically? I’m curious if the trust level badge contains the logic for advancing, or if the badge merely triggers on some other test succeeding.
In any case, I think defaulting to badges off is not such a great idea, but I can see merit in a setting for the default badge status:
Badges default to: [ enabled | disabled ]
And then a list of all the badges with current settings:
Nice Post: [ explicit enabled | explicit disabled | site default ]
Great Post: [ explicit enabled | explicit disabled | site default ]
…
I’m with @HAWK on this one. I’d love to see a better (more interactive) system for badges that are added. Two of my sites are closed, log in only environments, with one using SSO. As such, we’ve disabled a number of badges that are unobtainable in this setup, like shares and invites. One has no reply-by-email, so the email badge is disabled.
The most recent badge may be an extreme example (first badge to send a PM), released near end of month so it was awarded quickly - but it caught me by surprise too when I saw the PM in email logs. Some type of “a new badge has been added, check it out here” on the admin dashboard would likely be enough.
Yo también paso mucho tiempo leyendo aquí, pero de alguna manera logro perderme algunos temas realmente cruciales. Esta nueva función también me tomó completamente por sorpresa; lo primero que supe de ella fue en este tema. Gracias @HAWK por llamar nuestra atención sobre ello. Ahora la estoy explorando con mi equipo de moderadores para decidir si la mantenemos activada o no.
Quizás el equipo de Discourse podría intentar ser un poco más vigilante a la hora de notificarnos a todos (y especialmente a sus clientes de pago) sobre las nuevas funciones que se “impondrán” en nuestras comunidades y que podrían necesitar desactivarse.
Dicho esto, estoy profundamente agradecido con el equipo de Discourse por su trabajo continuo y diligente para desarrollar y hacer evolucionar este software increíble, y estoy muy contento con él, así como con la velocidad y el alcance de las mejoras. No tengo ninguna queja sobre la dirección que toma y confío plenamente en Discourse, y estoy asombrado cada día con lo que está ocurriendo con el software.
Además, no soy un cliente de pago, por lo que estoy muy dispuesto a aceptar la forma en que aparecen los cambios a través de un flujo constante de commits en git, y que frecuentemente una sola reconstrucción de mi sitio genera una serie de reconstrucciones en los días siguientes a medida que se ajustan las nuevas funciones y se corrigen los errores. Es divertido (a modo de búsqueda de huevos de Pascua) buscar cambios y nuevas funciones, y reportar errores y verlos corregidos rápidamente. Probablemente pueda contar con una mano, o incluso con solo unos pocos dedos, el número de veces que he tenido una sorpresa desagradable después de una actualización. Incluso entonces, no fue un gran problema y se resolvió rápidamente. No he tenido ni una sola queja de mi comunidad.
Me entristecería si el ritmo y la creatividad de las mejoras se ralentizaran porque el equipo tuviera que dudar de cada nueva función y pasar más tiempo mirando hacia atrás y preocupándose excesivamente por el impacto en las instalaciones existentes.
Creo que la solución para mí será vigilar la categoría Contribute > Feature para que se me notifique de cada nuevo publicación en esa categoría, aunque eso signifique algunas notificaciones adicionales sobre solicitudes de funciones que no necesito ver.
We have all native badges disabled but use custom badges.[quote=“codinghorror, post:6, topic:61371”]
You should disable badges globally if you don’t want badges.
[/quote]
I definitely do want badges. 
But I want to be able to choose which ones, and I don’t want new ones that I don’t know about to be activated by default.
This is such a rare use case though. Can’t say when we would get to that.
It’s a big change to make new badges not activated by default?
It’s not on our roadmap for the forseeable future, no.
/me does the PR-welcome dance, with full ruffles and flourishes
Ok, fair enough.
Is there an easy way to know when new badges will be added?
Actually my real issue here isn’t so much the badges but the fact that users are receiving messages from me that I wasn’t aware were being sent.
What are the criteria that kick this message off?
You can learn everything there is to know about the new feature that prompted this topic over here:
De hecho, esto se está convirtiendo en muchas notificaciones nuevas e innecesarias para mí, así que volveré a dejar de seguir la categoría Contribute > Feature.
Por favor, no reduzcan el ritmo de desarrollo, pero si es posible, intenten encontrar formas de comunicar de manera oficial sobre las funciones que realmente se están implementando y que aparecerán en la rama tests-passed.
