175 Comments
тна Return to thread

Weird substack behavior

Expand full comment

For a second I thought you meant all the people who are cashing in on the trend for being "heterodox" opinionators.

Expand full comment

On the other hand Ashley Feinberg's substack will be worth whatever she charges in the future. She found ANOTHER secret twitter/instagram account yesterday - this time Jamie Dimon's. (She's also found Josh Duggar's Ashley Madison account, Seb Gorka's Amazon wishlist, James Comey's Twitter/Instagram, DTJ's hunting forum posts and Pete Buttegieg's wikipedia editing)

Expand full comment

You must be referencing something about which I am completely unaware.

Expand full comment
Comment deleted
Apr 29, 2021
Comment deleted
Expand full comment

ЁЯТ▓ЁЯТ▓ЁЯТ▓

Expand full comment

The controversy over this kind of baffles me. I don't understand why I need to care one way or the other.

Expand full comment

Noticed some double posting for some reason.

Expand full comment

I've seen this since the beginning. And it must all be local because all replies show up in both double posts.

Expand full comment

Has anyone else seen this? Sometimes I go to reply and it seems to work but the browser just hangs. I get the browser is waiting for the server to respond and that I can cancel or wait. I usually have to refresh. I thought maybe it was the substack servers hanging but if I open up a new window and go to W4C it seems to be fine.

Expand full comment

Previously, if I posted a new comment, it would refresh the page, so I needed to make sure I checked all the new comments before I posted (using your ctrl+f trick). Now, it doesn't refresh, so I can post whenever!

Expand full comment

I have had that happen across different sites using Chrome over this week. Buttons sometimes didn't respond.

Expand full comment

I am using chrome so maybe it's something that started happening after an update.

Expand full comment

This happened to me a couple times last week (in Chrome, if that makes a difference). Refreshing the page fixed the issue for me too.

Expand full comment