I tried to <3 this post a couple of hours ago and got an error each time. Tried again just now and still getting errors, but the <3 count has increased.
Not sure if there's any algorithm ala YT, but count this comment as a "thanks mate, appreciate the ongoing content".
Based on limited testing, I think it would resolve if you reset browser data or erased data for substack.com alone. But should you? Substack still seems to be making ongoing "changes" (disfigurements) to their content management backbone which is likely leading to all these cache/code conflicts, which means resetting would be a temporary fix - and besides, what if you mess up your Wordle history?
In Safari, you can snipe *just* the substack cache in Preferences > Privacy > Website Data. This will lead to having to sign in again.
I just published and then tried liking my own ranting, unintelligible post and it worked. Then I could like yours. No other action taken.
And yeah, the ongoing changes to the stack interface is surely messing with behind the scenes stuff. They seem to change it quite often too. Weird given there was nothing essentially broken requiring so many "fixes". Ah well can't complain when it's free.
Incroyable. And I am getting the "SWW" message on your post despite having thought I resolved issues with other substack pages via deleting cache. Worst website data deletion EVER.
I tried to <3 this post a couple of hours ago and got an error each time. Tried again just now and still getting errors, but the <3 count has increased.
Not sure if there's any algorithm ala YT, but count this comment as a "thanks mate, appreciate the ongoing content".
Based on limited testing, I think it would resolve if you reset browser data or erased data for substack.com alone. But should you? Substack still seems to be making ongoing "changes" (disfigurements) to their content management backbone which is likely leading to all these cache/code conflicts, which means resetting would be a temporary fix - and besides, what if you mess up your Wordle history?
In Safari, you can snipe *just* the substack cache in Preferences > Privacy > Website Data. This will lead to having to sign in again.
I just published and then tried liking my own ranting, unintelligible post and it worked. Then I could like yours. No other action taken.
And yeah, the ongoing changes to the stack interface is surely messing with behind the scenes stuff. They seem to change it quite often too. Weird given there was nothing essentially broken requiring so many "fixes". Ah well can't complain when it's free.
Incroyable. And I am getting the "SWW" message on your post despite having thought I resolved issues with other substack pages via deleting cache. Worst website data deletion EVER.