Chris Anderson

Go to your ACP and navigate to Themes and click on the "Edit HTML and CSS" option as shown below:

Navigate to:
core/front/global/globalTemplate
Append the following just above </body> which is located at the very bottom:
      <a rel="me" href="https://Your Mastodon Server Name/@UserName"></a>
    </body>
</html>
This will place a hidden rel="me" on the front page of your site that your server should see and validate you.
<a rel="me" href="https://Your Mastodon Server Name/@UserName">Mastodon</a>
"If" you include the underlined "Mastodon" as shown above you will get a clickable link shown up on your webpage which probably is not ideal which is why I did not include it.  You could also place the rel="me" code on other pages you might have on your site but you need to include the page in your profile such as shown below:
https://mysite.com/aboutme.html
Your profile will show your website as being validated but with the page appended to the website.
Depending on your server it could take anywhere from a few seconds for your domain to be validated to several hours.

Free plugin awaiting approval.

@Andy Millne The latest uploaded version seems to have corrected both issues.  Thanks for posting such timely updates.

I've submitted a new minor version release (1.3.1) that should resolve this. thanks for letting me know.

As it currently stands in Version 4.7.11 Beta 2, once you click on the check mark shown below the deletion process is executed, and no trace of the action is logged.
I suggest that upon clicking on the check mark the request is moved to a new section called "Deletion Requests Completed" with the photo and email redacted as they would be considered PII.  But the deletion request and the day it is completed should be logged for auditing purposes.
This way you could detail later that a member by the name of "X" who joined on a particular date was ultimately deleted "per request" on another particular date.

As it currently stands in Version 4.7.11 Beta 2, once you click on the check mark shown below the deletion process is executed, and no trace of the action is logged.
I suggest that upon clicking on the check mark the request is moved to a new section called "Deletion Requests Completed" with the photo and email redacted as they would be considered PII.  But the deletion request and the day it is completed should be logged for auditing purposes.
This way you could detail later that a member by the name of "X" who joined on a particular date was ultimately deleted "per request" on another particular date.

That endpoint might work "today" but I would recommend reaching out to Amazon to see if that endpoint will always work.  I would hate to have you start relying on the data being available to your users via S3 and one day that endpoint no longer works as Amazon really wanted you to point to a specific endpoint like: s3.us-east-2.amazonaws.com which is what worked for me in the past.
 

@Square WheelsYou're not alone in getting the error message above.  I was able to set up and use Amazon S3 in the past using the provided instructions but last night I spent several hours trying to get it to work once again to no avail on several different sites.  The error message doesn't provide sufficient clues as to what might be amiss.

Well that's depressing. It's unfortunate to see such longstanding issues persist.
I understand that addressing them might not be a priority in the current 4.X version, however, it's disheartening to learn that this matter has been lingering for quite some time without a resolution.
IPS Staff: It would be reassuring to know if there are any plans or considerations for addressing these concerns in future updates.
Kind regards.

Please check out the deprecation discussion above as you are not the only one concerned about this feature (and other features) being deprecated.

For my taste, “account deletion” is too well hidden under “security and privacy”. 
I would suggest to either change the tab name or to give this function its own tab, like this third-party solution does it. 

We have not posted anything formally, but you are free to create your own LMS if you like.

Why not do a license check for testinstall.  If running under that license type disable all functionality you wouldn't want running under that kind of environment. 

Let me introduce the feedback and the new 'MyClassifieds' area.
Here are some screenshots of the work in progress:
User block:

MyClassifieds page (very early stage)

Add feedback modal when seller confirm a deal

Use this:
 

v2.3.0 is currently pending approval
NEW
Settings added a new check against your site's "Allowed email domains for registration" configuration Tracker 'Sender' information has been split out to separate 'Name' & 'Email address' columns added quick search functionality (Name, email address and IP address are searched) added the ability to submit reports to AbuseIPDB Filters added "No issues detected" filter added "Email domain not allowed" filter added "Email domain block advised" filter added "Reported"/"Not reported" filters changed "Banned" filter's language string to "Email banned" filters will now only display if they are relevant to your chosen settings. Some examples: the "Email banned" filter will be available only if the check against your site's "Non-Registrable Email Addresses" configuration is enabled. the "Email domain not allowed" filter will be available only if the check against your site's "Allowed email domains for registration" configuration is enabled. mailcheck.ai results are now included when using the 'Disposable email address' filter

Ideally there should be a “staging mode” with settings to turn off payments, emails and things like that. 

I think that's a great idea, and I'm going to add it to my resource hehe.
YOINK!!!

I've just uploaded a new version (1.3.0) to the marketplace that includes support for excluding user groups from Connections results.
 

I'm currently self-hosted and have made the appropriate code change and the app appears to be working as "expected".  Thanks for the quick fix posted above. 😀 

OK - I'll look into it over the weekend.

The longest awaited iPhone feature is almost here, native iOS notifications, and we couldn't wait to ensure it is enabled for your Invision Community.
Invision Community 4.7.9 is iPhone push notification ready for when Apple release their latest iOS update later this month. This means you'll finally get notifications on your phone, even when you do not have your browser open, to alert you of new content on followed items and more. A feature Android owners have enjoyed for a while.

With notifications, you can have an authentic native app experience with built-in Invision Community features such as the manifest editor.
The manifest editor allows you to edit your theme icons, colours and URL for when your members add your community to their phone's homepage. This manifest file helps mobile devices understand how to display your community site when launched from the home screen.

Your members can add your community to their home screen with the share button. Once it has been added, it looks and feels like a native app downloaded from the App Store.
With Apple finally allowing native notifications and Invision Community's mobile-ready UI coupled with the manifest editor, you can have a real app experience without needing a mobile app.
iPhone PWA.mp4
We intend to bring more functionality and ease of use to mobile devices over the coming releases.
We hope you're looking forward to iOS native push notifications as much as we are!
The features discussed in this announcement are available in both Invision Community and Invision Community Classic.

View full blog entry

I’ll do it. Never had this request before, that’s why it isn’t there.  👍

Coming soon...

As it already exists for Online Events, it would be a nice improvement to add an external link field (display as a button on Front End) in the form event creation for Physical Event.
When organizer proposes physical events, they often have a dedicated website to register attendees (outside of Invision).