Hisashi

It could be something like this, just an idea

I saw it on your website, one thing I noticed, the comments bar is a little above the description/title of story on mobile, maybe it would be interesting to change the design.

Includes reaction. Not notification. But we can add this later. Now, we want to make sure the comment extension works generally, then we'll work on its detail. You can take a look and test in on my demo site.
the comment on the story app is different from another apps of IPS. We had to implement this extension in another way.

The user who posted receive notification of comments? Including reactions?

The comment extension is ready. It is currently installed and active on my demo site. Before uploading the new version, as you know the review may take time, so it is better to test it. I am testing it. If you have time, please test it on my demo site and PM me your comments and possible problems so I can look into them.
http://ips.valacoding.com/index.php?/events/
Thanks

That's the biggest rewind I've seen from IPS in years of service. 🤯
The marketplace is an excellent showcase for small and big developers to publish their work that would have a potential chance of being bought, you've killed every chance for these products to be discovered.
There are many small modifications that enrich the IPS, and now they will no longer have visibility.
People will now have to apply for paid service one by one, for features that were already available in marketplace.

It was added several releases ago:

Awesome! I'll wait for the next news so, I have some ideas for that, if you're interested in listening.

Yes,
You should enable this feature in the app settings

No, but I think that's a good idea .
I'm working on the comment extension for the stories. It will be released this weekend, after that I'll work on the idea .
 
Thanks for sharing 

That's the biggest rewind I've seen from IPS in years of service. 🤯
The marketplace is an excellent showcase for small and big developers to publish their work that would have a potential chance of being bought, you've killed every chance for these products to be discovered.
There are many small modifications that enrich the IPS, and now they will no longer have visibility.
People will now have to apply for paid service one by one, for features that were already available in marketplace.

@Lindy I sincerely see other ways for you to do this.
As I said earlier, the marketplace is a great showcase that connects developers to IPS customers without leaving here. Having this removed makes life difficult for your clients in trying to find resources quickly without having to go to thousands of developer websites.
My idea is, remove the paid market and keep a free market so that developers can maintain this showcase, so they start offering two versions of the product. A free one, where the user could get it directly from the IPS website, and the paid (full) version that would be described within the product and the user would be redirected to the developer's store. Where he would have all financial responsibility for the product.
Example 1

Example 2

 
IPS could go another route, which in this case would be to charge a small fee to developers who publish resources with a limited free version. And keep the market for developers who support the community with completely free resources.
Many of these resources are made with good heart and are freely available in the market, such as translations that connect people all over the world, and all of these will be "lost".

That's the biggest rewind I've seen from IPS in years of service. 🤯
The marketplace is an excellent showcase for small and big developers to publish their work that would have a potential chance of being bought, you've killed every chance for these products to be discovered.
There are many small modifications that enrich the IPS, and now they will no longer have visibility.
People will now have to apply for paid service one by one, for features that were already available in marketplace.

To be clear, as I was one who brought up the security concerns in this topic, I absolutely was not referring to any known instances or developer here, but merely the potential for it to occur and increasingly so when IPS becomes 100% hands off with third party applications.  Apologies if it came across that way.  I've seen enough security exploits in my own career (not anything IPS or IPS third party related) to warrant the concern.  Again not a reflection of any developer here or the quality of their code, I'm simply proactively thinking about the possibility and considerations regarding preventative measures.  If anyone feels such a security concern is  completely unnecessary or overkill, I would appreciate your particular insight as to why.  I certainly don't know the underpinnings of IPS code, so perhaps there is a reason a client doesn't need to have an elevated concern over it.
I'd still like to know what IPS corporate customers do, if it's anything like the corporations I've worked with (unrelated to my IPS projects), there is full fledged InfoSec and AppSec scanning of all application code before any deployment with Production (real user/member) data.  Generally for a hobby site, I'm not very concerned with data loss (with regular backups available to restore as needed), but I am concerned about data breaches involving PII.

Perhaps this would be the perfect time to come back with the "Requests Forums"? @Matt
Honestly, I feel it's too intrusive to have to message each developer. Creating a topic telling about your project and letting a developer be interested in it is more pleasant for both sides.

I feel you may want to re-read the above. There are no claims anyone has done such as thing that I have read in this topic. Someone has asked about what security precautions they can use on their site when using items that are developed by someone other than Invision.  I'm sure as a developer yourself, you appreciate the importance of someone thinking about the security of their site?

@Lindy I sincerely see other ways for you to do this.
As I said earlier, the marketplace is a great showcase that connects developers to IPS customers without leaving here. Having this removed makes life difficult for your clients in trying to find resources quickly without having to go to thousands of developer websites.
My idea is, remove the paid market and keep a free market so that developers can maintain this showcase, so they start offering two versions of the product. A free one, where the user could get it directly from the IPS website, and the paid (full) version that would be described within the product and the user would be redirected to the developer's store. Where he would have all financial responsibility for the product.
Example 1

Example 2

 
IPS could go another route, which in this case would be to charge a small fee to developers who publish resources with a limited free version. And keep the market for developers who support the community with completely free resources.
Many of these resources are made with good heart and are freely available in the market, such as translations that connect people all over the world, and all of these will be "lost".

@Lindy I sincerely see other ways for you to do this.
As I said earlier, the marketplace is a great showcase that connects developers to IPS customers without leaving here. Having this removed makes life difficult for your clients in trying to find resources quickly without having to go to thousands of developer websites.
My idea is, remove the paid market and keep a free market so that developers can maintain this showcase, so they start offering two versions of the product. A free one, where the user could get it directly from the IPS website, and the paid (full) version that would be described within the product and the user would be redirected to the developer's store. Where he would have all financial responsibility for the product.
Example 1

Example 2

 
IPS could go another route, which in this case would be to charge a small fee to developers who publish resources with a limited free version. And keep the market for developers who support the community with completely free resources.
Many of these resources are made with good heart and are freely available in the market, such as translations that connect people all over the world, and all of these will be "lost".

That's the biggest rewind I've seen from IPS in years of service. 🤯
The marketplace is an excellent showcase for small and big developers to publish their work that would have a potential chance of being bought, you've killed every chance for these products to be discovered.
There are many small modifications that enrich the IPS, and now they will no longer have visibility.
People will now have to apply for paid service one by one, for features that were already available in marketplace.

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

That's the biggest rewind I've seen from IPS in years of service. 🤯
The marketplace is an excellent showcase for small and big developers to publish their work that would have a potential chance of being bought, you've killed every chance for these products to be discovered.
There are many small modifications that enrich the IPS, and now they will no longer have visibility.
People will now have to apply for paid service one by one, for features that were already available in marketplace.

That's the biggest rewind I've seen from IPS in years of service. 🤯
The marketplace is an excellent showcase for small and big developers to publish their work that would have a potential chance of being bought, you've killed every chance for these products to be discovered.
There are many small modifications that enrich the IPS, and now they will no longer have visibility.
People will now have to apply for paid service one by one, for features that were already available in marketplace.

That's the biggest rewind I've seen from IPS in years of service. 🤯
The marketplace is an excellent showcase for small and big developers to publish their work that would have a potential chance of being bought, you've killed every chance for these products to be discovered.
There are many small modifications that enrich the IPS, and now they will no longer have visibility.
People will now have to apply for paid service one by one, for features that were already available in marketplace.

Suggestion
Could have an option for the publisher to inform if the content is for Adult.
When the user enters the video page, a warning appears informing that it is for adults and if they want to continue.

Ex: