13.

ImageMagick is used by IPS to handle uploads of images, resizing them, compressing them and creating thumbnails.
Why not give the community admin the option to use ImageMagick to convert uploaded images by users to WebP?
As long as WebP is now accepted by IPS 4.6, I imagine that would be very simple to add this feature to the suite.
I am having a great experience converting the images that I post on my community to WebP. Same quality and much less bytes than JPG or PNG or GIF.

Absolutely agree with you.
It's been a pain to create a portal with IPS, pages is extremely difficult to use, not at all intuitive or friendly. The community here does not give you the code for what you want (like wordpress community often does) and you will not find blogs, websites or your doubts anywhere other than here.
Go with WP for your main website and IPS for the forum. That's it.

Luca,
IPS is still the preferred choice for forums, so your question comes up quite often in entrepreneur groups I belong to. Folks understandably want to learn one platform instead of two, if possible.
Luckily, there's an easy answer.
Wordpress is the standard for blogs. The platform is the CMS of choice for an ever-growing number of businesses, small and large. 
At times, Wordpress is a challenge in terms of security, backups, caching and hosting. But it is a well-supported platform that continues to get better and better for its users.
IPS is at least 15 times (maybe 20) times more difficult to use. Also, and you probably already know this, but if you're self hosting (not using paid IPS cloud services), asking for help in any way is met with extreme resistance and almost outright hostility. The message is brutally clear. I finally just hired a developer to handle the IPS side of things. Life is too short to fear asking questions about a service you pay for, right?
So no, you absolutely do not want to use IPS pages as a substitute for a Wordpress blog. You'll be posting routinely and want a user-friendly platform like Wordpress.
Use IPS only for forums, and possibly the gallery if integrated with your forum. This is critically important if you're self hosting. And this is just as critical: be prepared to solve ALL problems and have ALL questions answered by someone you trust - who is an advanced PHP developer.
Just my two cents.
Best of luck to you.

With my experience of using both WordPress and IPS Community for years, I would choose and recommend WordPress for blogs.
And there is no other choice between those two, honestly, IMO.
IPS isn't bad for what it was initially created for, i.e., for forums. But not more than that.

With my experience of using both WordPress and IPS Community for years, I would choose and recommend WordPress for blogs.
And there is no other choice between those two, honestly, IMO.
IPS isn't bad for what it was initially created for, i.e., for forums. But not more than that.

Yes, make it optional with the ability to upload the custom sound.

Yes, make it optional with the ability to upload the custom sound.

Hi,
Audio notifications were removed from the 4.6 series. My suggestion is to add it back, as our users are missing this feature. Maybe adding an option in the user's account so they can enable/disable it on an individual basis?
Cheers.

ACP > Word Filters
The word filters allow duplicate entries. For instance, if I create a filter:
Replace: <this>
With: <that>
and then create the same filter again, the system will allow it, and we end up with two identical filters.
IMO, the system should check if the filter already exists, and display an error saying that the filter already exists, and preventing us from creating it again.
Thanks

It would be better to use the native method everywhere and fallback to the JS-based method only when needed, so the majority of users of modern browsers won't experience problems just because of a minority of technically backward Apple browsers. It's very easy because native lazy loading works perfectly fine when used with JS-based method at the same time.

It would be better to use the native method everywhere and fallback to the JS-based method only when needed, so the majority of users of modern browsers won't experience problems just because of a minority of technically backward Apple browsers. It's very easy because native lazy loading works perfectly fine when used with JS-based method at the same time.

Getting school flashbacks where you have to wait to move on because the stupid kids still don't get 1 + 1.
 
Fallback like @13. mentioned please.
Your product's main feature should be prioritzed above 2 bad browsers that form a minority.
Altough yes, safari is the 2nd most used browser, it's still only 18% of the world market (and declining).
So a fallback for these should do until it can be removed eventualy.
https://gs.statcounter.com/
 
It's not just a simple scrolling issue but an overall performance killer.

The thing is, unless the image sizes are specified on the page, it doesn't matter which method you use, the page will still jump around as it loads. So, instead of height: auto, as it seems to be at the moment, the height of image thumbnails really should be set to the correct number of pixels. 

It would be better to use the native method everywhere and fallback to the JS-based method only when needed, so the majority of users of modern browsers won't experience problems just because of a minority of technically backward Apple browsers. It's very easy because native lazy loading works perfectly fine when used with JS-based method at the same time.

I didn't like the badges from when I first saw them.  Now that they've been in place for a while, they look even worse.  Plus, I have no idea what their purpose is.
I have not updated my sites yet, probably in a few weeks.
I will definitely not be using the new badge system.

If it's a busy topic, with lots of posts coming quickly, and you don't quote the post you want to be replying to, it might get confusing.

Gutenberg 

Suggestion.
I would love to see separate limits for positive and negative reactions in the IPS:


Thanks.

Partially related suggestion:
 

Well, it's your assumption. No more no less. But what about the diagnostics instead of assumptions? WIll IPS provide informative error instead of just "-200"?
93 frames and 816kb is nothing for GIFs. Most of uploaded GIFs on my forums has a lot more frames and sizes (and a lot of them was uploaded when i used ImageMagic).

As i already said, problem is not related to the count of frames of to the size of the GIF, it just appears with some of GIFs, not matter how large or small they are, or how much frames does they have. I've uploaded bigger GIFs with much more frames and it worked just fine. Played around with timeouts and memory limits, e.t.c. and it does not affected the error with GIFs which has lower size and less frames.
Does not matter, the actual problem is lack of information in the error, that's it.

For me, it is not important which editor to use, but how exactly it will be customized by IPS.

The main thing I hope for is that IPS won't carry over all the same bugs that they added to the current editor and haven't been fixing for years. Such as the complete inability to delete mentions in mobile Chrome, for example:

1620649541089.mp4
As well as get rid of additional overcomplications, such as replacing existing editor functions. For example, fast and easy URL embedding on clumsy and slow:

👍   


👎 

Gutenberg 

Gutenberg 

For me, it is not important which editor to use, but how exactly it will be customized by IPS.

The main thing I hope for is that IPS won't carry over all the same bugs that they added to the current editor and haven't been fixing for years. Such as the complete inability to delete mentions in mobile Chrome, for example:

1620649541089.mp4
As well as get rid of additional overcomplications, such as replacing existing editor functions. For example, fast and easy URL embedding on clumsy and slow:

👍   


👎 

For me, it is not important which editor to use, but how exactly it will be customized by IPS.

The main thing I hope for is that IPS won't carry over all the same bugs that they added to the current editor and haven't been fixing for years. Such as the complete inability to delete mentions in mobile Chrome, for example:

1620649541089.mp4
As well as get rid of additional overcomplications, such as replacing existing editor functions. For example, fast and easy URL embedding on clumsy and slow:

👍   


👎