realaravinth/fediparty-wiki
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Update FediverseParty agreement

Browse source
This commit is contained in:
lostinlight 2019-12-29 15:41:22 +00:00
parent d9104a9a69
commit c5994077dc
1 changed files with 6 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
FediverseParty-agreement.md
View file

@ -1,15 +1,13 @@
1. Account - schould have one (long, strong) password known to all the editors.
**1.** Account will have one (long, strong) password known to all the editors.
2. It must have rules that we all agree upon and list somewhere for own reference. For starters:
**2.** Account will post about anything [^1]Fediverse related but not violating rule (3). New software announcements / reshares, welcoming any Fedi newcomer movements (TwitterExodusScotland etc), promoting Fedi projects, posting useful bits of info about Fedi (nicely formated with points •, emojis, paragraphs, etc).
a) posts dedicated to anything *Fediverse related but not violating rule (b) - new software announcements / reshares, welcoming any Fedi newcomer movements (TwitterExodusScotland etc etc), promoting Fedi projects, posting useful bits of info about Fedi (nicely formated with points •, emojis, paragraphs, etc).
**3** Posts must not be explicitly *politically* or *religiously* aligned because not all editors will have the same opinion about controversial Fedi topics / dramas - better leave such posts for one's personal accounts. Please, be friendly and optimistic (we're a "party, after all:).
b) posts should not be explicitly politically / religiously / etc aligned because not all editors will have the same attitude towards various controversial Fedi topics / dramas (better leave such posts for one's personal accounts)
**4** Each post from this account will end with a line indicating its author in any of these forms: "by @nickname@server.com", "by Strypey". Additionally, the account profile description will list all its administrators: "This account is administered by @.., @.., @.. and @..". The followers will understand who they're talking to / whom each individual answer in the thread represents.
c) probably best to end each post from this account with "by @nickname" note, so that readers know who they're talking / whom each individual answer in the thread represents
**5**. Any Direct Messages sent from this account for "official" private questions / offers to Fedi developers will also be signed at the end similar to public posts (see (4)). Any account administrator will read these DMs but won't answer in the thread unless they are the one who initiated the conversation - or unless they also want to take part in the conversation with their own suggestions. Our correspondents must not be confused who they're talking to.
*By Fediverse we currently agree to count software using any of the four protocols. Which means we won't post about XMPP, Matrix or any other federating things from this account.
[^1] By Fediverse we currently agree to count software using any of the four protocols: diaspora, ActivityPub, Zot, OStatus. We won't post about XMPP, Matrix or any other federating things from this account.
3. Software. I vote for Mastodon / Glitch-soc instance. As much as I'd love Friendica or Hubzilla extra features, they sometimes catch weird bugs that may prevent messages reaching Mastodon - which is the biggest source of our target audience, as of today. Gitch-soc allows long posts (up to 10.000), more pall variants (I think?), bookmarks - it's more flexible than Mastodon and ensures solid Mastodon interoperability.
4. Strypey initially said such an account may be useful for DM-ing Fedi developers and having some "official" private conversations ("officially representing fediverse.party"). I think it's OK (?) but since several people will have access to the account we should may be decide that if someone starts a DM thread about some Fediverse/Party question, others will read it but won't answer in the thread unless they are the one who initiated it. Or else our correspondents may be a bit confused who they're talking to. Such DMs also require a "by @nickname" signature at the end, I think, not to be anonymous for the correspondent.