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.
Recently, many of his responses to comments at the linked article were being dumped onto the bottom of the page of comments, basically out of sight. In some cases, threads were splitting apart inappropriately, with responses (or even just a single response out of many others still nested properly within the thread itself) either thrown to the very bottom or hanging out elsewhere where they don't belong.
I watched, live, as one of these bollixed up threads suddenly shifted from the very bottom of the page all the way to the top.
This is ridiculous, as it is rendering the commenting experience utterly pointless.
Great. Thank you. Let's see where this goes. There are many possibilities. One is that my request to Substack Support got ignored or attached to another request that has been solved. I may make another request but that may backfire. We now have a record of this in the comments, perhaps, maybe only temporarily. I will now make a "Save To PDF" time/date stamped archive to what appears to me as the total comment trail for this article. Thanks again.
We shall see how this goes. I programmed big tree node projects. And there is a good chance that this is nefarious. I am eager to see if they ever provide an explanation of how this type of thing is possible and a solution. They claim they are busy and that too is questionable to me. I have opened tickets with them before and got much better response than now. There are simply too many things pointing to it probably being nefarious for me to ignore. Google got people hooked and then turned evil. Similar things happened at Facebook, YouTube, etc. Is this just the first warning signs of it also happening at Substack. What do you think?
Do you mean that you had trouble getting back onto Gab? For me, Gab was easy to get into. If you had problems getting onto Gab, are they things that also might limit others? If so, what is a better alternative suggestion?
Thank you for this valuable suggestion. I am studying it. Is it for us? Is it just for video oriented backup or does it back up all the text and the comments? Does it also automatically expand comment trails, expand AI shortened comments to their actual full length, and store the complete comment trails? Etc.? I hope others will look into this and weigh in on the discussion. Thanks again.
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?
Can we solve this by adapting to the situation and developing a protocol for how we post comments that works around the sporadic Substack errors? Please offer suggestions.
NEW SUBSTACK SOLUTION SEEKING COMMENT SORTING ISSUE?
There is now another new issue with the Substack comments. Substack gives three sort methods:
1. Top First
2. New First
3. Chronological
Up until now, these appeared to work. Now they do not appear to work. I am tired, sleep deprivation, so it would be helpful if others could please try sorting these comments and reply to this comment (no guarantee where the reply might end up) and share what happens for you when you sort these comments by the three options.
To make it worse, I just tried sorting again and it seemed to work alright. So, sometimes the sort method works as expected, sometimes it doesn't?
The more people who can become involved, the better.
I have had severe problems with Substack since Friday 17th Feb.
I can't edit things. I have written to the ZenDesk to alert them to the problems I am having - I also am not receiving notifications when people comment on my posts or answer me in others' posts. My posts are often delayed from publishing, waiting in draft for days at a time! It is driving me up the wall tbh. Still no help from ZenDesk and I have emailed twice.
As documented in Solution Seeking Substack articles, we have experienced similar things here. It looks like it, and other things, have succeeded in getting this Solution Seeking attempt seriously off track. So far.
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>
Done!
Publication link: https://solutionseeking.substack.com/
Subject: AI/software interference with proper nesting of comment threads
Description:
This is becoming a big problem for this author's substack.
First noticed on "Did World War 1 End Due To Military Mutinies And People's Revolutions?" https://solutionseeking.substack.com/p/did-world-war-1-end-due-to-military but is also showing up with the comments to other posts by this author on his substack.
Recently, many of his responses to comments at the linked article were being dumped onto the bottom of the page of comments, basically out of sight. In some cases, threads were splitting apart inappropriately, with responses (or even just a single response out of many others still nested properly within the thread itself) either thrown to the very bottom or hanging out elsewhere where they don't belong.
I watched, live, as one of these bollixed up threads suddenly shifted from the very bottom of the page all the way to the top.
This is ridiculous, as it is rendering the commenting experience utterly pointless.
Great. Thank you. Let's see where this goes. There are many possibilities. One is that my request to Substack Support got ignored or attached to another request that has been solved. I may make another request but that may backfire. We now have a record of this in the comments, perhaps, maybe only temporarily. I will now make a "Save To PDF" time/date stamped archive to what appears to me as the total comment trail for this article. Thanks again.
I noticed the errors and was worried. Glad someone is on this. No worries.
Thanks for the information. Did you notice the errors on the Solution Seeking Substack, somewhere else, or both?
Not on the Solution Seeking Substack. Just general errors. Doing some triage to see if it was different on different devices...
Please consider contacting Substack support as per the pinned comment and addendum just published. Thank you.
The confusion matters. A lot. Hopefully Larry they can fix this .
If not, gab?
That been hard for this guy to get back on to. But i do hope it can go well, anywhere.
We shall see how this goes. I programmed big tree node projects. And there is a good chance that this is nefarious. I am eager to see if they ever provide an explanation of how this type of thing is possible and a solution. They claim they are busy and that too is questionable to me. I have opened tickets with them before and got much better response than now. There are simply too many things pointing to it probably being nefarious for me to ignore. Google got people hooked and then turned evil. Similar things happened at Facebook, YouTube, etc. Is this just the first warning signs of it also happening at Substack. What do you think?
Do you mean that you had trouble getting back onto Gab? For me, Gab was easy to get into. If you had problems getting onto Gab, are they things that also might limit others? If so, what is a better alternative suggestion?
Its just a case of gab seeing a used email address again. Happens occasionally. Another weird thing in a weird tech world
Please consider contacting Substack support as per the pinned comment and addendum just published. Thank you.
I need the how to. Never had a ticket with the moderator(s) b4
You can probably do a better job of it than I have. I have failed so far. Maybe you, or others will find a way of having more success than I have had?
One way is to go to this URL.
https://support.substack.com/hc/en-us/requests/new
And then maybe reference the following Substack article that describes the issue while putting your own spin in it:
https://solutionseeking.substack.com/p/challenging-suspicious-substack-errors
Then, maybe after making the request to Substack, tell us what happened and how it went, and offer us feedback and advice?
https://open.substack.com/pub/corbettreport/p/contentsafe-solutionswatch?utm_source=share&utm_medium=android
Posted the above link about a platform called Content Safe. Obviously there are many experiencing a need for back-up platforms.
Thank you for this valuable suggestion. I am studying it. Is it for us? Is it just for video oriented backup or does it back up all the text and the comments? Does it also automatically expand comment trails, expand AI shortened comments to their actual full length, and store the complete comment trails? Etc.? I hope others will look into this and weigh in on the discussion. Thanks again.
Please consider contacting Substack support as per the pinned comment and addendum just published. Thank you.
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?
Can we solve this by adapting to the situation and developing a protocol for how we post comments that works around the sporadic Substack errors? Please offer suggestions.
That is useful information. Thank you.
NEW SUBSTACK SOLUTION SEEKING COMMENT SORTING ISSUE?
There is now another new issue with the Substack comments. Substack gives three sort methods:
1. Top First
2. New First
3. Chronological
Up until now, these appeared to work. Now they do not appear to work. I am tired, sleep deprivation, so it would be helpful if others could please try sorting these comments and reply to this comment (no guarantee where the reply might end up) and share what happens for you when you sort these comments by the three options.
To make it worse, I just tried sorting again and it seemed to work alright. So, sometimes the sort method works as expected, sometimes it doesn't?
The more people who can become involved, the better.
Thank you.
I have had severe problems with Substack since Friday 17th Feb.
I can't edit things. I have written to the ZenDesk to alert them to the problems I am having - I also am not receiving notifications when people comment on my posts or answer me in others' posts. My posts are often delayed from publishing, waiting in draft for days at a time! It is driving me up the wall tbh. Still no help from ZenDesk and I have emailed twice.
As documented in Solution Seeking Substack articles, we have experienced similar things here. It looks like it, and other things, have succeeded in getting this Solution Seeking attempt seriously off track. So far.