• Welcome to the Chevereto user community!

    Here users from all over the world gather around to learn the latest about Chevereto and contribute with ideas to improve the software.

    Please keep in mind:

    • 😌 This community is user driven. Be polite with other users.
    • 👉 Is required to purchase a Chevereto license to participate in this community (doesn't apply to Pre-sales).
    • 💸 Purchase a Pro Subscription to get access to active software support and faster ticket response times.

Features deprecate for V4 (old topic)

Status
Not open for further replies.
Not sure about personal mode being removed but the rest looks good!
This mode should be delivered by a specialized user interface, not by adding conditions to the existing system
To deliver personal mode using the same interface for multiple users is counter productive. Two interfaces doing something different should be indeed two different systems, not the same.
 
Mixed content flagging SFW/NSFW

This system works by individually flagging each image as SFW/NSFW and this feature also affects the user interface as in any given listing the experience will vary depending on how many images are flagged and the visitor configuration for displaying these contents. This also means a cache problem as for every listing the contents to be listed vary per peer.

I believe that it will be better to create explicit NSFW sections, just like old video stores with restricted adult sections and whatnot, imagine the misery of having "Finding Nemo" next to a blurred copy of "Sexual Slaves".

Stuff like show/hide NSFW content setting under user profile will be still there. The change is that there won't be anymore albums, categories or tags holding mixed NSFW and SFW at the same time. An Album/Category/Tag will hold either only SFW or only NSFW content, there won't be context mixing anymore in this regard, there won't be individual image flagging.
 
Listings with mixed privacy

If you go to explore, search or pretty much any given listing, you may encounter that the system enables to list content aware of the private content if you have access to it. This may look as a neat feature, but is very expensive to carry specially with larger collections. Problem is that each user ask the database for a different list so imagine the load of an album with 20,000 pictures and the impact of just a couple of users listing contents.

Even with cache, the problem is that the listing job is too expensive if each user requires its own version of it. This is very similar to the effect of having NSFW flagging everywhere, it compromises the listing performance. Fortunately, we can get rid of this by simply stop making mixed listings and having a place for the public, a place for the private.
 
Dear all,

This topic has outdated information, it was posted when I did a bad planning trying to provide a drop-in replacement for V3. That was before, the older plans. The process will be now progressive, none of the announced stuff will be deprecated right-away and all versioning organization will be published on GitHub for a better understanding.

I'm sorry for the confusion this may have caused.
 
Status
Not open for further replies.
Back
Top