mirror of
https://github.com/lldap/lldap.git
synced 2026-04-25 08:15:52 +03:00
[GH-ISSUE #401] Support other file formats for avatar #154
Labels
No labels
backend
blocked
bug
cleanup
dependencies
docker
documentation
duplicate
enhancement
enhancement
frontend
github_actions
good first issue
help wanted
help wanted
integration
invalid
ldap
pull-request
question
rust
rust
tests
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/lldap-lldap#154
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @pixelrazor on GitHub (Dec 30, 2022).
Original GitHub issue: https://github.com/lldap/lldap/issues/401
Avatars can only be a JPEG currently. It would be nice if other formats (ex. PNG) were supported
@nitnelave commented on GitHub (Jan 24, 2023):
The ldap attribute is jpegPhoto, I'm not sure how other file formats are handled. If someone knows more about it, I'm all ears.
@pixelrazor commented on GitHub (Jan 24, 2023):
My thinking here was the file upload can accept other formats, then convert to jpeg. No storage changes needed or anything, just FE changes
@nitnelave commented on GitHub (Jan 24, 2023):
There are several problems with that:
and so on.
Those problems definitely have solutions, but that's not what I want to do with my time/code.
@pixelrazor commented on GitHub (Mar 21, 2023):
Quic kreading into it - the image crate seems like the perfect solution. the only thing we'd need to sort out is the output jpeg quality.
this answer and the link for testing in it seems to suggest we lean towards 80-90. I'd almost suggest lower since it's for avatars, but i don't know if other applications might try to display it in a larger area? Either way, 90 would at least be a good start as is has minimal loss and has the largest impact on size
@nitnelave commented on GitHub (Mar 23, 2023):
Sure, we can look into that, if you feel like implementing it. The conversion should be done client-side, though.