LOL you have demonstrated loudly and clearly that you don't care tho so sorry, you can't ever use that argument again. Said the guy who created "chat" when "weather" wasn't interesting enough NO Chat is ephemeral. Posts are not. You can't put a chat on a post because then the discussion about it becomes time-sensitive and subject to "who is looking at it right this moment." I am under NDA, but I will say that one of the most stolid, staid and conservative platforms I use is rolling out a theme builder. It has absolutely nothing to do with the functionality of the software (which costs four to five figures depending on how it's configured) and everything to do with human factors engineering and the fact that we're all stuck in UIs all day long now.I suspect that if I made block or mute temporary, there would have been backlash.
I can see the value of the user-page blog thing, but it quickly becomes a whole other type of posting with all the formatting issues that brings.
I've considered that it might be interesting to give OPs the option to have chat or comments appended to their post and see what happens.
I don't think that's a fair assessment. I care more than you suspect, and likely more than I have let on. You might not like what I have done, but it's not because I don't care. IRC was useful but unreliable. Chat was a replacement for that. It was fairly easy to do because of its limited interaction with the application. Same with weather. Some things that seem like they should be easy are difficult, and some things that seem like they would be difficult are easy. This falls in the first category. I think chat on posts could be fun/interesting. It definitely wouldn't be fitting for all posts, but I can imagine that for some posts it might be more fitting. Chats on posts would probably be saved to the database.LOL you have demonstrated loudly and clearly that you don't care tho so sorry, you can't ever use that argument again.
Said the guy who created "chat" when "weather" wasn't interesting enough
That's your fault. Why? Why not let on? It doesn't benefit you in the slightest and dissolves your credibility and my empathy. You started this by saying, effectively, there's a whisper campaign of butthurt people who I won't mention and in order to soothe their savaged fee fees I'm going to impose a solution on everyone else that isn't up for discussion, isn't up for debate, starts now and will end when I feel like it and then the minute goobster goes look everyone you can no longer truly delete your posts how wondrous you jumped RIGHT the fuck in to say woo hoo let's end anonymity without any discussion whatsoever. It was only when a dozen of us rang alarm bells in your face that you waved off. You are behaving DANGEROUSLY. What you are doing is demonstrating that nobody here has any ownership stake but you, that the rules will change at any time and the only inputs that you will consider are the ones that interest you. I've been dealing with this for three months now - my kid's private school is doing the same "we really care, we just don't feel obligated to demonstrate it" bullshit and half their enrollment is threatening to leave. You're both making the same mistakes: you have given no thought whatsoever to user agency and you have felt no need to give anyone the impression that their input matters in the slightest. It's disempowering, alienating and off-putting in the extreme because what you're doing is communicating I'm only here for the people who agree with me. Classic coder mistake, and why non-coders hate coders: "hey it'd make life way better if you did this one simple thing" "yeah that thing's not actually simple I'm gonna do this other thing instead" "no one asked for that in fact it makes our life worse" "yeah but it's easier and I'll be able to tell our boss I solved your problem" "you aren't you're making my job harder" "tough shit you can't do my job so suck it." I have LIVED MY LIFE dealing with interfaces designed by UI experts and dealing with interfaces designed by coders. The choices are obvious and immediate and the long term effects are unavoidable. An interface that wraps around the code is universally terrible and will be adopted by the people who have to use the product while an interface that had code written for it may be less feature-rich but will be used by everyone. I used to design massive AV projects and half my goddamn budget was on the control system because you know what? If the History department can't even turn on the goddamn projector it won't matter if the lecture hall has 7.1 surround. Yeah you also thought a twelve hour waiting period in the "are you thoughtful" corner would be beneficial to the site. Let me be clear: I don't want this. I don't want this SO HARD. I would turn it off if I had the option, and if I didn't have the option, I wouldn't post. There is no "chat" section on any blog platform anywhere ever. "Then we can be the first!" no, candy corn doesn't go with zucchini either but guaranteed some schlub tried that somewhere and didn't write down the results because it was so immediately, obviously, verifiably terrible.I don't think that's a fair assessment.
I care more than you suspect, and likely more than I have let on.
Some things that seem like they should be easy are difficult, and some things that seem like they would be difficult are easy. This falls in the first category.
I think chat on posts could be fun/interesting.