Existing players used to logging in with their character name and moo password must signup for a website account.
- hex 2m
- Tanin_Guest 23s [Welcome to Sindome]
- Wulf 5m
a Butako 2m https://i.imgur.com/GsU4a79.jpg
- Angeline 12s
- FluffyPuff 2m
- AdamBlue9000 17s Rolling 526d6 damage against both of us.
- PsycoticCone 45m
- Burgerwolf 1m PANCAKES
- Raven 55m I lost myself, in the dark charade.
- Crooknose 11s
- Soltan 4h
- Archangel212168 20s
- Pladdicus 8m uh
a Mench 3h Doing a bit of everything.
- Rillem 22m Make it personal.
- Vanashis 4h
- zxq 35s Tools: https://ansicolortool.neocities.org
- Yizhi 5s
And 23 more hiding and/or disguised
Connect to Sindome @ moo.sindome.org:5555 or just Play Now

Security Network Snooping
Fucking cameras... I an' I always getting hacked.

While camera hacking as it currently exists does have its uses, it still leaves just a little to be desired. Last night, I had a Sindome Dream involving some plot or another, and it gave me a pretty cool idea.

When a decker hacks a camera/wiring hub/screen(?)/whatever, they could get the option to add themselves (or another grid username) to some kind of remote viewing list for the network that device is connected to, essentially turning their gridterm into a portable security monitor hooked into the network (before someone scrambles to tell me this is overpowered, there is chrome that does the same and is arguably much harder to steal from someone)

The amount of active feeds you can have at once would obviously vary depending on what tier of gridterm you have, and it would be just as easy for another decker to remove you from this list as it was for you to add yourself to it in the first place. It would result in an increase in people asking deckers to hack cameras for them, now that they can provide a feed of the entire network, allowing someone to potentially scope out a building or gather intel on their opponents, and also more people hiring deckers to keep the public-facing aspects of their network secure with ICE and daemons.

Being on someone's security network could… potentially…? have other benefits down the line, but I think this is more than enough to start.

(Edited by Baguette at 4:48 am on 7/15/2026)

I would much rather this have to do with the secure tech skill, rather than another thing with cameras and security stuff go to deckers as secure tech is very barren.
I don't see why it couldn't be both.
Deckers to keep them safe from Grid breaches, SecTechs to keep them safe from physical breaches

(Edited by Baguette at 5:01 am on 7/15/2026)

It's a nice idea but as it stands there are a few things I want to bring up.

1. Having complete 24/7 access to cameras outside peoples pads, or even inside their pads, I think is unbalanced. There are OOC rules against installing cams outside peoples pads for this reason.

2. For certain IC reasons..having access to some people's feeds, if they have a certain chrome installed would be extremely OP even if it is limited till they have a decker remove it.

I think this idea might be more plausible if instead of entire security feeds, the terms were scanned to indivudal cameras for 24/7 monitoring. Maybe even limited to Nova or Liteterms due to the processing power required, with the obvious caveat of cams outside pads being a nono.
1. You're completely right, and taking that into consideration maybe the decker's connection to the security network could be limited. Like, for example, they get thirty minutes of access each time they run the command to add themselves. Even if they keep spamming that command forever, they will eventually be forced to back off as they run out of programs and/or the Grid Heat generated by the device grows larger and larger. This way, deckers won't be getting eternal access to someone's net just because they're too lax on their security to hire a decker of their own.

2. I wouldn't call it OP, but I would say it's all the more reason to hire a decker to install ICE and daemons on your exposed devices. That way, in that scenario, you would be alerted of someone trying to breach your network and be able to sever that chrome's connection from it before you were compromised. I mean, come on, doesn't that entire situation just sound cool as fuck?

As for your last point, I do still like the idea of being able to monitor individual cameras/microphones forever, but I would *really* like if it were integrated with my idea including the two points I made above. Being able to temporarily be in someone's entire network, or forever (until you're kicked off, anyway) have access to individual cams.

(Edited by Baguette at 5:02 am on 7/15/2026)

But it is OP, Baguette. Because of how scanning devices and storing devices work, it kinda becomes an issue.

While I made my comment about I'd much rather anything like this be secure tech-related, it's just way too OP to have access to a full camera feed. For long periods of time, let alone the potential for forever.

And if you're scanning an outside camera that has someone's internal network on it and you get access to their internal network from that, is that balanced? Would it work on bridged networks? Would secure techs get an added ability or tool to be able to help combat this in some way, or would they exist in this scenario to just be camera installers who have no way to help guard or protect their clients against the nature of device scans?

I get wanting to have deckers do cool and awesome stuff with cameras or other devices. But there does come a point where one has to ask if the cool suggestions and ideas would make it so one archetype just sorta overruns and overtakes a great deal of the already limited ability of a different archetype.
look man i just want deckers to be able to do anything further than "go to excessive lengths to get physical access to a certain device for the groundbreaking payoff of a list of names and how much they get paid a week"