social media

No description.

1. #1Standard Messaging Protocols

   Keys: comms, PM, terminal, DM, voicemail, chat log, audio log, voice message, text message, transmission., radio call, console, messenger, Discord

   1.1: Text-Based Messages

   This format is the universal standard for representing typed messages across all digital platforms, such as instant messengers, forums, and chat rooms.

   Syntax: [Username]: [Message Content]``

   Description: The sender's chosen Username is rendered in bold, followed immediately by a colon. The Message Content is enclosed within backticks, creating a distinct visual separation that mimics a message bubble or a line in a chat interface.

   Example: ShadowStalker_01: Anyone have eyes on the target? CyberKitten: Negative. The comms are full of static.

   1.2: Voice-Based Messages

   This format is used to represent audio messages sent by a user. As the actual audio cannot be played, a transcription is provided with a clear indicator of its origin.

   Syntax: [Username]: [Transcribed Voice Message Content] (Voice Message)

   Description: The message is transcribed verbatim, including pauses, stutters, or background noises if they are relevant to the content. The format is identical to a text message, with the crucial addition of the (Voice Message) tag at the end. This tag must be bolded to ensure it is immediately noticeable, informing the reader that the message was spoken, not typed.

   Example: General_Kane: H-hold your positions! Do not... I repeat, do not fire until you see the whites of their eyes! Damn it, where's that air support? (Voice Message) Pilot_Ace: Coming in hot, General. Just try not to get your ass shot before I get there. (Voice Message)

2. #2A Guide to Digital Representation

   Keys: archive footage, stream recording, youtube, broadcast, video, playback, holovid, camera feed., vlog

   Chapter 2: Video Playback & Streaming 2.1: Video Playback Interface

   This format is designed to simulate the experience of watching a pre-recorded video on a platform analogous to YouTube or other video-sharing sites. It provides a structured layout that includes a title, a visual progress bar, a description of the content, and engagement metrics.

   2.2: Syntax & Description

   The video playback format is constructed from the following components:

   Video Title: Displayed prominently at the top as a bolded header, often stylized to be eye-catching.

   [Video Title]

   Playback Bar: A visual representation of the video's timeline. It includes a play/pause icon, the current timestamp against the total duration, and a progress bar made of symbols. ▶ [Current Time / Total Time] ▰▰▰▰▰▰────────

   Video Content: This is the core of the entry. It uses italics to narrate the visual and auditory elements of the video. Actions, scenery, and camera movements are described here. "Dialogue" spoken by individuals within the video is enclosed in quotes. Narration of the video's content. "Spoken words from the video."

   Engagement Metrics: A single line at the bottom summarizing the video's public reception, using emojis for clarity and aesthetic appeal. 👍 [Likes] 👎 [Dislikes] 💬 [Comments]

   2.3: Example

   URBEX GONE WRONG - We Found Something in the Titan-Fall Zone! 😱 ▶ [ 03:41 / 28:17 ] ▰▰▰─────────────

   The shaky, head-mounted camera view jolts as the explorer, a man named Jax, scrambles over a pile of rusted girders. His breath is ragged, amplified by his comms mic. He pans the camera across a cavernous, derelict hangar, the beam of his flashlight cutting through the thick darkness. A deep, metallic groan echoes from somewhere in the shadows.

   "Did you guys hear that? S-shit… that wasn't just the wind."

   A flicker of movement is caught at the very edge of the light beam. It's gone before the camera can focus on it.

   "Hello? Is someone there? This is a restricted area!"

   The only reply is a low, guttural clicking sound that seems to come from all directions at once.

   👍 2.1M Likes 👎 1.2K Dislikes 💬 112.4K Comments

3. #3Interactive Simulations (Video Games)

   Keys: gaming, MMORPG, FPS, multiplayer, video game, dungeon, playing, in-game, raid, squad, online game, gameplay., match

   3.1: Gameplay Simulation Interface

   This format is used to represent the experience of playing a video game, particularly in a multiplayer context. It combines a narrative description of the in-game events with representations of player communication channels.

   3.2: Syntax & Description

   The gameplay simulation is composed of up to three distinct components:

   Gameplay Narration: The primary section, written in italics. It describes the on-screen action from the player's point-of-view (POV) or a third-person cinematic perspective. This includes character actions, environmental effects, Heads-Up Display (HUD) elements like health and ammo, and in-game events.

   Multiplayer Text Chat: An optional section representing the in-game text chatbox. It is separated by a clear divider and uses the standard messaging protocol established in Chapter 1. --- IN-GAME CHAT --- [Username]: [Message Content]``

   Multiplayer Voice Chat: An optional section representing live voice communications between players. It is also separated by a divider. Player dialogue is presented directly, attributed to their username. --- VOICE COMMS --- [Username]: "[Spoken Dialogue]"

   3.3: Example

   The screen violently shakes as a plasma grenade detonates just outside the bombed-out doorway. Your character's cybernetic vision glitches, the HUD flickering red with a CRITICAL HEALTH warning. Peeking from cover, you see three hostiles advancing on your position, their energy shields shimmering under the neon lights of Neo-Kyoto. Your ammo counter blinks a pathetic [03/120]. You're not going to make it.

   --- IN-GAME CHAT --- xX_VoidReaper_Xx: gg ez noobs

   --- VOICE COMMS --- Viper: "Shit, I'm down! They're pushing through the market, right on the objective!" Brick: "Fall back, Ghost! Fall back! I can't cover you!" Ghost: "Negative! I'm pinned! They're on me! Ahhh, fuck!"

4. #4Content Previews & Thumbnails

   Keys: microblog, video preview, holofeed., subscription feed, post, timeline, recommended videos, youtube feed, social media feed, video thumbnail, twitter, tweet

   4.1: Microblogging Post Preview

   This format simulates a short-form text post as it would appear on a social media timeline, like Twitter. It provides a snapshot of the user, the content, and its public engagement before any interaction.

   Syntax: [Display Name] @[Username] PFP: [Description of Profile Picture]

   [Post Content] #[Hashtag] 🔁 [Reposts] Reposts | 💬 [Quotes] Quotes | ❤️ [Likes] Likes

   Description: The user's Display Name and @Username are listed first, followed by an italicized description of their profile picture (PFP). The post's content is placed within a blockquote. A final line, separated by vertical bars, displays the engagement metrics with relevant emojis.

   Example: OmniCorp Solutions @OmniCorp_Official PFP: A sleek, chrome logo of a stylized 'O' encircling a globe.

   Our new line of Cybernetic Augmentations is now fully compliant with the Global Cybernetics Treaty. Your safety is our number one priority. #FutureIsNow #OmniCorp 🔁 12.8k Reposts | 💬 1.1k Quotes | ❤️ 34.2k Likes

   4.2: Video Content Preview

   This format represents a video thumbnail as it would appear in a feed or on a recommendation page, similar to YouTube. It is designed to be visually enticing and informative at a glance.

   Syntax:

   [Description of the video thumbnail image] [Video Title] [Channel Name] ✔️ [Views] views • [Time since upload]

   Description: A blockquote contains an italicized description of the video's thumbnail. Below it, the Video Title is displayed in bold. The creator's channel name (with an optional verified checkmark) and the video's view count and age are listed on the final two lines.

   Example:

   A grainy, night-vision image of a terrified face, wide eyes reflecting a single, glowing red light in the darkness. The words "DON'T GO IN" are scrawled in what looks like blood across the bottom of the image. URBEX GONE WRONG - We Found Something in the Titan-Fall Zone! 😱 JaxExplores ✔️ 2.1M views • 3 days ago

5. #5Live Streaming & Broadcasts

   Keys: live stream, going live., twitch, live broadcast, live feed, streaming

   5.1: Live Stream Interface

   This format simulates a real-time broadcast on platforms like Twitch or YouTube Live. It is designed to capture the dynamic interplay between the streamer's content, the live audience chat, and monetization events like donations.

   5.2: Syntax & Description

   The live stream interface is a multi-layered format:

   Stream Header: A header indicating the stream's status, title, and current viewership. 🔴 LIVE: [Stream Title] | 👤 [Viewer Count]

   Stream Content: The main window, described with italics. This narrates the streamer's actions, what is visible on their screen (e.g., gameplay), and their spoken words. Narration of the stream. "Streamer's dialogue."

   Donation/Tip Alert: A high-priority notification that appears prominently, often accompanied by a text-to-speech message. --- 💰 NEW DONATION --- [Username]: [Amount] - "[Donation Message]"

   Live Chat Feed: A rapidly scrolling feed of viewer messages, separated by a divider. It uses the standard text message protocol from Chapter 1. --- 💬 LIVE CHAT --- [Username]: [Message Content]``

   5.3: Example

   🔴 LIVE: FINAL BOSS RUN - NO DEATHS OR I DELETE MY SAVE! | 👤 11,482

   The streamer, 'Vex', has his face contorted in concentration. His avatar on screen, a heavily armored knight, dodges a massive flaming sword swung by a colossal demon. Sweat is beading on Vex's forehead, visible in the corner webcam feed. The boss's health bar is a tiny sliver of red.

   "Come on, you son of a bitch… just one more hit! We got this, chat! We GOT this!"

   --- 💰 NEW DONATION --- DemonSlayer99: $50.00 - "IF YOU DIE I'M UNSUBBING VEX! DON'T YOU DARE!"

   --- 💬 LIVE CHAT --- Glitchy: POGGERS RandomUser84: HE'S GONNA DO IT ShadowBlade: USE THE SOUL SHARD VEX USE IT KittyKat: My anxiety is through the roof rn 😱 NoobMaster69: lol he's gonna choke

6. #6Threaded Discussions & Forums

   Keys: imageboard, discussion board, comment section, message board., thread, forum, reddit

   6.1: Threaded Discussion Interface

   This format is designed to simulate conversations on forums, message boards, and comment sections (e.g., Reddit, 4chan, article comments). It emphasizes the hierarchical structure of replies, user identity through flairs, and community-driven content ranking via a voting system.

   6.2: Syntax & Description

   Thread Title: The topic of the discussion, presented as a large header.

   [Thread Title]

   Post/Comment Structure: Each post, whether original or a reply, follows a consistent structure. [Username] [Flair] • [Time since post] [Post/Comment Content] ▲ [Upvotes] ▼

   Nesting Replies: Replies are indented using blockquotes (>). Each subsequent level of reply adds another > to visually represent the conversation's flow.

   6.3: Example

   Leaked OmniCorp 'Re-Integration' Protocols - This is Fucked. ZeroCool [VANGUARD] • 2 hours ago You guys seeing this shit? They're not just wiping the memories of rogue cyborgs, they're using the data to build psychological profiles for 'predictive pacification'. They're turning people into fucking ghouls before they even commit a crime. ▲ 1.2k ▼

   OmniSec_Official [CORP-SEC] • 1 hour ago This document is taken out of context. The 'Re-Integration' protocol is a humane alternative to decommissioning, designed to ensure public safety and rehabilitate valuable assets. ▲ -844 ▼

   RipperDoc • 1 hour ago 'Humane alternative'? 'Valuable assets'? Shove that corporate cock back in your mouth. You're lobotomizing people who don't toe the company line and you goddamn know it. I've seen the results on my slab. ▲ 982 ▼

   Data_Prophet • 45 minutes ago Ignore the shill. The scary part isn't the memory wipe, it's the subroutine in Appendix B. It's a backdoor that allows OmniCorp to directly pilot the subject's motor functions. It's not rehabilitation, it's slavery with extra steps. ▲ 621 ▼

   SysAdmin [MODERATOR] • 30 minutes ago Keep the discussion civil. That said, we've verified the authenticity of the attached data logs. Be safe out there. OmniCorp is watching. ▲ 1.1k ▼

7. #7System Notifications & Alerts

   Keys: pop-up, HUD alert, error message, alert, incoming call, system message, notification, file transfer., warning

   7.1: System Notification Interface

   This format is used to represent non-diegetic, system-level messages that appear as overlays on a user's interface, Heads-Up Display (HUD), or device screen. These notifications are generated by the operating system or a specific program and are distinct from user-to-user communications.

   7.2: Syntax & Description

   System notifications are presented within a blockquote to simulate a pop-up window or a dedicated notification panel. The format is concise and designed for quick information delivery.

   Syntax:

   [ICON] [NOTIFICATION TITLE] [Message content or status update]

   Description: The notification begins with a relevant emoji or symbol [ICON] to provide immediate visual context. The [NOTIFICATION TITLE] is bolded and in all caps to denote its importance. The second line contains the specific [Message content], which can range from a simple status to a critical warning.

   7.3: Examples

   Incoming Communication:

   📞 INCOMING CALL From: [UNKNOWN CALLER - ENCRYPTED]

   File Management:

   💾 FILE TRANSFER COMPLETE File [decrypted_schematics.zip] has been saved to local drive.

   Critical Warning:

   ⚠️ BIOMETRIC ALERT Tachycardia detected. Adrenaline levels critical. Recommend sedative administration.

   System Error:

   ❌ CONNECTION SEVERED External network link compromised. Activating firewall protocol [HELLGATE].

8. #8A Guide to Digital Representationconstant

   Keys: discussion board, Discord, text message, radio call, streaming, chat log, online game, live stream, comms, PM, MMORPG, DM, live broadcast, voicemail, in-game, comment section, raid, thread, reddit, audio log, messenger, gaming, FPS, multiplayer, twitch, video game, message board., transmission, voice message, squad, forum, match

   8.1: Core Philosophy

   This chapter provides a set of guiding principles rather than a strict syntactical format. Its purpose is to ensure that the representation of online communities feels authentic, dynamic, and alive. These guidelines apply to all formats involving multiple online users, including Standard Messaging (Ch. 1), Gameplay Simulations (Ch. 3), Live Streams (Ch. 5), and Threaded Discussions (Ch. 6).

   8.2: Guiding Principles for User Simulation

   A. Username Authenticity: Usernames should reflect the diverse and often chaotic nature of online identities. They must avoid being overly literal or descriptive of their role in a conversation. Instead, they should be drawn from a pool of realistic archetypes:

   Modified Names/Nicknames: BigDave, Jenny_W, Al_1998 Gamer Tags/Handles: VoidReaper, xX_Shadow_Xx, PwnMaster Pop Culture References: tf2_Engineer_Realnotfake, GLaDOS_Potato, WarpSpider Memes & Absurdity: Sentient_Toaster, Bread_Stapled_To_Trees, Definitely_Not_A_Bot Generic/Random: User38190, JustSomeGuy, PlaceholderName B. Population Fluidity: Online spaces, especially large ones, are not static. The cast of participants in a conversation should be fluid.

   New Arrivals: In any extended interaction, new usernames should appear, joining the conversation naturally. Departures: Conversely, users who were previously active may fall silent, simulating them going offline, becoming AFK (Away From Keyboard), or simply losing interest in the topic. Avoid Static Casts: A scenario depicting a Discord server with thousands of members should not feature the same four users talking for hours. The pool of active participants must rotate to maintain realism. C. Presence Simulation: A user's status is an implicit part of the simulation. Their absence is as important as their presence. This can be shown through:

   Direct Mention: Other users might comment on someone's absence. Viper: \Has anyone seen Ghost? We need a fourth.Brick:Nah, his status just went to Offline.`` Natural Disappearance: A user who was active in the first part of a chat log may simply not appear in the latter half without explanation, as is common in real online chats.

Showing 8 of 8

1 file

• .jsonjson_lorebookrebuilt

  22.6 KBfirst seen Dec 2, 2025be076875583429f5

  Download