Board groups / query_see_board
I was just looking in to removing the membergroups column in boards. One solution is to add another table. I was thinking instead of another table, a permission 'can_see' in board_permissions.
Another possible permission would be can_ignore.
At the same time, change permission to char(30) instead of a varchar(). A couple of more bytes in the database, but faster lookups.
I am interested to know what Wedge did.
Re: Board groups / query_see_board
Reply #2 –
What usability issues did you discover?
Re: Board groups / query_see_board
Reply #4 –
More importantly, why is it so hard for you to do a little work yourself?
Hint: I said there were usability issues when it was a mod, the link for which I even provided for you to save you having to spend time searching for it. I assumed you'd be smart enough to put 2 and 2 together to make 4 and read the comments in the mod's thread, but clearly I overrated your abilities. This is why I'm naturally a dick to you.
Re: Board groups / query_see_board
Reply #6 –
I think doing that part makes sense as well
Re: Board groups / query_see_board
Reply #8 –
Dunno, I'm not a big fan of "private topics" in "common" boards... I find it hard to always have the doubt if a topic is accessible to someone or not, etc...
Privacy is privacy (well, not that what we can provide in a php script can be called privacy anyway) and should stay in another place I think.
Re: Board groups / query_see_board
Reply #9 –
Privacy concerns are valid at Facebook for instance, but if you clearly indicate somewhere a list of users who can read your stuff, then it's really not a problem anymore... ^^
Re: Board groups / query_see_board
Reply #10 –
Yeah, but I hate when I send someone a link and he answers me: "oh I can't read it, can you sum it up or send me the content of it?".
It already happens with normal boards, only think that before do anything I should think (again) "will the one I'm sending the link to be able to open that link?" would be a pain...