With the revelations in these past couple days, it's become quite clear that the current /mlpol/ policy page is out of date and misleading, even intentionally so.
The most misleading statements is in the FAQ:
>What staff has administrative access to the server, and why?
>Atlas: super sexy owner of mlpol.net former /pol/lack, access because yes
This statement is untrue and misleading. Atlas is not the owner of /mlpol/ and has not been for some time now. This really should have been announced prior to the happening, but that's a separate discussion.
It is not acceptable to leave misleading information about the boards page, because it makes adequate transparency and community input impossible, so it really needs to be fixed as soon as reasonably possible. However, changing it is a very serious issue that warrants community discussion on the matter, so let's talk about what the policy board says, what anyone thinks it should say, and how it should be stated.
For starters, the topic above also relates to the staff rules, particularly rules #2:
>2. Staff will maintain a level of transparency with the community
This rule seemed clear enough when it was written, but now it seems as though it lacks specificity and is open to very liberal interpretation. The definition of transparency is easy enough to understand, but the wording "a level of transparency" is evidently vaguer than it seemed. According to recent revelations, informing the community about a change in ownership was not considered to be within that level of transparency, and leaving blatantly untrue statements on the policy page was deemed to be acceptable under said policy.
So the questions are is:
>What exactly is the staff's standard of transparency in regards to what the board deserves to know?
>What kinds of information are considered to be open to the community?
>How is the standard of transparency maintained and enforced, and what is the decision making process for revealing something or leaving it secret?
>What members of staff are responsible/accountable for making sure that the operations and issues concerning /mlpol/'s structure and community are disclosed to the public?
>On what basis is the community able to confidently trust that the staff is being honest and transparent with them, and how are users able to confirm this other than taking the policy page at face value?
>Does the /mlpol/ staff consider it necessary to inform the community about big changes in staffing, policy, ownership of the board or operations before they occur, or only after the matter?
>In the event that it occurs, do the staff have any policies concerning "sensitive" information deemed too risky to expose? (perhaps things such as personal information and doxxable data)
In addition, rule #2 outlines committments to the community made by the staff, but reveal very, very little about how the staff make decisions amongst themselves, how the staff is managed, and most importantly, how the staff policies are enforced. The Staff policy does mention some things thing in regards to rules are enforced and says in four places that staff found to break the rules face "punitive measures" up to immediate dismissal. Now, several of those lines are as-written described as zero-tolerance policies, but that is also questionable, because although rule #1 #3 and #4 serious and clear enough to call for those measures, rule #2 is, apparently, vague enough to be open to interpretation and has even be observably broken and disregarded either through premeditated intent or negligence before. Earlier discussions brought up the issue that zero tolerance policies might put persons on the defensive and potentially harm transparency. There are surely degrees of accountability between doing nothing and outright expulsion, but those degrees are not defined anywhere.
So, questions arise from that:
>How exactly does the /mlpol/ staff discipline itself?
>Are there degrees by which staff consider and account for alleged misconduct?
>Who is/are the final arbiter(s) for considering if/when actions by the staff violate the letter or spirit of the rules?
>How can the users of the board confidently trust that staff are accountable for inappropriate behavior?
>How do the staff con
The complications with rule #2 also proppose issues with rule #3:
>3. Staff will take all community suggestions into account
>As this is a community site and not a top-down dictatorship like some other sites user input is very important
Rule #3 is in essence contingent on the proper application of rule #2, because transparency is necessary for healthy site user input, and site user input is indeed very, very, very important because it distinguishes /mlpol/ from other chans where talking this stuff on /qa/ for weeks on end doesn't actually produce any long-term results. The community cannot voice it's opinions on matters if they are not punctually made aware of them, let alone if the policy page misleads them.
So, questions arise from that:
>Aside from merely using the board, how are the staff able to ensure that their decisions represent the will of the community?
>How, and through what mediums, does the staff make sure that community considerations are taken into account and fascilitate user input?
>On what matters is community consideration deemed to be necessary in decision making?
>How often does the staff seek out direct user input on matters of any kind?
/qa/ - Questions and Answers
Keeping the community together by giving you a voice
135 replies and 31 files omitted.
Anonymous
No.6095
>>6086
>A hierarchy is a must. If not, ask Celestia.
Last I checked, the staff did not claim to be exalted goddesses. They're just humans who signed up at the right time. They're capable of mistakes, and they're equally capable of having bad ideas. That's not a bad thing, it just means that they're people.
>A hierarchy is a must. If not, ask Celestia.
Last I checked, the staff did not claim to be exalted goddesses. They're just humans who signed up at the right time. They're capable of mistakes, and they're equally capable of having bad ideas. That's not a bad thing, it just means that they're people.
>>6094
The point of a policy page, a constitution, or anything like that is to set clear limits on how power can be used along with guidelines on how power should be used.
The point of a policy page, a constitution, or anything like that is to set clear limits on how power can be used along with guidelines on how power should be used.
1623507734.png (90.8 KB, 529x711, F3E3B7A25A9B29A84F461ED3F7D81045-92961.png)
How about someone who thinks policy should be changed propose a specific change of what it should be changed to.
What if members had to vote on putting staff in or out of power? So a vote is needed before a new staff member can be added or an old one can be demoted
>>6099
A lovely idea in spirit, but so easily exploitable by a variety of potential agendas that dont support the site. Beyond that, the implementation of such a policy would be a nightmare.
Janny positions used to be a thing though, just saying
A lovely idea in spirit, but so easily exploitable by a variety of potential agendas that dont support the site. Beyond that, the implementation of such a policy would be a nightmare.
Janny positions used to be a thing though, just saying
>>6099
That is a decent idea to address things like accountability, but as >>6100 to says, it's not exactly easy to implement, and could also be exploitable by discord trannies who just get a bunch of off-site weirdos to bomb strawpolls. Kind of like how that stupid goat and the snailfaggot did so to manufacture the illusion of intolerance to gay pony stuff on the board and scare away users.
However, I'm not really concerned about that, because we stopped being the target of persistent raiders more than three years ago; these days it's just the occasional troll, so there's little need for excessive paranoia.
The real implementation challenge is that /mlpol/ users have very little way of actually knowing who the staff are or how they operate. There's probably only a handful of users who even know the user-names of the staff, and they can't exactly vote on things that they're not aware of. If anything it would end up with brief flame wars with both sides accusing each other of having personal grievances, while the rest of the board just watches not knowing wtf is going on.
>>6100
>Janny positions used to be a thing though, just saying
Used to be a thing? Whatever happened to that? Was that a product of all staff having admin access?
>>6098
I'm starting to feel like this thread is too derailed to even talk about this... Perhaps another thread for that would help us not get confused about everything.
But on that note, I'm starting to feel like the "no generals" rule is kind of oddly applied. Fact of the matter is that we still have generals on /mlpol/, even if the ones with "general" in their name got explicit permission (/sg/ and filly). Existing de-facto generals on this site include:
>Art thread
>Jewish Concentration thread
>Random News thread
>Garbage Can (we have /sp/. Why is this necessary?)
>the roleplay threads on /vx/
>All-encompassing tabletop thread
>Covid thread
>Etc
A thread that lasts several months, either through bumps or being remade, is a de-facto general. By that definition, most of /mlpol/'s content is created in generals. Whether these generals are beneficial or detrimental to the site is open for debate, but I think it's worth reviewing if we want to keep the "no generals" rule, since it hasn't really been enforced.
[Read more] That is a decent idea to address things like accountability, but as >>6100 to says, it's not exactly easy to implement, and could also be exploitable by discord trannies who just get a bunch of off-site weirdos to bomb strawpolls. Kind of like how that stupid goat and the snailfaggot did so to manufacture the illusion of intolerance to gay pony stuff on the board and scare away users.
However, I'm not really concerned about that, because we stopped being the target of persistent raiders more than three years ago; these days it's just the occasional troll, so there's little need for excessive paranoia.
The real implementation challenge is that /mlpol/ users have very little way of actually knowing who the staff are or how they operate. There's probably only a handful of users who even know the user-names of the staff, and they can't exactly vote on things that they're not aware of. If anything it would end up with brief flame wars with both sides accusing each other of having personal grievances, while the rest of the board just watches not knowing wtf is going on.
>>6100
>Janny positions used to be a thing though, just saying
Used to be a thing? Whatever happened to that? Was that a product of all staff having admin access?
>>6098
I'm starting to feel like this thread is too derailed to even talk about this... Perhaps another thread for that would help us not get confused about everything.
But on that note, I'm starting to feel like the "no generals" rule is kind of oddly applied. Fact of the matter is that we still have generals on /mlpol/, even if the ones with "general" in their name got explicit permission (/sg/ and filly). Existing de-facto generals on this site include:
>Art thread
>Jewish Concentration thread
>Random News thread
>Garbage Can (we have /sp/. Why is this necessary?)
>the roleplay threads on /vx/
>All-encompassing tabletop thread
>Covid thread
>Etc
A thread that lasts several months, either through bumps or being remade, is a de-facto general. By that definition, most of /mlpol/'s content is created in generals. Whether these generals are beneficial or detrimental to the site is open for debate, but I think it's worth reviewing if we want to keep the "no generals" rule, since it hasn't really been enforced.
>>6101
>Was that a product of all staff having admin access?
No, that was just a result of everyone having been a jannie for 'long enough', in case of those who began as jannies. Atlas' primary concern was to ensure 24/7 surveillance of the site be they jannies, mods, or admins. After a while, jannies were just sort of transitioned into moderators, for ease of more staff functions than jannies were set to be able to do. This was all on the old code, which hasnt been coded to differentiate between staff positions.
Theres honestly no concern for abuse of admin privs by current staff, but there is something to be said for staff that performs little/no function for the site, especially as pertains to being available for a collective staff meeting
>Was that a product of all staff having admin access?
No, that was just a result of everyone having been a jannie for 'long enough', in case of those who began as jannies. Atlas' primary concern was to ensure 24/7 surveillance of the site be they jannies, mods, or admins. After a while, jannies were just sort of transitioned into moderators, for ease of more staff functions than jannies were set to be able to do. This was all on the old code, which hasnt been coded to differentiate between staff positions.
Theres honestly no concern for abuse of admin privs by current staff, but there is something to be said for staff that performs little/no function for the site, especially as pertains to being available for a collective staff meeting
Anonymous
No.6104
>>6101
Also to the point about generals, the high bump limit and extended catalog veritably ensure that theres never so many active 'generals' that stuff gets wiped. Spike's thread gets bumped every few weeks, because the 'generals' arent being remade every other second, hence enforcement of that rule is more geared toward prohibiting nonsense generals like the nightly twilight thread
Also to the point about generals, the high bump limit and extended catalog veritably ensure that theres never so many active 'generals' that stuff gets wiped. Spike's thread gets bumped every few weeks, because the 'generals' arent being remade every other second, hence enforcement of that rule is more geared toward prohibiting nonsense generals like the nightly twilight thread
Anonymous
No.6105
>>6102
>being available for a collective staff meeting
I've noticed this has been an issue. Perhaps there should be a bulletin/schedule of sorts.
>being available for a collective staff meeting
I've noticed this has been an issue. Perhaps there should be a bulletin/schedule of sorts.
Just for the record.
1- I firmly oppose ANY change to the police page.
2- I think that buckling to demands for such a change will open the door for more and more "democratic" changes. We all know what the word "progressiveness" means.
3- The Admin/staff is well versed about to manage efficiently this board.
4- Community input wasn't or isn't hindered for a policy page at all, therefore calls to change it because of that is void.
5- Happenings and Generals are a guidance and mostly apply to newfags.
7- Even to the naked eye the policy page appears not to reflex reality, in practice is meaningless because /mlpol/ was and is working smoothly. Again, if it isn't broken, don't fix it.
7- At this point, I no longer believe that calls to change the policy page are in good faith, even a nigger can see that.
1- I firmly oppose ANY change to the police page.
2- I think that buckling to demands for such a change will open the door for more and more "democratic" changes. We all know what the word "progressiveness" means.
3- The Admin/staff is well versed about to manage efficiently this board.
4- Community input wasn't or isn't hindered for a policy page at all, therefore calls to change it because of that is void.
5- Happenings and Generals are a guidance and mostly apply to newfags.
7- Even to the naked eye the policy page appears not to reflex reality, in practice is meaningless because /mlpol/ was and is working smoothly. Again, if it isn't broken, don't fix it.
7- At this point, I no longer believe that calls to change the policy page are in good faith, even a nigger can see that.
>>6106
Are you going to make an argument against changing the policy page besides "fuck democracy" and the old "appeal to tradition"?
Democracy has its faults but what other methods are there to keep power in check?
Are you going to make an argument against changing the policy page besides "fuck democracy" and the old "appeal to tradition"?
Democracy has its faults but what other methods are there to keep power in check?
Anonymous
No.6108
>>6107
>what other methods are there to keep power in check?
>to keep power in check
Okay, here it is the key argument. For those asking change, the real issue is the Administration.
Allow me to repeat my mantra: If it isn't broken, don't fix it.
>what other methods are there to keep power in check?
>to keep power in check
Okay, here it is the key argument. For those asking change, the real issue is the Administration.
Allow me to repeat my mantra: If it isn't broken, don't fix it.
Anonymous
No.6109
>>6106
>1
That's fine. It's still worth discussing though.
>2
>"progressiveness"
Who the fuck said anything about progressiveness?
>3
That's debatable.
>4
>void
What, are you talking about? This is just a /qa/ thread, not a fucking court.
>5
>Mostly appy to newfags
What is supposed to distinguish newfags from oldfags on an anonymous board? Rules should be applied evenly.
>5
There are definitely things worth fixing/considering. It was only yesterday that the errors were amended
>6
Stop lumping everyone together.
[Read more] >1
That's fine. It's still worth discussing though.
>2
>"progressiveness"
Who the fuck said anything about progressiveness?
>3
That's debatable.
>4
>void
What, are you talking about? This is just a /qa/ thread, not a fucking court.
>5
>Mostly appy to newfags
What is supposed to distinguish newfags from oldfags on an anonymous board? Rules should be applied evenly.
>5
There are definitely things worth fixing/considering. It was only yesterday that the errors were amended
>6
Stop lumping everyone together.
>>6106
You're welcome to all those impressions, however I contest your allegations of good faith. I use mis-directive tactics deliberately, and I've gotten what I came for. The refined policy is quite precise in its wording. The policy retains and overtly emphasizes that ultimate discretion is with staff. That's an advisable and strategic position, as staff stands primarily against subversion and infiltration. That discretion is emphatically for bans and such, but is implied for the entire running of the site. Meaning, the application and interpretation of the rules, which are intended to be more in spirit than in rigid lines, are at the discretion of staff.
Beyond that, data has been updated, and staff will hopefully be arranging for a Tea time With uhhhhh I recommend booz, btw[/-] ..... or some other form of board interactivity. It seems a win for all sides
You're welcome to all those impressions, however I contest your allegations of good faith. I use mis-directive tactics deliberately, and I've gotten what I came for. The refined policy is quite precise in its wording. The policy retains and overtly emphasizes that ultimate discretion is with staff. That's an advisable and strategic position, as staff stands primarily against subversion and infiltration. That discretion is emphatically for bans and such, but is implied for the entire running of the site. Meaning, the application and interpretation of the rules, which are intended to be more in spirit than in rigid lines, are at the discretion of staff.
Beyond that, data has been updated, and staff will hopefully be arranging for a Tea time With uhhhhh I recommend booz, btw[/-] ..... or some other form of board interactivity. It seems a win for all sides
1623543067_1.jpg (2.4 MB, 1784x2760, jones-jewish-revolutionary-spirit-cover1.jpg)
>>6107
>Are you going to make an argument against changing the policy page besides "fuck democracy" and the old "appeal to tradition"?
A captain and a helmsman are needed to keep the ship steady, sailors not.
If those people are not up the task, a mutiny may ensue; however this is not the case at all and calls to restrict their power because of muh future conflicts are a sure source of friction and troubles. Also this is not Friendship.
>Are you going to make an argument against changing the policy page besides "fuck democracy" and the old "appeal to tradition"?
A captain and a helmsman are needed to keep the ship steady, sailors not.
If those people are not up the task, a mutiny may ensue; however this is not the case at all and calls to restrict their power because of muh future conflicts are a sure source of friction and troubles. Also this is not Friendship.
1623543360.jpg (71.2 KB, 800x450, little-pony-ice-cream-800x450.jpg)
Anonymous
No.6113
Anonymous
No.6114
>>6112
Don't treat the "demanding party" like it's one person.
Also, what demand are you referring to?
Don't treat the "demanding party" like it's one person.
Also, what demand are you referring to?
>>6111
A ship withoutsailors seamen is dead in the water.
>As this is a community site and not a top-down dictatorship like some other sites user input is very important
Thanks for hearing out our concerns.
>>6110
I am also looking foward to more interactive chances. Although it can be hard to find the time especially considering the circumstances globally.
A ship without
>As this is a community site and not a top-down dictatorship like some other sites user input is very important
Thanks for hearing out our concerns.
>>6110
I am also looking foward to more interactive chances. Although it can be hard to find the time especially considering the circumstances globally.
1623548630.png (109.1 KB, 1042x1024, My Little Pony - Dr. Whooves - Facehoof.png)
>>6115
>top-down dictatorship
>fictitious exaggerations
This sounds to me like those lesbians that were fingered when young and now proclaim to be rape survivors.
>top-down dictatorship
>fictitious exaggerations
This sounds to me like those lesbians that were fingered when young and now proclaim to be rape survivors.
I am so appalled by all of the shit-flinging here. Posters seem more concerned about each other's "motives" thinking it'll somehow end the site, or making passive aggressive remarks about obscure drama and "gaslighting", than actual policy discussion.
So far the only things about the policy discussed have been:
>Please edit the fee incorrect lines on the page so it's accurate (done)
>Consider the future of the no generals rule? (no conclusion reached)
>Maybe staff should have clearer rules for themselves? (no progress into what that even means)
122 replies and everything except that has just been shit-flinging. Leave the fucking drama at the door.
So far the only things about the policy discussed have been:
>Please edit the fee incorrect lines on the page so it's accurate (done)
>Consider the future of the no generals rule? (no conclusion reached)
>Maybe staff should have clearer rules for themselves? (no progress into what that even means)
122 replies and everything except that has just been shit-flinging. Leave the fucking drama at the door.
>>6117
>So far the only things about the policy discussed have been:
And leave everything like it was.
>So far the only things about the policy discussed have been:
And leave everything like it was.
1623551007.png (1.7 MB, 1024x1042, 297B4789BF3087D9F47FDDFF81C58749-1785914.png)
>>6117
>Consider the future of the no generals rule
As I understand it, and as Atlas explained to me, the reason Generals were so hated was because they were their own self contained communities that disrupted a greater unified board identity and participation. On /mlp/ they were especially hated for useless bumps and making the board feel smaller, although on /pol/ they were basically necessary to sustain many threads on the extremely fast paced and spam-filled board. I don't really think the no-generals rule is helpful on /mlpol/ and I don't really care to keep it. I don't know if I've ever enforced it.
I don't think any rule should be touched until all of them are revised.
>Maybe staff should have clearer rules for themselves?
Staff rules have really never been very clear. Code of conduct is generally brought up when someone perceives an infraction, rather than in any formally stated list of rules. There has historically been a hierarchy, but as Elway mentioned in another thread that has mostly melted away. There's a general rule to consult other moderators before taking action, and as much as possible all decisions are as collective as possible, but you don't need permission to delete child porn links. In any case, I think that staff rules are mostly an internal matter anyways.
[Read more] >Consider the future of the no generals rule
As I understand it, and as Atlas explained to me, the reason Generals were so hated was because they were their own self contained communities that disrupted a greater unified board identity and participation. On /mlp/ they were especially hated for useless bumps and making the board feel smaller, although on /pol/ they were basically necessary to sustain many threads on the extremely fast paced and spam-filled board. I don't really think the no-generals rule is helpful on /mlpol/ and I don't really care to keep it. I don't know if I've ever enforced it.
I don't think any rule should be touched until all of them are revised.
>Maybe staff should have clearer rules for themselves?
Staff rules have really never been very clear. Code of conduct is generally brought up when someone perceives an infraction, rather than in any formally stated list of rules. There has historically been a hierarchy, but as Elway mentioned in another thread that has mostly melted away. There's a general rule to consult other moderators before taking action, and as much as possible all decisions are as collective as possible, but you don't need permission to delete child porn links. In any case, I think that staff rules are mostly an internal matter anyways.
>>6120
> I don't really think the no-generals rule is helpful on /mlpol/ and I don't really care to keep it.
Basically what I'm getting at. I'm not adamant about removing it, but idk if it does is any good.
>I don't think any rule should be touched until all of them are revised.
Also a fair consideration, although given the past 120 posts idk how we can go about getting there in a productive/civil manner.
>I think that staff rules are mostly an internal matter anyway
That's a decent point, although I think it's worth it for the community to be aware of internal matters.
As you just noted, the staff situation has changed before, and will probably change again in the future for whatever reason. Making users more aware of internal matters would give Anons the chance to voice concerns and decide if they're comfortable with changes as they occur.
> I don't really think the no-generals rule is helpful on /mlpol/ and I don't really care to keep it.
Basically what I'm getting at. I'm not adamant about removing it, but idk if it does is any good.
>I don't think any rule should be touched until all of them are revised.
Also a fair consideration, although given the past 120 posts idk how we can go about getting there in a productive/civil manner.
>I think that staff rules are mostly an internal matter anyway
That's a decent point, although I think it's worth it for the community to be aware of internal matters.
As you just noted, the staff situation has changed before, and will probably change again in the future for whatever reason. Making users more aware of internal matters would give Anons the chance to voice concerns and decide if they're comfortable with changes as they occur.
>>6116
Uhhh I think you may have misquoted the wrong guy. I just reposted the policy page stuff. And made a semi-serious seamen joke.
Unless that's a reply to the reply to the chain of replies.
Everybody has their talents, wisdom and skillsets for various situations and tasks.
>>6117
>>6118
I think an example of the rules in motion provide greater accessibility. I think that would be nice. Right now the history behind them is there for sure. So discussing the context behind the rules and the intent would be nice.
>>6120
This provodes context and the reasoning behind the rule so it's not simply no generals, it's no generals that take the cues from cesspools.
Uhhh I think you may have misquoted the wrong guy. I just reposted the policy page stuff. And made a semi-serious seamen joke.
Unless that's a reply to the reply to the chain of replies.
Everybody has their talents, wisdom and skillsets for various situations and tasks.
>>6117
>>6118
I think an example of the rules in motion provide greater accessibility. I think that would be nice. Right now the history behind them is there for sure. So discussing the context behind the rules and the intent would be nice.
>>6120
This provodes context and the reasoning behind the rule so it's not simply no generals, it's no generals that take the cues from cesspools.
>>6122
This, the no generals could be reworded for clarity, but it's like a restaurant sign that says "no animals", where exceptions are allowed for service animals, who know how to behave.
>>6120
Speaking of staff rules, can we assume that any remaining staff have learned their lesson and have been put on notice about NOT harassing, doxing, editing/deleting posts, and otherwise targeting users who make them mad but otherwise arent breaking any letter or spirit of a rule?
This, the no generals could be reworded for clarity, but it's like a restaurant sign that says "no animals", where exceptions are allowed for service animals, who know how to behave.
>>6120
Speaking of staff rules, can we assume that any remaining staff have learned their lesson and have been put on notice about NOT harassing, doxing, editing/deleting posts, and otherwise targeting users who make them mad but otherwise arent breaking any letter or spirit of a rule?
>>6123
>Speaking of staff rules, can we assume that any remaining staff have learned their lesson and have been put on notice about NOT harassing, doxing, editing/deleting posts, and otherwise targeting users who make them mad but otherwise arent breaking any letter or spirit of a rule?
If we say yes, will you stop shitting up the entire site with your autism?
>Speaking of staff rules, can we assume that any remaining staff have learned their lesson and have been put on notice about NOT harassing, doxing, editing/deleting posts, and otherwise targeting users who make them mad but otherwise arent breaking any letter or spirit of a rule?
If we say yes, will you stop shitting up the entire site with your autism?
>>6124
>the entire site
Hey, you decided it was a good idea to lock my thread. How'd THAT work out for ya?
>if we say yes, will you
So long as it's not an empty promise, sure. I'm not one of the aggrieved parties and I cant speak to/for them, but so long as the site is safe from *ahem* those shenanigens going forward (I cant imagine any other pressing issues to address and I know itll be a cold day in hell before I'm anywhere near the loop XD) my case is rested. Serious question though; in the event of future incidents where anons feel it necessary to object or report staff behavior, how should they go about resolving the issue? Even before I started hammering the point, there has been some observable contempt thrown around about even discussing the policy.
Tl;dr a bit more community involvement is all I can really offer.
>the entire site
Hey, you decided it was a good idea to lock my thread. How'd THAT work out for ya?
>if we say yes, will you
So long as it's not an empty promise, sure. I'm not one of the aggrieved parties and I cant speak to/for them, but so long as the site is safe from *ahem* those shenanigens going forward (I cant imagine any other pressing issues to address and I know itll be a cold day in hell before I'm anywhere near the loop XD) my case is rested. Serious question though; in the event of future incidents where anons feel it necessary to object or report staff behavior, how should they go about resolving the issue? Even before I started hammering the point, there has been some observable contempt thrown around about even discussing the policy.
Tl;dr a bit more community involvement is all I can really offer.
>>6125
Dude, stop. You're being a bitch.
Shitting up other threads is not going to help you accomplish your goal, and it's quite frankly been in thorn in the side to the rest of us who want to have a productive conversation about policy.
Dude, stop. You're being a bitch.
Shitting up other threads is not going to help you accomplish your goal, and it's quite frankly been in thorn in the side to the rest of us who want to have a productive conversation about policy.
>>6123
Well, until a few months ago, we had a staff member who would edit user's posts, would get into arguments with users, and - when he got angry, and while still posting anonymously - would claim that he was a moderator and would threaten action against them. We were going to fire him for doings exactly the above, getting into an argument, threatening to delete a user's post, and then actually deleting a post, but knowing we would do this, he quit before we could fire him. So yes. Since he's been gone, the last few months have been pretty good actually, and I'd say the staff is solid, if maybe we could use another member.
>>6125
>Hey, you decided it was a good idea to lock my thread. How'd THAT work out for ya?
Are you claiming that you de-railed OP's thread in retaliation for John Elway locking that "why was I banned" thread? You have bitched about your personal grievances in the Fallout: Equestria thread, the board emojis thread, and the Seb thread on /sp/, and basically every recent thread on /qa/, often posting with a name, I guess hoping it will give you greater credibility with users. Is all of that your response to Elway locking your thread?
[Read more] Well, until a few months ago, we had a staff member who would edit user's posts, would get into arguments with users, and - when he got angry, and while still posting anonymously - would claim that he was a moderator and would threaten action against them. We were going to fire him for doings exactly the above, getting into an argument, threatening to delete a user's post, and then actually deleting a post, but knowing we would do this, he quit before we could fire him. So yes. Since he's been gone, the last few months have been pretty good actually, and I'd say the staff is solid, if maybe we could use another member.
>>6125
>Hey, you decided it was a good idea to lock my thread. How'd THAT work out for ya?
Are you claiming that you de-railed OP's thread in retaliation for John Elway locking that "why was I banned" thread? You have bitched about your personal grievances in the Fallout: Equestria thread, the board emojis thread, and the Seb thread on /sp/, and basically every recent thread on /qa/, often posting with a name, I guess hoping it will give you greater credibility with users. Is all of that your response to Elway locking your thread?
1623612857.jpg (130.4 KB, 1078x1110, 68cc89050ba30045e8771146a546249e46323acf7fd26a501e9052a105736060_1.jpg)
>>6125
>Hey, you decided it was a good idea to lock my thread. How'd THAT work out for ya?
pic
Seriously though, while I remain utterly perplexed as to what, if anything, you're actually angry about, I think you can relax about the "shenanigans". I don't know of any shenanigans currently going on, and we have no plans of incorporating any in the future.
>Serious question though; in the event of future incidents where anons feel it necessary to object or report staff behavior, how should they go about resolving the issue? Even before I started hammering the point, there has been some observable contempt thrown around about even discussing the policy.
Well, as I've said in previous threads, anyone who has any issue they would like to discuss is welcome to make a thread about it here, and that's generally how these issues are brought up. Ironically, this very thread was a discussion on site policy until you decided to derail it. I also have made it clear that I'm willing to personally listen to issues that users bring up to me privately via Discord, and I have heard and dealt with such concerns before. As I've said, I don't guarantee anyone that they will necessarily get the outcome they would like, but we're always willing to hear user complaints. However, if you're just going to spam incoherent, angry walls of text at me and make obnoxious demands, then I reserve the right to ignore you and/or bantz on you. This site is basically a service provided free-of-charge to the mlpol community, and staff are unpaid. You're honestly entitled to absolutely nothing here; we try to accommodate as many users as we can, but if you really don't like the way the site is being run there's nothing stopping you from fucking right off and starting your own. MLPOL at one time had as many as four independent sites operating simultaneously, this just happened to be the one the community settled on.
Anyway, I'll stop derailing the thread now. Apologies to OP.
[Read more] >Hey, you decided it was a good idea to lock my thread. How'd THAT work out for ya?
pic
Seriously though, while I remain utterly perplexed as to what, if anything, you're actually angry about, I think you can relax about the "shenanigans". I don't know of any shenanigans currently going on, and we have no plans of incorporating any in the future.
>Serious question though; in the event of future incidents where anons feel it necessary to object or report staff behavior, how should they go about resolving the issue? Even before I started hammering the point, there has been some observable contempt thrown around about even discussing the policy.
Well, as I've said in previous threads, anyone who has any issue they would like to discuss is welcome to make a thread about it here, and that's generally how these issues are brought up. Ironically, this very thread was a discussion on site policy until you decided to derail it. I also have made it clear that I'm willing to personally listen to issues that users bring up to me privately via Discord, and I have heard and dealt with such concerns before. As I've said, I don't guarantee anyone that they will necessarily get the outcome they would like, but we're always willing to hear user complaints. However, if you're just going to spam incoherent, angry walls of text at me and make obnoxious demands, then I reserve the right to ignore you and/or bantz on you. This site is basically a service provided free-of-charge to the mlpol community, and staff are unpaid. You're honestly entitled to absolutely nothing here; we try to accommodate as many users as we can, but if you really don't like the way the site is being run there's nothing stopping you from fucking right off and starting your own. MLPOL at one time had as many as four independent sites operating simultaneously, this just happened to be the one the community settled on.
Anyway, I'll stop derailing the thread now. Apologies to OP.
Anonymous
No.6132
>>6130
>until a couple months ago we had a few staff members
>one of whom did so on advise and/or witnessing other staff members
>started fights by calling out other staff for rules violations, or a refusal to actually operate in any staff capacity, preferring to hugbox on discord and pretend the users have no need/right to know significant changes to the staff, namely Atlas
Fixed those for you. It would be too troublesome to amend them all, but that will suffice.
>are you claiming
No, but it illustrates bad faith from the outset. If being an asshole is actionably against the rules, that's an important detail for a site committed to free expression to declare.
One last correction. Nigel is fine by the way, he is developing his game more. We talk every so often, and he's proven to be a decent listener when you can phrase things correctly.
For the observer, this is an important detail because aside from spelling corrections, the only posts I edited or deleted were Nigel's, except those requested by a user.
Go ahead Lotus. Claim the same.
As far as getting piss drunk and doing stupid shit, yep. Guilty as charged. This is among several reasons I openly stated my removal from admin was appropriate, and my subsequent quitting was then cursory.
But as the new policy states/implies, ultimate discretion is up to staff; to punish Ninjas' misdeeds or forgive Lotus' included. But now, regardless of what anyone thinks of me, the cat is out of the bag.
As far as derailing, this has everything to do with policy, from the literal written policy, to its interpretation, as well as the attitude with which it is applied, and especially under what circumstances it is being violated and why.
[Read more] >until a couple months ago we had a few staff members
>one of whom did so on advise and/or witnessing other staff members
>started fights by calling out other staff for rules violations, or a refusal to actually operate in any staff capacity, preferring to hugbox on discord and pretend the users have no need/right to know significant changes to the staff, namely Atlas
Fixed those for you. It would be too troublesome to amend them all, but that will suffice.
>are you claiming
No, but it illustrates bad faith from the outset. If being an asshole is actionably against the rules, that's an important detail for a site committed to free expression to declare.
One last correction. Nigel is fine by the way, he is developing his game more. We talk every so often, and he's proven to be a decent listener when you can phrase things correctly.
For the observer, this is an important detail because aside from spelling corrections, the only posts I edited or deleted were Nigel's, except those requested by a user.
Go ahead Lotus. Claim the same.
As far as getting piss drunk and doing stupid shit, yep. Guilty as charged. This is among several reasons I openly stated my removal from admin was appropriate, and my subsequent quitting was then cursory.
But as the new policy states/implies, ultimate discretion is up to staff; to punish Ninjas' misdeeds or forgive Lotus' included. But now, regardless of what anyone thinks of me, the cat is out of the bag.
As far as derailing, this has everything to do with policy, from the literal written policy, to its interpretation, as well as the attitude with which it is applied, and especially under what circumstances it is being violated and why.
>>6121
>I think it's worth it for the community to be aware of internal matters. As you just noted, the staff situation has changed before, and will probably change again in the future for whatever reason. Making users more aware of internal matters would give Anons the chance to voice concerns and decide if they're comfortable with changes as they occur.
I want to address this as well as the suggestion in >>6099 that hiring or removing staff should be up to a vote, and why I disagree strongly with both.
First, I'll address the idea of staff elections. mlpol.net staff is something like a law enforcement agency, or a tech support group. And it sort of makes sense to have a position like a Sheriff be elected, because who is selected as sheriff sets a tone for policy. Do you want loser enforcement or stricter enforcement? Do you trust the guy at the top or not? And that's what voting is best at: expressing the preferences of the community, and what people want for their community.
But each new and existing member of staff isn't the equivalent of Sheriff. They are more an equivalent of a Sheriff's deputy, someone who is hired to bring about the vision of the law or the guy on top. And it makes absolutely no sense to have every single deputy or lower employee be elected. For one, there is no way the people voting can possibly have enough information to make that decision. They can only get a minimum of information and maybe hear a few arguments, but they can never do what an actual hiring committee can do, which is spend several days over a period of weeks interviewing, gathering information, and considering.
Second, if you need to fire someone, especially on a board like this, then you need to do it immediately before that staff member can find a way to retaliate. Sure, you can give a staff member in charge the power to suspend an account but not formally "fire" the offending staff member, but then this leads to a whole trial over whether the dismissal was correct, and this leads back into the problem of the userbase at large not having sufficient information. Context of actions is important, and the people actually on staff will know more about context than the userbase at large.
Democracy is great at being a measure of community preferences, as most people know what they want and don't want, and what they like and don't like. It isn't so great as a way of making complex and information-heavy decisions. The general policy direction of the site is a perfectly valid subject of a vote, but staff hiring? Not so much.
And further, the userbase may be moderated or have tech support from a staff member, but they don't have to interact with and work with the staff member on a daily basis. mlpol.net staff is a team. As mentioned before, one of the unwritten but still persistent internal staff rules is that as much as possible, moderator actions and changes to the site code are decisions that are to be made with the consultation and approval of at least one other staff member. This rule hasn't applied to blatant spam, but still it is a rule we try to follow. The staff, to be effective, must cohere and work together as a team. The people who are on staff have much more interest in making sure incoming staff are people they can get along with, and much more of an understanding of how the new person will work with the group. Another reason why staff hiring should remain with staff.
As for how the users are supposed to know who is and is not on staff, this actually refers back to another staff rule: when you post as a member of staff, you never post anonymously, or with an anonymous moderator capcode. You always post under your staff handle, and a capcode. This way, users know who the staff are, and who is saying what. It probably wouldn't hurt to add a staff members list to the policy page.
Finally, on the subject of "awareness of internal matters," much of what occurs has no business being public. Most of what happens within staff is complete silence, statements like "deleted cp links," personal bullshitting, or discussing the best way to make a color cycle. Trivialities that have no relevance to people outside. And when there is disagreement, it can be personal in nature. Staff leaving or entering is often surrounded by drama and is the result of interpersonal relationships within staff. And we have little desire to let drama spill out onto the board. That's actually yet another one of our little unwritten rules. Keep disagreements and drama within staff. The staff has, since march, been very harmonious and there would be little to report besides "all quite within the staff discord server." But even if it weren't quiet, internal matters ought to remain internal matters.
[Read more] >I think it's worth it for the community to be aware of internal matters. As you just noted, the staff situation has changed before, and will probably change again in the future for whatever reason. Making users more aware of internal matters would give Anons the chance to voice concerns and decide if they're comfortable with changes as they occur.
I want to address this as well as the suggestion in >>6099 that hiring or removing staff should be up to a vote, and why I disagree strongly with both.
First, I'll address the idea of staff elections. mlpol.net staff is something like a law enforcement agency, or a tech support group. And it sort of makes sense to have a position like a Sheriff be elected, because who is selected as sheriff sets a tone for policy. Do you want loser enforcement or stricter enforcement? Do you trust the guy at the top or not? And that's what voting is best at: expressing the preferences of the community, and what people want for their community.
But each new and existing member of staff isn't the equivalent of Sheriff. They are more an equivalent of a Sheriff's deputy, someone who is hired to bring about the vision of the law or the guy on top. And it makes absolutely no sense to have every single deputy or lower employee be elected. For one, there is no way the people voting can possibly have enough information to make that decision. They can only get a minimum of information and maybe hear a few arguments, but they can never do what an actual hiring committee can do, which is spend several days over a period of weeks interviewing, gathering information, and considering.
Second, if you need to fire someone, especially on a board like this, then you need to do it immediately before that staff member can find a way to retaliate. Sure, you can give a staff member in charge the power to suspend an account but not formally "fire" the offending staff member, but then this leads to a whole trial over whether the dismissal was correct, and this leads back into the problem of the userbase at large not having sufficient information. Context of actions is important, and the people actually on staff will know more about context than the userbase at large.
Democracy is great at being a measure of community preferences, as most people know what they want and don't want, and what they like and don't like. It isn't so great as a way of making complex and information-heavy decisions. The general policy direction of the site is a perfectly valid subject of a vote, but staff hiring? Not so much.
And further, the userbase may be moderated or have tech support from a staff member, but they don't have to interact with and work with the staff member on a daily basis. mlpol.net staff is a team. As mentioned before, one of the unwritten but still persistent internal staff rules is that as much as possible, moderator actions and changes to the site code are decisions that are to be made with the consultation and approval of at least one other staff member. This rule hasn't applied to blatant spam, but still it is a rule we try to follow. The staff, to be effective, must cohere and work together as a team. The people who are on staff have much more interest in making sure incoming staff are people they can get along with, and much more of an understanding of how the new person will work with the group. Another reason why staff hiring should remain with staff.
As for how the users are supposed to know who is and is not on staff, this actually refers back to another staff rule: when you post as a member of staff, you never post anonymously, or with an anonymous moderator capcode. You always post under your staff handle, and a capcode. This way, users know who the staff are, and who is saying what. It probably wouldn't hurt to add a staff members list to the policy page.
Finally, on the subject of "awareness of internal matters," much of what occurs has no business being public. Most of what happens within staff is complete silence, statements like "deleted cp links," personal bullshitting, or discussing the best way to make a color cycle. Trivialities that have no relevance to people outside. And when there is disagreement, it can be personal in nature. Staff leaving or entering is often surrounded by drama and is the result of interpersonal relationships within staff. And we have little desire to let drama spill out onto the board. That's actually yet another one of our little unwritten rules. Keep disagreements and drama within staff. The staff has, since march, been very harmonious and there would be little to report besides "all quite within the staff discord server." But even if it weren't quiet, internal matters ought to remain internal matters.
Are there any other policy questions worthy of their own thread, so I can put an end to this dumpster fire?
>>6158
Okay, are there any other policy discussions that people would rather remain kept contained in this shit-flinging thread, before I make any more posts?
Okay, are there any other policy discussions that people would rather remain kept contained in this shit-flinging thread, before I make any more posts?
>>6168
Nobody? Nobody's going to act offended if I ask a new question or raise a new topic about the policy page?
Nobody? Nobody's going to act offended if I ask a new question or raise a new topic about the policy page?
Anonymous
No.6172
>>6173
As far as I can tell, only these lines:
>Using information for any purpose, including selling to others, data mining for malicious purposes, or for any reason are grounds for immediate removal from staff position, permanent banning from the site
>Staff found to deliberately delete threads or posts to avoid discussing important topics about the site can face punitive measures up to and including dismissal
>Staff found to be deliberately removing community suggestions to avoid changes on the site or push their own agenda will be subject to punitive measures up to and including dismissal
Nothing else is on the policy page. Just guidelines for those particularly egregious acts.
As far as I can tell, only these lines:
>Using information for any purpose, including selling to others, data mining for malicious purposes, or for any reason are grounds for immediate removal from staff position, permanent banning from the site
>Staff found to deliberately delete threads or posts to avoid discussing important topics about the site can face punitive measures up to and including dismissal
>Staff found to be deliberately removing community suggestions to avoid changes on the site or push their own agenda will be subject to punitive measures up to and including dismissal
Nothing else is on the policy page. Just guidelines for those particularly egregious acts.
>>6175
You are neglecting a key phrase.
>All moderation decisions and bans are ultimately up to staff's discretion
Translation: the enforcement (or refusal to enforce) of those staff guidelines is subject to staff.
Ergo: staff has rules, but only if they feel like it. And, if they feel like going beyond the rules in their enforcement, thats something they also reserve the right to do also.
Legalese is a bitch
You are neglecting a key phrase.
>All moderation decisions and bans are ultimately up to staff's discretion
Translation: the enforcement (or refusal to enforce) of those staff guidelines is subject to staff.
Ergo: staff has rules, but only if they feel like it. And, if they feel like going beyond the rules in their enforcement, thats something they also reserve the right to do also.
Legalese is a bitch
[Reply] [Last 50 Posts] [Last 100 Posts] [Last 200 Posts]
You are viewing older replies. Click [View All] or [Last n Posts] to vew latest posts.
Clicking update will load all posts posted after last post on this page.
Post pagination: [Prev] [1-50] [51-100] [101-150] [151-185] [Next] [Live (last 50 replies)]
185 replies | 47 files | 24 UUIDs | Page 8
[Add to Thread Watcher]