Issue: bisq-network/roles#21
To provide a single, authoritative and trustworthy @bisq_network Twitter account that anyone can:
-
follow, to stay up to date with bisq;
-
@mention, to reference bisq in conversation with others;
-
@mention, to ask questions about bisq and provide feedback
Twitter is an important communication channel and news source for many people in bisq’s larger community. Most bisq contributors operate personal Twitter accounts, but no one bisq contributor should, by default, maintain control over the official @bisq_network account. This document specifies the requirements for assuming the role of @bisq_network Twitter account operator, such that (a) potentially any contributor can fulfill the requirements with minimal time and effort, and (b) account followers get consistent, valuable from it.
In general, the idea is that announcements, observations and opinions about the bisq network should come from contributors' own personal Twitter accounts, and that the primary role of the @bisq_network account is to follow these contributors and 'curate' their content by liking and retweeting it. This principle is expanded upon in various sections below.
The operator SHOULD post a monthly report in the form of a comment on the linked GitHub issue for this role. The report SHOULD include (but is not limited to):
-
A recap of the statistics available in Twitter Analytics;
-
Screenshot(s) from Twitter Analytics as appropriate;
-
Operator commentary
An example of this kind of report can be seen here.
All tweets to and from the account are posted in the #twitter channel of the bisq Slack team. The operator SHOULD discuss tweets with other contributors in this channel, especially when in doubt whether or how to respond. If necessary, the operator MAY escalate specific tweets to specific contributors by reaching out to them directly. In any case, the operator SHOULD use their discretion in collaborating or escalating tweets in whatever way they see fit, so as to ensure an accurate and timely response to questions or comments about bisq on Twitter.
The operator MUST issue monthly BSQ compensation requests to cover the cost of their labor. For convenience, such reports MAY be kept concise, simply linking to the current month’s report (as per Reporting above).
The operator MAY automate the fulfillment of any of the requirements in this document, as they see fit, so long as such automation does not degrade the quality of content coming out of the account.
Note that any efforts to automate the operation of the account SHOULD be submitted as a separate compensation request, i.e. SHOULD NOT be grouped in with the operator’s usual monthly compensation requests as described in Compensation above.
In case of extended absence not exceeding one month, the operator MAY delegate their responsibilities to another individual of their own choosing ("the delegate"). If the operator is unable to attend to their responsibilities during any such absence, then they MUST delegate their responsibilities as follows.
The operator MUST mention that delegation is occurring, and for what duration, in a comment on this role’s linked GitHub issue.
The delegate MUST carefully read and adhere to all requirements in this document, including 2FA setup and changing the "operated by @individual" statement in the account bio. Failure to fulfill requirements may result in the partial or complete confiscation of the operator’s BSQ bonding.
The delegate MAY issue a compensation request for their services rendered.
The account operator MAY terminate their participation in this role by giving notice at least one month in advance.
Notice of termination MUST be given in a comment on this role’s linked GitHub issue. The reason for this requirement is to ensure that other individuals interested in playing this role can subscribe to that GitHub issue and know that they will hear about it if and when the current operator decides to leave.
The operator SHOULD set themselves up to receive Twitter notifications in whatever way they see fit, such that they are able to fulfill the requirements that follow below.
a.k.a. "direct messages" or "DMs"
Because the account only follows bisq contributors (see Following below), it is unlikely that the account will receive any direct messages at all. In the event that direct messages are received, the account SHOULD reply as the operator sees fit, providing that the reply is factual in nature, and not an expression of the operator’s personal opinion or views.
The account SHOULD NOT tweet anything on its own. The logic behind this requirement is simple: the bisq network is not a person; it has no opinions of its own and it cannot make observations of its own; therefore it has nothing to tweet about. What the account SHOULD do is monitor bisq contributors' Twitter activity and retweet their bisq-related tweets (see Retweets); it MAY also reply to and like certain tweets (see Replies and Likes).
The account SHOULD retweet bisq-related tweets from the people it follows, subject to the discretion of the account operator. Contributor tweets should not be "mechanistically" retweeted, but rather curated to avoid the account becoming repetitive or noisy, and to avoid retweeting negative or otherwise unproductive content.
The account MUST retweet release announcements made by bisq network repository maintainers as soon as possible, and preferably immediately, but in any case within 24 hours.
The account SHOULD reply to tweets that ask @bisq_network a direct question. When feasible, the reply SHOULD contain the answer to the question being asked, but the reply MAY also simply redirect the questioner to a more appropriate venue, e.g. the bisq forum or a particular bisq repository’s GitHub issues.
The account MAY reply to tweets mentioning @bisq_network, if the operator believes that the most effective action would be to tweet a reply directly from the @bisq_network account.
The account SHOULD reply to tweets mentioning @bisq_network in order to correct objective inaccuracies.
The account SHOULD NOT engage in extended Twitter conversations and MUST NOT engage in contentious debate or argument. If extended conversation or "defense" of bisq is necessary, the account should let individual contributors engage from their own personal Twitter accounts.
The account MAY quote tweets if it is deemed by the account operator to be a more effective technique than retweeting or replying alone.
Quoting MUST NOT be used to express the operator’s personal opinions or observations (for the same reasons detailed in 'Tweeting' above), but MAY be used to express facts about the project.
The account MUST follow current bisq network contributors. A current contributor is anyone who has had a compensation request accepted in the preceding 3 months UNLESS the contributor (a) does not have a Twitter account, or (b) indicates they do not wish to be followed (see below).
The account MAY follow any number of alumni contributors. An alumni contributor is anyone who has had a compensation request accepted in the past, but who has not had a request accepted in the last 3 months. The specific set of alumni contributors that is followed is left to the operator’s discretion.
The account MUST unfollow anyone who indicates they do not want to be followed.
The account MUST NOT follow anyone other than the accounts enumerated above.
The account MAY like any bisq-related tweet at the operator’s discretion. The definition of "bisq-related" is also left to the operator’s discretion, but the operator SHOULD take a conservative approach here. If in doubt, leave it out.
The name MUST be "bisq" and MUST NOT be amended to promote certain views, e.g. [UASF] or [NO2X] as is often done in the larger bitcoin/crypto community.
The header image MAY be changed at the operator’s discretion, but the operator SHOULD discuss any such changes with a quorum of other contributors first to ensure rough consensus if the image is changing significantly.
The bio MUST include the text “operated by @individual”, where @individual is the operator’s username.
The website field MUST be set to https://bisq.network.
The @bisq_network account is not and CAN NOT become a verified account. Per Twitter’s verification documentation, verifying organization or company accounts require "an organization or company email address". The bisq network is not a company or traditional organization and as such has no "organization email addresses".
See Reporting above.