NireBryce

reality is the battlefield

the first line goes in Cohost embeds

🐥 I am not embroiled in any legal battle
🐦 other than battles that are legal 🎮

I speak to the universe and it speaks back, in it's own way.

mastodon

email: contact at breadthcharge dot net

I live on the northeast coast of the US.

'non-functional programmer'. 'far left'.

conceptual midwife.

https://cohost.org/NireBryce/post/4929459-here-s-my-five-minut

If you can see the "show contact info" dropdown below, I follow you. If you want me to, ask and I'll think about it.


NireBryce
@NireBryce

INFORMATIONAL


Norms, Internet Civil Engineering N. Bryce
DRAFT Request for CoHosts: 1 E. Ard
COHOST-DRAFT CoHost Poster
Category: Infrastructural
June 2022

CHP 21407



Recommended Names for "Posts" and "SHARES"



Abstract

This document describes a proposed standard set of names for the actions "post" and "share" on the https://cohost.org/ (henceforth "CoHost") Social Management Platform. It is informed by observations of the existing community, and is intended to start a shift towards standardization of the vernacular.

Status of This Document

This document is not a CoHost Roadmap Track specification, it is published for informational purposes.

This document is a product of the Norms working group of the Internet Civil Engineering (NICE) group, and represents informaton that the NICE has deemed valuable to provide for permanent record. Documents approved or publication by the NICE are not a candidate for any level of Posting Standard; see Section 6 of Cohost.org Terms of Service.

Information about the current status of this document, any errata, and how to provide feedback for it may be obtained at CHP 21407

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT, "RECOMMEND", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC 2119].

Table of Contents

  1. Introduction.................................1
  2. Style Conventions............................1
    1. Choost    ...................................1
    2. Rechoost   .................................1
  3. Security Considerations......................1
  4. Appendix A. Related Procedures ..............1
    1. A.1. Revising This Document...............1
  5. Acknowledgements.............................1

1. Introduction

The ultimate goal of communication is mutual understanding with the least cognitive overhead. To this end, this document RECOMMENDS a standardized language for the two most common Actions within the broader global CoHost Social Management ecosystem.

Though augmenting comprehension is the primary goal, there are manifold benefits. Using a common glossary assists with onboarding new CoHosts, who may not be familiar with the ebbs and flows of the intellectual idea-space of the postbox.

While this document is just a recommendation, we sincerely hope that the CoHost Social Management Platform community can move closer to a common vernacular, regardless of if it adopts these RECOMMENDATIONS

2. Style Conventions

This document RECOMMENDS adoption of standardized phrasing for the two most common Actions in the CoHost Social Management Platform.

2.1 Choost

The keyword CHOOST is proposed to describe the most elemental action of any Social Management Platform, the POST. It may be formatted as "Choost" or "choost". It was chosen via sampling feedback from participating CoHosts, found within CHP 18319. CHOOST strikes a balance between the blandness of 'MEMO' and the unprofessionalism of 'TOOT'. The authors feel that this is a community open to the idea of something fun, but still practical.

2.2 Rechoost

The keyword RECHOOST is proposed to describe the action of sharing a CHOOST. It may be formatted as "ReChoost", "Re-Choost", "rechoost". Much like CHOOST, this was chosen via sampling participants from CHP 18319. As this refers to the act of sharing a CHOOST, the RE prefix makes it clear that this is not the CHOOST itself.

3. Security Considerations

As the CoHost Social Management Platform does not have strict language checking, it is important to enforce community norms around keywords such as CHOOST and RECHOOST. Without this, hostile actors may introduce keywords with undefined meanings, such as calling a RECHOOST a "retweet" or "boost", both of which are advertising market competitors, putting both the CoHost Social Management Platform and all COHOSTS at risk of memory-based psychic harm.

With that in mind, RECHOOSTING a COHOST using unsanctioned language should be deterred if containment of the memetic contageon is not possible.

Aknowledgements


NireBryce
@NireBryce

I humbly suggest we also adopt CHP 21599, "COHORT" as the key word for "FOLLOWERS"


You must log in to comment.