Linux-Is-Best

Back in the day (long ago), nearly every project and development I know about used CKEditor. In its heyday (gold age), WYSIWYG editors were still a relatively new concept (I feel old. ), and CKEditor was considered top of the line. Times have changed.
Ideally, you want your editor not to be the focus of your development. By that, I mean to say the editor should blend effortlessly in the background as something you do not notice (an afterthought). So many developments no longer use CKEditor because the editor itself often gets in the way.  I cannot count the many times when I have heard or experienced why something was not functioning right because of the editor.  Or why something could not be developed or extended because of the editor. The editor (CKEditor) is not the afterthought it should be.  Even here on Invision, the editor and its limited functionality has proven problematic by the sheer request to work around it https://invisioncommunity.com/search/?q=editor&quick=1&type=forums_topic&nodes=499
Speaking personally, I love where Invision is going. I admire their creativity in where they are taking the development. I enjoy many of the features and am looking forward to the new features they have suggested they have planned. But I dislike the editor. It is my 'pet peeve' for Invision. I know of only two developments that still use CKEditor (the other is not a forum, and they use CKEditor 5). In both of them, I dislike the editor (v4 and 5). Why? Because in both of them, nearly all the issues I encounter, all the bugs I stumble upon, and all lack of functionality and adaptability surround CKEditor.  Besides Invision, only vBulletin, whose market share is shrinking and development has become stagnant, concerning forum software, still uses CKEditor.   
I do not expect Invision to change editors overnight. As SeNioR- pointed out, it is not easy to change editors, not even to CKEditor 5.  So regardless of the discission (whether we stay with CKEditor or change editors), we are still looking at a large transition. We have two (2) years to think this through and explore our options before CKEditor 4 reaches the end of life. Plenty of time to think this over.
You'll note I did not specify any particular editor (besides a few examples I gave). My request is not to promote any specific one, only that an exploratory investigation be conducted and that Invision considers their options.
 

CKEditor 4 is reaching the end of life (source). Instead of jumping onto the CKEditor 5 bandwagon, I propose Invision consider an alternative editor. There are many well-established modern editors such as, for example, TinyMCE, Froala, Quill, and Redactor, to name a few. Any of these would make satisfactory alternatives.
 
CKEditor may be 'old school,' but it has become bloated, larger in file size and load time.  Most of the issues it encounters often have to do with responsive layouts on a mobile device and excessive load time. As mobile continues to dominate the landscape, I feel it may be prudent to focus on an editor development that has kept up successfully with the times with the least issues.
 
Changing the editor should not be expected in the next release. But a roadmap should be considered for a future transition.  Thank you for your time and consideration. 😀

great, thanks a lot.

Add the following to your .htaccess file
# BEGIN GZIP COMPRESSION <IfModulemod_gzip.c> mod_gzip_onYes mod_gzip_dechunkYes mod_gzip_item_includefile.(html?|txt|css|js|php|pl)$ mod_gzip_item_includehandler^cgi-script$ mod_gzip_item_includemime^text/.* mod_gzip_item_includemime^application/x-javascript.* mod_gzip_item_excludemime^image/.* mod_gzip_item_excluderspheader^Content-Encoding:.*gzip.* </IfModule> # END GZIP COMPRESSION Or if you were using Nginx (for future reference), you would add this to your config file (nothing you need to worry about, since you are using Apache).
gzipon; gzip_comp_level2; gzip_http_version1.0; gzip_proxied any; gzip_min_length1100; gzip_buffers168k; gzip_types text/plain text/html text/css application/x-javascript text/xml application/xml application/xml+rss text/javascript; gzip_varyon;  

Add the following to your .htaccess file
# BEGIN GZIP COMPRESSION <IfModulemod_gzip.c> mod_gzip_onYes mod_gzip_dechunkYes mod_gzip_item_includefile.(html?|txt|css|js|php|pl)$ mod_gzip_item_includehandler^cgi-script$ mod_gzip_item_includemime^text/.* mod_gzip_item_includemime^application/x-javascript.* mod_gzip_item_excludemime^image/.* mod_gzip_item_excluderspheader^Content-Encoding:.*gzip.* </IfModule> # END GZIP COMPRESSION Or if you were using Nginx (for future reference), you would add this to your config file (nothing you need to worry about, since you are using Apache).
gzipon; gzip_comp_level2; gzip_http_version1.0; gzip_proxied any; gzip_min_length1100; gzip_buffers168k; gzip_types text/plain text/html text/css application/x-javascript text/xml application/xml application/xml+rss text/javascript; gzip_varyon;  

Add the following to your .htaccess file
# BEGIN GZIP COMPRESSION <IfModulemod_gzip.c> mod_gzip_onYes mod_gzip_dechunkYes mod_gzip_item_includefile.(html?|txt|css|js|php|pl)$ mod_gzip_item_includehandler^cgi-script$ mod_gzip_item_includemime^text/.* mod_gzip_item_includemime^application/x-javascript.* mod_gzip_item_excludemime^image/.* mod_gzip_item_excluderspheader^Content-Encoding:.*gzip.* </IfModule> # END GZIP COMPRESSION Or if you were using Nginx (for future reference), you would add this to your config file (nothing you need to worry about, since you are using Apache).
gzipon; gzip_comp_level2; gzip_http_version1.0; gzip_proxied any; gzip_min_length1100; gzip_buffers168k; gzip_types text/plain text/html text/css application/x-javascript text/xml application/xml application/xml+rss text/javascript; gzip_varyon;  

As a matter of opinion, I like the location of the badges. I feel far too many things are centered on "postbit" on most forums, which adds too much noise. The unification of everything neatly in its place means I often tune stuff out and forget something is there. Introducing a little harmless chaos to the layout gives the site character and makes it more attractive. If someone wanted it centered, they could perform a template edit or perhaps use some CSS. But I, for one, like the location 'as is.' 
 
As for the coloring of the badges, I believe that depends on the avatar. Where it is located can cause a bit of a color clash depending on what your avatar looks like. I am using Linux (openSUSE Tumbleweed) with Mozilla Firefox ( Mozilla/5.0 (X11; Linux x86_64; rv:89.0) Gecko/20100101 Firefox/89.0 ) and find no real issue. But for argument's sake, attached are a few random screenshots. 







Upon uploading my attached (see post above), I notice they look a little rough around the edges. But this being an alpha, I do not presume the images used were of HD quality, merely proof of concept.

I wish for the option (in a future release) to disable any and all IP address logging.  In 2021 folks change IP addresses as easily as opening a new browser window tab.  I see no point, and it only slows down the site to resolve addresses while adding more to the database. 

CKEditor 4 is reaching the end of life (source). Instead of jumping onto the CKEditor 5 bandwagon, I propose Invision consider an alternative editor. There are many well-established modern editors such as, for example, TinyMCE, Froala, Quill, and Redactor, to name a few. Any of these would make satisfactory alternatives.
 
CKEditor may be 'old school,' but it has become bloated, larger in file size and load time.  Most of the issues it encounters often have to do with responsive layouts on a mobile device and excessive load time. As mobile continues to dominate the landscape, I feel it may be prudent to focus on an editor development that has kept up successfully with the times with the least issues.
 
Changing the editor should not be expected in the next release. But a roadmap should be considered for a future transition.  Thank you for your time and consideration. 😀

In my opinion, it would be great if there was an option in the group settings which disallowed IP logging. This would be useful for administrators, moderators, and groups for people that have a thing for privacy.
A good reason to disable IP logging for admins/mods is that if a security breach ever occurs, the forum administration team will badly be affected (affected the most). 

OK

I was online this morning and noticed the upgrade page here on Invision. But I think my 1st clue that we were on the final release was the bug tracker soon vanished afterward. 😅
I am still waiting on the CKEditor v4 fix that will resolve Mozilla Firefox Mobile. I figure it will be a few months before CKEditor fixes that (that's not an Invision issue, but still).  I, of course, also need to figure out why IN_DEV does not work for me.  For now, 4.6 is something for me to play with and play with I shall.

Since we are on the topic. I know that @Real Mythotical will soon have his 4.6 running on the latest PHP v8 setup and maybe available to hire.

I was online this morning and noticed the upgrade page here on Invision. But I think my 1st clue that we were on the final release was the bug tracker soon vanished afterward. 😅
I am still waiting on the CKEditor v4 fix that will resolve Mozilla Firefox Mobile. I figure it will be a few months before CKEditor fixes that (that's not an Invision issue, but still).  I, of course, also need to figure out why IN_DEV does not work for me.  For now, 4.6 is something for me to play with and play with I shall.

When will 4.7 release?

 
Serious well deserved applause to the entire team!

Yes.
I invite everyone to check out the suggested demo I linked in my OP post.  Please, do, test the page load times, responsiveness, and mobile usage of the editors.  For those of you who are more skilled and who are able, I also invite you to check out the underlined code.  Do compare and see for yourself (absolutely).
CKEditor 5 -- https://ckeditor.com/ckeditor-5/demo TinyMCE -- https://www.tiny.cloud/docs/demo Froala -- https://froala.com/wysiwyg-editor Quill -- https://quilljs.com Redactor -- https://imperavi.com/redactor These, of course, are only a small handful of possibilities.  There are many other alternative editors available, and if anyone would like to suggest something else, please do.
 

Pleased contact tapatalk for support for their app.

Welcome to part 3 ( Part 1 & Part 2 ) of our series for 3rd party developers.
 
Let's recap the interesting stuff:
A new extension was added to the core app to allow 3rd party apps to extend the achievements.
Content Items can be marked as anonymous
We have cleaned up our code and have removed almost all the deprecated methods and variables!
 
One if the most concerning changes for IN_DEV users will probably be our new ACP warning once the CSRF Key is being exposed in the ACP

 
That's nothing to worry about, it's only returned with enabled IN_DEV mode, but please take it serious and try to avoid any redirect to any URL containing the CSRF key and containing user generated content.

I would love for this.
At the minute members will send me a PM, I have a ready made reply which gives them 30 days and makes them aware that once deleted, no going back.
If they change their mind they can cancel the request by dropping me a PM again.
After they confirmed they have seen my message and still want to go ahead, I post restrict their account and set a reminder for 30 days.
To have this automated would be great as it feels like I’m being threatened half the time as they don’t agree with a post being pulled or haven’t banned x member.
I take the hardline approach in that look, we don’t hold you hostage, I’m also not begging any member to stay.
Automated system would work like this in my mind.
Once they click delete account, show a customisable notice that has a timer where they can’t click submit for 30 seconds or something so notice is read and they are aware of this is irreversible.
Let admins select a cooldown period length, during which disables their account, can’t post, use PM’s. If they attempt to it opens up a would you like to reactivate your account notice.
Allow admins to choose what happens after the cooldown period, to remove all content, assign posts to anonymous or the username but close account.
This would be huge for me personally.

I can confirm this does not happen in Firefox, but it does in Google Chrome.  I don't use Firefox, generally, but downloaded it to test this out 🙂
 

No such issue on my sites with Firefox.

Friday? Booo. Saturday? Blahhhh. Sunday? Who needs it! 
Welcome back to another fine edition of Hump Day, the best day, and today's is a doozy. 
We've officially launched 4.6 Beta 3! 🎉 
It's available for download or per request if you're on Cloud.
We're pretty confident things will be stable, but don't take our word for it; please make backups before updating. 
The official release will make its red carpet debut in the very near future.
What's changed from Beta 2 to Beta 3? @Matt passed along these changes (see below). It's worth mentioning these updates are our new team members, @Christopher Pei and @Marshall Slemp, first bug fixes. 👏 
Fixed an issue where Weekly and Monthly Email Stats were not displayed correctly Fixed an issue where CSV downloads were limited to 25 rows. Fixed an issue where editing a Link for an Image would not save. Fixed an issue where images added to a Custom Email were not showing up in the email being sent to the customer after a purchase. Fixed some spacing issues with member lists in various blocks. Fixed an issue where adding a theme setting to a parent theme didn’t update children themes with the new setting. Fixed an issue where the database checker may show un-needed database changes. Fixed an issue where an invalid “oembed” widget plugin type would appear when creating a block. Fixed deleting a widget not using JSON_PRETTY_PRINT for the widgets.json file. Fixed an issue where Achievements rebuilding would not finish Fixed an issue where Achievements badges would show in the hovercard during a rebuild. Fixed an issue where changing an authors name from anonymous would not reset the “is_anon” flag Fixed an issue where some ajax content was indexable by search engines Fixed an issue where badge counts could be wrong  

I know, that's a lot of awesomeness to absorb.
What are your thoughts? Have you been using any of the Beta releases thus far? We'd love to hear from you in the comments!
 
Related:
 

Honestly, that's not what happens in practice. The majority will simply use and grow to work with whatever the default is set to, even if the default is a functionally inferior version, as long as the minimum feature set for creators is maintained.
My source for this is Moodle - which made a transition from TinyMCE to its own home-grown editor Atto a few years ago. While inferior functionally (objectively) compared to the legacy version of TinyMCE they were using, the reality is that Atto did enough to support most things that people needed, and the community plugged the remaining holes as they saw it.
My source for the other end of the scale is one of the Moodle derivatives, which followed the TinyMCE -> Atto route and in the last couple of versions introduced their own editor to replace Atto, called Weka. All three editors remain available, but Weka provides zero table support which is a deal-breaker for some content creators. (Their justification is that they intend content to be consumed by mobile and their mobile app does not support tables.)
Basically as long as whatever editor is not so broken that it's deemed unusable by the majority, whatever the vendor does will just be accepted because people will generally move with change.
A new editor, in whatever capacity, is a hefty undertaking to consider not only users' needs (all sets of users) but also to consider security of whatever formatting is being done, as well as side functionality such as uploaded/embedded media.

Yeah, I know, great title, right...? I just don't know how to better explain it.
Our community has the "Users must acknowledge issued warnings before posting again?" option ticked, because we're very strict in regards to following our community guidelines and rules. However, we've also set up one of the warnings as an no-points anonymous management message to a member for times when we want to tell a member something like "we've edited your thread's title" (ahem ahem... 😛) and don't want them to be intimidated by the "YOU'VE BEEN WARNED, BOY!" popup and the "you must acknowledge..." banner (which some new member just miss altogether and send support requests saying they can't post).
Is there a way to have one (or some) of the warnings not require acknowledgment, or have it a per-warning toggle?
If there isn't, can you make it so? 

I wish for the option (in a future release) to allow members to delete their own accounts. As easy as it is for someone to join, they should also have the option to leave. When doing so, their content should be reassigned as "guest."