The Heff

Wow, another thread starts to descend into chaos. 😕 I was actually quite interested in seeing if the OP would elaborate on how they'd see this working.

I'm curious how you'd see this working on IPS. I imagine it could be a complex innovation depending on how you'd envision handling replies between users who are responding to each other rather than the first post. Facebook comments are sorted by the most relevant or newest, but they aren't a conversation as such. They are usually a direct response to the original content rather than a conversation between the users. Conversations between users typically take place in response to a single comment and are grouped under said comment. In the below image there are four comments that are a response to the post which are completely unrelated to each other. There are, however, replies to one of those comments where a conversation has begun:

I joined in May 2011 and purchased the software for use with a gaming community. Since then it's also been used for a photography community, horse rescue charity and, currently, an astronomy community. I've never, not once, considered leaving for a competitor. The software and support has been top-notch throughout. P.S. Please do tell about @Lindy being locked out of his own data centre...

GDPR is about protecting citizens' privacy and data. As long as the data is destroyed in a secure manner, meaning it cannot be recovered, then you should have no issues. That said, since since you're worried about requirements to give notice or retain data, you should consult a legal professional to satisfy yourself that no such requirements exist.

In my case, I noticed the PayPal errors before the patch was available. I ran the support tool to no avail. This means, of course, that having already run the support tool I wouldn't go and run it again, so the patches remained an unknown. My timing meant that I literally missed them. I'm hoping the calls in this thread result in something more proactive, even if we have to opt in to it.

That depends entirely on the admin's own situation - what is trivial for one admin may not be for another. The point is, some of us want to know when patches are released... We want to be bothered. 🙂

I like that idea of a constant, but not that one. I don't habitually use development builds but I do want to know about patches. Good idea though. 👍

You assume correctly, it is the same. 🙂

Merry Christmas IPS team! 🎅🤶🎄 I have some feedback on the user of forum specific rules to improve the display of them, particularly in ensuring that users posting in forums are aware of forum-specific rules. I use a set of rules for our sales area of our community. It is a dedicated forum space for our users to advertise their property for sale to others. In doing so, we expect them to abide by a set of rules: As you can see, these are clearly displayed as soon as a user enters the specific forum. These are set in the ACP in the area specifically provided for this purpose: If a user follows a fairly traditional workflow, by navigating to the specific forum to create a new post, the rules are seen. However, we now have a different workflow available to users where this will not be the case. There is, on the forum index, a 'Start new topic' button: Clicking this button requires you to select a forum to create the new topic in: A user's workflow may instead therefore be to: visit the index; click on the 'Start new topic' button; and select a forum to post this in. When this workflow is followed, the user in question never sees the forum-specific rules. They are taken to the editor on which the forum specific rules are not displayed: This means that, in the event of a dispute, the user can validly claim to have been unaware of any specific rules they may have breached. Although this can be remedied on a case-by-case basis through tactful moderation, it would be better and more efficient to simply ensure the forum specific rules are visible to users using this workflow to create new topics. Thanks for reading. 🙂

The issue is that we may not know we're affected until something goes wrong, which could result in a lost registration, loss of content, loss of revenue, etc. I'd certainly advocate a more proactive approach to patching since I want to know if there is a possibility that an issue affects my community, rather than find out later when it could be too late. Even if it's just a banner or email notification, that'd be much better.

Not true, since a good user interface can improve efficiency in using it. Just because it’s not the front end doesn’t mean it shouldn’t be improved.

Hello, Can this application be used to create notifications for moderators when a member's subscription expires? We want to be able to monitor subscriptions more proactively. Thanks

It’s literally in the article... at the end.

That’s very odd as on the iOS app I always end up at the last post, with no visibility of the posts before it.