Went through the process with the Support chat bot. At this stage, there's nothing to be done but wait. I'll try to post Notes on occasion and see what resolves.
Update #3: I'm in contact with Substack and they are working to address the issue. Mills Baker has been a great help already. It seems something was broken in a recent update and they're working to fix it.
I worked for a few years at a tech start up and this experience feels a lot like that one. I had a knack for finding broken things to the point I was a minor folk hero with the programmers.
In any case, all seems to be in order at this stage. I'll update this space with anything interesting. Presuming all goes well, I'll do a post mortem on Sunday.
Thanks to Mills and his Substack Musketeers the issue has been fixed. As it likely affected more people than me I greatly appreciate their time and attention on this matter. I live to serve, ultimately.
I'll skip the boring stuff to simply say it looks like we caught a bug on Thanksgiving night. Probably something got broken in an update. At the end of the day, shit happens what can you do?
It appears the issue is ongoing. From my perspective, it's like I'm stuck in some kind of slow mode.
Mills Baker, one of the good people of Substack, just posted about the issue. Seems like something did just break. In any case, I'm extremely grateful for Mills and the work he does.
Makes you realize the folks working here are a class act.
Well, if what Substack said today is correct, and I have no basis for saying otherwise, then my suspicions are unfounded. At least in this case. I still distrust the corporate newbies and will keep an eye on them.
Yours is not the first instance of this lately; there's been a fair rash of folks getting suspended and a handful of bans in the last couple of weeks, all with no notice, no warning, and no follow-up explanation. Something foul is afoot on Substack.
I agree. The other day my publication sent me notices that there was stuff needing moderated. When I looked, there was nothing there. Not sure if related but an important data point.
Update:
Went through the process with the Support chat bot. At this stage, there's nothing to be done but wait. I'll try to post Notes on occasion and see what resolves.
Thanks for your patience, everyone!
Update #3: I'm in contact with Substack and they are working to address the issue. Mills Baker has been a great help already. It seems something was broken in a recent update and they're working to fix it.
I worked for a few years at a tech start up and this experience feels a lot like that one. I had a knack for finding broken things to the point I was a minor folk hero with the programmers.
In any case, all seems to be in order at this stage. I'll update this space with anything interesting. Presuming all goes well, I'll do a post mortem on Sunday.
Update FINAL:
Thanks to Mills and his Substack Musketeers the issue has been fixed. As it likely affected more people than me I greatly appreciate their time and attention on this matter. I live to serve, ultimately.
I'll skip the boring stuff to simply say it looks like we caught a bug on Thanksgiving night. Probably something got broken in an update. At the end of the day, shit happens what can you do?
All is well, folks. As you were.
Update #2
It appears the issue is ongoing. From my perspective, it's like I'm stuck in some kind of slow mode.
Mills Baker, one of the good people of Substack, just posted about the issue. Seems like something did just break. In any case, I'm extremely grateful for Mills and the work he does.
Makes you realize the folks working here are a class act.
The greatest notes warrior to ever do it. And now you’re on leave. The notes feed suffers without you, Phisto
I'm not surprised this would go hand in hand with the influx of corporate journos arriving and colonizing the place.
I'm not willing to draw that link yet, but it has certainly crossed my mind.
Well, if what Substack said today is correct, and I have no basis for saying otherwise, then my suspicions are unfounded. At least in this case. I still distrust the corporate newbies and will keep an eye on them.
Seems a bit odd to receive a ban from Notes without getting a heads up. Do keep us informed.
That's what I thought, too.
I don't mind a ban per se. I mean, maybe I screwed up. It's possible.
Knowing what's going on seems like basic courtesy.
It’s those bloody Russians at it again, I’m telling ya!
This is BS.
Phisto, please, you can't do this to me. I literally cannot survive without seeing you post every five minutes 😭
Umm , we're not buddies or anything, but I really hope it isn't a ban .
You doing genuinely ban - worthy stuff ?
Buuuuulll sheeeet.
No offense, but you aren't political pornhub or anything.
So , yeah , that would suck.
Totally not fair .
On a serious note, how/who do we speak up to?
Restack this piece and ping Best, McKenzie, and Mills?
Mills strikes me as best.
I only recognize Mill’s name on sight, so I am not able to tag the others out of hundreds. Done though!
Donde est Franco?
Yours is not the first instance of this lately; there's been a fair rash of folks getting suspended and a handful of bans in the last couple of weeks, all with no notice, no warning, and no follow-up explanation. Something foul is afoot on Substack.
I agree. The other day my publication sent me notices that there was stuff needing moderated. When I looked, there was nothing there. Not sure if related but an important data point.
Please keep us in the loop! 🙏🏻🇺🇸
Substack is a corporation with a CEO that is seriously enchanted by the idea of getting the pot.
That absolutely rules out being a good person.
Banning without explanation? That's just missing code.
It will get steadily worse from here.
I'll will defiantly let you know when, I land in a better place.
~
I know you give these guys tons of credit, and it saddens me that your lesson on these people lie in front of you. You are one of the best.
~
Peace friend.
Check my latest update. Looking good.
Things like this should not happen.
Simply because this will give rise to more guessing than there was an actual problem.