.

NiceGuy35 said:
- Converting the favorites list to a precreated set that all users have by default named favorites, that is accessed by clicking the "favorites", like currently. Clicking the favorite/unfavorite button on a post will then add/remove the post to the favorites set, in stead of the ambiguous "favorites list".

No. A set would a pain to have to navigate each time, I prefer it as it is, a public list of images right there. Seriously, the point of favorites is to show your support. If you don't want to show it, why are you trying to show it?

Furrin_Gok said:
... Seriously, the point of favorites is to show your support. If you don't want to show it, why are you trying to show it?

.

Furrin_Gok said:
No. A set would a pain to have to navigate each time ...

.

A quick and alternate way to keep your "favorites" private is to just upvote them and view it as a set by searching "votedup:<username>". This will only work when you're logged in though, but it will be for your eyes only (with the exception of site staff).

However, if you intend to use the voting system normally, then a faster and easier way to add posts into sets is needed.

TheGreatWolfgang said:
A quick and alternate way to keep your "favorites" private is to just upvote them and view it as a set by searching "votedup:<username>". This will only work when you're logged in though, but it will be for your eyes only (with the exception of site staff).

However, if you intend to use the voting system normally, then a faster and easier way to add posts into sets is needed.

.

Pixiv:
When you bookmark a post, you have to select "public" (default) or "private".
I'd prefer two "Favorite" buttons.

This comes with some more complicated semantic because it means having to store either a per user status, or a per favorite status and then checking them when displaying the each post page. An investigation into how much impact this has on page load time would need to be done. it also interacts heavily with the search system. further complicating that system. All of the systems surrounding the favorites system have been set up to work as though the information is and should be displayed publicly.

Votes used to have a loophole, but were not publicly displayed in a list all over the site, which made the task much easier.

This is not an acceptance, just a note about things I need to do if this becomes a thing.

KiraNoot said:
This comes with some more complicated semantic because it means having to store either a per user status, or a per favorite status and then checking them when displaying the each post page. An investigation into how much impact this has on page load time would need to be done. it also interacts heavily with the search system. further complicating that system. All of the systems surrounding the favorites system have been set up to work as though the information is and should be displayed publicly.

Votes used to have a loophole, but were not publicly displayed in a list all over the site, which made the task much easier.

This is not an acceptance, just a note about things I need to do if this becomes a thing.

.