Thank you for your nice feedback. I just created a thread on !fedigrow@lemm.ee , I’ll definitely include this.
FYI, at the moment the only people who can know the list of subscribers to a community are that community’s instance admins, via the database directly, so not something very accessible for mods.
I had not considered that as a possibility/did not know.
That definitely throws a wrench into the subscriber only idea - at least not without admin support.
I assume that most instances have some rule against vote manipulation. A complementary idea I had was to - for a set period, make a post restating the change and request that community members upvote it for visibility. Such as 1x post a week or what-have-you - varying the day to accommodate for folks on different schedules. (Workday folks, vs weekend folks, etc)
Definitely an option without the request for upvotes, regardless of instance rules, but perhaps without as much reach.
Hello,
Thank you for your nice feedback. I just created a thread on !fedigrow@lemm.ee , I’ll definitely include this.
FYI, at the moment the only people who can know the list of subscribers to a community are that community’s instance admins, via the database directly, so not something very accessible for mods.
I had not considered that as a possibility/did not know.
That definitely throws a wrench into the subscriber only idea - at least not without admin support.
I assume that most instances have some rule against vote manipulation. A complementary idea I had was to - for a set period, make a post restating the change and request that community members upvote it for visibility. Such as 1x post a week or what-have-you - varying the day to accommodate for folks on different schedules. (Workday folks, vs weekend folks, etc)
Definitely an option without the request for upvotes, regardless of instance rules, but perhaps without as much reach.
Yes, otherwise we would have probably gone that route.
Your other idea would probably be seen as vote manipulation indeed unfortunately