[Tagging] Feature Proposal - Voting - Cryptocurrencies with payment tag

[Mateusz Konieczny]

Yeah, while this proposal will likely fail - such invading should be treated as 
invalidating proposal vote.

While new contributors to OSM are welcome, in this case we are interested in
opinions of OSM contributors.

Not in things like https://archive.md/a8Qia

It is not a place for https://en.wikipedia.org/wiki/Boaty_McBoatface
or repeat of something like
https://www.mentalfloss.com/article/52524/15-polls-hijacked-internet

Note that we have precedence for invalidating proposal votes without
having an explicit rule for that, see
https://wiki.openstreetmap.org/wiki/Proposed_features/motorcycle_friendly/tag_description

<insert rant here about cryptocurrency speculators being annoying in one more way>

Oct 19, 2021, 04:44 by zelonewolf at gmail.com:

> This vote is being actively brigaded by crypto enthusiasts directing other crypto enthusiasts with no connection to OSM to create OSM wiki accounts in order to vote for this proposal.  Even more concerningly, the talk discussion indicates that proponents of a specific, obscure crypto-currency are being directed to this wiki vote as a group.  While this vote is currently failing, I believe the vote is invalid and should be shut down.  This vote does not represent a confirmation/documentation of community consensus as intended by the proposal process.  As such, we should not allow it to proceed further.
>
> On Wed, Sep 22, 2021 at 9:04 AM András Fuchs <> andras.fuchs at gmail.com> > wrote:
>
>> Voting has started for Cryptocurrencies with payment tag. 
>> https://wiki.openstreetmap.org/wiki/Proposed_features/Cryptocurrencies_with_payment_tag
>> _______________________________________________
>>  Tagging mailing list
>>  >> Tagging at openstreetmap.org
>>  >> https://lists.openstreetmap.org/listinfo/tagging
>>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20211019/32c56d58/attachment-0001.htm>