The only reason its ideal to encourage them to get a QOTO account is because we garuntee your qoto account on the other servers. In the sense that if someone steals your username from qoto on another server we will delete taht user to free up the name for you. So its a good idea.
While we would like them to be active here strictly speaking they arent required
@design_RG by the way this is a good reason not to delete inactive accounts I havent thought of. Our policy (though I never wrote it down and should) was always to garuntee users from qoto on other services. So users who are only interested in our other services have a real need in some cases to have an account here they never post to.
The social side is just one service in my mind. I would be more than happy to see open source projects move into our GIT instance, use our forum for support, and have no interest in the social media side. Not everyone who wants to be a developer for an open-source project we host should be required to be active here. Hell A lot of the people on gitlab that are developers for my own projects that I pulled in from git have inactive accounts here and only use the GIT side.
@freemo
>> by the way this is a good reason not to delete inactive accounts I havent thought of. Our policy (though I never wrote it down and should) was always to garuntee users from qoto on other services.
I can see that maybe a revision is in order -- as the instance priority imo should be to have active user accounts and no zombie ones. So -- if a person is deserving of using any of the other services (and Discourse should be fully open to new signups if we want it to be useful for new project ideas) this could be verified upon an application, with reference to the applicant other online presences.
@zleap