Jump to content

Community

Lindy

Management
  • Content Count

    4,179
  • Joined

  • Days Won

    261

Lindy last won the day on November 6

Lindy had the most liked content!

About Lindy

  • Rank
    That Lindy Character

Contact Methods

Profile Information

  • Gender
    Male
  • Location
    Forest, VA

Recent Profile Visitors

107,087 profile views
  1. I'm sorry for any inconvenience. It looks like there was a payment issue and we just need to verify some information. Unfortunately, I don't see any emails from you in our system, but feel free to contact me directly and I'll do my best to help. Thank you.
  2. It sounds like you're using it as a helpdesk of sorts -- is there a reason you wouldn't use the Commerce support system?
  3. As a corporate legalese disclaimer: while we try to provide basic tools to help you achieve compliance with relevant laws and regulations, the onus of ensuring compliance with your local jurisdiction and that of your visitors, falls upon you. If in doubt, we always recommend seeking out the service of a local attorney. CCPA is actually far less restrictive than the GDPR so there is no cause for hysteria (I will concede when I saw the headline months ago, I thought "oh dear, what is the United State of California up to now?" As far as California regulations go, this is actually fairly reasonable. 🙂 If you already comply with the GDPR, you really don't need to do much different for CCPA. The key takeaways, in our opinion, are: - You must have a cookie policy. You seemingly do not need to obtain explicit consent, but I would recommend the cookie banner and you should always have a privacy policy. You do need to be transparent and document how you use cookies. - We have not built the software with the intention of mining and selling your user data and we have no plans of doing so. If you are selling or otherwise using user information for financial gain, there are in fact requirements under the CCPA - notably a banner or similar disclaimer that allows the visitor to prohibit you from selling the information. That is up to you to work out and not within the scope of Invision Community. - As with the GDPR, the rules can change when you get into third party advertising, what the third party is receiving and how it is being used. Again, it is unfortunately up to you to ensure compliance. - Similar to the GDPR, the CCPA does provide for a right-to-erasure. It is important to note that just because someone says "I want my account deleted" - that does not mean you are legally required to do so under all circumstances and this is true with the GDPR as well. For example, we will not purge the record of a recent customer. You should speak to your accountant regarding federal record keeping requirements, but federal law trumps the CCPA and even if that were not the case, the CCPA itself provides for exceptions. I've seen customers panic at a request and wipe a customer and their history, so don't be afraid to research and be mindful of your rights and obligations while still trying to respect your users'. The CCPA is largely aimed at promoting transparency and thwarting the unauthorized sale/misuse of data. There's nothing wrong with that and nothing to panic about. Again, we cannot account for the laws and regulations of every locale around the world. Even within the EU, different member states may have more stringent regulations than others. We try to help with basic universal compliance, but the software would fill a 1TB drive if we were to embark on China regulations, EU -> Great Britain regulations, EU -> Germany regulations, US -> Federal regulations, US -> California regulations, Russia regulations, etc. etc. Once we get past some universal functions like cookie banners, privacy/cookie pages and some basic member tools like export - you should take it from there based on advice from your own local counsel (not to be confused with the armchair experts with YouTube or Google law degrees!) I hope this helps.
  4. The few of you responding have been here a long time and you should know by now that we take your trust seriously and to the best of my knowledge, we have never given any reason, in 18 years, to question that commitment to privacy and security. We anticipated a few hiccups with the transition and we've made adjustments based on bugs and feedback, as we always do. That said, @Woodsman the unfounded spreading of FUD simply cannot continue. I appreciate your past business, incredible loyalty and above all - your service, but the "sheep to slaughtering" metaphors and rhetoric are irrationally over the top and an indication this has fully run its course with no positive result to be had from here. The reality is, virtually any Internet based company will use at least one data processor. Hopefully you're not under the impression that everything you provide IPS is housed on a computer under the desk in my office. Our infrastructure is in fact housed within Amazon Web Services (AWS) - so AWS is considered a processor. If you pay by credit card, Stripe is a processor - they will have your information. PayPal as well. Google is a processor, as is Sendgrid and yes, Zendesk. While any of those companies could be breached, the overall risk is low and all have comprehensive security protocols and teams in place to minimize the risk. All of these organizations are leaders in their respective industries and have the trust of individuals, private companies, public companies and government institutions. It's very regretful if they do not have your trust as well. Woodsman, I've taken the liberty of saving you further stress and I have removed you from Zendesk. Unless you click into support again, they will have no record of your existence. As a final point of clarification: Zendesk is how we have chosen to communicate with our customers. To associate such communication, your name and email address are stored in a profile in that system upon first contact (this also occurs if you just send an email.) No billing details, addresses, etc. are collected or stored by Zendesk. We utilize a real-time widget that displays basic license data from Commerce for our agents to view (it is not stored on Zendesk servers) - everything else, we click the name and are taken directly to your Commerce profile on our systems. Zendesk is a highly regarded helpdesk system with the trust of thousands and if we felt there were any measurable risk to our customers, we wouldn't have even considered them. A notification that you will be taken to an "external" site for support is a fair and reasonable request - I'll get on looking into that. I feel we have adequately addressed the privacy concerns as it relates to our use of Zendesk. If there's any other product or support feedback not related to this, please definitely feel free to open a new topic. Thank you!
  5. We need your real name - you are a customer. Zendesk is now how we communicate with you and we communicate with people, not usernames. 🙂 Addresses, billing information and other personal details are not pulled through Zendesk. There are far larger corporations than IPS that use and trust Zendesk - including Expedia, Slack, Fox, Vodafone and others. We take the privacy of our customers seriously and over 17 years with no major incidents is a testament to that. That commitment to privacy will not change and while we truly appreciate your business, it is unfortunately not a reasonable expectation to dictate how we run ours or what tools we use to do so. Zendesk is a reputable Helpdesk product, not a marketing or data mining company. As mentioned, we have a DPA with them. If you would like to forego your data being processed by Zendesk, you may contact us one final time stating so and we will remove your profile from Zendesk. As ALL communication with us now flows through Zendesk, however, you will no longer be able to communicate with us without ending back up in Zendesk. There is no "opt-out" that would still allow communication and support.
  6. We can simply clear your Zendesk profile if you'd like (it would not recreate unless you use the support system) but you would not be able to communicate with us any longer as all emails and contact forms go through Zendesk at this time.
  7. Marketplace developer by day, privacy attorney by night? I feel there should be some cape twirling. 🙂 Our privacy policy and the GDPR permits use of processors to fulfill the requirements of providing your purchased products and services. We adhere to both our own promise to data protection as well as the inherent legal requirements by ensuring any processors used also employ the same stringent data protection standards. We have a DPA in place with Zendesk and you are welcome to review their privacy information: https://www.zendesk.com/company/customers-partners/privacy-and-data-protection/ If you would like to "opt out" of Zendesk processing your information, you are of course not required to utilize the support desk.
  8. Have the background tasks completed? The tasks convert all of those old tags to proper HTML. If everything is done and the posts still aren't right, it's important you contact us as soon as possible to investigate. In the event a restore and reupgrade needs to be performed, you obviously do not want to let too much time lapse.
  9. This is a known issue that will be patched next week.
  10. Probably best to take this sort of thing to PM. I can confirm this as a valid alt account and purchase though.
  11. Thanks for reaching out. Somebody else might "get" this before I do, but I'm having a difficult time visualizing what you're after. When this functionality was created, we assume if there's no payment, there's no sale as such and thus, there is no "checkout" / payment. While we can consider a suggestion to provide some sort of "$0 confirmation" - often, there's a different or better way to meet the goal. So, if you could please explain your use-case and workflow, it would help us better understand what exactly you're after.
  12. It's likely you have only opted to restrict new content. You have other options available to control accounts you've flagged as spammer. It sounds like you want to just tick the 'ban member' setting and you should no longer have this issue. 🙂
  13. I’m sorry to hear that you’re frustrated. With thousands of customers across the globe, we try our very best to provide the stellar support that is consistent with our 17yr+ reputation while still maintaining an efficient workflow. Like most companies, we admittedly don’t always hit the mark and when such occurrences are due to a breakdown on our side, we do our best to make it right. With that said, your comments about support and the product are a bit confusing. You’ve submitted 4 tickets this year (not including the “your support sucks” ticket - which we will gloss over as I know emotions can run high.) All tickets were promptly answered - one within 30 minutes. Another within 12 hours - on a weekend. Another submitted on Saturday evening was addressed first thing Monday morning. I’m unable to find any indication that you’ve actually experienced any technical issues that are due to software “faults” based on your ticket history. One ticket was related to branding removal, two were due to third party customizations which, when you said you removed/reinstalled, resolved the issue and finally, the other that seemed to push you over the proverbial edge was our inability to help you change HTTP status codes and customize your server-side error messages, via a support ticket. Your latest issue you’ve posted about elsewhere, but haven’t brought up in a ticket, suggests you may have a rewrite issue. I realize you didn’t get the outcome you were looking for and you have an expectation that we should provide third party / customization support. In a perfect world, we would have the luxury of being everything to everyone, but unfortunately, our product support team are not developers and unfortunately, traversing server systems, debugging code we didn’t write (third party plugins/apps) and pinpointing line numbers to change code for HTTP status codes is simply not a reasonable expectation of base/included support. It’s always disheartening to disappoint a customer and it’s something we take seriously, however, sometimes expectations don’t always fall in line with what can reasonably be provided. Finally, while I have never subscribed to the customer is always right philosophy. I do firmly believe in approaching every service issue individually, ensuring I understand the customer concerns, reviewing the background and identifying where the breakdown occurred. With me personally, approach is everything and as a consumer, I practice what I preach. If my Internet service goes down, I do not call Comcast and berate the agent for I know it is not their fault personally and I find people are much more receptive to a calm, respectful exchange vs rants and insults — treat others like you wish to be treated. Likewise, if a customer approaches and says “I know things happen, but I’m having this issue and not getting anywhere. Can you please help?” I personally guarantee the results will be far more favorable than “you guys suck”, “this is a _____ joke”, “I’m going to sue you”, “I’m starting a social media campaign against you.” The latter will never yield any positive results here. We prefer positive relationships with mutual respect and courtesy; we’re all on the same side and your success is our success. If you’re ever unhappy with a support interaction, please ask for it to be escalated. At this point, I suggest taking a couple of days and then I would absolutely welcome you to contact me personally for further discussion — in hopes of “rebooting” and working towards more positive interactions. Thank you for taking the time to provide your feedback.
  14. Brent, We appreciate the feedback! I certainly understand there are still some niche sites - notably certain techy/dev sites that still rely on to BBCode both because they find it easier and it’s what they know. The (comparatively) few still using it are very passionate about using it and we can definitely appreciate that. At the same time, the BB in BBCode stands for Bulletin Board. It was created long before WYSIWYGs in the 90’s by UBB. The web has since long evolved and with the advance of proper WYSIWYG technology, so BBCode is really rare to encounter. Be it Google Docs, email or virtually any modern editor, we all use buttons or shortcut keys like command-B as second nature, which works even with markdown. The real issue is the fact that it’s simply not native to any modern editor (that I am aware of) - including the one we integrate with, CKEditor. We have a backend “parser” that converts your BBC tags to HTML upon submission, but there is no way to convert that back for editing or any other purpose. To maintain overall stability as well as compatibility with editor updates, our only intention with Invision Community 4 was to ensure some degree of backwards compatibility for those who still use tags when submitting content. The software in fact does that and while BBCode will be deprecated (which simply means it will not be further developed) in a future release, we have no immediate plans to remove it entirely. While there are still traditional software packages that have legacy BBCode support, you will find that most modern community platforms have no native (built-in) support for BBCode and I think it’s extremely unlikely we will ever see it make a comeback (although I said the same thing about bellbottoms.) We are always open to ways to improve your experience with the editor and if you’re struggling to get things formatted properly using native functionality, we would welcome you to open a support ticket so we can see what you’re trying to achieve and try to offer some help. Thanks again for taking the time to share your concerns!
  15. Confusing, right? 🙂 As we’ve been around for nearly two decades, things have evolved and changed. When IPS was founded, there was really only one product to speak of - Invision Board (IBForums) - the company was legally formed as Invision Power Services, Inc. and the product was then called Invision Power Board (IPB.) As the product line evolved and licensing changed, we referred to the products collectively as “IPS Community Suite.” Some called us IPS, some called us IPB, some called us Invision - so when IPB was discontinued several years ago, we began branding as “Invision Community.” The parent company remains Invision Power Services (IPS) - we call the platform itself Invision Community. The package names in the client area is a fair point - we’ll get those updated. Thanks for your continued interest as well as your referrals. Hopefully this helps clear up our identity. 😉
×
×
  • Create New...