Lindy

Please try now

I'm not sure what you're seeing, David -- but there's a valid DMARC record.

DMARC has been enabled on that domain, which should resolve your concern. There are only a couple of DNSSBLs that major email providers such as Yahoo and Google reference for deliverability: spamhaus is one. Other sbl's have minimal, if any impact. Please keep in mind that the cloud email service offered by your package is shared among thousands of clients. While both we and AWS take every necessary step to be responsible stewards, minimize spam and auto remove from DNSSBLs that have impact, no provider can guarantee 100% deliverability 100% of the time on a shared platform. If email is mission critical to your community, you may wish to consider using our SendGrid integration and obtain an account with a dedicated IP add-on from them. This ensures that you are the only one using the sending IP. Hopefully the above will help alleviate your concern.

We unfortunately do not have a mechanism to pause a cloud package, however, should you let the service expire, you have 60 days to reactivate before service is permanently terminated.

Are you using incognito or private browsing?

We're sorry for any inconvenience. We have been hit with a run of large-scale Distributed Denial of Service attacks against a few customers that seemingly attracted a lot of negative attention. We are constantly improving our mitigation systems, but there are rare occasions when there's a delay while the system mitigates while minimizing disruption to legitimate traffic. Thank you for your patience and ongoing business.

Please let us know if the issues editing, etc. are resolved now.

Sorry for any inconvenience. This will be addressed shortly.

We do not currently do this for retail cloud plans, however, this is something we will look at. Thanks for your inquiry.

We strive to ensure our cloud platform leverages the latest, most advanced, secure and performant technologies available. To achieve this, maintenance is of course regularly necessary. While the vast majority of updates and maintenance are performed seamlessly behind the scenes, there are occasions where a brief outage may occur. On September 20 @ 10:00PM (EDT), an upgrade to our EU infrastructure will be performed. The maintenance window will be one hour, however, we expect service interruption, if any, to only last a few moments. Please note that this does not impact all EU customers; only those who are served by our EU platform. Thank you for your patience and, as always, you may find up-to-date information on our Status Page.

This will be rolled out very shortly!

I understand where you're coming from; it was indeed a tough decision. There is also, however, the side of the Marketplace that we've kept largely to ourselves and that is the costs associated with operating it. Many assume this has been an additional revenue stream for IPS, but the reality is, it has never even broken even. To explain why and in the spirit of transparency, let's use the example of a basic $5 plugin purchase; with our 10% commission, minus transaction fees, etc. we net virtually nothing, but we assume all the risk. This means, if someone decides they're unhappy with a resource (even though we have an all sales final policy), or uses a fraudulent payment method and a chargeback is performed resulting in us losing that dispute, we pay a $15-20 fee--the author is not charged this fee and usually retains the proceeds from the original sale. It takes dozens and dozens of sales of that single resource to break even on that one transaction. Multiply that by countless chargebacks and incidents of fraud in addition to the immense development time required to review resources, the administrative time to handle customer vs developer disputes, support overhead, payout fees, etc. the Marketplace actually costs us a significant amount to provide and maintain. The costs have actually exponentially increased as the use of the Marketplace has decreased. Previously, there were more good sales to help lessen the blow of the bad sales, however, with a 75% decline in usage over recent years, the volume is simply no longer there, so the losses are subsequently no longer sustainable, even if we were to triple our commission rates, which would only hurt us and the resource authors. On a scale of full app stores such as Apple, Google, Steam, etc. you have enough volume to chase the bad with good and the numbers add up. We are, of course, not Apple. As has been said, the vast majority of our customers today appear to either prefer their installation to be "stock" or to have custom development performed by third party providers. The top three Marketplace resources are currently installed on only 2% of communities (that report statistics to us, to be clear). I know how easy we've made it for those who like lots of tweaks and resources and we hope you will continue to enjoy these resources, but unfortunately, we can no longer prop up and absorb the losses of a declining ecosystem. I fully meant what I said in the original announcement - we are excited to be able to redirecting the resources expended in supporting the Marketplace towards improving the platform on the whole and creating new opportunities for motivated third party developers to connect with interested customers for custom development, integrations, services and yes, premade resources. For those that are active in third party resource utilization, I'm very encouraged by and grateful to @Joel R for his interest and commitment to bringing our loyal third party contributor community together again in a way that provides them more freedom and opportunities.

Yes, you'll be able to transfer after the closure as well.

To be clear, you will still be able to visit independent websites to obtain premade resources if you wish. From our standpoint, the trend has simply moved more towards custom development or stock installations.

Not at all; both apps are very popular outside of our own use.