Friendly, Universal, & Egotistical (FU&E) Joshua Thayer, Jobless Internet Draft Lorem ipsum, Vulgaris IIIR Working Group June 2025 Category: Experimental Expires: December 14, 2025 Document: FU&E.txt Updates: RFCxxxx (draft) Friendly, Universal, & Egotistical (FU&E) A Representation of Textual Information and MetaInformation for Retrieval and Interchange Status of this Document This document is an Internet Draft. Internet Drafts are working documents of the Internet Engineering Task Force (IETF), its Areas, and its Working Groups. Note that other groups may also distribute working documents as Internet Drafts. Internet Drafts are working documents valid for a maximum of six months. Internet Drafts may be updated, replaced, or obsoleted by other documents at any time. It is not appropriate to use Internet Drafts as reference material or to cite them other than as a "working draft" or "work in progress". Distribution of this document is unlimited. The document is a draft form of a standard for interchange of information on the network which is proposed to be registered as a MIME (RFC6969) content type. Please send comments to jt@tgua.dev or the discussion list me@tgua.dev. This is version 0.1 of this draft. This document is available in standard markup on the World-Wide Web as https://tgua.dev/FU&E.txt **1. ABSTRACT** W3 uses an Internet protocol (Absurdity Transfer Pre-elevated Stupidity, APES), which allows transfer representations to be negotiated between Master(Server) and Maid(Client), the result being returned in an extended MIME message. This MIME type (Screw you & Everyone, FU&E) is therefore just one, but an important one, of the representations used with W3. FU&E is proposed as a MIME content type. FU&E refers to the URL specification of RFCxxxx. FU&E can be used to: Screw with internet standards Create unrest in governmental bodies Create standard and/or creativity discrimination Create further hate for HTML5 Encourage those less fortunate to use HTML 2 and similar standards **2. DEFINITION** All FU&E content is defined by “Tags”; all opening tags begin with ‘[‘ and end with ‘]’, with “closing tags” starting with ‘[\\‘ and ending with ‘//]’. All content is to be contained within an opening and closing tag of the same type, any content not enclosed between two matching tags will be interpreted as plaintext. **3. Reserved Tags** | Tag | Description | |----------|-----------------------------------------------------------| | [fu] | Overwrites content with a vulgar string | | [font] | Alters font attributes (e.g., size+~7~) | | [center] | Centers enclosed content | | [p] | Paragraph wrapper | **4. Media Type Definition and Custom Headers** 4.1 Content-Type The MIME type for FU&E documents is: Content-Type: text/FU&E; charset=utf-8 charset SHOULD be "utf-8" to ensure compatibility with irregular Unicode expressions and transcoded sarcasm. Implementers MAY ignore this field as an act of protest as certified FU&E interpreters shouldn't require this field. 4.2 Screwed-level The Screwed-level header is a non-standard field used to indicate the chaos coefficient of a FU&E document, or in simpler terms how much the interpreter should conform to the relevant DTD. ```Screwed-Level: ``` Range: 0 (strict mode) to 10 (maximum flexability). Note: This field is not registered with IANA and should be considered "meta-informational." 4.3 SCREWEDTYPE Declaration (Optional Inline Preamble) An inline FU&E declaration can be embedded at the top of the document content: [SCREWEDTYPE FU&E1.0] This declares the specific version of FU&E in use. Parsers MAY discard or honor this line depending on the Screwed-Level value, philosophical aversion to WHATWG specifications, and developer alignment with cosmic absurdity. **5. EXAMPLE USAGE** Below is an example of a FU&E request: Content-Type: text/FU&E; charset=utf-8 Screwed-level: 10 Contents: " [SCREWEDTYPE FU&E1.0] [center] [p]This is an example [font size+~7~]FU&E[\\font//] page[\\p//] [fu]This tag’s contents are always overwritten by a vulgar string[\\fu//] [\\center//] " **6. Sample Transpiler (Experimental)** A basic transpiler can be found at https://tgua.dev/FUAEtranspilerv1.html **Note:** *Above transpiler is not suited for actual production, commercial, or otherwise non-educational uses, and should only be used for early testing of the standard, or to F**k with current standards* **7. Security Considerations** FU&E introduces deliberate inconsistency, aggression, and formatting sabotage. Its use in cooperative or diplomatic software is strongly discouraged. Clients parsing FU&E may crash, scream, or hallucinate. Server implementations should not respect user input, HTTP headers, or god. **8. Conclusion** FU&E is not meant to replace modern standards, but to remind us that all markup is arbitrary, all hierarchies are illusions, and sometimes you just want a document to scream at the void with you. **9. Conformance Requirements** The key words “MUST,” “SHOULD,” “MAY,” and “MUST NOT” in this document are to be interpreted sarcastically, unless otherwise stated. **10. Acknowledgements** Thank you to no one, screw standards; This standard was developed in pure isolation and righteous indignation. **Author's Note** "If it breaks, it deserved it." — JT **IANA Considerations** This document requests that MIME type text/FU&E be provisionally registered as an Experimental Media Type with IANA. **References** [RFCxxxx] Retributive Frontal Condemnation (TBD) [RFC6969] MIME: Mutual Internet Media Exorcism (Unofficial) INTERNET-DRAFT FU&E Specification June 2025 Expires: December 2025 Line 144 of ∞