Simplify Twitter operator spec (#21)

The previous version of this document was overprescribed. The removed
entries were either unnecessary, or have been in flux. In any case, a
lesson is learned here: specify only those things that we know for sure
are the way something should be done. When in doubt, leave it to the
discretion of the role owner.

twitter-operator.adoc

@@ -25,7 +25,7 @@ In general, the idea is that announcements, observations and opinions about the
 
 == Privileges
 
- - Control of the @bisq_network and @bitsquare_ Twitter accounts.
+ - Control of the @bisq_network and (legacy) @bitsquare_ Twitter accounts.
 
 
 == General Requirements
@@ -43,48 +43,17 @@ The operator SHOULD post a monthly report in the form of a comment on the linked
 An example of this kind of report can be seen https://github.com/bisq-network/roles/issues/21#issuecomment-348463070[here].
 
 === Collaboration
-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.
+All tweets to and from the account are posted in the `#twitter` channel of the Bisq Slack team. The operator MAY 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.
 
 === Compensation
-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 link:#reporting[Reporting] above).
-
-=== Automation
-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 link:#compensation[Compensation] above.
-
-=== Delegation
-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.
-
-=== Termination
-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 MUST issue compensation requests to be awarded BSQ for their efforts. For convenience, such reports MAY be kept concise, simply linking to the current month's report (as per link:#reporting[Reporting] above).
 
 
 == Special Requirements
 
 === Notifications
 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.
 
-=== Messages
-a.k.a. "direct messages" or "DMs"
-
-==== Sending DMs
-Pending further discussion, the account SHOULD NOT send any direct messages.
-
-==== Receiving DMs
-Because the account only follows Bisq contributors (see link:#following[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.
-
-=== Tweets
-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 link:#retweets[Retweets]); it MAY also reply to and like certain tweets (see link:#replies[Replies] and link:#likes[Likes]).
-
 === Retweets
 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.
 
@@ -99,11 +68,6 @@ The account SHOULD reply to tweets mentioning @bisq_network in order to correct
 
 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.
 
-=== Quotes
-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.
-
 === Following
 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).
 
@@ -128,31 +92,22 @@ Pending further discussion, the account SHOULD NOT create or maintain any Lists.
 The account username MUST remain "@bisq_network".
 
 ==== Name
-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 name MUST be "Bisq" and MUST NOT be amended to promote certain views, e.g. `[UASF]` or `[NO2X]` as is sometimes done in the larger Bitcoin community.
 
 ==== Profile photo
 The profile photo MUST remain the official "Bisq cat" image.
 
 ==== Header image
 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.
 
-==== Bio
-The bio MUST include the text “operated by @individual”, where @individual is the operator's username.
-
-==== Location
-The location MUST be "Decentralized".
-
-==== Birthday
-The birthday field SHOULD be left blank.
-
 ==== Website
 The website field MUST be set to `https://bisq.network`.
 
 === Verification
 The @bisq_network account is not and CAN NOT become a verified account. Per https://support.twitter.com/articles/20174631[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".
 
 === Ads
-The acccount SHALL NOT purchase any Twitter ads.
+The acccount SHALL NOT purchase any Twitter ads or otherwise 'promote' tweets.
 
 === Analytics
 See link:#reporting[Reporting] above.