AlexWebsites

I use:
 

What's New in Version 1.0.1:
Added TAGs field in the form  

Just saw this mod now. I believe it's really useful every once in a while when status updates discussion gets too much traction. I often lecture people not to use status updates for things that might spark a big discussion. Keep updating it 🙂

I have to say, I'm very happy with this. I just converted two status updates to topics with ease, saved myself so much time. If this ever gets updated, I would say add an option to add tags before the topic is created, maybe under the topic title entry. That's really my only last step I do now.

Works great! Solves the issue of members posting status updates that really should be topics. 

Would be nice to have better video upload ability for users and automatic conversion and such. Back in the day I used to used FFMPEG but it was never as good as the mainstream video platforms and people nowadays default to uploading to youtube and other "large" platforms. I would be interested in cloudflare streaming even if it was a third party app for a video gallery. I'd like to see something like where if a user posts a video to a topic or other area, it embeds it within the post/comment, but lives in the gallery or a video section and not as an attachment. Even for images that get attached, something during the upload process to also add it to gallery at the same time.

@AlexWebsites 
In the beginning, it was best to keep them separate but we no longer have to do that. The tools available to us today helps us to keep things simple.
We just have 1 set of ad units for all sites. 
Today, it's simple to do reports based URLs (sites), key-values (ie. URLs, Page, Usergroup...), etc. 
TIPS:
If you have AdX and Adsense, make sure AdX is set to "Default for Dynamic Allocation" (Admin > Linked Accounts)
(Just make sure because some accounts that had Adsense approved before AdX may have Adsense set to Dynamic Allocation. If this happens to you, you could be losing a lot of money.)
A key-value can be a url, usergroup, page, etc. It can be anything that you want to target. For example, you want to target a specific usergroup with a campaign. Or, maybe you want to target a group of members based on a custom Profile Fields. (This is very handy when a specific customer wants to target a specific group of people on your site.)
Keep your naming convention simple for ad units, rules, etc.  
For ad units, I use the standards when naming my units:
ros_leaderboard ros_medrec ros_largerec ros_skyscraper ros_halfpage ros_banner ros_mobile ros_sticky etc If you require 2 leaderboard ad units on the page, I recommend being specific on the 2nd. For example, name it post_leaderboard ... for another medrec found below the fold, name it bot_medrec, etc.
You can use the same naming convention for Price Rules. 
Naming is very important. You look at the name and it tells you everything you need to know. 
(Keep in mind that your site design may change frequently but you shouldn't do the same with ad units.)
Create Price Rules per ad units. Learn everything you can about price rules.
Use Header Bidding and Adsense (alongside your Ad Manager setup) to put pressure on the auction

No but I can take a look...

When you create a new subscription in SNS, use https or http if you are not SSL

 
With the bouncer app, you'll be provided with a url to the bouncer app. This is the endpoint, the actual url that processes the bounced message.

No, I don’t use an email protocol. You don’t need that for this app. Try deleting those. Are you using email with some other notification because email feedback forwarding from SES will send you an email on each instance if you need that. You don’t need to set up an email protocol in SNS for this app, only https, unless you need that for some reason.

So if you send an email from that email address (same as what is used by IPS) to a bad email, you get an email notification that it bounced but NOT an entry into the database via the endpoint, correct? With email feedback forwarding on, If you get an email saying something bounced, then SES is sending and now you just need to figure out why it’s not going to the topic and then to the endpoint.
That’s all I can think of, I’m really not sure why it’s not working for you. It works for me. 

Nice! Now we just need Amazon SES API Sending instead of SMTP!

InnoDB is officially recommended, yes. In fact some places, like AWS, don't even support MyISAM anymore.
Apache versus Nginx and MySQL vs MariaDB really depend on personal preference, though bear in mind our support team are mostly familiar with Apache and MySQL.

1. It's recommended to just use InnoDB.
2. Yes, it's good to set expiration headers on static content. Usually, around a month for static resources is recommended. For core stylesheets and such, IPS uses a "cache buster" query string any time anything important is updated, so you don't have to worry about old cached content causing issues.
3. Absolutely use opcache with PHP. Even with the default configuration it can make a major improvement in performance.
4. No experience with it personally.
5. Redis can be used to lower MySQL database load on things like view counters and such which are used for both guests and members alike. There's also other cached data that it can use to improve performance. Redis will improve performance primarily if MySQL overhead is high on your server.

@AlexWebsites I have tried both and they both work very well. Redis does a lot more then memcached out of the box and you can still use it with centminmod, along with all the constant tweaking that eva2000 does. 

Under the support section, you'll see to the right system info. If IPS is using Redis, you'll see something like:

Are you using Redis?

 

I reached out to IPS support but they would not say if its planned for a future release. I also reached out to @HeadStand but she's pretty busy right now. @Callum MacGregor has a plugin for sparkpost also. Would be nice to know if IPS is going to include something, if not...I would then outsource it. I prefer not to outsource if something native is coming. 
 

Could it be implemented on 4.5?

Hey @Gauravk,
If you're looking to have your server professionally tuned, I'm happy to offer my services to you.
You can find my rates and contact me here:
 

For new members, I'd like to prohibit them from posting links until they have at least (variable number) posts.  This will help discourage spammers. 
I thought IPS had that feature a few years ago, but it seems to have been dropped.  Please bring it back.
Yep, I'm fully aware of the other anti-spam features in IPS, and I use them.  But there's nothing at all like this.  Think of it as a "backstop" in case a spammer slips by the other features, which seems to be happening with increasing regularity, despite changing the QA response often.

I don’t have any issues, just wondering what urls and what is being appended to them, haven’t tried anything yet. Figured I ask to see if anyone has it configured already to share.

@Paul E.  Yea either would accomplish what I was hoping for.

@AlexWebsites I pass the RSS to IFTTT which then outs it to Facebook and Twitter.  I used to use it for Google+ before it shut down.  For Discord I use Discordrss bot.   Hope this helps.

One major pain tho is that Cloudflare messes up your RSS feed.  So ever since I started using Cloudflare I've been unable to automate my social media presence, which sucks.  If anyone knows how to work around that, a solution would be greatly appreciated, albeit a little off topic.

  

Your apology will not return the lost money and time.
Tell me better what will change in customer notification policy (consider, i may not open ACP for weeks). 

The mobile version can become very fast if IPS changes the concept of CSS rules.
If CSS basic rules are created for mobile version, the responsive design  only contains changes to the desktop, for example ...
.ipsRule {....} @media screen and (min-width:768px) {.ipsRule {...}} @media screen and (min-width:980px) {.ipsRule {...}} @media screen and (min-width:1280px) {.ipsRule {...}} @media screen and (min-width:1440px) {.ipsRule {...}} etc using a media query with only min-width will shorten the volume of CSS and improve the performance of browsers while processing CSS rules.
But, in this version 4.5, I think this will not be done.