Skip to main content
Became Hot Meta Post
added 3 characters in body
Source Link
Dalija Prasnikar Mod
  • 28.3k
  • 11
  • 79
  • 110

I was browsing Azure collective articles and I found an article posted by a user (Microsoft Azure Employee) who was not the author of the article.

The real author, also a Microsoft employee, was credited as the author, but the article didn't link to the original post, but rather the author's LinkedIn account.

Now, it is possible that MS has employees dedicated to posting around content that other MS employees write and from their perspective this is fine.

But, on Stack Overflow we expect that people who write posts are their authors, not that the whole thing is written by someone else. Also linking to the LinkedIn account is too much like "self" promotion that is also not appropriate.

Self-Help Document to handling Errors due to deprecation of Legacy TLS protocols

Is this article following SO rules?

If not, what is the appropriate course of action, since they cannot be flagged?

I was browsing Azure collective articles and I found article posted by a user (Microsoft Azure Employee) who was not the author of the article.

The real author, also a Microsoft employee, was credited as the author, but the article didn't link to the original post, but rather the author's LinkedIn account.

Now, it is possible that MS has employees dedicated to posting around content that other MS employees write and from their perspective this is fine.

But, on Stack Overflow we expect that people who write posts are their authors, not that the whole thing is written by someone else. Also linking to the LinkedIn account is too much like "self" promotion that is also not appropriate.

Self-Help Document to handling Errors due to deprecation of Legacy TLS protocols

Is this article following SO rules?

If not, what is the appropriate course of action, since they cannot be flagged?

I was browsing Azure collective articles and I found an article posted by a user (Microsoft Azure Employee) who was not the author of the article.

The real author, also a Microsoft employee, was credited as the author, but the article didn't link to the original post, but rather the author's LinkedIn account.

Now, it is possible that MS has employees dedicated to posting around content that other MS employees write and from their perspective this is fine.

But, on Stack Overflow we expect that people who write posts are their authors, not that the whole thing is written by someone else. Also linking to the LinkedIn account is too much like "self" promotion that is also not appropriate.

Self-Help Document to handling Errors due to deprecation of Legacy TLS protocols

Is this article following SO rules?

If not, what is the appropriate course of action, since they cannot be flagged?

Active reading [<https://www.youtube.com/watch?v=1Dax90QyXgI&t=17m54s>].
Source Link
Peter Mortensen
  • 31.3k
  • 4
  • 22
  • 14

I was browsing Azure collective articles and I found article posted by a user (Microsoft Azure Employee) thatwho was not the author of the article.

RealThe real author, also a Microsoft employee, was credited as the author, but the article didn't linkedlink to the original post, but rather the author's LinkedIn account.

Now, it is possible that MS has employees dedicated to posting around content that other MS employees write and from their perspective this is fine.

But, on Stack Overflow we expect that people who write posts are their authors, not that the whole thing is written by someone else. Also linking to the LinkedIn account is too much like "self" promotion that is also not appropriate.

Self-Help Document to handling Errors due to deprecation of Legacy TLS protocols

Is this article following SO rules?

If not, what is the appropriate course of action, since they cannot be flagged?

I was browsing Azure collective articles and I found article posted by user (Microsoft Azure Employee) that was not the author of the article.

Real author, also Microsoft employee, was credited as author, but article didn't linked to original post but rather author's LinkedIn account.

Now, it is possible that MS has employees dedicated to posting around content that other MS employees write and from their perspective this is fine.

But, on Stack Overflow we expect that people who write posts are their authors, not that the whole thing is written by someone else. Also linking to the LinkedIn account is too much like "self" promotion that is also not appropriate.

Self-Help Document to handling Errors due to deprecation of Legacy TLS protocols

Is this article following SO rules?

If not, what is appropriate course of action, since they cannot be flagged?

I was browsing Azure collective articles and I found article posted by a user (Microsoft Azure Employee) who was not the author of the article.

The real author, also a Microsoft employee, was credited as the author, but the article didn't link to the original post, but rather the author's LinkedIn account.

Now, it is possible that MS has employees dedicated to posting around content that other MS employees write and from their perspective this is fine.

But, on Stack Overflow we expect that people who write posts are their authors, not that the whole thing is written by someone else. Also linking to the LinkedIn account is too much like "self" promotion that is also not appropriate.

Self-Help Document to handling Errors due to deprecation of Legacy TLS protocols

Is this article following SO rules?

If not, what is the appropriate course of action, since they cannot be flagged?

Source Link
Dalija Prasnikar Mod
  • 28.3k
  • 11
  • 79
  • 110

Collective article written by one person and posted by another

I was browsing Azure collective articles and I found article posted by user (Microsoft Azure Employee) that was not the author of the article.

Real author, also Microsoft employee, was credited as author, but article didn't linked to original post but rather author's LinkedIn account.

Now, it is possible that MS has employees dedicated to posting around content that other MS employees write and from their perspective this is fine.

But, on Stack Overflow we expect that people who write posts are their authors, not that the whole thing is written by someone else. Also linking to the LinkedIn account is too much like "self" promotion that is also not appropriate.

Self-Help Document to handling Errors due to deprecation of Legacy TLS protocols

Is this article following SO rules?

If not, what is appropriate course of action, since they cannot be flagged?