Add the slack platform support

[ash0521]

I hope this time will work,,,RUN

[BinaryHB0916]

Thanks, Ash. The community will check this by the following Monday.

[ash0521]

Could you please build now?

[ash0521]

😪

[ash0521]

Please take a closer look and say something

[nykma]

I'll take a close look after CI is passed.
I suggest you to build and test it locally before committing

• Run gofmt -l . until no output
• Run make build until no error
• Write test of this validator (like other validators do in this project)

If you have no clue what I'm saying, learn how to programming using go first. This project is not udemy for you.

[ash0521]

Sorry,I forget gofmt, please stay online,I change now

[ash0521]

Clear

[ash0521]

Don't run,I will all checked then text you,when totally resolved

[ash0521]

Man it has been a long time, Please finish

[nykma]

Good, but we still need a test to represent the whole workflow (at least validation workflow). Especially, I want to know the format of field Identity and ProofLocation (and the reason). They will be all self-explained in unit tests so no need to reply to it here.

Also, don't put Slack API key in the test code, just code and run locally on your machine. Commit the core part when you're done.

Take validator/twitter/twitter_test.go or validator/minds/minds_test.go as samples.

[ash0521]

Build

[ash0521]

sorry, i'm working.

[ash0521]

Please finish quickly

[nykma]

I follow telegram test code.

platforms differ widely, don't just copy / paste other platform's impl / test code. You can take them as a reference, but duplicate them must not work.

So you still don't understand the whole workflow of how ProofService works. Learn it in doc, and try to use it (MaskBook browser plugin's identity binding function) first. Until then, let's discuss about impl details.

[ash0521]

Check this,https://myworkspace.slack.com/archives/C1234567890/p123456789012345.

[nykma]

Also, don't post private chat into this public discussion.

[nykma]

Check this,https://myworkspace.slack.com/archives/C1234567890/p123456789012345.

C1234567890? Is this real? Did you copy it from your workspace?

[ash0521]

No,This is example.

[nykma]

What I need is a real ProofLocation in the test. You should run this test locally on your computer, and submit it when it's OK.

It will be better if you add some instruction of "how to get ProofLocation" in README.md.

[ash0521]

My public channel id,C04Q3P6H7TK

[nykma]

My public channel id,C04Q3P6H7TK

Write it in test then.

[ash0521]

And you say do we need to add slack,Slack is better than discord,Big company uses slack,Most slack users are company employees.

[nykma]

And you say do we need to add slack,Slack is better than discord,Big company uses slack,Most slack users are company employees.

I thought a little bit after that, I'm now realized that it worth to be supported, for on-premise scenario.

[ash0521]

Should we add page limit to our code?

[ash0521]

I got ProofLocation shape, ProofLocation will be proof message link.

[ash0521]

Okay, Please help me in testing code
Check the minds testing reference
Can you please explain me the requirements of the testing code 🙏🙏
Can I get proof payload before code merge?
Also I can't generate signature in go
But ProofLocation and AltID is confirmed, ProofLocation will be proof message link and AltID will be UserID.

[ash0521]

Please tell🙏🙏

[ash0521]

Please would you cooperate to end it?

[nykma]

Don't flood message in PR. Github is not IM, you should NOT expect immediate response from others.

Can you please explain me the requirements of the testing code

1. Generate a keypair by your own, note down pubkey (you will use it in tests like here )
2. Generate a sign payload (using your own GenerateSignPayload()) and a post payload (using your own GeneratePostPayload()) in your own playground mini program described below. Note down all necessary info to help you rebuild validator.Base in test case like this.
3. Sign the sign payload using private key generated in 1 , and place Base64 sig into post payload generated in 2
4. Publish / send / post the post payload in real world (in your case, send it in a slack channel), like the common user will use ProofService finally. Copy the proof location (in your case, maybe the message share link. If message link doesn't have the info you need to Validate(), you need to find another way), and use it in your test like this.
5. Setup your slack API key locally, and run your test. If test went green, submit your code, not your API key.

Can I get proof payload before code merge?

Write a small cmd/playground-ish by yourself, and generate one using your own GeneratePostPayload() func. Should be not that difficult.
BTW, Don't submit your playground, write and use it locally for your own.

Also I can't generate signature in go

Impossible you can't generate sigs. There are many helper functions in util/ and util/crypto/ for you to use.
Again, cmd/playground mini program just said before.

ProofLocation will be proof message link and AltID will be UserID.

ProofLocation, kinda correct (if "message link" has the info you need when Validate()). AltID, not quite. See discussion in PR #45 for what AltID stands for.

[nykma]

I'M NOT A TEACHER CORRECTING YOUR HOMEWORK. REPRESENT YOUR RESULTS IN YOUR CODE.

I'll not respond to any homework-ish reply from now then.

[ash0521]

🥲

[ash0521]

Please take a look now

[nykma]

Current code is OK to merge after CI turns green. Thank you for your contribution!