In T117#2207, @MacFan4000 wrote:

In T117#2182, @VancityRothaug wrote:

Considering this extension would be used for community votes, I believe that a community vote to introduce it would be needed. However i would recommend that usage of all extension features is restricted to stewards to control the "validity" of the discussions carried out at Test Wiki

This - community consensus is a must.

Just checking in.....

I would be fine installing it for testing, but not for community discussion.

In T117#2182, @VancityRothaug wrote:

Considering this extension would be used for community votes, I believe that a community vote to introduce it would be needed. However i would recommend that usage of all extension features is restricted to stewards to control the "validity" of the discussions carried out at Test Wiki

I'm not able to create webhooks, so probably easiest for @Justarandomamerican to configure this one as they have the proper permissions.

@Aviram7 not just sensitive rights, but also community votes such as changing of clauses etc. I strongly support this extension.

@MacFan4000, any update on this?

The securePoll is going to be proven very helpful for community and easy to held voting of advanced sensitive privileges.

Considering this extension would be used for community votes, I believe that a community vote to introduce it would be needed.

In T117#2179, @VancityRothaug wrote:

While SecurePoll would be a good extension to test, I believe it would also make a good use for community discussions and its addition should be considered.

While SecurePoll would be a good extension to test, I believe it would also make a good use for community discussions and its addition should be considered.

This seems to be resolved, though there was a problem previously.

The reply button is working fine for me.

This has occurred to me as well.

always remove as a publisher/subscriber before renaming.

In T118#2133, @Harvici wrote:

This again looks like an error developed while User:0hD33r! was renamed - I suggest that a sys admin recreate that account - maybe that will fix it?

This again looks like an error developed while User:0hD33r! was renamed - I suggest that a sys admin recreate that account - maybe that will fix it?