Signed-off-by: Anirudh Oppiliappan anirudh@tangled.org
+40
appview/pages/funcmap.go
+1
-1
appview/pages/templates/layouts/profilebase.html
+44
appview/pages/templates/user/fragments/editAvatar.html
+17
-3
appview/pages/templates/user/fragments/profileCard.html
+4
-2
appview/pages/templates/user/settings/emails.html
+4
-2
appview/pages/templates/user/settings/keys.html
History
7 rounds
2 comments
1 commit
expand
collapse
Signed-off-by: Anirudh Oppiliappan <anirudh@tangled.org>
3/3 success
expand
collapse
expand 0 comments
1 commit
expand
collapse
Signed-off-by: Anirudh Oppiliappan <anirudh@tangled.org>
3/3 success
expand
collapse
expand 0 comments
1 commit
expand
collapse
Signed-off-by: Anirudh Oppiliappan <anirudh@tangled.org>
3/3 success
expand
collapse
expand 0 comments
1 commit
expand
collapse
Signed-off-by: Anirudh Oppiliappan <anirudh@tangled.org>
3/3 success
expand
collapse
expand 0 comments
1 commit
expand
collapse
Signed-off-by: Anirudh Oppiliappan <anirudh@tangled.org>
expand 0 comments
1 commit
expand
collapse
Signed-off-by: Anirudh Oppiliappan <anirudh@tangled.org>
expand 2 comments
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.
1 commit
expand
collapse
Signed-off-by: Anirudh Oppiliappan <anirudh@tangled.org>
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)