Subj : Avatar Data Messages
To   : apam
From : Digital Man
Date : Sun Nov 14 2021 18:50:12

  Re: Avatar Data Messages
  By: apam to Digital Man on Mon Nov 15 2021 11:12 am

 >  > 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.

It helps with Avatar supprot in networks/conferences that may require real names without revealing the BBS's users' real names unnecessarily.

 >  > 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.

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).

 > 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.

Yeah, you'll probably want to change that behavior. :-)

 > 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.

Sure, no problem.
-- 
                                            digital man

Breaking Bad quote #9:
"Cheesedick" - I know that one [word]. How about that? - Hank
Norco, CA WX: 76.4øF, 31.0% humidity, 3 mph NNE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.14-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.