Matt

Yes. Custom emojis are still available. But only for you, no one else. 

I'd argue that a large number of community owners/administrators know their user base, and have a pretty good idea of how new features and changes would be received. Most owners would be looking at this from a perspective of "how well will this do on my site?" and not "how good is this for me personally?"

Whaaaaaat Matt F coming in with the clutch MVP post of the thread!? That's awesome news, thanks for sharing/teasing!
Respectfully, I do not think your suggestion would really solve anything and in fact would make UX worse. Having extra space above/below the box area that is clickable-to-enable-text-input but is otherwise redundant will be super confusing to users, and would make the post editor not WYSIWYG compliant. Users need to see that what they're typing in the editor (and especially how it is presented in the editor) will be 100% accurate to how the post will appear on publish.
I would recommend waiting for V5 to come out and trying out the icon. While every user's experience will of course be different and there will likely be room for improvement in the UI, in my view I really do not think any user (no matter their level of experience) will miss these two clear icons sitting in the box area:

If a user is so inexperienced that you think they will not know what those buttons do, I will imagine the first thing said user would do is experiment and click those buttons to see what function they served. And there, problem solved.
My only suggestion regarding this topic is that, perhaps the arrow buttons should be permanently visible on the box in the post editor (at present in the V5 alpha those blue icons only appear if you hover your mouse over the box - and that's a scenario where I do believe that inexperienced users may have difficulty, as they may not think to hover over the box in order to reveal a solution they're looking for).

With v5, you can probably save a lot of hassle and just use the backticks to generate inline code. Either way, applications have a framework to add new editor functionality, including buttons.
  CleanShot 2024-05-21 at 10.29.11.mp4  
 

Not to contradict Marc, but there will be a global Table of Contents widget for which you can apply anchors to headings and box titles (stay tuned for more page builder updates 🙂)
Yes, in fact in a few minutes I was able to create a plugin for KBD elements

We're still getting docs together so please be patient but the development of supported buttons and content types is much more streamlined than in cke4.

With v5, you can probably save a lot of hassle and just use the backticks to generate inline code. Either way, applications have a framework to add new editor functionality, including buttons.
  CleanShot 2024-05-21 at 10.29.11.mp4  
 

With v5, you can probably save a lot of hassle and just use the backticks to generate inline code. Either way, applications have a framework to add new editor functionality, including buttons.
  CleanShot 2024-05-21 at 10.29.11.mp4  
 

With v5, you can probably save a lot of hassle and just use the backticks to generate inline code. Either way, applications have a framework to add new editor functionality, including buttons.
  CleanShot 2024-05-21 at 10.29.11.mp4  
 

With v5, you can probably save a lot of hassle and just use the backticks to generate inline code. Either way, applications have a framework to add new editor functionality, including buttons.
  CleanShot 2024-05-21 at 10.29.11.mp4  
 

With v5, you can probably save a lot of hassle and just use the backticks to generate inline code. Either way, applications have a framework to add new editor functionality, including buttons.
  CleanShot 2024-05-21 at 10.29.11.mp4  
 

With v5, you can probably save a lot of hassle and just use the backticks to generate inline code. Either way, applications have a framework to add new editor functionality, including buttons.
  CleanShot 2024-05-21 at 10.29.11.mp4  
 

These changes look really good!  
I am super happy to see the sticky toolbar and the embedding will be a great addition!  Plus, that means my custom Pages pages will now embed like everything else on the site.
I do have a question, will the embedding be editable in the editor?  Most importantly resizing things like YouTube embeds and potentially allowing users to make embedded links into squares, rectangles, etc?  Also, will this hopefully fix YouTube links posted via Zapier to be auto-embedded?

It's always worth ensuring you cover the basics when doing a security review, and this includes:
- Ensuring you are using the very latest version of Invision Community. We have a bug bounty program running where people can test the security of our platform and report weaknesses, this has led to several improvements over the years. Likewise, we also receive reports from security professionals who let us know about potential vulnerabilities, and these are fixed and new versions released in a very timely manner. We do tag releases with a security notice when applicable in our release notes. This is also communicated to your AdminCP.

- Consider multi-factor authentication. If you have signed up for an online service, the chances are your email/username and password has been leaked. You can check with "Have I been pwned". Using multi-factor authentication means that even if someone had your username and password from another service and you re-use the same password across multiple platforms, then they could still not log in. I recommend that everyone does this for those with AdminCP access.

- Always use a unique password for each site you sign up to. Use a password manager (built into iOS, or tools like 1Password) to keep track of them. Consider changing your password every few months.

- Review those with AdminCP access and do not grant it lightly. If you can log into the AdminCP and edit themes and languages, you can add code that can execute any PHP command. It is largely why the AdminCP code has different session management, a different login form and a different URL. It is a very powerful tool.

- Review your logs regularly, especially the admin log in logs and actions to ensure there is nothing remiss inside.

Source mode isn't possible in v5 due to how modern editors manage text. It's not like the old days where it markup was thrown around it and called it good.

What do you need to do that requires source mode? With the new editor in v5 you can add new functionality (and button based styles) still.
Why would anyone do that?

You probably need to go through a Facebook approval process that frankly very few have the energy for.

You know you’ve made a fool of yourself when the realisation kicks in during the post merge time on here.

When you change that setting, it doesn't go back and update images uploaded before that date. Any images over your setting, should be resized and saved. Note that Gallery will always try and store the original image alongside the resized versions.

I still find the claim Someone can misuse card details to be a very alarmist sentence. Card details are not stored on the platform in any way. Nobody could log in, and get your details to use elsewhere or on another account for example.
Feel free to request new features in our feedback area. We have no problem with that, and encourage as much. This is however, not a security flaw in our platform. Its actually a security flaw elsewhere (they got the passwords from somewhere), and flaw in that the users themselves are using the same user/pass combinations.
I'm incredibly confused by your statement on 2FA. If you set up google authenticator for example, yes it requires the user to participate. However it also requires a user to participate to verify using email. You can enforce users to set this up. In the case of old users who have not logged in, you could also enforce password changes for those user, which will send an email to enforce a password change, invalidating all passwords for those users. The tools are indeed there to do this. I understand they aren't the tools you personally would like, however they are present for you to use.
We fully understand you would like to see changes on that. We love the thoughts our users come up with at times. Nobody at all has dismissed your suggestion. What is not going to happen though, is even if we decide to add something of this nature, we are not going to add a new method of logging into the software overnight. I'm sure you can appreciate very quickly making large changes in account security is what causes security issues in the first place? 

Yes. Custom emojis are still available. But only for you, no one else. 

As above, source mode has been removed. Modern editors (all of them) manage markup differently. If you added something the editor couldn't handle via HTML, then it would just remove the unsupported code when you hit edit.

Source mode was added back when we had BBCode and it was.. less than perfect in how it handled it, so it allowed admins to go in and edit it to fix it. Likewise, CKEditor was such a pain to write plugins for, it was easier to just say "oh, use source mode to add stuff". Tiptap is much easier to develop for.

What do you use source mode for?

For example, I add a class to an embedded YouTube video to center it. The embedded block does not respond to the centering buttons from editor.

For records in Pages.
Tables Removing tags, that I cannot remove or repair other ways, like <abbr>-tags Adding styles like ipsButton or ipsMessage

Source mode isn't possible in v5 due to how modern editors manage text. It's not like the old days where it markup was thrown around it and called it good.

What do you need to do that requires source mode? With the new editor in v5 you can add new functionality (and button based styles) still.
Why would anyone do that?

Source mode isn't possible in v5 due to how modern editors manage text. It's not like the old days where it markup was thrown around it and called it good.

What do you need to do that requires source mode? With the new editor in v5 you can add new functionality (and button based styles) still.
Why would anyone do that?

Source mode isn't possible in v5 due to how modern editors manage text. It's not like the old days where it markup was thrown around it and called it good.

What do you need to do that requires source mode? With the new editor in v5 you can add new functionality (and button based styles) still.
Why would anyone do that?