Jennifer M

A little update:
I'll send the FILE to all those who signed up for the beta tomorrow.

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!
 

I would recommend to use our Profile completion setup. You can force a user to complete their profile when they complete their registration or you can turn off quick registration and any field that you have setup in the Profile to be shown on Registration will again.

I would recommend to use our Profile completion setup. You can force a user to complete their profile when they complete their registration or you can turn off quick registration and any field that you have setup in the Profile to be shown on Registration will again.

To clarify since @Joel R mentioned me specifically... 😂
We will be sticking with CKEditor 4 for a little while. While we will presumably move to CKEditor 5 some time in the future, it is currently still very new and maturing (when Joel asked me, it was before 5.11.2.0 was released which is when they re-added paste from word). But most importantly, to move would require a lot of development time (to upgrade our custom plugins) for what will be, to the end-user, very little change. And since CKEditor plans to continue releasing updates to version 4 for the foreseeable future we're not missing out on bug fixes or security patches.
Obviously if you're experiencing issues, please submit a support ticket and we can look into that - if you're not seeing the same problems on CKEditor's demo, the problem is likely our end and so it's probable that moving to CKEditor 5 wouldn't resolve it.

Doesn't really answer my question, however. I can go to any site and post someone's name...that's not the same as retaining records of a user unnecessarily.
But anyways, I'm not going to get drawn into a legal debate about GDPR right now. 😛 

While IPS may not support FA5 yet as we have a lot to work on and consider there are ways to allow for this, in fact I personally use FA5 on my personal sites. It requires a minor edit to the custom.css and including the FA5 code. It would be beneficial if you allowed users to provide FA5 icons.
If you include the CDN or similar the code you need to make both FA4 and FA5 to work is:
.fa { font-family: "FontAwesome" !important; } With this and including the FA import code FA5 codes will work as well as all FA4 icons currently included on IPS.

og:title should not be missing on any page whatsoever. If it is, I suspect that might be an issue with a custom theme.
og:image will be present on every single page so long as you upload a default image (edit your theme and visit the Logos tab to upload a default social sharer image, which will be overridden when there is a more specific or appropriate image throughout the site).
Twitter cards themselves have been implemented, but naturally it will depend on the context of each individual page which tags are produced.

Is this really starting all over again? How many times does it have to be pointed out that URL delisting shown in the Search Console cannot be caused by the sitemap generation?
Listing and delisting happens when Google crawls the actual URL and it is decided based on what it finds on that URL. That’s it!
The sitemap can only help Google to find the URL faster. Nothing in the sitemap will cause an URL to be delisted. How could it? It’s just URLs saying “please check this out, Google!”. No slow or incomplete sitemap will cause delisting. No faulty sitemap will cause delisting. No entirely missing sitemap will cause delisting. Nothing in the sitemap can cause delisting. 
If you find an actual bug in the sitemap creation you can demonstrate to be true, better open a support ticket or start a new topic about this bug and nothing else instead of adding it to this huge pile of “I don’t like my Google stats and I will just blame IPS and ask them to fix it”. 

First version is going to provide only oauth login (and it's going to be sold for only 10$ early adopter price)  so that people can finally use this feature again. And then we'll include the bot features which we're already working on in an later release once we tested everything and once we finished the GUI for this stuff.

All I can say is: No matter if you want to see new content, new registrations, commerce data, downloads submissions, application form data, trophy promotions, IPS errors in discord, you'll be able to do it;)