BM hashing EOS ID's from shared data?
Was about to add a ban on a player reported by another server, but noticed we got a (I believe) hashed EOS ID when viewing the profile. If that hash is selected as an identifier and the ban is applied, the ban updates it to show the full EOS ID. See attached for a player profile we only have shared data on and thus showing the hashed ID, but as soon as a ban is placed the full ID becomes available, albeit only inside the ban itself.
Is there any real reason for this, or would it be possible to simply share the full ID to make sharing information easier between communities? ❤️
Solution:Jump to solution
And yes, we're aware that EOS IDs as a category are currently missing from data sharing. Will get that fixed
17 Replies
That could be a permission thing, you the ORG Owner?
Cause I don't show hashed.
Not the org owner, but have all the perms. As said its only for players that we have shared data on, but it resolves the full ID once you apply a ban.
It's more of an annoyance, as the full ID is still accessible, it might as well be there to begin with. 
Would make sharing ban info a lot easier.
@Hordicus Sorry for ping, but any chance you could clarify on this? As the data is already there it's just an unnecessary hurdle when it comes to sharing bans with other communities.
Would make sharing ban info a lot easier.
@Hordicus Sorry for ping, but any chance you could clarify on this? As the data is already there it's just an unnecessary hurdle when it comes to sharing bans with other communities.I don't see us modifying that. The sharing organization chose to hash it. Even if it has to be revealed for a ban I don't see why we'd otherwise undermine their wishes
Wait, there’s a setting to hash identifiers with data sharing?
What Meeps said, I'm not seeing an option to hash EOS ID's? 
I suspect if it's not selected you'll see it hashed
Though, I don't see EOSID as an option here to not hash
Hm... I changed our data sharing to you, check how https://www.battlemetrics.com/rcon/players/1160946905 shows up, not getting any identifiers from your org on that profile so just have to toggle it and see if it changes.
it may be because I see the player, but don't have any history with them
as in I only see it as identifiers from other data sharing agreements
Oh nevermind, tired me mistook EGS ID for EOS. 
lol
The box for the identifier has to be ticked in order for the shared identifier to not be hashed
Solution
And yes, we're aware that EOS IDs as a category are currently missing from data sharing. Will get that fixed
Thank you very much for confirming! 