#Join
bitcointalk: ZiSaarina
telegram company: t.me/ZiSaarina
FACEBOOK : https://www.facebook.com/ZiSaarina
twitter company: @ZiSaarina
Topic: [BOUNTY] INTENSE COIN - Blockchain backed decentralized VPN - SIGNATURES + XMAS (Read 8666 times)
May 12, 2018, 01:57:19 PM
May 05, 2018, 03:29:09 PM
#join
bitcointalk: ZinoZviev
Telegram company: @ZinoZviev
FB : @ZinoZviev
twitter : @ZinoZviev
bitcointalk: ZinoZviev
Telegram company: @ZinoZviev
FB : @ZinoZviev
twitter : @ZinoZviev
April 04, 2018, 05:45:36 AM
As mentioned in the main ITNS ANN thread (looks like SlowGrowth forgot to cross-post here), those that were missed for the fact that Slack display names were not properly read have been re-evaluated. According to our re-evaluation of the 446 people that were excluded from the original airdrop for the reason of not finding their Slack/Discord membership information, 95 of these users were actually qualified to receive payment.
Please see the new tab in the airdrop sheet here, labeled Airdrop RECHECK. We are giving the community 48 hours to double-check this to verify that the entries are correct as re-checked. If there is an issue, please DM @SlowGrowth#2620 on Discord. After that process is complete, we will issue the promised 1k ITNS reconciliation payments to those missed originally and qualifying according to this form (see column should_be_paid).
Please see the new tab in the airdrop sheet here, labeled Airdrop RECHECK. We are giving the community 48 hours to double-check this to verify that the entries are correct as re-checked. If there is an issue, please DM @SlowGrowth#2620 on Discord. After that process is complete, we will issue the promised 1k ITNS reconciliation payments to those missed originally and qualifying according to this form (see column should_be_paid).
Looks okay this time. thanks.
Thanks for your patience and understanding everyone. The payments were sent in TXs:
Code:
5491faa0499b7c19465a384ec8718b17afa19200c91334fd8e620af2efb29d1f
2a39b519ae42e2e63c2880ad0c2d2bf88cc371e364312c953a092c20d8c24151
c7ed1df1178b4431fd3ecea6aa422dff806813396285f908ff476d4b68aef383
a2f71e1285319026bf041eb186486b8d852b88228acb0c8be3469ba867aec737
2a39b519ae42e2e63c2880ad0c2d2bf88cc371e364312c953a092c20d8c24151
c7ed1df1178b4431fd3ecea6aa422dff806813396285f908ff476d4b68aef383
a2f71e1285319026bf041eb186486b8d852b88228acb0c8be3469ba867aec737
Thanks. Received my share.
April 04, 2018, 12:12:52 AM
As mentioned in the main ITNS ANN thread (looks like SlowGrowth forgot to cross-post here), those that were missed for the fact that Slack display names were not properly read have been re-evaluated. According to our re-evaluation of the 446 people that were excluded from the original airdrop for the reason of not finding their Slack/Discord membership information, 95 of these users were actually qualified to receive payment.
Please see the new tab in the airdrop sheet here, labeled Airdrop RECHECK. We are giving the community 48 hours to double-check this to verify that the entries are correct as re-checked. If there is an issue, please DM @SlowGrowth#2620 on Discord. After that process is complete, we will issue the promised 1k ITNS reconciliation payments to those missed originally and qualifying according to this form (see column should_be_paid).
Please see the new tab in the airdrop sheet here, labeled Airdrop RECHECK. We are giving the community 48 hours to double-check this to verify that the entries are correct as re-checked. If there is an issue, please DM @SlowGrowth#2620 on Discord. After that process is complete, we will issue the promised 1k ITNS reconciliation payments to those missed originally and qualifying according to this form (see column should_be_paid).
Looks okay this time. thanks.
Thanks for your patience and understanding everyone. The payments were sent in TXs:
Code:
5491faa0499b7c19465a384ec8718b17afa19200c91334fd8e620af2efb29d1f
2a39b519ae42e2e63c2880ad0c2d2bf88cc371e364312c953a092c20d8c24151
c7ed1df1178b4431fd3ecea6aa422dff806813396285f908ff476d4b68aef383
a2f71e1285319026bf041eb186486b8d852b88228acb0c8be3469ba867aec737
2a39b519ae42e2e63c2880ad0c2d2bf88cc371e364312c953a092c20d8c24151
c7ed1df1178b4431fd3ecea6aa422dff806813396285f908ff476d4b68aef383
a2f71e1285319026bf041eb186486b8d852b88228acb0c8be3469ba867aec737
March 26, 2018, 04:16:40 PM
As mentioned in the main ITNS ANN thread (looks like SlowGrowth forgot to cross-post here), those that were missed for the fact that Slack display names were not properly read have been re-evaluated. According to our re-evaluation of the 446 people that were excluded from the original airdrop for the reason of not finding their Slack/Discord membership information, 95 of these users were actually qualified to receive payment.
Please see the new tab in the airdrop sheet here, labeled Airdrop RECHECK. We are giving the community 48 hours to double-check this to verify that the entries are correct as re-checked. If there is an issue, please DM @SlowGrowth#2620 on Discord. After that process is complete, we will issue the promised 1k ITNS reconciliation payments to those missed originally and qualifying according to this form (see column should_be_paid).
Please see the new tab in the airdrop sheet here, labeled Airdrop RECHECK. We are giving the community 48 hours to double-check this to verify that the entries are correct as re-checked. If there is an issue, please DM @SlowGrowth#2620 on Discord. After that process is complete, we will issue the promised 1k ITNS reconciliation payments to those missed originally and qualifying according to this form (see column should_be_paid).
Looks okay this time. thanks.
March 26, 2018, 08:54:44 AM
As mentioned in the main ITNS ANN thread (looks like SlowGrowth forgot to cross-post here), those that were missed for the fact that Slack display names were not properly read have been re-evaluated. According to our re-evaluation of the 446 people that were excluded from the original airdrop for the reason of not finding their Slack/Discord membership information, 95 of these users were actually qualified to receive payment.
Please see the new tab in the airdrop sheet here, labeled Airdrop RECHECK. We are giving the community 48 hours to double-check this to verify that the entries are correct as re-checked. If there is an issue, please DM @SlowGrowth#2620 on Discord. After that process is complete, we will issue the promised 1k ITNS reconciliation payments to those missed originally and qualifying according to this form (see column should_be_paid).
Please see the new tab in the airdrop sheet here, labeled Airdrop RECHECK. We are giving the community 48 hours to double-check this to verify that the entries are correct as re-checked. If there is an issue, please DM @SlowGrowth#2620 on Discord. After that process is complete, we will issue the promised 1k ITNS reconciliation payments to those missed originally and qualifying according to this form (see column should_be_paid).
Thank you so much for this. I was very much disappointed when I didn't receive the airdrop but now I've checked my ITNS wallet address and now the should_be_paid column says yes.
I'm so happy
Thanks
March 25, 2018, 08:21:40 PM
I think now half of the participants will have FB LIKE NOT VALIDATED 
Just as in the original assessment of airdrop participants, we did not exclude users that failed FB like validation since most people did not have proper privacy settings and we did not warn users ahead of time.
March 25, 2018, 02:01:59 PM
I think now half of the participants will have FB LIKE NOT VALIDATED
March 25, 2018, 10:55:46 AM
As mentioned in the main ITNS ANN thread (looks like SlowGrowth forgot to cross-post here), those that were missed for the fact that Slack display names were not properly read have been re-evaluated. According to our re-evaluation of the 446 people that were excluded from the original airdrop for the reason of not finding their Slack/Discord membership information, 95 of these users were actually qualified to receive payment.
Please see the new tab in the airdrop sheet here, labeled Airdrop RECHECK. We are giving the community 48 hours to double-check this to verify that the entries are correct as re-checked. If there is an issue, please DM @SlowGrowth#2620 on Discord. After that process is complete, we will issue the promised 1k ITNS reconciliation payments to those missed originally and qualifying according to this form (see column should_be_paid).
Please see the new tab in the airdrop sheet here, labeled Airdrop RECHECK. We are giving the community 48 hours to double-check this to verify that the entries are correct as re-checked. If there is an issue, please DM @SlowGrowth#2620 on Discord. After that process is complete, we will issue the promised 1k ITNS reconciliation payments to those missed originally and qualifying according to this form (see column should_be_paid).
March 06, 2018, 08:25:30 AM
Below is their reply on Slack. Totally disappointing all this and probably the worst experience from all the airdrops I have participated so far.
ThePigwee
@nicholasgr the airdrop has finalized and all rewards have been paid out. If you missed the airdrop, and it was for this reason, I sincerely apologize. Since payments have been distributed already based on a set amount, we will not be making any additional payouts. I know it’s upsetting, and I understand why you are upset. All I can say is I am sorry that you missed out.
ThePigwee
@nicholasgr the airdrop has finalized and all rewards have been paid out. If you missed the airdrop, and it was for this reason, I sincerely apologize. Since payments have been distributed already based on a set amount, we will not be making any additional payouts. I know it’s upsetting, and I understand why you are upset. All I can say is I am sorry that you missed out.
March 05, 2018, 06:50:17 PM
The team here is simply ignoring us hoping that the matter would settle in a few days. Here is what one of the team members posted on slack
Quote
ThePigwee [8:00 PM]
@Gandalf86 morning friend. We are a P2P decentralized VPN. Bitcoin Talk is going to be a little grumpy for the next two or so days I assume. No one enjoys missing out on an airdrop. All the rules were provided. Some people missed because they put in their Slack display name rather than their username
Do you think that the matter will settle if you don't reply on this thread?@Gandalf86 morning friend. We are a P2P decentralized VPN. Bitcoin Talk is going to be a little grumpy for the next two or so days I assume. No one enjoys missing out on an airdrop. All the rules were provided. Some people missed because they put in their Slack display name rather than their username
LOL! They are joking probably. We have complied with the rules. If they believe that the username is different than the display name and they dispute also what Slack officially says, they are invited to give specific and serious information. Otherwise, they are arbitrary withhold payments by violating the rules. And of course we will not let it go. If they believe that the case will be settled in a couple of days by ignoring this issue, they are simply mistaken.
March 05, 2018, 05:51:52 PM
The team here is simply ignoring us hoping that the matter would settle in a few days. Here is what one of the team members posted on slack
Quote
ThePigwee [8:00 PM]
@Gandalf86 morning friend. We are a P2P decentralized VPN. Bitcoin Talk is going to be a little grumpy for the next two or so days I assume. No one enjoys missing out on an airdrop. All the rules were provided. Some people missed because they put in their Slack display name rather than their username
Do you think that the matter will settle if you don't reply on this thread? @Gandalf86 morning friend. We are a P2P decentralized VPN. Bitcoin Talk is going to be a little grumpy for the next two or so days I assume. No one enjoys missing out on an airdrop. All the rules were provided. Some people missed because they put in their Slack display name rather than their username
March 05, 2018, 12:39:05 PM
By the way, what you have extracted as my "username" is nowhere in my profile (can not understand where did you find such information!!) and when you search in slack directory with the "username" you have extracted, it finds zero results. However if you search the directory with the display name (the @name I inserted in the airdrop form) which is the proper username in Slack nowadays, it gives the proper results. I can not write it clearer than this, i believe, so am really sorry if you guys cannot understand.
Sounds like a good (and the only fair) solution to me. The IntenseCoin guys needs to re-verify all those that haven't received an airdrop because of a Slack username issue and compare the submitted @username with what's shown in that "Slack Directory". I'm not on Slack, but I guess this is some form of follower list. Finally send out the missing airdrops.
I checked the airdrop form. It asked for your slack username. It specifically said username. Screenshot below. 565 people were paid and used the proper information requested by the form. To those that incorrectly filled out the form, I'm sorry, that stinks, but the payments were already made. 2.5million ITNS was allocated to this airdrop and was distributed among the properly validated submissions.
https://i.imgur.com/awkq5lR.png
Dear valiant, it looks like we have completed the Slack username correctly as requested by the form that you mention. However, it looks like that the IntenseCoin team is confused of what a Slack username is and the verification process that you followed was not correct. Please check my above messages with the official response from Slack along with the contents of their official webpage which defines that the username is actually the display name. Therefore, all of us that we have properly completed the form with our username/display name, we are looking forward for your necessary actions. Thanks.
March 05, 2018, 08:04:50 AM
this all shows the qualification of the team
March 05, 2018, 07:06:55 AM
they screwed up and they know it
They were asking for the Slack username, we provided our Slack username and they considered our participation invalid since they used an unknown username (no one knows how they found it and why they consider it as our username) to make the validations! wtf ?!
At the same time they did not disqualify those who did not like their facebook page despite the fact that the initial post of this thread with the Xmas airdrop is asking for same.After the response from Slack support showing without any doubt that the username is actually the display name, awaiting a better explanation from the IntenseCoin team.
March 05, 2018, 06:27:37 AM
they screwed up and they know it
March 05, 2018, 05:23:25 AM
Also I have contacted Slack. Please see below their response for your reference. I can send a copy of the original email if required. It was clearly a mistake to withhold payments due to the Slack username validation since apparently the team used wrong criteria to validate.
Hi Nicholas,
Thanks for getting in touch. Slack introduced display names last year which took the place of usernames. Display names allow users to choose what their teammates use to @mention them. Some users may still be able to view their old username here from before these changes were introduced. https://slack.com/account/settings#username
Please note however your display name is what users use to @mention you and I can see your display for your profile is@nicholasgr
I hope this information helps and if you have further questions please do let me know.
Hi Nicholas,
Thanks for getting in touch. Slack introduced display names last year which took the place of usernames. Display names allow users to choose what their teammates use to @mention them. Some users may still be able to view their old username here from before these changes were introduced. https://slack.com/account/settings#username
Please note however your display name is what users use to @mention you and I can see your display for your profile is@nicholasgr
I hope this information helps and if you have further questions please do let me know.
March 05, 2018, 04:51:36 AM
For the avoidance of any doubt whatsoever, please see below from the official website of Slack which says that the username is same with display name. So it is now even more clear that it was a mistake of the IntenseCoin team to disqualify a lot of people from their airdrop due to the Slack validation. Awaiting to follow the rules of their airdrop or otherwise explain us the reason that they do not follow same.
https://get.slack.help/hc/en-us/articles/115004846068-Slack-updates-and-changes
Quote
Display names and @mentions
Now that the Slack app is available in other languages, display names (formerly called usernames) can support spaces, capitalization, and non-Latin characters. To get someone's attention, type the @ symbol, then simply select a name from the list. Change your display name or dig into @mentions for more.
Unquote
https://get.slack.help/hc/en-us/articles/115004846068-Slack-updates-and-changes
Quote
Display names and @mentions
Now that the Slack app is available in other languages, display names (formerly called usernames) can support spaces, capitalization, and non-Latin characters. To get someone's attention, type the @ symbol, then simply select a name from the list. Change your display name or dig into @mentions for more.
Unquote
March 04, 2018, 06:34:15 AM
in any application, the user name is the user name. If I write the answer and the user's name is written in the chat, then this is the user's name. it's simple. wtf
What do I see in the end? Those who do not care for the user's name or do not write anything in the slack - he got the airdrop
The half a year of development and such elementary mistakes, we still have a long process. And probably these two thousand coins will not cost a dozen bucks
What do I see in the end? Those who do not care for the user's name or do not write anything in the slack - he got the airdrop
The half a year of development and such elementary mistakes, we still have a long process. And probably these two thousand coins will not cost a dozen bucks
I really cant understand them. What to say... I really want to hear where is this slack username located in my profile since i can not find
Same here, the team is not even ready to accept their faults and want to pin it on us. I posted multiple times on the forum to have some transparency regarding the airdrop. But no use, we are nobody.
And about being fair, is it fair that the people who don't care about intense, who will never look back at it, or don't even know that they received ITNS in the airdrop receive the ITNS in their wallet, and the ones really deserving don't just because of some silly mistake from the teams end? Can you please justify this @valiant1 @ThePigwee
The people achieved (this is an achievement!) to distribute 2.5 million coins to less than 600 people!!!
So they can not accept their fault now since they will have to pay for it. March 04, 2018, 06:26:07 AM
in any application, the user name is the user name. If I write the answer and the user's name is written in the chat, then this is the user's name. it's simple. wtf
What do I see in the end? Those who do not care for the user's name or do not write anything in the slack - he got the airdrop
The half a year of development and such elementary mistakes, we still have a long process. And probably these two thousand coins will not cost a dozen bucks
What do I see in the end? Those who do not care for the user's name or do not write anything in the slack - he got the airdrop
The half a year of development and such elementary mistakes, we still have a long process. And probably these two thousand coins will not cost a dozen bucks
I really cant understand them. What to say... I really want to hear where is this slack username located in my profile since i can not find
Same here, the team is not even ready to accept their faults and want to pin it on us. I posted multiple times on the forum to have some transparency regarding the airdrop. But no use, we are nobody.
And about being fair, is it fair that the people who don't care about intense, who will never look back at it, or don't even know that they received ITNS in the airdrop receive the ITNS in their wallet, and the ones really deserving don't just because of some silly mistake from the teams end? Can you please justify this @valiant1 @ThePigwee
Jump to: