Matt
Management
-
Joined
-
Last visited
Everything posted by Matt
-
The following languages are supported: English, French, German, Italian, Portuguese, and Spanish. We are not going to build a simple API because as explained above, pushing and pulling data from AWS services is only a tiny part of the architecture. -
While many in this topic are experienced and capable server administrators, a high number of our customers are not. A good amount of support we manage is to do with CDNs, Redis, Elasticsearch, etc where server configurations are incorrect, the service is badly set up or unsupported versions are used. I'm not here to debate the technical ability of our customers, though. There is more to sentiment analysis than just fetching the numbers from an AI service. What we are interested in are trends over time, and for that we have separate architecture running Python, which is the most efficient language when it comes to raw math, aggregating and making sense of the data which is sent back directly into the cloud platforms database; there is actually very little product code for this reason. Even simple things like pulling the data and sending it to AWS for processing isn't done via CRON or a task, we use a custom task runner within our cloud platform to do it. It's more efficient to develop this way. I realise we haven't spoken much about our cloud platform, but there's more to it than just using the AWS SDK in the product code.
-
We're using an AWS service to return sentiment based on the content of the posts. We can then do an average to find the sentiment for the topic. Eventually, we'll look at building out guided moderation features based on this, and concepts such as alerting moderators to topics trending negatively, etc. It's an expensive service, so it'll be a feature on our top tier packages. @Matt Finger has been writing python code on our cloud platform to crunch the numbers and aggregate them so we can view trends over time.
-
I understand why you feel like this. For 20 years we've been a downloadable source company and everything has been focused around that. However, we have to move with the times. As people demand more interactivity and sophistication from apps, we need to use technologies outside of a standard "LAMP" stack offered by most self hosting companies. A small number of customers have the ability to set up a PHP server, a MySQL server, a Node server, Redis, and configure authentication systems including WAF and CDN, most do not and when you rent out that much hardware, the cost per month won't be far from one of our platform costs. Social media platforms have increased expectation of what a modern web app can do. Leveraging cloud architecture allows us to develop features that can compete on a UI level. Worth noting that "Sentiment" is only there as we test out the system, that's not final UI. 🤣
-
Guys. Sentiment down 10%.
-
Good work everyone: Sentiment: [63.5000] Positive | [14.2500] Negative | [7.8750] Neutral
-
I adore and love this reply Andy! You are just the best! I love free puppies!! We can literally code a "vibe check" feature now! "Sorry, your post does not pass the vibe check" *opens PHPStorm*
-
Now it's just 44% positive. Well done for killing the vibe, guys. Sentiment: [44.0000] Positive | [21.8000] Negative | [11.2000] Neutral
-
Sentiment analysis puts this topic and it’s replies as 99% positive. Sentiment: [99.5000] Positive | [0.0000] Negative | [0.5000] Neutral
-
Welcome to our April developer's update! This month has seen the developers work on a variety of features coming to our cloud platform, some of which we've been testing here, which include real-time updates on what members are viewing and when they are typing replies and an image scanner which not only identifies what is in the image, it also tags it for search results. Furthermore it can also hold images for moderation if they contain nudity, etc. We've got more to come and will announce them as they are finished. The cloud platform features leverage multiple technologies such as node, JWT security, and AWS specific functionality, enabling us to build pretty impressive new features quickly. As we expect more sophistication and algorithmic crunching from our web apps, we're starting to break out of the PHP and MySQL limitations to deliver forward-thinking features. Of course, we have plenty of new features coming to all platforms, including the self-hosting version; I can talk about a few changes we've made but let's start with some housekeeping. There will not be a full release for May, although we will be releasing several betas throughout the month. We are taking this time to finalise a few bigger changes to our codebase. For those running their own servers, we are updating the minimum PHP requirement to 7.4 and the recommended version to 8.0. If you're not sure which version you currently use, now is a good time to check! We are working on PHP 8.1 compatibility still and are aiming to have that finished for June's release. The list of fixes already in the June release is as follows: Core - Fixed an issue that may prevent attaching audio files to content. - Fixed a minor typo in the forms.css template. - Fixed upload area not showing on minimised editors for guest users. - Fixed an issue where post counts were incremented even when a new item was held for approval via the profanity filters. - Fixed an issue where filters and sort options do not persist between deleting members in the Admin CP. - Fixed an issue where sitemap may show entries from offline applications. - Fixed an issue where support account may show as the latest registered member. - The Editor Preview Button was removed from ACP Editors. - Removed the deprecated FX Country code from the Geolocation class. - Removed the ability to rebuild existing attachment thumbnails due to an incompatibility with content attributes required for lazy-loading. Gallery - Fixed an issue with the followed Gallery Images page. - Fixed an issue with rebuilding thumbnails on legacy communities where the original image may no longer exist. Pages - Added the missing `__indefart_cms_page` language string. - Fixed an issue where sorting by a numerical field could duplicate the option with an incorrect label. - Fixed issue with 'image upload' block carousels not working in the sidebar - Fixed an issue where custom Yes/No fields, when used as a database filter, were ignored when further sorting. Converters - Fixed an issue rebuilding some profile photo images. Commerce - Improved performance when updating a large number of existing purchases. - Removed deprecated Amex Express checkout options. - Fixed a niche issue where a renewal invoice (for manual payment) would not be generated if a PayPal Subscription was cancelled on an active purchase. Calendar - Fixed an issue where the day view wouldn't show today's events when it's being used as the default calendar view. A few items still being finished before being sent for peer review include tweaks to search logging. Andy added the ability to specify which groups to log anonymous search sessions. We got some feedback that bot searches were polluting the results, making it hard to discern search trends from members over time. As we anonymise the search data, we can't pick out specific member groups once it's been written. Andy also moved the search logs to their own page to reduce confusion over what the data represents. Andy has also been working on some activity stream improvements to bring a "Solved/Unsolved" filter option to allow you and your members to find unsolved (or indeed solved) topics quickly. This will require a search index rebuild after upgrading. You may also find a few new hook points added, which are in the following locations: \IPS\Helpers\Form\Upload::populateTempData() This is called from within processUploads and allows you to modify the data before it is saved into core_files_temp. \IPS\applications\forums\modules\front\forums\topic::finishManage() This is called during manage() and allows you to modify the $topic before it is returned to \IPS\Content\Controller. If you have to overload manage() in your apps, you may find this a better hook point. \IPS\Content\Search\Index\indexData now allows $content modification before it is stored via an extension in /applications/{app}/extensions/core/SearchIndex That's it for this month! -
It seems that this mod is a little too ….radical.
-
Hi Nigel. As Marc said please start a ticket or alternately you can contact sales (https://invisioncommunity.com/contact-us) and we will be happy to answer your questions.
-
Can you take a screen shot of the right hand filter box when it is not showing any topics? We are working on some tweaks for this feature to make it clearer which forums have been selected.
-
We're using ElasticSearch here, so we can use the 'Any time' option. MySQL just struggles, so we had to limit it to Specified Time Period > 365 days. if ( \IPS\Settings::i()->search_method === 'elastic' ) { $streamDateOptions['all'] = 'stream_date_type_all'; }
-
You can also filter each forum to show just unsolved posts.
-
I believe the sharing links only show in forums that are accessible by guests. If you need to log in to see a forum, the share links won't be visible (as most services will just return a 404).
-
This has now been fixed, and the button should work correctly.
-
Hi Philip, our records show that your license expired in February this year, which is why you've been moved from the clients group.
-
Opentype beat me to it. We have a guide on recovery mode:
-
I understand what you mean. You're saying your site is my-site.com, and you have created a directory 'forums' and put the forums in there, so the JSON should report the site as 'my-site.com' but it's reporting 'my-site.com/forums'. I'll open an issue.
-
We tend to iterate through releases. We like to get a solid feature out there and see how it fares in the real world. If we take on too much feedback, we’d not ship for months.
-
-
I like this idea. We rarely write internally needed APIs. We use Zapier which saves us a lot of development time and costs.
-
There’s definitely more gears than cheers here. Ok, so we don’t “ignore” feature requests. We have thousands of customers that use their communities in diverse ways. We can’t add every single feature that is requested, but over the years we have added hundreds. We look for trends, and feature requests that are asked for from multiple sources many times. Things like better stats, more robust spam management, better mod tools, improvements to SEO come up often and as such are regularly featured in new releases. Features like this one find little support among other customers so we are less likely to include it. It’s also worth mentioning that we have a vision for our product and sometimes good feature suggestions don’t fit it. It’s the same with any piece of software. Gaps in our functionality are often filled by our marketplace authors. As for trying to link what our marketing department are doing to being less able to develop code, that’s just not what happens internally. There’s more to Invision Community than just me. I probably do the least amount of coding here now. I appreciate your input nonetheless.
-
We removed post numbers a long time ago because they are not a consistent metric. Consider: Post Hidden Post Hidden Post Post Post Post You will see: Post A - #1 Hidden Post B- #2 Hidden Post C- #3 Post D - #4 Post E- #5 Post F - #6 "Post number 4 is the winner!" - you refer to Post D. However, a member will see: Post A - #1 Post D - #2 Post E- #3 Post F - #4 So to them Post F is the winner. Likewise when you delete a post or two after mentioning "See post 4", post 4 is actually post 6 when you delete two posts, etc. It's just not a reliable number. If you leave gaps in the post number to skip hidden posts, it becomes obvious to members where there have been deleted posts or hidden posts.
