Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues • Hacker News Board

Re: Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues

#301

Post by confluence_perf » Tue, Jan 05, 2021, 5:22 PM UTC

Slackwise wrote: post #300

confluence_perf wrote: post #28

Earlier quoted context omitted.

Sorry to hear it's been a frustrating experience. I'm a PM for Confluence Cloud and we're always trying to make it better. Would you be willing to share more specifics, such as: - Pages with content X are the slowest - Trying to do A/B/C is annoyingly slow - etc ? (edit: looks like HN is severely limiting my reply rate so apologies for delays) We're trying to focus on frustrating pages/experiences rather than number…

> I'm a PM for Confluence Cloud and we're always trying to make it better. Can you guys please make Ctrl-S save and not exit editing? My muscle memory is costing me 10+ seconds of load times every time I type a paragraph and reflexively save, getting dumped back to the view mode of a document. The slow load times exacerbate the problem tremendously. I honestly don't know a single product that treats Ctrl/Cmd-S as "Sa…

Hi Slackwise,

This is interesting -> I don't think Ctrl+S should be exiting editing in any form, can you describe this a little bit further? When you hit this is it:

a) moving to Preview (you can see the changes you made, but in preview mode not page view mode (the page tree won't be visible)

b) browser returns to the 'view page' (page tree visible), but your changes are not published (you may see a tag at the top "UNPUBLISHED CHANGES")

c) something else (please describe)

Second question: what does the browser's forward/back buttons display after the 'ctrl+S' result?

Re: Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues

#302

Post by guitarbill » Wed, Jan 06, 2021, 11:16 PM UTC

maccard wrote: post #276

guitarbill wrote: post #268

Earlier quoted context omitted.

Point still stands, right?

I don't think so. If it's mediocre, then it's mediocre compared to something else, but in reality it's best-in-class. It just turns out that the opposition isn't exactly bringing it's a game.

so what do they work on?

Re: Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues

#303

Post by Slackwise » Mon, Jan 11, 2021, 10:00 PM UTC

confluence_perf wrote: post #301

Slackwise wrote: post #300

Earlier quoted context omitted.

> I'm a PM for Confluence Cloud and we're always trying to make it better. Can you guys please make Ctrl-S save and not exit editing? My muscle memory is costing me 10+ seconds of load times every time I type a paragraph and reflexively save, getting dumped back to the view mode of a document. The slow load times exacerbate the problem tremendously. I honestly don't know a single product that treats Ctrl/Cmd-S as "Sa…

Hi Slackwise, This is interesting -> I don't think Ctrl+S should be exiting editing in any form, can you describe this a little bit further? When you hit this is it: a) moving to Preview (you can see the changes you made, but in preview mode not page view mode (the page tree won't be visible) b) browser returns to the 'view page' (page tree visible), but your changes are not published (you may see a tag at the top "U…

This isn't the cloud offering, but on-prem. I assume they're the same.

The about page says "Confluence 6.15.2".

When I click "Edit" to edit a page, via `/pages/editpage.action?pageId=`, and hit Ctrl-S, it takes me back to the view mode rendered via `/display/SPACE/Page+Title`.

Absolutely infuriating and wastes an incredible amount of time. I can't get over my muscle memory. The "Save" button in the bottom-right does the same and appears to be what the hotkey activates. No mention of it being a "Save and Quit Editing". Hovering over the button says "Save your page (Ctrl-S)".

Re: Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues

#304

Post by confluence_perf » Tue, Jan 12, 2021, 5:19 AM UTC

Slackwise wrote: post #303

confluence_perf wrote: post #301

Earlier quoted context omitted.

Hi Slackwise, This is interesting -> I don't think Ctrl+S should be exiting editing in any form, can you describe this a little bit further? When you hit this is it: a) moving to Preview (you can see the changes you made, but in preview mode not page view mode (the page tree won't be visible) b) browser returns to the 'view page' (page tree visible), but your changes are not published (you may see a tag at the top "U…

This isn't the cloud offering, but on-prem. I assume they're the same. The about page says "Confluence 6.15.2". When I click "Edit" to edit a page, via `/pages/editpage.action?pageId=`, and hit Ctrl-S, it takes me back to the view mode rendered via `/display/SPACE/Page+Title`. Absolutely infuriating and wastes an incredible amount of time. I can't get over my muscle memory. The "Save" button in the bottom-right does…

Thanks for mentioning that -> honestly I keep forgetting to ask because I work on the Cloud side.

I will see if I can find some server folks to ask around, but obviously can't promise any movement.

Re: Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues

#305

Post by still_grokking » Tue, Jan 12, 2021, 11:50 PM UTC

confluence_perf wrote: post #28

dalrympm wrote: post #22

I'm curious, I'm a Cloud customer and I can tell you that the service is incredibly slow even for a small scale setup (2 Jira Projects and 3 Confluence Workspaces). There's an insane amount of network requests seemingly for mouse tracking. By telling everyone here, that Atlassian Cloud products are insufferably slow, am I violating the ToS? I was actually thinking about doing a write up on the issues I've had but thi…

Sorry to hear it's been a frustrating experience. I'm a PM for Confluence Cloud and we're always trying to make it better. Would you be willing to share more specifics, such as: - Pages with content X are the slowest - Trying to do A/B/C is annoyingly slow - etc ? (edit: looks like HN is severely limiting my reply rate so apologies for delays) We're trying to focus on frustrating pages/experiences rather than number…

>I'm a PM for Confluence Cloud and we're always trying to make it better.

That's the problem. It's beyond repair since many, many years. You can only make it worse.

Ditch it! Throw it away, and rewrite from scratch. If you don't bungle it again (here lies the risk, as we're still talking about Atlassian) you'll have a better product then ever in one year.