There are a few issue with publishing Debug LogIds.

The first is that most are very specific and, more often than not, don't mean much to anyone but the developers who are working on a specific issue. The next is that many are created for a specific need and are used once or twice, or on rare occasions when a particular issue arises. Finally, they should really only be used "as needed" or as instructed as some can impact disk space pretty quickly. If a server administrator is less experienced, activating a debug log can end up causing more issues if it's not used with express instructions from our tech support guys or from a dev. If we put them out there, someone may go "hey, I can just activate this debug log and send that along" not realizing that the log may grow very large, very quickly. 

And, while it could be said that we could post them with huge, red caveats about disk space, and only using them when instructed, etc. we all know that people gloss over that stuff most of the time.