Cool. I was thinking like meara, that I'd want to be able to unblock a single post, but Jon and Amych's explanation works for me.
'Unleashed'
Buffistas Building a Better Board
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
There is nothing ooky about process or flow, grumble, but otherwise I'm with amych.
There is nothing ooky about process or flow
Nothing at all ooky about the, uh, process. I was just looking over it before I hit "post" and said, "ooh, buzzword!".
amych needs to revocabularize her paradigm.
Good of you to give amych pushback on that, Jon.
it could be designed so that "unblock-a-post" would be an add-on. That is, let's get the block-a-poster-and-all-his/her-posts done first. Adding the unblock-a-single-post wouldn't require us to undo what had already been done.
In terms of my usage patterns at TT, I don't see the value in separating them. I block user X, and I'm good with that, except that someone reacts to post #1557, and I want to go and see what that post says. I do not want to unblock the poster, I just want to know what this particular kerfuffle is. I don't want to set up a scenario where I have re-blocking overhead to do after I click to read that post.
I think we need to sunset our outdated terminology and repurpose ourselves.
I see ita's potential usage.
In the blinvisible message, I'd prefer there not be a link, what with the eye-catching and all. At that point, I've already taken the action. Perhaps a link to the putative relevant faq portion elsewhere?
I think the best-of-breed experience we're blue-skying here will be extensible into new vocabularistic domains by EOY.
Fire bad. Tree pretty.