-
Welcome to the Chevereto User Community!
Here, users from all over the world come together to learn, share, and collaborate on everything related to Chevereto. It's a place to exchange ideas, ask questions, and help improve the software.
Please keep in mind:
- This community is user-driven. Always be polite and respectful to others.
- Support development by purchasing a Chevereto license, which also gives you priority support.
- Go further by joining the Community Subscription for even faster response times and to help sustain this space
Use same image if duplicated
- Thread starter Thanos92
- Start date
Thanks for your suggestion.
I think that what Flickr does is a bad practice that adds complexity to the system in the form of manage authority and permission over a single image for n+1 of users. What bothers me is that is just to save space, which is the cheapest asset in the whole thing.
Not because Flickr does something it means it is meant to be follow, I don't want to work on that. However, V4 is modular. If you ask directly to me I will answer based on my experience, but other devs may be interested.
I think that what Flickr does is a bad practice that adds complexity to the system in the form of manage authority and permission over a single image for n+1 of users. What bothers me is that is just to save space, which is the cheapest asset in the whole thing.
Not because Flickr does something it means it is meant to be follow, I don't want to work on that. However, V4 is modular. If you ask directly to me I will answer based on my experience, but other devs may be interested.