Matt Finger

If you're referring to the React Server Components CVE, then no since it only uses a react front end.

So, for each hour during which a URL is used in the Iframely platform, a hit will be counted, "whether for resolving or displaying content". Since the HTML returned for the embed is really an iframe pointing to Iframely, subsequent views add up to 1 hit per hour as well. Again, please refer to their pricing page for more details.

You'll have to confirm package details with Iframely, however there's nothing indicating you cannot stay on the starter plan indefinitely. I believe the 90 days is how long you have before you even need to pick a plan. Please refer to their pricing page for more details. IframelyPricing - IframelyCompare Iframely pricing plans – find the right option for your needs with flexible API limits, features, and transparent costs.

I get where you're coming from, though I'd like to point out a few reasons why the pricing may be more reasonable than some seem to think Existing oEmbed domains still work and will take precedence over Iframely. In other words, sources such as X, Youtube, Reddit and more will not go through Iframely or incur any hits. So if the pricing doesn't work out then you are still going to have access to content from these major providers. When you setup the integration in the AdminCP, Iframely is restricted based on what domains you've whitelisted, so it isn't like every URL/embed causes an Iframely hit. In fact, most embeds will probably not incur hits with Iframely Their free tier currently includes 1000 hits per month and an extra $4 per 1000 hits, while their business tier includes 10,000 hits for $49 per month. This means, if you don't care for the content cards or "Powered By" icon, you can get 10,000 hits for $36, not $50 Managing an oEmbed directory with this many providers and URL configuration options, each individually tested and maintained over time, is no easy feat. While it certainly is not an absolute necessity on every community, from a developer's perspective their pricing seems very reasonable for what they're offering.

There are a couple not noted in the changelog which are QoL in regards to the code editor IPS template highlighting is supported in the monaco-based code editors When multiple languages are supported, code editors can dynamically determine which language is used. They will also remember user selections Content in code editors is saved as a draft between reloads before submitting.

Yes, the option is inside the editor permissions in the AdminCP

So, long story short, if the custom HTML format is a result of a valid Invision Community 5 Editor Extension, then yes quotes can contain any content that can be created with the editor outside a quote. However, if the custom HTML is a result of a ckeditor4 plugin or direct source editing, then yes pretty much all custom formatting beyond basic bold, headings, italics, etc will be lost. (Hence why it's not recommended to edit source directly in v5)

Yeah, for the new line arrow vs area feedback please put it in a topic in the feedback forums. As for better docs, this is what we have put together at the moment https://invisioncommunity.com/forums/topic/480617-ic-5-editor-extension-javascript-framework/

On our end, nothing has really changed here; certainly not JS interaction with the ads. After investigating your communities, the delay after page load indicates a slow response from the Ad provider as the externally supplied script tags are executed immediately on page load. Yep, I can confirm this issue and see the problematic code. We'll try to get a fix in the next couple releases 🫱‍🫲.

This is actually because the font colors from CKEditor4/IC4 have been preserved. Looks like the original blog post was edited to fix it but for some reason this topic wasn't updated in the process. I shall log an issue for this so that we can address further.

I'll create a bug for this. Just to be clear, by "initial scan", do you mean right after exiting the page editor or every time the page initially loads?

Can you please share the browser version and machine you are using? Yes, that's is correct. The issue ultimately lies in Chrome itself, but we are addressing it to the best of our ability, applying a fix whenever we identify a source of slowness. That said, it's one of those things that doesn't affect any of the devices used by members of our staff which makes it hard to track down.

Yes, it is not currently possible to translate but feel free to create a bug report so this doesn’t get lost.

Yes, post in bugs please so we don't get duplicates, but this is fixed already in the next beta.