Joel R

There's also Custom Notifications by @Fosters available in the Marketplace.  

I'd like to officially lend my support for Amazon SES. 
SparkPost currently costs me $20 / mo on a plan for 50,000 emails (and this was after I suppressed the majority of my email notifications to switch to a lower plan).  The equivalent cost on Amazon SES would be $5 / mo.  This represents cost savings of $180 / yr.  
The cost savings are too big to ignore for independent communities.  

Use the support tool to rebuild cache... maybe reinstall the pluign.

My site tanked 50% after switching from vbulletin and took about 6 months to recover fully.
Check out this article: 
 
Here's another topic on SEO that may be of interest 🙂
 
 

We were averaging around 850-900 visitors every day for over a year with Vbulletin 5. Immediately after the migration we dipped below 500 visitors a day...... then it slowly crawled upwards when after two months we began averaging 700 visitors a day....... that is until today. In the last week we've noticed a slight upward fluctuation and today it just busted past the average taking us to a new site record.

Now, before anyone gets really excited one can see that on July 7th I purchased this plugin. Today is less than a month later - August 7th. Now the problem is throughout this month have I not only installed this plugin and seen it work as Google is reporting no-index and actually de-indexing a lot of thin material, but I've also implemented other changes such as making the site W3C Validate. My particular site really suffered from thin content because we use a RSS Importer to create news articles and those are only small clips created from articles and are published. The plugin no-indexed those particular topics but yet when comments filled out below the OP the no index was changed to index.
Since December of 2018 when I migrated from Vbulletin 5 to IPS4 our traffic has been relatively low receiving anywhere from 500-800 visitors in a 24 hour span. Our highest visitors for one 24 hour day had topped out at a little over 900 visitors. I was just surprised to see our daily stats which has now past the mid way tracking for the day. After 12 hours we've set our own personal record using IPS4 and now pushed past 1,048 visitors. If today's trend continues we'll nearly double our traffic. I'm hoping that the changes made in the last 3 weeks or so are finally being noticed by Google's algorithm. The most difficult thing about SEO work is that one has to make changes and wait for Google to reindex the site which can take weeks or months depending on the size. I'm referring to a delayed observation = change, wait, and see.
Your thoughts?
William

I'd like to officially lend my support for Amazon SES. 
SparkPost currently costs me $20 / mo on a plan for 50,000 emails (and this was after I suppressed the majority of my email notifications to switch to a lower plan).  The equivalent cost on Amazon SES would be $5 / mo.  This represents cost savings of $180 / yr.  
The cost savings are too big to ignore for independent communities.  

I'd like to officially lend my support for Amazon SES. 
SparkPost currently costs me $20 / mo on a plan for 50,000 emails (and this was after I suppressed the majority of my email notifications to switch to a lower plan).  The equivalent cost on Amazon SES would be $5 / mo.  This represents cost savings of $180 / yr.  
The cost savings are too big to ignore for independent communities.  

In general: Yes. You would create a new Record Display template and modify it. 
Showing the recent contributors is not directly possible though. I wish that were a stock feature as well when the Wiki functionality is turned on. 

@FASEOFMARS This is the most interesting topic of the month because it brings up the larger question: what is Invision Community and what does it offer relative to other community software? 
Invision Community is a software that is fundamentally designed for community of content.  This means things like shared discussion, group blogging, group galleries, collaborative wikis. It requires design principles like permanence, organization, structure.  
What you want is a community designed for users.  This means user posts, user blogs, user albums.  It requires design principles like social connections, levels of privacy, and emotion.  
There are important, fundamental distinctions between the two.  Invision Community overlaps with both, but it's fundamentally designed for communities of content.  
I see you struggling with this answer, and I struggle with it too.  My personal community is social in nature, and I have users who treat it exactly like Facebook.  They almost exclusively post status updates.  Sometimes I worry that users don't know how to use forums anymore.  In the past week, I have had: 
- a user report a post, so he can reply back with a comment.  
- a user write his first topic in my Test Topics category, literally the worst and last board you could possibly choose out of a dozen other public boards.  
As the Community Advocate for IPS, I encourage every client to think very hard about evolving themselves into a community of content. You must pair your forums with definitive, valuable, and unique content.   You won't win if you try to stay as a social community of users.

I'd like to officially lend my support for Amazon SES. 
SparkPost currently costs me $20 / mo on a plan for 50,000 emails (and this was after I suppressed the majority of my email notifications to switch to a lower plan).  The equivalent cost on Amazon SES would be $5 / mo.  This represents cost savings of $180 / yr.  
The cost savings are too big to ignore for independent communities.  

I'd like to officially lend my support for Amazon SES. 
SparkPost currently costs me $20 / mo on a plan for 50,000 emails (and this was after I suppressed the majority of my email notifications to switch to a lower plan).  The equivalent cost on Amazon SES would be $5 / mo.  This represents cost savings of $180 / yr.  
The cost savings are too big to ignore for independent communities.  

I'd like to officially lend my support for Amazon SES. 
SparkPost currently costs me $20 / mo on a plan for 50,000 emails (and this was after I suppressed the majority of my email notifications to switch to a lower plan).  The equivalent cost on Amazon SES would be $5 / mo.  This represents cost savings of $180 / yr.  
The cost savings are too big to ignore for independent communities.  

I'd like to officially lend my support for Amazon SES. 
SparkPost currently costs me $20 / mo on a plan for 50,000 emails (and this was after I suppressed the majority of my email notifications to switch to a lower plan).  The equivalent cost on Amazon SES would be $5 / mo.  This represents cost savings of $180 / yr.  
The cost savings are too big to ignore for independent communities.  

I love them! In fact, I'm the bloody bastard that told @CodingJungle to add them in the first place.  It helps me be notified when when tricky members try to create duplicate accounts.  But it's acting as it's designed.  
If your mods won't want these notifications, then instruct them to adjust their notification settings.  
@CodingJungle might also have an SQL query that you can run.  

Thanks for this kind and unexpected topic and appreciate for my work. 🙃🙂

Some interesting and broad choices in there.  I was just curious to see how you discovered Invision Community as a choice within your search.  
Thanks for the compliment on my article.  I sometimes say smart things and impress myself, ha.  

Plugin pending approval
 

@ASTRAPI is helping me move my community over to Wasabi and Cloudflare.  
For any Invision Communities who are currently using Amazon S3, then you may want to seriously investigate the pricing for Wasabi or other S3 compliant services.  Wasabi is significantly cheaper (80% cheaper), charges nothing on exit bandwidth, and compatible with CloudFlare.  It's a drop-in replacement for S3, so for purposes of your ACP, you would treat it like an Amazon S3 storage.  

@FASEOFMARS This is the most interesting topic of the month because it brings up the larger question: what is Invision Community and what does it offer relative to other community software? 
Invision Community is a software that is fundamentally designed for community of content.  This means things like shared discussion, group blogging, group galleries, collaborative wikis. It requires design principles like permanence, organization, structure.  
What you want is a community designed for users.  This means user posts, user blogs, user albums.  It requires design principles like social connections, levels of privacy, and emotion.  
There are important, fundamental distinctions between the two.  Invision Community overlaps with both, but it's fundamentally designed for communities of content.  
I see you struggling with this answer, and I struggle with it too.  My personal community is social in nature, and I have users who treat it exactly like Facebook.  They almost exclusively post status updates.  Sometimes I worry that users don't know how to use forums anymore.  In the past week, I have had: 
- a user report a post, so he can reply back with a comment.  
- a user write his first topic in my Test Topics category, literally the worst and last board you could possibly choose out of a dozen other public boards.  
As the Community Advocate for IPS, I encourage every client to think very hard about evolving themselves into a community of content. You must pair your forums with definitive, valuable, and unique content.   You won't win if you try to stay as a social community of users.

Disagree, I’m the star on my forum.
My mum told me.

V15 released!
Messenger - Conversation - Participants block up top, though not user links, are now formatted, because Joel asked me.

Interesting, what type of issue did you have? I've been using AWS S3 with Cloudflare using Full Strict mode without any problems. I use it for Theme files too, taking 1000's of Requests off my server every hour and bringing the Theme files closer to my international visitors.
Re the brief discussion on Public access to files (Astrapi addressed this in his excellent guide)
In general it's a really bad idea to make your files public on S3, I'd definitely recommend keeping them private whilst permitting/restricting access via IAM permission policies and API Keys.
Amazon have really increased awareness of this when you look at the s3 bucket configuration console, but in there documentation there are still outdated references to be found stating you have to make bucket content public when actually you don't and shouldn't. It's true that 99% of your stored content is going to be everyday pictures of cute cats and hot cars etc but it makes sense to also consider the impact, cost and repercussions of someone directly accessing say, a list of passwords and authentication details shared between staff, or photos uploaded to private gallery albums containing EXIF gps coordinates identifying where a photo was taken. 
If you keep your files and bucket restricted with no public access, you help reduce and mitigate risk. Some quick examples here would be:
you don't have to be as concerned about potential security issues (confidential documents or images uploaded as attachments in price forums or PMs, for example), you help maintain higher GDPR compliance (both with the principles of the GDPR and Data Protection legislation and in terms of complying with your site's published GDPR policy),  and you help negate the risk of people or bots finding and publishing direct URLs to your content and therefore being able to bypass your CDN entirely which poses an escalated risk of higher monthly S3/CDN usage costs, potential for DDoS attacks from a financial attack vector rather than aimed at taking down your site etc. Wasabi, don't get me wrong and I have nothing against it and haven't yet used it myself, is attractive price-wise, but its cost saving is relevant to your individual usage case. S3 is already very low cost, especially if you front it with a CDN like Cloudfront, Cloudflare or both, so 80% of little becomes quite little. Unless you are storing and accessing massive amounts of data, the difference in cost against AWS S3 could be almost negligible for the average IPS community, a few cents or maybe a dollar or two. 
Plus when you start looking at Wasabi's documentation, it becomes apparent that there are some services and functionality that they don't provide or that are planned for a future date. If you a bit of a performance nut enthusiast like me and want to attain increased or 100% Pagespeed ratings, some of those services may become more relevant and necessary to you. For example, if you are going to self host webfonts like Google Fonts, Icomoon and Font Awesome to get to that 100% rating, or you (hopefully) have a good Content Security Policy set up, your are definitely going to need CORS headers.
https://wasabi-support.zendesk.com/hc/en-us/articles/360006985652-How-do-I-use-CORS-and-custom-domains-with-Wasabi-
Again, I'm not intending to distract or diminish Wasabi, just highlighting that there are possibly additional considerations for some IPS communities more than others and that AWS have lots of extra tools, bells and whistles.

Regarding performance, my experiments show a small degradation of performance (15% ~ 20%, measured with a RUM script) during the period I used the preload setting.

One of the biggest reasons for switching from AWS S3 to Wasabi is that you can use Cloudflare. 
Even if you don't have a need for third party storage like Amazon S3 or an S3 compatible storage, you should be investigating Cloudflare anyways with your server admin.