The current usage model for the media server looks like:
select your media and add details (keep aliased? description?)
auth
???
call the api to get data about the image
build your own ui based off this data
There's two immediate problems.
data isn't stored permanently (is not "backed up" by git, unless, like me, you just upload them locally and then push to git, but then... what's the point of so much theater?)
it's kind of just painful to use.
Problem 1's solution could be to use a bucket to store media / data.
Problem 2 is a little more complicated. I think it would be to just explore different UI/UX, make sure we're always returning useful data, and perhaps add some documentation. Then maybe this could be useful to the public.
In addition to improving media hosting UX, I'd also like to add some support for links +/ web archives. Honestly something like vue might be good here. I'll probably split this off into a separate project at that point.
The current usage model for the media server looks like:
There's two immediate problems.
Problem 1's solution could be to use a bucket to store media / data. Problem 2 is a little more complicated. I think it would be to just explore different UI/UX, make sure we're always returning useful data, and perhaps add some documentation. Then maybe this could be useful to the public.
In addition to improving media hosting UX, I'd also like to add some support for links +/ web archives. Honestly something like vue might be good here. I'll probably split this off into a separate project at that point.