DW Filter Mgmt: ? Needful to know facts
Nov. 2nd, 2012 11:21 pm![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
codeswitcher.livejournal.com posting in ![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png){kind=small}
cs_hackerary1) What are the per-user maximums for:
a) Number of grantees?
b) Number of filters?
c) Number of tags?
d) Char length of usernames?
e) Char length of tags?
2) What are the three levels of NSFWness or whatever that feature does, "anything (show all content)", "safe or non-explicit", and "safe for work only"? Wait, is this the same thing as "Age Restrictions"? (I think I may be about to get offended. Is there controversy about this?)
a) Does it map to a setting per journal or per comment?
b) "Ratings" right? Is there a ratings icon? (Otherwise I'll just use the letter "R".)
c) Is there some abbreviated version of those lengthy descriptions? I need some concision in this interface.
d) There is no "NSFW only" option? Nobody wants porn filters?
3) "AND" tag subscriptions? Really? Are there people using this? Because it adds a lot of difficulty (to say nothing of confusing the poor end users) for what I suspect is not going to be a popular feature. I'm ready to be wrong, of course. But it would be great if we didn't have to support this.
4) I'm contemplating the extant filter management tool, and a current limitation is that you cannot subscribe to different tags at different Ratings levels for the same person. So, if you want to sub to Rhonda's snarry and wincest filters, but: (1) her snarry stuff is really explicit -- NSFW -- but it's no problem for you because it's pretty 'nilla, while (2) her roy/roy alternates between really dark h/c but not always, and you don't want to read the torture but do want to tune in when it's not triggery. So you want to sub to rhonda:snarry:all but rhonda:roy/roy:safeforworkonly.
The interface approach I'm thinking of would support doing this, kinda by accident. However, will the back end? Because if the back end won't support that, then I should do something to add that constraint to the front end.
Put another way: the Rating filter seems to modify the user, not the tags.
Which is a round-about way to say, I think I'd better have some idea how subscriptions are represented in the db. I was imagining a three-column hash table, user_id/tag_id/rating_id. Except maybe I'm imaging user_id/[array of tag_ids]/rating_id to handle the "AND" case. But in any event, with all three foreign key fields being many-to-many. Which on further contemplation is not what's happening?
5) What characters are not allowed in tags and might be used as delimiters?
a) Number of grantees?
b) Number of filters?
c) Number of tags?
d) Char length of usernames?
e) Char length of tags?
2) What are the three levels of NSFWness or whatever that feature does, "anything (show all content)", "safe or non-explicit", and "safe for work only"? Wait, is this the same thing as "Age Restrictions"? (I think I may be about to get offended. Is there controversy about this?)
a) Does it map to a setting per journal or per comment?
b) "Ratings" right? Is there a ratings icon? (Otherwise I'll just use the letter "R".)
c) Is there some abbreviated version of those lengthy descriptions? I need some concision in this interface.
d) There is no "NSFW only" option? Nobody wants porn filters?
3) "AND" tag subscriptions? Really? Are there people using this? Because it adds a lot of difficulty (to say nothing of confusing the poor end users) for what I suspect is not going to be a popular feature. I'm ready to be wrong, of course. But it would be great if we didn't have to support this.
4) I'm contemplating the extant filter management tool, and a current limitation is that you cannot subscribe to different tags at different Ratings levels for the same person. So, if you want to sub to Rhonda's snarry and wincest filters, but: (1) her snarry stuff is really explicit -- NSFW -- but it's no problem for you because it's pretty 'nilla, while (2) her roy/roy alternates between really dark h/c but not always, and you don't want to read the torture but do want to tune in when it's not triggery. So you want to sub to rhonda:snarry:all but rhonda:roy/roy:safeforworkonly.
The interface approach I'm thinking of would support doing this, kinda by accident. However, will the back end? Because if the back end won't support that, then I should do something to add that constraint to the front end.
Put another way: the Rating filter seems to modify the user, not the tags.
Which is a round-about way to say, I think I'd better have some idea how subscriptions are represented in the db. I was imagining a three-column hash table, user_id/tag_id/rating_id. Except maybe I'm imaging user_id/[array of tag_ids]/rating_id to handle the "AND" case. But in any event, with all three foreign key fields being many-to-many. Which on further contemplation is not what's happening?
5) What characters are not allowed in tags and might be used as delimiters?
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
Date: 2012-11-04 01:19 am (UTC)no subject
Date: 2012-11-04 01:19 am (UTC)1b. Limit of access filters: 60
Limit of subscription filters: Currently none, asking for ballparks, but I imagine it could get up to 60 to match access, we'll see.
1c. Number of tags: 1000 free, 1500 paid, 2000 premium
1d. Username length: 25 characters maximum.
1e. Char length of tags: 40 characters maximum.
no subject
Date: 2012-11-04 01:22 am (UTC)I'd have to do some investigating to see if people use this, but I can think of possible use cases: for instance, a roleplay community where each post is tagged by the characters involved, and you want a filter that contains both of the characters.
no subject
Date: 2012-11-04 01:23 am (UTC)So basically, entries can have three states:
* No warning
* NSFW
* 18+
There...really isn't that much controversy to speak of, other than needing to reduce the number of click throughs to get to content in some very annoying use cases. They are explained here. So:
* anything -- would include entries whether or not they had a warning
* safe or non-explicit -- includes unmarked and NSFW entries
* safe for work only -- includes only unmarked entries
no subject
Date: 2012-11-04 01:24 am (UTC)I think possibilities could be:
* anything
* non-explicit
* unmarked
no subject
Date: 2012-11-04 01:24 am (UTC)We only have icons for the individual warning levels. Using the letter R is fine. I think this from the Silk set (which we already use) might also be appropriate despite its name but I'm on the fence:
http://en.wikipedia.org/wiki/File:Page_white_error.png
Another possible icon would be an exclamation mark in a circle--easy to make in a vector program.
no subject
Date: 2012-11-04 01:25 am (UTC)Not yet, but they totally do want the option, that is bug 1868
Just isn't there yet. In which case additional abbreviations for states could be:
* marked
* explicit
* NSFW
no subject
Date: 2012-11-04 06:17 pm (UTC)I think you mean per entry--in my testing, it only respects the warning on the entry. A journal marked 18+ with an unmarked entry will still show entries from that journal in a filter where only unmarked entries were allowed. I feel like this is a bug, but on the otherhand if somebody put a 18+ journal but only allowed NSFW or lower, then they'd never see any posts from that person they put onto their filter, hrm. Will have to bring this up somewhere.