On this question, I added definition. Is that a tag we should have?
The summary would be something like:
Definitions of common aviation terms for reference by those new to the industry
Or something to that effect
If you have 2000 or more rep, you can see the most edited posts. Some of the posts have been edited upto 20 times, by the OP only. What's the logic behind doing this?
I don't have any problem with it. Just curious to know!
Area 51 metrics suggest that we should have over 90% traffic from search engines. Now, suppose that you are a user, who is not associated with Aviation.SE in anyway. You search for something like "How is an aircraft tracked in sky?"
Since Aviation.SE has one of the best SEO ratings, our results ...
This question got me thinking this. As there are passengers to commercial aviation, the same is the relation of bombs to bombers. So, should we consider such questions about the artillery on-topic as well?
Artillery is very much why defense-aviation and bomber prosper!
@FreeMan I'm surprised nobody'd asked it before. I had to talk to 2 instructors and a mechanic to get to the point where I figured I understood the differences "well enough" so I was happy to write it down for the next curious soul :)
(the mechanic was the one who pointed out that there are "non-sensitive" altimeters with Kollsman windows so you can't always rely on that. "Three pointers and a Kollsman window" seems to be a good indicator though)
In this answer reference was made to "sensitive" and "non-sensitive" altimeters.
What is the definition of each, what are the differences, and why would one be used in preference to the other?
And why isn't it called an "insensitive" altimeter?
And if anyone knows what TSO (if any) covers "non-sensitive" altimeters I'd love to know. (It might be in C10b but I'm not spending 15 bucks for a copy of the TSO to find out. I'm a cheap bastard. :P)
@DanHulme I've seen non-sensitive ones in "classic" planes (like cubs) around here, but even those usually when the altimeter dies they pop in a sensitive one because the shops have those on the shelf.
I've never seen one like the white-faced one I found the picture of (where the face of the instrument turns with the knob) in person - THAT would freak me out.
@FreeMan The sensitive altimeter tells you it's OK, everyone makes bad landings every now and then, you'll do better next time.
The non-sensitive altimeter calls you an asshole and tells all the other instruments what a lousy pilot you are :)
@BretCopeland I think we should take a semester off to bum around Europe, maybe date a nice French model and do regretable things while drunk off our collective ass on wine.... What, it's not like college graduation?!
@JayCarr Might want to express what you agree with via a comment somewhere. The only part which seems to be controversial is when privilege levels should be raised.
I wish there were some way to make that a "super featured" post on the main page...maybe with flashing lights and such so people would be sure to see it ;)
@BretCopeland the privilege level thing is tricky. I think it may need to be finer-grained than a "Beta / Graduated" switch. Definitely should be independent of design though.
@voretaq7 I'd actually agree with that sentiment. But I figure if they push it back to "when you have a site design" we can always talk more about making things finer grained.
Hence the "throwing all possible support behind the proposed solution"
I like the idea of giving people a heads up "privilege levels are going up in 30 days" gives people the ability who are on the verge of losing something they want to scramble for more rep before it disappears.
@BretCopeland easier to flip, harder to modify (knob could be a simple multiplier for "fully graduated" numbers - but yeah it would require a code change to put in a knob so probably not happening any time soon :)
Mostly I just want to have someone who is familiar with the site and it's needs controlling the "knob". I'm not a fan of just moving privledge requirements around because some other arbitrary goal has been achieved. I think the mods should just crank them up when it feels like the right time.
@BretCopeland I don't want to confused the issue at the moment... Maybe someone can be brave and post the idea on Meta after the discussion on this has died down.
@JayCarr that would require every site to have a SE employee moderator - there are lots where there just aren't many employees interested in the field.
(though it would be nice if Stack could afford to hire an employee to basically be their representative on each site :)
It's a prudent move, that place is just ridiculous and uninformative. Whoever thought a bunch of volunteers could answer code questions well was deluding themselves ;)
I still approve, I just figured it would be better to just star the comment... Anyway, out of curiosity, are all devs at SE giving moderator privileges?
There are some implicit privileges employees get though, such as mod-like powers on any meta site (even without a diamond), and being able to see deleted stuff even if you don't meet the rep requirements.
It's like the review queues on SF: I could clean them out but that's such a soul-crushing task there's only so long you can do it before you want to just bludgeon people with a wrench while shouting "HAVE YOU READ THE GODDAMN MANUAL?!" :)
2
and then your wrench is all dirty and you have to go buy a new one.
I'm not saying people wouldn't lose anything, but the most important privilege for making the site work is probably close votes, and that only goes up to 3k.
I guess I only need around 4k for that. Going is just getting slower these days, I'm kind of out of questions.
Which is funny, because you'd think I'd now know all the answers but...rather I just sit around and read answers to questions from people much smarter (or at least more esoteric) than myself.