Dll

One thing that jumps out is that your choice of music hasn't improved with the new version. 

One thing that jumps out is that your choice of music hasn't improved with the new version. 

One thing that jumps out is that your choice of music hasn't improved with the new version. 

One thing that jumps out is that your choice of music hasn't improved with the new version. 

One thing that jumps out is that your choice of music hasn't improved with the new version. 

Ok grandpa.

One thing that jumps out is that your choice of music hasn't improved with the new version. 

One thing that jumps out is that your choice of music hasn't improved with the new version. 

One thing that jumps out is that your choice of music hasn't improved with the new version. 

As you may know, Invision Community 5 is currently in development, and progress has been great, with many areas starting to come together.
Almost all of the significant code restructuring has been completed, with much progress on the UI and the new theme bearing fruit. A fair few new features are complete, but some aren't quite ready to show, as they need a little love from Ehren.
I wanted to share a little teaser of Invision Community 5; how many new things or changes can you spot?
The small print
Please remember that the features, functionality and UI shown in this little teaser are pre-beta, so they are subject to change. The features and functionality shown here aren't all that has been completed; many new features are 'code-complete' but waiting for some UI polish before we're ready to share more. Essentially, what you're seeing is a work in progress.
We don't have a release timeframe in mind yet, but we'll let you know when we do!

☀️ Welcome to this week's Invision Community Insight! ☀️
Thank you for checking out our weekly, round up post. I hope you have had a wonderful week. Below are a few announcements to bring to your attention. 
 
Current Happenings
For our Cloud customers, I did want to draw your attention to our post: Changes to traffic control. Please ask any questions that you have there. 
 
Our Marketplace Closure announcement was posted this week. We will follow up with more information.
 
On Deck
We have postponed our next release a bit which now makes it our September Release. Spam Improvements and bug fixes are to be expected. You can check out our Spam Improvements Blog for more information. 
Changelog
With that said, changes for version 4 are limited for now but for those that like to see what we are up to line by line, here is the changelog for the week for version 4. 
 
 

Spam has always been an ongoing battle for community owners as spammers find new ways to circumvent existing anti-spam practices.
We have seen an uptick in new ways spammers are breaking through existing defense.
As such, we here at Invision Community continue to look at new ways for community managers to combat against spam. For our September release, we have added several new tools that can prevent spammers from registering in the first place and help combat them even if they register successfully.
Let's take a look at these new tools and settings.
Geolocation based registration filtering
Oftentimes, spam attacks can originate using bots and servers from specific regions. Using our existing Geolocation service, we have now added filters that will allow administrators to hold registrations from specific regions for administrator review, or deny the registration entirely.

Using this, administrators whose communities are under a spam attack from a specific region, can temporarily filter registrations from that region. Multiple regions can be defined at once, and each individual region can either be held for administrator review, or denied completely.
Disposable Email Filtering
We have added an extra option to our spam defense system to filter users registering with throwaway disposable emails, which are often used by spammers to bypass email validation.

During Spam Defense checking, we now also check the domain in use for the registration against a frequently maintained list. If the user passes through the normal spam defense checking, but is found to have a disposable email address, then the administrator can define one of the following actions to be taken.
Allow the registration to proceed Allow the registration, but moderate all posts (which an option to remove moderation after a certain amount) Flag the account for administrator review Register the account but immediately ban it Completely deny the registration For both Geolocation and disposable email filtering, the existing Spam Defense Whitelist is always honored ahead of these filters.
Contact Us Email Verification
A common pain point has been the Contact Us page. While the spam does not go to a user facing location, it does still land in the administrators inbox, or other area defined by the sites Contact Us settings.
To help with this, if a visitor who is not logged in attempts to use the Contact Us page, then in addition to the existing CAPTCHA, the administrator can optionally require the person to verify their email address before the message is ever sent. This applies to all Contact Us behaviors, including any added by third party applications.
Cloud Content Analysis
For our Invision Community Cloud customers, we have also added an additional layer of spam prevention after registration.

After a user registers, or if the account has been dormant, then the first few content submissions will be analyzed using a custom developed algorithm within our platform.
The algorithm takes into factor many different elements of the content, and will rank the post between 1 (not spam) and 5 (definitely spam).
The algorithm can be constantly adjusted and improved based on trends without any intervention from the administrator, and without the need to update to new releases of Invision Community.
The administrator can then decide one of the following actions to take based on the score that was received.
Allow the submission Hold the submission for moderator review Deny the submission completely Of course, specific groups can be made exempt from this and not have their content checked at all, which is useful for sites with subscription based registrations which may not want to have this applied to new subscribers, but do want to have new non-subscribers checked.
Spam can quickly become a headache for most community managers, and these new tools will help further combat it at the source. For our enterprise and Invision Community Cloud customers, being able to check for spam when posting is a new tool which will further filter out more of those annoying topics and posts.
We hope these new features give you additional tools in the fight against spam.
The features and changes presented here are available in the following packages:
Geolocation based registration filtering, Disposable Email Filtering, Contact Us Email Verification: Beginner, Creator, Creator Pro, Team, Business, Enterprise, Invision Community Classic (Self Hosted).
Content Analysis: Beginner, Creator, Creator Pro, Team, Business, Enterprise.

View full blog entry

Adsense and google analytics are very separate things.

Caught me. Very much read that incorrectly 😄
 
John, please could you confirm this is definitely adsense you are referring to?

🎆 🇺🇸 Welcome to this week's Invision Community Insight! 🇺🇸 🎆
Thank you for checking out this weekly round up post. I hope you have had a lovely week and are looking forward to Independence Day celebrations! 
This week's updates from the Invision Community team are below. 🙂 
 
Current Happenings
New Version

Our July beta is ready! Upgrade to the official July release later this month. 
As with all beta releases, upgrading your community is at your own risk. Please make sure you backup before upgrading! 
Here is what is slated for the July release, version 4.7.12. https://invisioncommunity.com/release-notes/
 
Closed for Holiday
We will be observing the Independence Day holiday in the United States on July 3 and 4. Our support services will be delayed but we are happy to asset you as soon as we are able.
 
Finally, for those that like to see what we are up to line by line, here is the changelog for the week for version 4. Changes are limited for now as we focus attention on version 5. More information will be shared about version 5 at a future date. 
Changelog
 

Because downloading it all is still going to block something else from loading. So by moving all the CSS to be pre-loaded, it's actually going to block things that should and would have downloaded first. Browsers are actually quite good at prioritising these days, so you can do more harm than good by messing with the order and preloading potentially large files that don't actually need to be pre-loaded.
In an ideal world the key CSS (eg the CSS needed to render the visible part of the page) would be pre-loaded or hard coded into the html. Just not all of it. 

This is how we see it too. Preloading everything may trick google but it makes it harder for your browser to figure out loading order. 

Because downloading it all is still going to block something else from loading. So by moving all the CSS to be pre-loaded, it's actually going to block things that should and would have downloaded first. Browsers are actually quite good at prioritising these days, so you can do more harm than good by messing with the order and preloading potentially large files that don't actually need to be pre-loaded.
In an ideal world the key CSS (eg the CSS needed to render the visible part of the page) would be pre-loaded or hard coded into the html. Just not all of it. 

Preloading all of the css is not a good idea. 

You should only prefetch files that need to be loaded as a priority, js, CSS or whatever else.

Because downloading it all is still going to block something else from loading. So by moving all the CSS to be pre-loaded, it's actually going to block things that should and would have downloaded first. Browsers are actually quite good at prioritising these days, so you can do more harm than good by messing with the order and preloading potentially large files that don't actually need to be pre-loaded.
In an ideal world the key CSS (eg the CSS needed to render the visible part of the page) would be pre-loaded or hard coded into the html. Just not all of it. 

Because downloading it all is still going to block something else from loading. So by moving all the CSS to be pre-loaded, it's actually going to block things that should and would have downloaded first. Browsers are actually quite good at prioritising these days, so you can do more harm than good by messing with the order and preloading potentially large files that don't actually need to be pre-loaded.
In an ideal world the key CSS (eg the CSS needed to render the visible part of the page) would be pre-loaded or hard coded into the html. Just not all of it. 

Because downloading it all is still going to block something else from loading. So by moving all the CSS to be pre-loaded, it's actually going to block things that should and would have downloaded first. Browsers are actually quite good at prioritising these days, so you can do more harm than good by messing with the order and preloading potentially large files that don't actually need to be pre-loaded.
In an ideal world the key CSS (eg the CSS needed to render the visible part of the page) would be pre-loaded or hard coded into the html. Just not all of it. 

Sorry for the inconvenience; we have deployed a change on our end to hopefully alleviate this concern. 

Yes