keepworking

The idea is to put channel codes into existing address schemes such as email, sms, phone call, etc. that can identify "for whom did I share this address".

This code will be generated as a random number, and I would like to use a method that prevents me from sending mail to my address without this channel code.

It will work like some kind of extended protocol in the existing communication protocol.

We have apparently suffered too much from contacts we receive from an unspecified number of people. Simply because someone has sold our contact information to another person, or has not managed it properly.

Some people would have been victimized by phishing, some would receive too many ads to get important news, some would profit off the hook by selling contacts without guilt

Wouldn't it be possible to reduce the damage if there is a random code attached every time you share an e-mail with people and record who you shared it with?

If I remove the code when I sell my contact to someone else, I think it's a pretty effective way if I can't get in touch with me without the code, and if I can't guess the code and deceive you into something else

In the case of phishing, when a criminal impersonates a state agency and makes contact, if the contact is from a clothing brand that joined last week, no one will be deceived.

No matter which channel you start to receive spam mail, you can refuse to receive all mail that comes to the shared channel.

You can even hold the person who provided the channel responsible for selling the e-mail address or neglecting to manage personal information without asking for consent.

Maybe it will be cumbersome to share your contact information.

But this may also make the process convenient for platforms or service layers.

There are many cases where you type your e-mail address directly when you sign up for membership, but there are many cases where you use chrome to type it automatically. At this time, the system can add a channel code and let you register automatically.

It can also be implemented through extensions and things like that. These days, passwords are also made into random numbers, so it's not that difficult to create a device that can alleviate this complexity.

So far, it's been a simple idea. Will it really work if it's implemented? Will it help people if I try to create a project that implements it?

Thankyou

I just came up with the idea of a little simple lottery system with hash.

{Time of purchase of lottery } + {lottery number} + {buyer id} +...

The above form is listed each time the buyer continues to be added, and the winner's lottery number is derived from the hashing value of the data.

I think it is difficult to manipulate because it does not require the reliability of any random number generator and because the participants provide random numbers.

I don't think the hardware resources will be big, and I think it's a pretty easy way to implement and for participants to verify, so can you give me some advice?

When I look at reference images of the structure of the software on Wikipedia, etc., the name of the creator is this. I looked for materials to learn from this person's blog or something like that, but I couldn't find any. Does anyone know?