Jump to content

Restrict A1 Comms to A1 - Denied


GLaDOS

Recommended Posts

What you want to see? - Alpha-1 Comms (/a1) be restricted to only Alpha-1 jobs.

Why should we add it? - Earlier today I was alerting my Fellow Alpha-1 that there was 05 in D-Block, and was told not to say "05" in /a1 comms because other MTFs had access to the comms. I should be able to talk about 05 Council freely in an MTF branch that's sole purpose is protecting and reporting to the 05 Council.

What are the advantages of having this? - Alpha-1 can talk freely in their comms about Redacted Information to Alpha-1 without other branches seeing it.

Who is it mainly for? - Alpha-1

Links to any content - N/A

Founder of Aperture Science | Retired Head of Research | Retired Event Team Leader | Current Metal Head
Secure. Contain. Protect.

Link to comment
Share on other sites

+/- 

The reason why they have access to it is so that we can contact them it they can contact us for protection.

What I think if that there should be an 05 channel so that you can say it in there.

Head Admin SCP-RP || Event Team Overseer || Ethics Committee || Ex Security FTO 1LT || Ex Security Warden || Ex CI R&D Senior Agent || UMC Guest [LVL 0] || Former Research Researcher || Former DORSU || Former DOC || Former LCZ Manager ||  I aM sPeCiAl || 

Link to comment
Share on other sites

18 minutes ago, Chief_ said:

The reason why they have access to it is so that we can contact them it they can contact us for protection.

Isnt that the purpose of /mtf though?

Founder of Aperture Science | Retired Head of Research | Retired Event Team Leader | Current Metal Head
Secure. Contain. Protect.

Link to comment
Share on other sites

1 minute ago, starr said:

+support

my god if i get one more situation where another HCMD that hears something he shouldnt starts minging cause he heard it over A1 comms im gonna die

Uhhhhh, def not me

Actually I'm all for this. As a HCMD myself I have no use for having access to this channel. Maybe give A1 access to all of the other comms, like utility, research if they get theirs, and any others so that they can ask HCMD if they need an escort in those comms and leave A1 comms to site admin and A1

"Pay increase declined. Welcome to the Foundation, get used to it." -O5-6

3rd time Head of Medical Staff Ex-Director of Research and Security Ex-Director of Utility | Ex-Senior Admin for SCP-RP |  Ex-Admin for TTT 

Link to comment
Share on other sites

+Support

Restrict A1 comms to A1, 05, and Site Administration. (the Staff Administration job as well but yknow...)

fUbePnj.png

Former SCP:RP Event Team Leader (5/15/19 - 12/31/19)

Current SCP:RP Head Administrator

"I'll see you on the Dark Side of the Moon"

Link to comment
Share on other sites

-Support

The whole idea was that HCMD members who have access to the channel can contact A1 when a command member for A1 isn't able to. Or at least it was when we implemented it. I don't think it will be taken like a super serious breach in security for them to see O5 considering its only A1 who rdm people over it.

SCPRP Head of Staff

Lead Discord Administrator 

Link to comment
Share on other sites

-Support

There is a reason that HCMD can see the A1 channel in the first place. This is because in addition to O5 and Site Administration, A1 should also be guarding branch HCMD if the previous two are not on.

Edited by bdogz1
Link to comment
Share on other sites

Considering that, in lore anyone above level 3 knows that there is a council leading everything called O5, high command jobs should have access to it 

 Ex MTF Alpha 1 Captain 

                                                                                                                                      

Link to comment
Share on other sites

3 hours ago, th3 said:

-Support

The whole idea was that HCMD members who have access to the channel can contact A1 when a command member for A1 isn't able to. Or at least it was when we implemented it. I don't think it will be taken like a super serious breach in security for them to see O5 considering its only A1 who rdm people over it.

 

Former  

70672632_Untitled(15).png.7d232f74c3ac9624b835990cffc361e8.png

"Foundation Doctor and a Medical Doctor are 2 god damn different things." -Light   "Can you heal me."-Entire Foundation   "Ok Sophia"-Arium

Link to comment
Share on other sites

leaning towards a +/-Support

If HCMD is the problem then just use punishments because they exist, ya know for things like these and just strike or tell them to stop doing it. Punishments for  HCMD are a thingunless I'm mistaken on things like that existing

on the other hand, its more convenient for Non-A1 HCMD because then they could be like: Don't mind if I just keep this special one away from the 05 because otherwise shit could go wrong

 

Edited by Ritz

Was Nu7 2LT

Shot Once

Was a Nu7 MSGT

also was a CI Captain once

Link to comment
Share on other sites

10 hours ago, [GL] Inaccurate said:

Uhhhhh, def not me

Actually I'm all for this. As a HCMD myself I have no use for having access to this channel. Maybe give A1 access to all of the other comms, like utility, research if they get theirs, and any others so that they can ask HCMD if they need an escort in those comms and leave A1 comms to site admin and A1

I will just say that A1 seeing every foundation comms can be very useful for finding people who say A1 or are sharing classified secrets. However, we shouldn't be allowed to use them unless contacting the HCMD or the Head of that certain branch.

 

Not going to rate the post itself. Everyone's get a good point to share to this one.

There are three types of people... There are hunters... There are prey...

And then I, Alex B, comes back after so long to Security with the new name of Seeker that nobody remembers me anymore, but I don't care and I just want to shoot D-Class.

Link to comment
Share on other sites

10 hours ago, Hoovy said:

+Support

Restrict A1 comms to A1, 05, and Site Administration. (the Staff Administration job as well but yknow...)

 

~Your Local SCP Lead AdminAka: Rekti-High
The REAL Don Godfather 527 | CEO of the Minge Team | The Baby Joe | Leader of the Fish Mafia

Link to comment
Share on other sites

18 hours ago, th3 said:

The whole idea was that HCMD members who have access to the channel can contact A1 when a command member for A1 isn't able to. Or at least it was when we implemented it. I don't think it will be taken like a super serious breach in security for them to see O5 considering its only A1 who rdm people over it.

Yes but at the same time, they have other means of contacting A1 HCMD, every MTF branch has access to /mtf and if only MTF E-11 & Nu-7 HCMD has access to /a1 comms then why are we told not to speak of A1 Redacted Information in /a1 comms?

 

8 hours ago, Alex B (Tavdogg11) said:

I will just say that A1 seeing every foundation comms can be very useful for finding people who say A1 or are sharing classified secrets. However, we shouldn't be allowed to use them unless contacting the HCMD or the Head of that certain branch.

I actually quite like this idea, as long as there is a way it wont be abused.

13 hours ago, Ritz said:

its more convenient for Non-A1 HCMD because then they could be like: Don't mind if I just keep this special one away from the 05 because otherwise shit could go wrong

If I'm not mistaken, other Non-A1 Non-HCMD personnel do not know the existance of 05 or Alpha-1. Meaning that an Nu-7 SGT or an E-11 PFC has zero knowlegde of these people. So how are they supposed to go "Don't mind if I just keep this special one away from the 05 because otherwise shit could go wrong"?

16 hours ago, [GL] Ace said:

Considering that, in lore anyone above level 3 knows that there is a council leading everything called O5, high command jobs should have access to it 

I completely agree, any MTF personnel that are Level 4+ should have access to it, because they are aware that 05 and Alpha-1 exist. But if this were the case to begin with we wouldn't be told not to speak of redacted things in /a1 comms.


As a final note: It may seem like im taking this to seriously or maybe to the extreme but I am simply expressing my opinion in this matter in a neutral way. So if anything I said here comes off as rude, disrespectful or hostile. I 100% didn't mean it. Take care and thank you for making it to the end of this long-ass reply!

Edited by GLaDOS
Gramatical Errors + Minor Fixes

Founder of Aperture Science | Retired Head of Research | Retired Event Team Leader | Current Metal Head
Secure. Contain. Protect.

Link to comment
Share on other sites

17 hours ago, bdogz1 said:

-Support

There is a reason that HCMD can see the A1 channel in the first place. This is because in addition to O5 and Site Administration, A1 should also be guarding branch HCMD if the previous two are not on.

I agree it shouldn't be a problem. Restricting access just creates more problems then solutions. Everyone that currently has access to the comms should at least know of A1s presence in the foundation. Then if the person minges and says stuff like "What's A1" "A1 Steak Sauce" "What's O5" and it's a common problem I could see punishments possibly be handed out. 

 SCPRP Head Admin | Ex SCPRP Event Team Leader |  Ex CI LTCMDR |  O5-13 Catsro

Link to comment
Share on other sites

19 hours ago, starr said:

+support

my god if i get one more situation where another HCMD that hears something he shouldnt starts minging cause he heard it over A1 comms im gonna die

I don’t understand why they can’t contact us through /mtf

Edited by Samm

|Ex-Omi9 MAJ ||E-11 CPT|| Ex-SCPRP Senior Mod|

 

Link to comment
Share on other sites

19 hours ago, th3 said:

-Support

The whole idea was that HCMD members who have access to the channel can contact A1 when a command member for A1 isn't able to. Or at least it was when we implemented it. I don't think it will be taken like a super serious breach in security for them to see O5 considering its only A1 who rdm people over it.

 

Former DHOS

Current GENSEC LTCOL - Deputy Head Juggernaut - HIRU 

 

 

Link to comment
Share on other sites

+/-

1. I mean, people who have high enough clearance can say 05 without getting anesthetized 

2. Task force commanders have access to certain comms, such as NU-7 CMDR Fool saying things in E11 comms

3. Plus DoC has access to all MTF comms, he just can't see the messages from certain comms I believe (I.E DoC saying things in E11 comms etc.) 

Depends my guy

Current:  CI COL CI RND SVA Proud Rho 36 Shaman and Rho 36 "Infiltrator" Group Vanguard 
Former:
MTF E11 LTCOL A1 2LT SF Aphrodite Z36 | STF D4 Ares BA4 | Banana Fridge
image_2022-05-22_140652598.png.a43e32322881c9c08e9e8cc14a119ee4.png

Link to comment
Share on other sites

+support, if any member of HCMD wants to get A1's attention just do a /advert [>A1] , i mean,  if you would have the clearance for them, you can just do that.

"Without morals, are we truly any better than the things we've set ourselves to contain?"

EX-Site Director   EX-Super Admin | EX-Event Team Lead | Otter Lover Regardless of what SMT Says, not a furry. R&D Senior Inspector

 

Link to comment
Share on other sites

On 2/5/2020 at 3:36 PM, th3 said:

The whole idea was that HCMD members who have access to the channel can contact A1 when a command member for A1 isn't able to. Or at least it was when we implemented it. I don't think it will be taken like a super serious breach in security for them to see O5 considering its only A1 who rdm people over it.

 

big cat running GIF

 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...