#1 with new IP

#2

was 403'd at third attempt... So not dependent on whether or not logged in. Changed IP and...

I did a preview/edit and 403 at first attempt. Changed IP and...

... can post again (for three attempts).

So about three posts without preview gets 403.

Or the very first preview/edit

I just got a 403 after only one preview a few minutes ago.
Closed window and attempted to repost in a new window (Chrome) without preview: Same result.
Cleared cache/browsing history and reposted it succesfully in the same window.

michael, I'm not sure I have understood.

1. You got 403.
2. you closed the window, opened a new window and attempted to post (without preview). You got 403.
3.you cleared cache/browse history. Then in the same window, you reloaded the BH discussion page, clicked on 'reply', pasted your text, clicked on 'create post' and then it worked.

Did I get that right?

[I asked Squarespace to escalate the problem for management attention. I got a long reply which I took to mean 'no'. Today I sent them the following:

I know from experience on both sides of the fence that how a problem is viewed by an IT organisation can be quite different from how it is viewed by a user.

Here is my perspective, as a user, on how this problem has been handled by Squarespace.

■ The problem was induced by Squarespace itself in updating its anti-spam measures three weeks or so ago. Prior to that, the problem had not been seen by BH users.

■ There was no roll-back plan (or if there was one, it was not used) when the updated anti-spam measures first caused problems three weeks ago.

■ The original case was evidently closed by Squarespace in its 'bug tracker', despite the problem not having been resolved.

■ A new version of the anti-spam measure was tested in the Squarespace test environment and looked ok. But when rolled out a few days ago the problem was still there, showing that the test environment cannot be relied on.

■ The problem is now worse than ever (ie preview does not work at all, only two postings possible) which does not give the impression of a team working systematically towards a solution.

■ My request for the problem to be escalated for management attention was declined, despite more than three weeks having passed since it was first reported and it affecting many/most/all users on the blog.

■ The foregoing things indicate to me that the problem is not being taken seriously by Squarespace and that Squarespace's only plan for dealing with the problem is to continue as before. Reassuring words do not change that impression.

The thing would make me think it was now being taken seriously by Squarespace would be hearing that a manager has had a meeting with the relevant team, has given them the objective of resolving the problem to the customer's satisfaction within 24 hours, and has approved their action plan for resolving the problem.

Best regards

I typed some stuff, clicke preview/edit and got 403.

Now I'll try posting by using create post. I'm using the same window that got 403

OK that worked even without clearing any history

More stuff without preview

That worked. Again more stuff.

more stuff 4

OK that was 403'd. I cleared history (cache, browsing history) but did not change IP address.

So that went through. So possibly clearing cache/browsing history will clear it.

try again #2

try again #3

#4 got 403'd. I've cleared browsing history and cache again and...