Discussion about this post

User's avatar
Larry Druhall's avatar

Please see the Addendums above for updates as this dynamic situation unfolds.

PLEASE CONSIDER CONTACTING SUBSTACK SUPPORT ABOUT THIS COMMENT REPLY PLACEMENT ISSUE

Dear Solution Seeking readers and subscribers. The comment thread errors are being reported across the articles of Solution Seeking and might be escalating.

Please consider contacting Substack Support about this issue and sharing with a wider audience? So far Substack Support has not addressed this issue for me. Maybe your contact will help? Here is one way of contacting Substack Support. There may be other ways.

Thank you.

https://support.substack.com/hc/en-us/requests/new

<END OF EMAIL TO SUBSTACK SUPPORT>

Expand full comment
Larry Druhall's avatar

If this is malicious, the malicious programming might not be done at Substack? For a hypothetical example...

POSSIBLE EXPLANATION FOR SUBSTACK SOLUTION SEEKING COMMENT THREAD PLACEMENT ERRORS

If Substack is using third party company to handle it's comments, the possibly malicious programming may originate at the third party programming site. In that case, Substack itself might not have anything to do with the programming, which may have been given to Substack as part of a program update. For example, let's conjecture that Substack is using Company A for its web server processes that handle and store comments. Company A decides to sabotage Solution Seeking Substack comments. Company A puts the malicious comment thread programming into one of it's automatic updates and sends the update to Substack. Suddenly Solution Seeking is dealing with a program that maliciously places some comment threads in the wrong place. Substack itself has no knowledge of this, is busy, and has not yet really addressed our issue with any information and/or solutions to this problem.

But, in my opinion, we should find and use another platform to do our comments? This is complex enough without having to deal with this kind of issue. It should have been addressed by Substack support and solved by now?

Expand full comment
22 more comments...

No posts