179: Remove my email due to spam #1337

To reduce incoming spam

dang you got 1337

ACK aa452fa

plz squash

plz squash

feel free to use the "Squash on merge" GitHub button

Not refusing to merge, but I think we should figure out a better solution... :/

Not refusing to merge, but I think we should figure out a better solution... :/

What's your concern @luke-jr? You want one of the other BIP co-authors to ACK removing Marco as a co-author or you want Marco to provide a different email address which he doesn't mind being spammed?

edit: Oh you are one of the other co-authors :) Sorry I missed that.

My main concern is that people won't write BIPs at all because of spam fears.

I'm not sure the fears are justified - this seems to be prompted by a single human-written mass email to all BIP authors, the first in nearly a decade of the BIP process.

But it's not my place to say Marco must tolerate it either - so some solution is desirable. Maybe we should find a way to mask emails, or allow BIPs without emails published somehow?

Maybe we should find a way to mask emails, or allow BIPs without emails published somehow?

Offering the option of a PGP key or an email address? I guess the point of including an email address in the first place was as a way to contact the BIP author to discuss the BIP. It offers minimal identity spoofing protection (e.g. I pretend Marco co-authors my proposed BIP and list him as a co-author against his knowledge and without his permission).

Not refusing to merge, but I think we should figure out a better solution... :/

Your post advocates a

( ) technical ( ) legislative ( ) market-based ( ) vigilante

approach to fighting spam. Your idea will not work. Here is why it won't work. (One or more of the following may apply to your particular idea, and it may have other flaws which used to vary from state to state before a bad federal law was passed.)

https://craphound.com/spamsolutions.txt

My main concern is that people won't write BIPs at all because of spam fears.

People will write BIPs if the cost of being spammed is worth the benefits of the BIP.

On Thu, Jun 30, 2022 at 7:46 PM Luke Dashjr @.***> wrote:

My main concern is that people won't write BIPs at all because of spam fears.

I'm not sure the fears are justified - this seems to be prompted by a single human-written mass email to all BIP authors, the first in nearly a decade of the BIP process.

But it's not my place to say Marco must tolerate it either - so some solution is desirable. Maybe we should find a way to mask emails, or allow BIPs without emails published somehow?

— Reply to this email directly, view it on GitHub https://github.com/bitcoin/bips/pull/1337#issuecomment-1171506790, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMRS4W4LKIZDZIUBWKJJ7ELVRXMOHANCNFSM52I3DIMA . You are receiving this because you commented.Message ID: @.***>

Anything left to do here before merge?

I don't think this will suddenly cause every person in the world who would write a BIP to reconsider.

This is just something that Marco wants personally, and no one seems to be in disagreement.

We can continue discussion here or on the mailing list after merging, and people can unsubscribe to this PR if they don't want notifications of the discussion post-merge.

ACK. Marco seems to be in a hurry / not wanting to discuss in detail, so the faster we merge the faster Macro can unsubscribe this PR and move on.

In regards to the problem of spam, I don't think there is much we can do about it besides set recommendations on where / how to write your own email address if at all.

And really, the best recommendation would be "if you make a BIP, please be responsive to Github mentions and/or emails. WARNING: Once every decade or so someone might mass-email everyone, feel free to block those email addresses or use an alias for easier filtering."

I got that email on a couple of my anon psuedonyms' emails, but other than that I've almost never been contacted about a BIP ever.

Right, I'm not a BIP co-author for this BIP nor a BIP maintainer but I'd be for merging this and then discussing afterwards what should be done in future if similar requests are made in future. Especially as this is just a draft informational BIP.

@kallewoof @luke-jr