Signed-off-by: Anirudh Oppiliappan anirudh@tangled.org
Monorepo for Tangled
tangled.org
appview/pages: upload and render avatar #894
open
opened by
STACK 6
0
comments
round
#1
0
comments
round
#2
0
comments
round
#2
3/3
0
comments
round
#2
3/3
0
comments
round
#2
3/3
0
comments
round
#2
expand 1 commit
hide 1 commit
appview/pages: upload and render avatar
Signed-off-by: Anirudh Oppiliappan <anirudh@tangled.org>
expand 1 commit
hide 1 commit
appview/pages: upload and render avatar
Signed-off-by: Anirudh Oppiliappan <anirudh@tangled.org>
profileAvatarUrl is only used where models.Profile is available, is the uploaded profile picture not rendered across the board? (the previous PR in the stack implies otherwise, in which case, why do we need any special logic for avatar URLs on the appview?)
it exists to construct the blob url to to fetch from the pds. the avatar service merely checks if a blob url has been provided (if not, fallback to bsky). i could clean this up though, i didn't particularly like it myself.
Labels
None yet.
assignee
None yet.
Participants
2
profileAvatarUrlis only used wheremodels.Profileis available, is the uploaded profile picture not rendered across the board? (the previous PR in the stack implies otherwise, in which case, why do we need any special logic for avatar URLs on the appview?)identProfileAvatarUrlandAvatarUrl(the signature calculation logic is duplicated)