_Mark_

Thank you. I'm really not saying all this to whine and moan, but to stress the fact that some (I guess a sizeable chunk) of Invision's renewing clients aren't choosing to be self hosted because they're cheap or in order to "cheat you" out of money, because you guys damn well deserve this money - you made one hell of a software. We're doing it because it's the only viable option for our communities and businesses, and I think you'd agree with me on the fact we shouldn't be "punished" for that. 
I think that if there are technical difficulties or added costs or whatever in making this integration (or any other future feature) happen for self-hosted communities, you guys (if we're already on the subject of being open, upfront and vulnerable) should just be clear and say "hey, we want do to X, but for Y type community we have A, B, C difficulties. If you want this feature you're going to have to do 1, 2, 3". Just like was the case with Elasticsearch. It says right there - you're gonna need a dedicated server to run that. Just let us choose. Choosing for us, especially when we don't really have the choice to switch to a cloud program, just feels kinda jerky 😄 

I'm not, in any way, trying to be overly critical or harsh, but that post is pretty much 100% verbal fluff and no actual actionable content. We're all adults here, and we're all (I guess) community managers ourselves and know fluff when we see it. Maybe it's my Israeli no-bullcrap-"chutzpah" talking, but I'd would LOVE it if you could point out some of the actual technical reasons that led to making this decision, and how Invision is looking to proceed from here - is this feature never going to be available for self-hosted clients? Are you wanting to implement some sort of alternative? What's the probability of there being more of those cases in the future? Are you at all interested in doing the work needed to get hard-to-implement features available for self-hosted clients or will you put those efforts into more seamlessly integrating them for cloud clients?
 
I know what I'm saying might come off as harsh or rude, but you have to understand that none of us (I hope) bought the IPS suite as a single time purchase and "the next time" we buy a community software "we'll try something else". This isn't a bottle of shampoo, we're all making long-term plans based on your software, some of us have businesses involving actual money and peoples' jobs and livelihoods relying on it. So "being vulnerable" is nice and all, but it can't be taken to the bank, and is - honestly - kind of insulting. This whole interaction needs to be WAY more pragmatic and way less like we're a community of 10 year olds getting together to have a great time.

"Zapier is the first smart community enhancement available for Cloud and Enterprise Community customers exclusively."
Not liking this direction...

Even so why restrict us from it then? I'm sure we won't struggle to get through a compliance process. It's quite common when having to register for things like API keys from developer portals from the likes of Facebook, Twitter, WhatsApp...
If its a case of self-hosted server performance, our server's have been fine tuned using over 15 years Linux admin experience. What makes Invision think our self hosted infrastructures can't handle thousands of Zapier requests?
Surely there has to be a solution. I've been with Invision since 2006 using my own infrastructure, a lot of software we use is self hosted. I will never go SAAS any time soon. After waiting and waiting for self-hosted support of a new game changing feature like Zapier, I'm left shocked and disappointed. 😞
 

There are some really great changes there.
Users on my forums often get confused by file upload size limits - it's my main barrier to users using the gallery. Are there any improvements to either make it clearer what those limits are or to dynamically reduce the file size through compression as it's uploaded?