@MichaelMrozek Yeah, there are a few distinct groups complaining. And I certainly don't want to be associated with all of them. It's a giant mess of frustration due to various reasons.
I think Atwood's [Please Read the Comments](http://blog.codinghorror.com/please-read-the-comments/) has the perfect summary of the philosophy: "If your website is full of assholes, it's your fault."
Good news everyone, it was discussed on the Stack Exchange podcast, and we now have a site design. This should be rolling out as soon as we can get the design spec converted into workable CSS.
Completed layout:
If you have any comments before this is finalized, please let me know.
@MichaelMrozek Yeah... I was unmodded in a situation like that during a subreddit meltdown, back when I was active (several years ago). It wasn't great.
As the author of the work, I can offer a harsh (although biased) opinion on the matter.
The piece speaks to me, in that the singular turbine, whilst inhibiting flight, can both continue to fly, progressing through issues as Aviation.SE does.
Similarly, I feel as though the "Kneawwww" text also ...
Update:
STL synonym created instead of burnination: See stl
It appears that stl is "selectively" used for questions that utilize the Standard Template Library. However, this only applies to C++, and such code should already make use of the STL. Even if a C++ question doesn't utilize t...
For all that's wrong with Voat, they at least added an option for subcommunities to add reputation requirements for voting, and subcommunity-specific karma -- a baby step in the direction of the more segregated SE model.
In digestion, a bolus (from Latin bolus, "ball") is a mass of food that (with animals that can chew) has been chewed at the point of swallowing. Under normal circumstances, the bolus then travels down the esophagus to the stomach for digestion. Bolus has the same colour as the food that has been chewed by the person and is different from chyme. The bolus is a rolled up ball-like structure formed when the animal is about to swallow. Its pH is alkaline because of the presence of saliva.
== See also ==
Chyle
== References... ==
Good news everyone, it was discussed on the Stack Exchange podcast, and we now have a site design. This should be rolling out as soon as we can get the design spec converted into workable CSS.
Completed layout:
If you have any comments before this is finalized, please let me know.
@hichris123 Most of that criticism is just something I can't take seriously. If you look a bit closer it's just a user angry because their questions were downvoted or closed. There is a real issue with civility towards new users, but most of the complaints don't paint an accurate picture
@hichris123 We always talk about posts people make about our culture. A lot of times there's some truth to the posts and we can do something to help fix it, but this specific one is :|
SE is much more transparent than Reddit with moderation. The simple thing that deleted posts are visible to 10k users does a lot. And there is a dedicated meta for each site on SE
To be entirely honest, SE isn't listening (or maybe just responding) to a lot of stuff people request on meta. But most of that I can attribute to SE setting priorities, which is certainly understandable.
I propose we read posts like The decline of Stack Overflow with a critical eye and recognize that it's little more than a Google/copy/paste article designed to drive traffic to a blog.
Let's look closely at the examples illustrated in the article.
Here's that post today after being edited ext...
@Jaydles SE doesn't respond to a large part of meta feature requests. I'm reasonably sure that SE is reading far more of them that they're responding to, but I can't be sure.
When I remove the for loop I get an OutOfMemoryError. When I use for loop I don't get error. Can anyone help me in understanding this behavior?
public class JavaMemoryPuzzlePolite {
private final int dataSize = (int) (Runtime.getRuntime().maxMemory() * 0.6);
public void f() {
{
...
@MadScientist that is true (reading more than we respond to). Speaking for myself (which doesn't help much because I work on Careers, not the Q&A communities, these days), I would often read a request, then either make a note to discuss it with someone else internally or keep it open in a tab until I had time to write a thorough answer, and then just lose track of it.
@MadScientist Yeah, we read everything, at least in my case of [ios-app] and [android-app] I look at every question that comes in but I only respond when I have something factual to say
@MadScientist doesn't make up for the fact that we as a company should post responses to more than we do, but it is an honest explanation that it's just really hard to keep up on the Q&A requests
@MadScientist Feature requests have an additional problem in that as we grow, it's harder to come to agreement about how to (or even whether to) implement them.
@Vogel612 Yeah the markdown editor is a mess right now, changes are coming later this week hopefully. I spent the last month working on a completely new tablet UI (which is now out to beta and 20% of prod) but it's crashy :(
@JonEricson The hard part for us users is to know if our idea is ignored because it is crap, or just because nobody at SE that is responsible for it noticed it
There's a lot of variation in feature requests. There's "change the color of this button" which is easy. and then there's "build a whole new system to do thing X that might not even be a good idea philosophically speaking".
@AnnaLear I'm not blaming SE as much as I might appear right now. I understand that it's pretty difficult to appropriately respond to all the stuff we propose on meta. I still think that there's potential to improve on responding to stuff that seems reasonably popular, but maybe not something SE can implement just right now
Back when I was a mod and not a CM, I often thought "how hard can it be to respond to this? It would take a minute!". Then I got hired and I thought "Alright! Let's do this. This can't possibly take this much time." And then time passed and I went ... "Oh. I'm part of the problem now." :P
@AnnaLear I think the login improvements will be appreciated a lot. Especially by users like me that use a lot of sites from several devices, I really look forward to never seeing the damn "you've been logged in" banner ever again
The one thing I'm missing that I'm not sure will be implemented is having the top bar in chat rooms. That seems intentional, thought I'd still like to see notifications from chat directly
@MadScientist We have some plans to work on chat again and a UI redesign to make it suck less overall may be on the books. (I honestly don't know how far we're gonna go or where we're at with it right now.) It'd be nice if we could bolt the inbox on somewhere in there. We do have the technology.
Personally, I'd probably go even more towards a unified SE account, but I know that there's some heavy resistance to anything that looks like you've got an account on every SE site
My idea would be that you create an account with SE. And once you participated in any site, that site would be visible in your account without having to create an account. But I suspect too many people would object to that
@MadScientist The mobile apps do something similar to that. Not sure how much confirmation they go through when voting or anything, though.
With the new login in place, we'll be able to do something like "User clicks upvote. User sees pop-up along the lines of 'Do you want to join X Stack Exchange or just leave anonymous feedback?'"
The one thing that I probably would do is to simply hide all profiles from other sites that have no badges or posts at all on the site. I do tend to create that kind of account for flagging spam or stuff like that, but I never intend to particpate on the site
@MadScientist That could be an interesting UI option, but I don't think it's a good default for most people... especially as we launch sites on more controversial topics.
Folks get pretty protective of their profiles. I know before I worked here, I got a private beta invite for Sexuality... and I sure did create a sockpuppet for that one.
One of the harder parts of working here and evaluating feature requests is considering all the different types of users. A fair amount of time, in my experience, what I expect most people to do isn't what actually happens in practice. Turns out, I'm not a representative enough sample. :)
On that note... back to work.
People aren't gonna get accidentally logged out all by themselves, y'know.
@MadScientist Yeah, and out of those that are, there are a few different archetypes - people with multiple network accounts to prevent association, people who join new betas and then lose interest, people who are on two sites and they're crazy high rep there, etc. etc.
The one thing I've learned over time is that pretty much every issue is more complicated than I originally thought. If I would look back on my early meta posts, there are quite a few I wouldn't post in this form today
@MadScientist Oh to be young and innocent again. ;) Having said that, I still have faint hope that we might implement some variant of escalated chat moderation you proposed forever ago.
@AnnaLear That is one of the things I do see a bit different now, thought I have edited my post at some time. I still think this is necessary, but I also think a way around it is essential to avoid a clique of regular users abusing a chat room.
@MadScientist Yeah, it definitely needs more thought, but I think the core of the idea is really good and would alleviate some of the problems we currently have.