Rule Suggestion Change it so that "private" internal communications channels are treated as "addressed to" vs "encrypted"

Rule suggestions will be reviewed by Superadmins, this may take longer than standard content suggestions.
Ratman99

Ratman99

Well-known Member
Apr 17, 2026
30
2
41
What does this suggestion change/add/remove:
Makes it so the private internal channels, eg <E-11-Nu-7> are treated as addressed to, not private between addressor and addressee so the information is actionable by people in the overarching comms channel/s. NOTE THIS HAS NOTHING TO DO WITH O-COMMS

Edit: Another example to make it clear(er), if someone were to go <CL4> 008 is out, in CL3 comms, every CL3 can see it and take action on it, vs now where only CL4 can see it. So <XX> becomes a formal way to format a address to a specific thing vs actually being treated as private between the addressor and addressee as is now.

<br>Has something similar been suggested before? If so, why is your suggestion different?:
I dont think so
<br>Possible Positives of the suggestion (At least 2):
Will cut down on meta bait
Will cut down on comms clutter
May make role play to do with communications more interesting
<br>Possible Negatives of the suggestion:
It may make private comms a bit more of a hassle until people adjust to it.
<br>Based on the Positives &amp; Negatives, why should this suggestion be accepted:
I believe switching <xx-xx> in c comm to be a formalized address system vs a "treated as encrypted" between assessor and addressee would cut down on meta-bait and other iffy behavior, if someone wants a private chat, they can do it in person, set up a radio freq or use a phone, rather than use /c <me-you> "Lets breech 008".
 
Last edited:
Upvote -1 Downvote
Make it so the private internal channels, eg <E-11-Nu-7> are treated as addressed to, not fully private so the information is actionable by people in the overarching comms channel/s. NOTE THIS HAS NOTHING TO DO WITH O-COMMS
Click to expand...

So just like an E-11 saying "/oc Hello Nu-7, Can you do XYZ for us?" instead of "/c <E-11 - Nu-7> Can you do XYZ for us?"

This is very confusingly written in my opinion.
 
YandereMuffin said:
So just like an E-11 saying "/oc Hello Nu-7, Can you do XYZ for us?" instead of "/c <E-11 - Nu-7> Can you do XYZ for us?"

This is very confusingly written in my opinion.
Click to expand...
its confusing for me to explain, but i dont think we have defined it. As i have made you understand in DM's this is more for public benefit plus a picture:


This is what i am referring to [picture <SOP>], now granted i have a problem with this, but my suggestion initially excluded O-comms, more to mean the set up channels between GOI to talk privately. So for simplicity i am keeping it to /c comms. (in this explanation)

I think everyone should be able to see anything written in the comm lines they have access to, the whole <XXX> Encryption thing should just be treated as a formalized address system vs "we cant see it ICly". I have seen people metabait on it, use these when they have private channels etc etc. Like a CL4 addressing CL4's on CL3 comms, A1 used to do the "add them to the list" meme in /c etc etc. For IC comms (PM's are OOC), you have, a phone you can ring, you can summon them to a location to talk in person, or ring a office etc if you want a private chat vs using /c <me-you>.


Now in the picture example, i think O-comms should be reserved only if used from a X to Y, so if someone does this[as shown in picture], everyone who has access to open comms should be able to see it ICly, he could have just used /sop to talk on SOP comms.
1782326813804.png
 
Tub said:
Probably the most confusing suggestion I've read until the explanation. So you just want secure comms to be similar to pinging someone in discord where it's meant for the person you're pinging but everyone can read it?
Click to expand...
If that anology works then yes. I find the current encrypted line thing more confusing than this.
 
Proximo1021 said:
That doesn't really sound like a good idea, what if its like /c3 [S-Site Advisor] Did you approve of a 610 stuff. It really feels like it would make info breaching really easy
Click to expand...
i don't know what S means here, but that withstanding.

Kind of a split, it shouldn't lead to info breching as you shoudlnt be nattering about CL4 things on a CL3 line to begin with when you have CL4 chat, CL3 doesnt need to know about these, nor shouldnt know about this as it would just lead to metagaming. This applies to many if not all jobs as there are MANY secure ways to talk to specfic groups of people. (not withstanding if you dont share a secure comms line/need to talk to them specfically you can ask to meet up, use the radio if you have one, or use a phone)

And 2, kind of the point, that if someone goes /c [CL4] "get to 008 the zombies are spreading", it will be deemed a IC info breech and be punsiahble in chracter vs leading to OOC punsihment if you act on it. As that should be reserved for CL4 comms or specfic unit comms. vs being able to write what ever nonsense and be protected by it being deemed a "encrypted communication"


I just dont see the logic int his system, both for RP and utility. RP wise, its encrypted comms in a top secret site any personell can set up, utility wise its just a formalised way of going "hey you, come help", when that would suffice vs the <XX-YY>. Not withstanding my comments about metabait.
 
I am going to -support

"Kind of a split, it shouldn't lead to info breching as you shoudlnt be nattering about CL4 things on a CL3 line to begin with when you have CL4 chat, CL3 doesnt need to know about these, nor shouldnt know about this as it would just lead to metagaming" - There is a few CL3 roles that have knowledge on CL4 SCPs - they do not have CL4 comms. That is why you SECURE a comms to someone who can confirm information. A great example being ISD or SCUs.

If an SCU is helping run the checkpoint because of a lack of E-11 for example - they have no way to verify testing on CL4 SCPs if this gets accepted - they don't have a specific comms line that other CL3's cannot see. That is why Secure Comms exist.

Lets change it a tiny bit now - a CL3 Researcher was properly briefed on say SCP-079 for a test. When they go and move to get their test - and they decide they want to check something with their Executive (A CL4 RSD member), now the only way they can do it is either A) End their test, go find the Executive in person, pull them to the side and ask the question or B) Hope and pray the executive is not busy and can head down to SCP-079 within a reasonable timeframe. Instead of just /c3 {Me>Executive Researchers} Hey I was curious about [X] with 079 - I know you said [Y] but how does this relate to [Z]?

(as an example)

This is just an unneeded modification, any points made are in regards to the US Server.
 
You must log in or register to reply here.
Top Bottom
Back