I'm trying to wrap my head around the avatar data messages synchronet sends out. I think it's the base64 encoded bin of the avatar, followed
by
the user name associated with that avatar
OK, so I looked at the JavaScript code... it's not just base 64 it's compressed with lz string, and the md5 is a hash of the user's full name yes?
I have my system importing avatars from dove net, and I've written the exporting functions too, but am a bit to scared to actually export into
the SYNC_DATA channel in case there is an error.
So, I thought I'd practice in FSX_DAT.
so are you intending to reply to 'all' or is that another issue?
Hi,
I'm trying to wrap my head around the avatar data messages synchronet
sends out. I think it's the base64 encoded bin of the avatar, followed by the user name associated with that avatar
What's the md5: field? and why do not all avatar messages have it?
I guess it's some kind of checksum base64 encoded, but not sure what for?
Also, if I choose an avatar on one synchronet BBS, and it gets exported,
is that my avatar for all synchronet BBSes? or can I choose a different
one for each bbs i visit? If I do choose a different one on each bbs,
will the avatar show for messages from me from a particular bbs?
I suppose what I'm asking is if I were to import synchronet data
messages, do I take note of their origin and associate that avatar / username with a particular origin?
I'm trying to wrap my head around the avatar data messages synchronet sends out. I think it's the base64 encoded bin of the avatar, followed
by
the user name associated with that avatar
OK, so I looked at the JavaScript code... it's not just base 64 it's compressed with lz string, and the md5 is a hash of the user's full name yes?
I have my system importing avatars from dove net, and I've written the exporting functions too, but am a bit to scared to actually export into
the SYNC_DATA channel in case there is an error.
So, I thought I'd practice in FSX_DAT.
so are you intending to reply to 'all' or is that another issue?
It's an md5 sum of the user's real name, that keeps users' real names
more private while still allowing the successful lookup of their
avatar. Older versions of avatars.js didn't support the mapping of
avatar's to user's real names.
The avatar is mapped to the username *and* BBS, so the same username
posted from a different BBS won't necessarily be the same user and
thus not necessarily use the same avatar.
It's an md5 sum of the user's real name, that keeps users' real names more private while still allowing the successful lookup of their
avatar. Older versions of avatars.js didn't support the mapping of avatar's to user's real names.
Ah ok, I haven't been adding it to my exports, perhaps I should.
The avatar is mapped to the username *and* BBS, so the same username posted from a different BBS won't necessarily be the same user and
thus not necessarily use the same avatar.
That makes sense. Though at this stage I'm not sure how best to go about that, particularly for QWK networks.
Right now, what I've done is just take the most recent username / avatar mapping and update on the disk. So if some apam sends another avatar from another bbs it will overwrite mine - except locally.
It's not ideal, but if Talisman is displaying incorrect avatars, it's not going to hurt a Synchronet Setup.
Thanks for your help with this.
I store the name/md5->avatar mapping in a file that has the BBS-ID of
the source BBS in the filename (e.g. data/qnet/happylnd.avatars.ini).
I'm sure there are other ways do that (e.g. with a database).
Yeah, you'll probably want to change that behavior. :-)
I store the name/md5->avatar mapping in a file that has the BBS-ID of
the source BBS in the filename (e.g. data/qnet/happylnd.avatars.ini).
I'm sure there are other ways do that (e.g. with a database).
Ah ok
Yeah, you'll probably want to change that behavior. :-)
Yep, got stuck into it and figured out a way to do it. The downside is a
lot less messages have avatars now, for example before I had an avatar
for digital man it would work on messages you post in dovenet and fsxnet, now only dovenet (and I guess any other QWK net where your BBS name is VERT.)
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 30:44:18 |
Calls: | 141 |
Files: | 5,058 |
Messages: | 220,685 |