BitShares Forum
Main => General Discussion => Topic started by: ripplexiaoshan on January 27, 2015, 10:01:16 pm
-
If it changes frequently, then what's the meaning of having this? It will be very confusing, especially for all the established recipients, like some exchanges' accounts.
-
Robohashes are controlled by a 3rd party website.
They may update it whenever they want and they do not need to notify anyone.
EDIT: Furthermore robohashes are extremely unreliable way of verification and IMHO it shouldn't be used. It might even allow for easier scams.
-
Its open source it doesnt have to be 3rd party we can implement a local web service which will do the same thing and then we control wether it changes or not.
-
Decentralise the creation of images of robots ftw, it will revolutionise society. Secure life, liberty, and robot pictures.
:p
-
If it changes frequently, then what's the meaning of having this? It will be very confusing, especially for all the established recipients, like some exchanges' accounts.
Established participants with something to lose out of being impersonated hould spare 5mn to personalize their avatar.
-
I thought we already embedded the source code into bts client.. Not?
-
I thought we already embedded the source code into bts client.. Not?
I wanted to -- and even started working on it at one point -- but we ended up not doing this.
-
So everything was hitting this guys website? That list of delegates with robohashes.... generated off this website?
-
So everything was hitting this guys website? That list of delegates with robohashes.... generated off this website?
It seems to be true, by now.
-
So everything was hitting this guys website? That list of delegates with robohashes.... generated off this website?
It seems to be true, by now.
Yes, but it's a free service using CDNs to cache the robots so there's no issue with that imo. Maybe at a scale of hundreds of thousands of users we would put too much strain on them, but as it is I doubt they even noticed.
-
I thought we already embedded the source code into bts client.. Not?
I wanted to -- and even started working on it at one point -- but we ended up not doing this.
so which one will do it now?
-
NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO!!!!!!!!!!!!!!!!!!!!!!!!!
https://www.youtube.com/watch?v=hN-JpAyEPko
-
I like mine better now. +5%
-
We could just host the robohash script. I think that's the easiest thing to do provided there's already a good server to use.
-
What's the point of robot avatar anyway, the account name is already unique enough. Also this avatar apparently haven't stopped people from sending money to scam accounts such as "bter". I think it makes the client look childish and amateur tbh. It doesn't fit the overall theme of the client as a serious professional exchange.
-
What's the point of robot avatar anyway, the account name is already unique enough. Also this avatar apparently haven't stopped people from sending money to scam accounts such as "bter". I think it makes the client look childish and amateur tbh. It doesn't fit the overall theme of the client as a serious professional exchange.
This gave me an idea: it would be nice if the accounts could publish their own avatars on the blockchain, as part of the public info for the account (using wallet_account_update_registration). The client could then show this instead of the robohash. This wouldn't prevent scams, but at least it would allow people to choose their own avatar.
-
What's the point of robot avatar anyway, the account name is already unique enough. Also this avatar apparently haven't stopped people from sending money to scam accounts such as "bter". I think it makes the client look childish and amateur tbh. It doesn't fit the overall theme of the client as a serious professional exchange.
Few things would stop every scam. Most people who complain about the robots just simply don't understand the point of them.
A lot of it is simply resources but robot hashes are a particularly bad implementation. They have no cognitive relevance. There really is nothing that a brain can short cut into a script to store. I barely remember what my robothash looks like. I'm brown and have a grill .. or did. I know bm's was a red robot, but I couldn't tell it apart from any other red robot in a lineup.
I've heard multiple people say the robots are amatureish. I don't think they understand it is a security thing in general and just see it as giving people faces etc. So perhaps it would be worth considering the removal. You'd literally be better off taking 1000 images and combining 2 of them into a picture for a hash. So you have a walnut and a red sports car, or a frog and a rabbit side by side. More likely to remember something like that than minute differences in robohash. Not only that, people would be more familar with this type of thing from banking websites where they use a unique picture concept to try and mitigate phishing attacks which is related to what robohashes try to avoid. Instead people see it as some cutesy character.
-
What's the point of robot avatar anyway, the account name is already unique enough. Also this avatar apparently haven't stopped people from sending money to scam accounts such as "bter". I think it makes the client look childish and amateur tbh. It doesn't fit the overall theme of the client as a serious professional exchange.
This gave me an idea: it would be nice if the accounts could publish their own avatars on the blockchain, as part of the public info for the account (using wallet_account_update_registration). The client could then show this instead of the robohash. This wouldn't prevent scams, but at least it would allow people to choose their own avatar.
Then you have porn and questionable images.
And you have just helped people with scamming since they can just duplicate the images of others.
-
What's the point of robot avatar anyway, the account name is already unique enough. Also this avatar apparently haven't stopped people from sending money to scam accounts such as "bter". I think it makes the client look childish and amateur tbh. It doesn't fit the overall theme of the client as a serious professional exchange.
This gave me an idea: it would be nice if the accounts could publish their own avatars on the blockchain, as part of the public info for the account (using wallet_account_update_registration). The client could then show this instead of the robohash. This wouldn't prevent scams, but at least it would allow people to choose their own avatar.
Then you have porn and questionable images.
And you have just helped people with scamming since they can just duplicate the images of others.
Then what we probably need to solve this is a reputation system as what was envisioned by Keyhotee originally :)
-
Storing the avatar on the blockchain is out of the question.
Perhaps storing an URL of the avatar could be done ONLY if a significant fee in BTS is burned.
To avoid scams we can use a fast name visual similarity check. It should verify that each new account name is not similar to previously registered one.
If newly registered account name is similar to previously registered one => the new account cannot publish avatar unless that right is bought from the old account.
-
Storing the avatar on the blockchain is out of the question.
Perhaps storing an URL of the avatar could be done ONLY if a significant fee in BTS is burned.
To avoid scams we can use a fast name visual similarity check. It should verify that each new account name is not similar to previously registered one.
If newly registered account name is similar to previously registered one => the new account cannot publish avatar unless that right is bought from the old account.
This is way over-engineered. We need a simpler product, not going down rabbitholes like this.
Any publishing of pictures is bad. So you put a URL of the logo of a competitor and don't even try to have a similar name. People can not be allowed to put in images, it just opens up more social based attack vectors. The feature isn't needed if it requires extra features to counter-act the damage it does.
If there was open-sourced data with images + textual names they could be pulled into one big picture with something like imagemagic and then just extracted using canvas features in javascript. It gives an image that #1 doesn't look like it is trying to be a person/have a personality (whatever it is that people see as 'unprofessional'. It also works better than the robots as far as being able to remember them.
-
Then you have porn and questionable images.
We can already have questionable BTS account names (like racial slurs) why not questionable images too? The point is that if you want to self-censor to protect yourself from things you would rather not see, you should subscribe to a moderator/curator that marks certain content with appropriate flags so that your client can optionally hide/censor it and give you a simple/vague reason for why (unless you want to override it in specific cases).
And you have just helped people with scamming since they can just duplicate the images of others.
Yup, but I always (https://bitsharestalk.org/index.php?topic=9115.msg118191#msg118191) thought robohash / Safebots were a stupid and ineffective idea to begin with. I have already (https://bitsharestalk.org/index.php?topic=13747.msg179105#msg179105) described (https://bitsharestalk.org/index.php?topic=9414.msg122403#msg122403) the alternative (https://bitsharestalk.org/index.php?topic=9414.msg122433#msg122433) we should be using to protect against scams.
-
Then you have porn and questionable images.
We can already have questionable BTS account names (like racial slurs) why not questionable images too? The point is that if you want to self-censor to protect yourself from things you would rather not see, you should subscribe to a moderator/curator that marks certain content with appropriate flags so that your client can optionally hide/censor it and give you a simple/vague reason for why (unless you want to override it in specific cases).
Images are readily unintentionally consumed. Like I can have a wallet running on my desktop and if someone has some racial slur as an account and it pops up in the client it is not readily not seen unless someone reads all the text. Images are different. Basically trolling with pictures of big black dicks or whatever will be far worse than writing out "mrbigblackdick".
There is no need for a moderator, we just don't need to make what is a very minor problem into a possibly large one. Personally I've seen free speech forums pushed to the point of breaking and it was rarely because of the text causing problems. It was because joe who is browsing at work or has an uptight wife that couldn't stand having horribly nasty pictures show up randomly.
So thats the difference... I'm not sure why you'd even suggest an avatar moderator on accounts as I assume we both think self-selected avatars are a bad idea.
-
Then you have porn and questionable images.
We can already have questionable BTS account names (like racial slurs) why not questionable images too? The point is that if you want to self-censor to protect yourself from things you would rather not see, you should subscribe to a moderator/curator that marks certain content with appropriate flags so that your client can optionally hide/censor it and give you a simple/vague reason for why (unless you want to override it in specific cases).
Images are readily unintentionally consumed. Like I can have a wallet running on my desktop and if someone has some racial slur as an account and it pops up in the client it is not readily not seen unless someone reads all the text. Images are different. Basically trolling with pictures of big black dicks or whatever will be far worse than writing out "mrbigblackdick".
There is no need for a moderator, we just don't need to make what is a very minor problem into a possibly large one. Personally I've seen free speech forums pushed to the point of breaking and it was rarely because of the text causing problems. It was because joe who is browsing at work or has an uptight wife that couldn't stand having horribly nasty pictures show up randomly.
So thats the difference... I'm not sure why you'd even suggest an avatar moderator on accounts as I assume we both think self-selected avatars are a bad idea.
Yeah, I get there is a difference. And, I don't think it is a good idea for the client to show the avatars by default when browsing through a list of accounts in the client (or in bitsharesblocks.com). However, I think if you click on an account's page you should be able to click on an empty square to reveal the image that is linked to by that account. You should also be able to pin visibility of the avatar for that specific account if you want so that it does show up when casually browsing through your address book or other account lists or delegate lists in the client. That way you can see an up-to-date image of your contacts in your favorites / address book like you can with social networks.
-
My robot just switched back to "normal" ..
-
https://robohash.org/set_1/del0.cass?size=300x300
https://robohash.org/set_1/del0.cass?size=200x200
(https://robohash.org/set_1/del0.cass?size=300x300)
(https://robohash.org/set_1/del0.cass?size=200x200)
-
https://robohash.org/set_1/del0.cass?size=300x300
https://robohash.org/set_1/del0.cass?size=200x200
(https://robohash.org/set_1/del0.cass?size=300x300)
(https://robohash.org/set_1/del0.cass?size=200x200)
ya the real one is if you remove size