NXT :: descendant of Bitcoin - Updated Information

[chanc3r]

I guess one option would be for someone to create a site that will host all avatars.

http://gravatar.com ?

why can't you just specify an avatar url in an alias and put it in the client profile.

trying to store avatar data in the alias is a bit crazy and limiting.

and one site - how decentralized is that?

Once once client dev comes up with a good solution all the other client devs will copy it hopefully

[1714205224]

1714205224

[1714205224]

1714205224

[ferment]

Any consensus been reached on how to get an avatar that matches to an account? I know there was some talk about this some time ago.

What do you mean?

do u mean avatar on bitcointalk?

No, an avatar mapped somehow to a Nxt account ID. (to be used in messaging apps)

Couldn't we convert a small image to a base64 string and insert it as an alias transaction? The downside here is blockchain bloat.

That's not necessary, an URL is good enough.

However, the issue is how do we know which alias refers to the specific account avatar? If we use a special format, that can be squatted by others.

I guess one option would be for someone to create a site that will host all avatars. User sends AM to site account with avatar URL in it, and then it's possible to do site.com/3434343434.png to get that account's avatar - or a default one if not specified. But this is centralized.

Upload the avatar to an AM using FileReader.readAsDataURL() and the encoded data can work inline in HTML.

Then use an Alias with a URI like "nxtavatar:AM_TRANS_ID_HERE".

[NxtChg]

Yes, gravatar for account Ids.

I mean, why don't we just use it?

We can create a mail server and give users emails like "account@nxtmail.com" then clients can pull avatars from gravatar.

[wesleyh]

Yes, gravatar for account Ids.

I mean, why don't we just use it?

Isn't that tied to email addresses only?

[chanc3r]

Upload the avatar to an AM using FileReader.readAsDataURL() and the encoded data can work inline in HTML.

Then use an Alias with a URI like "nxtavatar:AM_TRANS_ID_HERE".

Prefer to store a link to the avatar which any client can pick up.
Expanding on this...
How about this - all accounts automatically own the alias <account number>
This alias is locked to the account.
You use this alias to store in URI format a hierarchy of parameters for the person who owns the account - this can be set and managed though the clients - one of these is the avatar.

[wesleyh]

Yes, gravatar for account Ids.

I mean, why don't we just use it?

We can create a mail server and give users emails like "account@nxtmail.com" then clients can pull avatars from gravatar.

Don't see a point in creating a mail server when we have AM.

[wesleyh]

Upload the avatar to an AM using FileReader.readAsDataURL() and the encoded data can work inline in HTML.

Then use an Alias with a URI like "nxtavatar:AM_TRANS_ID_HERE".

Prefer to store a link to the avatar which any client can pick up.
Expanding on this...
How about this - all accounts automatically own the alias <account number>
This alias is locked to the account.
You use this alias to store in URI format a hierarchy of parameters for the person who owns the account - this can be set and managed though the clients - one of these is the avatar.

Yes, this would be the solution - if that alias of account number was locked and only the account itself can own it, then we can do this. If it is squattable, then it isn't possible to do.

CFB, what are your thoughts?

[NxtChg]

Yes, gravatar for account Ids.

I mean, why don't we just use it?

We can create a mail server and give users emails like "account@nxtmail.com" then clients can pull avatars from gravatar.

Don't see a point in creating a mail server when we have AM.

Yeah, I guess it's better to store them on blockchain. Just need to figure out how to find them among all the messages in user account.

We need some sort of file system on top of AM, which will use AM as clusters and provide files.

[Mistafreeze]

Upload the avatar to an AM using FileReader.readAsDataURL() and the encoded data can work inline in HTML.

Then use an Alias with a URI like "nxtavatar:AM_TRANS_ID_HERE".

Prefer to store a link to the avatar which any client can pick up.
Expanding on this...
How about this - all accounts automatically own the alias <account number>
This alias is locked to the account.
You use this alias to store in URI format a hierarchy of parameters for the person who owns the account - this can be set and managed though the clients - one of these is the avatar.

I like it

[wesleyh]

Any consensus been reached on how to get an avatar that matches to an account? I know there was some talk about this some time ago.

What do you mean?

do u mean avatar on bitcointalk?

No, an avatar mapped somehow to a Nxt account ID. (to be used in messaging apps)

Couldn't we convert a small image to a base64 string and insert it as an alias transaction? The downside here is blockchain bloat.

That's not necessary, an URL is good enough.

However, the issue is how do we know which alias refers to the specific account avatar? If we use a special format, that can be squatted by others.

I guess one option would be for someone to create a site that will host all avatars. User sends AM to site account with avatar URL in it, and then it's possible to do site.com/3434343434.png to get that account's avatar - or a default one if not specified. But this is centralized.

Upload the avatar to an AM using FileReader.readAsDataURL() and the encoded data can work inline in HTML.

Then use an Alias with a URI like "nxtavatar:AM_TRANS_ID_HERE".

This is also a good possibility! We would have to go through all aliases a user owns though, but this should be 1 time only. Still prefer the other solution with locked account alias id's.

[ferment]

Upload the avatar to an AM using FileReader.readAsDataURL() and the encoded data can work inline in HTML.

Then use an Alias with a URI like "nxtavatar:AM_TRANS_ID_HERE".

Quoting myself... hah... Here's a better flow...

1. Nominate an account to act as the "avatar account". It's purpose is to receive AM and maybe define an alias to the account number.
2. Send an AM with the FileReader.readAsDataURL encoded image to the avatar account.
3. To find an avatar for an account look for the most recent transaction from the account to the avatar account.
4. Take encoded image and set to value of <img src="AM_DATA_HERE">. More on data urls
5. Rejoice.

* Avatars can be updated by sending a new AM to the avatar account.

nxt: 4915862015826193000

[l8orre]

I seem to be having issues with a few queries - eg:

http://holms.cloudapp.net:6874/nxt?&requestType=getAccountTransactionIds&timestamp=0&accountId=7126304194855053556

errorCode - 3
errorDescription - "account" not specified

Use "account" instead of "accountId".

Thanks, that did it! I think it slipped in when transferring the api from the wiki.

I also seem to have a problem with the deadline - docu says it should be in minutes. I get this reply for every request that has a deadline, sendMoney as well as placeOrder, etc ...

Do you see anything obviously wrong in the query below? Is maybe the 'REFTRANSACTION' to be dropped out of all queries? Thanks!

http://holms.cloudapp.net:6874/nxt?fee=1&secretPhrase=xxxxxxxxxxxxxx&requestType=sendMoney&amount=43&deadline=30&referencedTransaction=REFTRANSACTION&recipient=9998590259914237067

[Mistafreeze]

Any consensus been reached on how to get an avatar that matches to an account? I know there was some talk about this some time ago.

What do you mean?

do u mean avatar on bitcointalk?

No, an avatar mapped somehow to a Nxt account ID. (to be used in messaging apps)

Couldn't we convert a small image to a base64 string and insert it as an alias transaction? The downside here is blockchain bloat.

That's not necessary, an URL is good enough.

However, the issue is how do we know which alias refers to the specific account avatar? If we use a special format, that can be squatted by others.

I guess one option would be for someone to create a site that will host all avatars. User sends AM to site account with avatar URL in it, and then it's possible to do site.com/3434343434.png to get that account's avatar - or a default one if not specified. But this is centralized.

Upload the avatar to an AM using FileReader.readAsDataURL() and the encoded data can work inline in HTML.

Then use an Alias with a URI like "nxtavatar:AM_TRANS_ID_HERE".

This is also a good possibility! We would have to go through all aliases a user owns though, but this should be 1 time only. Still prefer the other solution with locked account alias id's.

With locked alias account id's, we open a whole new ability to have an actual profile to go along with an account. could be very useful down the road.

[wesleyh]

Upload the avatar to an AM using FileReader.readAsDataURL() and the encoded data can work inline in HTML.

Then use an Alias with a URI like "nxtavatar:AM_TRANS_ID_HERE".

Quoting myself... hah... Here's a better flow...

1. Nominate an account to act as the "avatar account". It's purpose is to receive AM and maybe define an alias to the account number.
2. Send an AM with the FileReader.readAsDataURL encoded image to the avatar account.
3. To find an avatar for an account look for the most recent transaction from the account to the avatar account.
4. Take encoded image and set to value of <img src="AM_DATA_HERE">. More on data urls
5. Rejoice.


nxt: 4915862015826193000

I don't think there is an api call to filter AM's where recipient = X and sender = Y, right? (this should be added)..

[chanc3r]

Upload the avatar to an AM using FileReader.readAsDataURL() and the encoded data can work inline in HTML.

Then use an Alias with a URI like "nxtavatar:AM_TRANS_ID_HERE".

Prefer to store a link to the avatar which any client can pick up.
Expanding on this...
How about this - all accounts automatically own the alias <account number>
This alias is locked to the account.
You use this alias to store in URI format a hierarchy of parameters for the person who owns the account - this can be set and managed though the clients - one of these is the avatar.

Yes, this would be the solution - if that alias of account number was locked and only the account itself can own it, then we can do this. If it is squattable, then it isn't possible to do.

CFB, what are your thoughts?

Well if <account number> is currently squattable you could always release a 'special' that is not available in the current code like @<account number> or pick a prefix string that no-one knows when you do the code update guys

[BloodyRookie]

@ NRS crypto algo bounty contestants:

Please, confirm that I should use the following files:

https://github.com/moadib/nxt_crypto_js/blob/master/crypto.js

https://github.com/gimer/curve25519nxt/blob/master/curve.js

https://github.com/Jaguar0625/JavaScriptNrs/blob/master/crypto_browser.js

https://github.com/BloodyRookie/nxtCrypto/blob/master/nxtCrypto.js

I will use only these files without the others from GIT repository.

Guys, u were talking about splitting the bounty to 4 parts. Did u come to a decision? If u r agree to split the bounty then I won't spend time on speedtests.

Well I wouldn't mind. We all spend a lot of time coding. I guess hoax and gimre don't mind too, but I haven't heard Jaguar's opinion yet.

[ferment]

Upload the avatar to an AM using FileReader.readAsDataURL() and the encoded data can work inline in HTML.

Then use an Alias with a URI like "nxtavatar:AM_TRANS_ID_HERE".

Quoting myself... hah... Here's a better flow...

1. Nominate an account to act as the "avatar account". It's purpose is to receive AM and maybe define an alias to the account number.
2. Send an AM with the FileReader.readAsDataURL encoded image to the avatar account.
3. To find an avatar for an account look for the most recent transaction from the account to the avatar account.
4. Take encoded image and set to value of <img src="AM_DATA_HERE">. More on data urls
5. Rejoice.


nxt: 4915862015826193000

I don't think there is an api call to filter AM's where recipient = X and sender = Y, right? (this should be added)..

Just call getAccountTransactionIDs for the account then loop and find the first one where recipient == avatar_account.

[wesleyh]

Upload the avatar to an AM using FileReader.readAsDataURL() and the encoded data can work inline in HTML.

Then use an Alias with a URI like "nxtavatar:AM_TRANS_ID_HERE".

Quoting myself... hah... Here's a better flow...

1. Nominate an account to act as the "avatar account". It's purpose is to receive AM and maybe define an alias to the account number.
2. Send an AM with the FileReader.readAsDataURL encoded image to the avatar account.
3. To find an avatar for an account look for the most recent transaction from the account to the avatar account.
4. Take encoded image and set to value of <img src="AM_DATA_HERE">. More on data urls
5. Rejoice.


nxt: 4915862015826193000

I don't think there is an api call to filter AM's where recipient = X and sender = Y, right? (this should be added)..

Just call getAccountTransactionIDs for the account then loop and find the first one where recipient == avatar_account.

Yes, I know this is how its done currently - but that's horribly inefficient.

[Come-from-Beyond]

Yes, this would be the solution - if that alias of account number was locked and only the account itself can own it, then we can do this. If it is squattable, then it isn't possible to do.

CFB, what are your thoughts?

Squatting is allowed. Let's find another way.

[ferment]

Upload the avatar to an AM using FileReader.readAsDataURL() and the encoded data can work inline in HTML.

Then use an Alias with a URI like "nxtavatar:AM_TRANS_ID_HERE".

Quoting myself... hah... Here's a better flow...

1. Nominate an account to act as the "avatar account". It's purpose is to receive AM and maybe define an alias to the account number.
2. Send an AM with the FileReader.readAsDataURL encoded image to the avatar account.
3. To find an avatar for an account look for the most recent transaction from the account to the avatar account.
4. Take encoded image and set to value of <img src="AM_DATA_HERE">. More on data urls
5. Rejoice.


nxt: 4915862015826193000

I don't think there is an api call to filter AM's where recipient = X and sender = Y, right? (this should be added)..

Just call getAccountTransactionIDs for the account then loop and find the first one where recipient == avatar_account.

Yes, I know this is how its done currently - but that's horribly inefficient.

You can limit the transactions with a timestamp - first to the date that NxtAvatars are introduced and then to last time an avatar was fetched. Transactions are now ordered so it should go quick.