10
Just to show that this has a real-world impact: I've lost track of the number of blog posts, reddit comments, etc I've seen claiming that OpenGL no longer works as of macOS Mojave!
Since OpenGL was indeed deprecated in macOS Mojave, the source of this misunderstanding is relatively obvious.
7
Well, we have users from all over the world for which English is the second or even third language they learned. Expecting proper use of words in all cases is probably asking a lot.
This doesn’t mean that proper use isn‘t important, it even helps everybody interested in improving their vocabulary. So if you see posts which would be more understandable with ...
7
I do tend to hide the link behind the page title, but I preface it thus
Apple KB - Use your iPad as a second display for your Mac with Sidecar
One thing I also do - this has been tested over time - is remove the 'location code' entirely, so rather than
https://support.apple.com/en-us/HT210380
or even
https://support.apple.com/kb/HT210380
I will reduce it ...
5
You can file a complaint by clicking on the "Contact" link at the bottom of the main page.
5
I am a heavy proponent of not hiding the link so I author my articles always to show the URL and KB and will append a quick summary or copy the title based on how pretty I feel that link should be.
I will almost never do the second where the KB is invisible when reading. The “descriptive” I prioritize is knowing the Apple link / KB and not the narrative ...
5
For me, the 'authority' of the link is important, and I'm more likely to accept information from a support.apple URL than 'hot.osx.skillz.biz'.
While that info can be gleaned from a mouse-over, having it visible, in some format, is my preference.
4
I tend to “prettify” links instead of having just the raw URL and this goes for not just Apple Support Documents, but articles, papers, etc. But, there are occasions where the raw URL is necessary.
Some Examples
Ask Different: See the existing question/answer Where is the list of canonical questions stored for Ask Different?
Apple Support: I have a ...
4
I think beta should be burninated as it’s a meta tag. Beta hardware, beta software, which software all beg the question.
I strongly prefer beta seed program for questions about that service. In reality, macOS or iOS should be the tag and the beta status and version should be in the body, not the tags. Just like you need to be specific about what version of ...
2
I would suspect that the vast majority of “depreciate” being used in place of “deprecate” are innocent typos. On more than a few occasions, I had to correct my phone’s autocorrect selection with that specific word choice. So, a simple fix via edit should suffiice.
However, regarding the word “removed,” this should be done with a some due diligence. I ...
2
By all means, change the word choice and let the moderation queue judge. Personally I would hesitate before bulk replacing deprecated with removed.
I agree that depreciate is likely to be mistakenly used instead of deprecate. The former is more frequently used in English language and may be being suggested by auto-correction tools.
Apple's use of "...
2
Thanks for you concern! The example you reference is a relatively new scheme; there are only two hits, both on your question today. Stack Overflow has nine hits, and I've checked a few and they all work.
However, the old scheme (e.g. https://forums.developer.apple.com/message/143196) has a lot more hits; over 450 across the network, 9 of them on Ask ...
2
I agree - if you’re sure you want to escalate - contacting the stack employees is an avenue to review any action here. Whether it’s moderators like you (you can access moderation tools due to reputation), elected moderators - going outside the community is always available.
I will link to this overall question on how to question moderator abuse:
What ...
1
If safe, I request we merge the tags beta and beta-seed-program into one tag named beta.
The question should include the usual details about what beta program, build number, etc. This will make it easier for people to follow or ignore and should help enforce consistency.
1
One of the primary goals of the SE platform was for it to become a searchable hub for maintained canonical information. What does this mean? In a post published several years after StackExchange launched, one of its co-founders, Joel Spolsky set out the group's shared vision:
It’s not just a Q&A platform: it’s also a place where you can publish things ...
1
This site focusses on finding solutions to practical problems. The three existing questions, while being broad, all ask a specific question about differences between models.
OTOH your question is rather broad and basically asks for a general overview of the differences between the currently known models. This wasn't work very well in a Q&A setup (are you ...
1
For the users without sufficient reputation to see the exact wording of why why this was closed see below for the exact text:
Questions must demonstrate a reasonable amount of research & understanding of the problem being solved. Please edit to either a) clearly describe your problem and the research done so far to solve it or b) include attempted ...
1
Very good question - the hiding of custom close reason seems like either a decision that should be reviewed or we should agitate for changing the threshold - I can see no reason why we shouldn’t let a user like you see precisely why the vote to close was cast.
Since they are not widely visible, first the reasons chosen seem appropriate to me, so I won’t be ...
1
Looks like we’ll maintain the current status. We can always act later if needed.
Only top voted, non community-wiki answers of a minimum length are eligible
