Martin A.

It would be nice Jordan if you can understand and implement, community feedback in your blogs. Here are few for you again:
https://invisioncommunity.com/news/invision-community/new-live-community-features-r1260/?do=findComment&comment=241259
https://invisioncommunity.com/news/invision-community/new-live-community-features-r1260/?do=findComment&comment=241264
It's not big ask - from AlexWebsites, Adriano and many others to clearly indicate in blog title - Cloud only feature. 
 
 

Jordan - Congrats
Matt - What does this position actually mean for clients?  How will he triage, prioritize, and escalate client feedback to the IPS team, all of whom can and do visit the forums themselves? What are the parameters for clients to help highlight and channel our feedback in an effective manner?  And finally, as a community advocate, what does he actually advocate?  Whom does he represent, and to what extent?  
Until the company articulates - and the community can validate - these above questions, this new position is entirely aspirational.  
Invision has attempted multiple community engagement tactics over the years.  And I have a long history of memory:
I remember IPS Release Notes when Charles said you were going to provide a roadmap.  That quietly disappeared and failed.  I remember Tagging when Lindy said you were going to tag the status of features.  That quietly disappeared and failed.   I remember how you removed Pre-Sales and merged Feedback from all product lines together.  Product Feedback is now a mess.   I remember how you recently launched a Slack channel for Marketplace devs.  How is that going?   I genuinely and honestly don't mind you guys trying new things - that's great.  Every community (and company) should always be experimenting and launching new initiatives.  But the past history of your community engagement is littered with no follow through.  How is this time different?    
To be blunt and on behalf of all of your retail clients, we don't need a Community Advocate to post memes.  We need a Community Advocate with the power to deliver and communicate on meaningful actions to drive our communities forward.

This brings back memories to when I made an app that did this back in 2010.

@Stuart Silvester was wearing a black turtleneck while typing this blog post.  True story.  😁

This brings back memories to when I made an app that did this back in 2010.

This brings back memories to when I made an app that did this back in 2010.

This brings back memories to when I made an app that did this back in 2010.

This brings back memories to when I made an app that did this back in 2010.

This brings back memories to when I made an app that did this back in 2010.

This brings back memories to when I made an app that did this back in 2010.

This brings back memories to when I made an app that did this back in 2010.

This brings back memories to when I made an app that did this back in 2010.

Any comments on this, @Matt?

Will this allow the member to use the same password as they had before? Kind of defeats the purpose if they can.

Will this allow the member to use the same password as they had before? Kind of defeats the purpose if they can.

Will this allow the member to use the same password as they had before? Kind of defeats the purpose if they can.

Will this allow the member to use the same password as they had before? Kind of defeats the purpose if they can.

Will this allow the member to use the same password as they had before? Kind of defeats the purpose if they can.

Will this allow the member to use the same password as they had before? Kind of defeats the purpose if they can.

Will this allow the member to use the same password as they had before? Kind of defeats the purpose if they can.

Important changes. Have in mind though, that user actions is usually one of the common problem for a security issue.
From my personal experience, we had to implement a way not to let users be able to use extremely easy passwords which had their accounts be compromised. Most important, not let users use their own username as a password and also some easy passwords like  sex, 12345, god, matt etc 🙂
 

I'm genuinely kind of confused as to why IPS is posting such an early announcement of 4.4.  While we're all excited for the newest version (insert more gifs here), this really is premature:
1. You can't actually download unless you specifically request beta.  
2. You probably don't want to download since it's beta.  
3.  Did I mention it's still in beta yet?
5. And not even late stage beta.  This is literally beta 1 with potential breaks to global template. 
4.  But whatever.  Party on.  This is like the pre-party before the preview party before the launch party, and by the time we actually get to download 4.4 we will all be so drunk and hungover from the partying that we really won't care what version we're actually using on our live sites. 

I guess @Adriano Faria @Martin A. and some others will be happy to hear that we've also cleaned up the code and provide now a clean way for 3rd parties to add own tabs to the club navigation 🙂
More information will be posted in a separate topic with the 4.4 changes for 3rd party developers 🙂

I've worked with @Michael R over the past few years on his custom themes and he's always been a great client to work with. Nice to see the extra effort he goes to in order to keep children and prying eyes away, very dedicated.
Happy holidays Mike!

wow such forum how ajax very community much member