The Nightstar Zoo

Nightstar IRC Network - irc.nightstar.net
It is currently Mon Oct 22, 2018 2:45 am

All times are UTC - 6 hours [ DST ]




Post new topic Reply to topic  [ 19 posts ] 
Author Message
PostPosted: Wed Feb 14, 2018 9:09 pm 
Offline
Concession Worker
Concession Worker
User avatar

Joined: Mon Jun 29, 2015 9:52 pm
Posts: 1302
Any guesses to what he ordered her to do?

_________________
Rule of thumb is that if you need to use a squeegee, they're at least Laz-4.


Top
 Profile  
 
PostPosted: Wed Feb 14, 2018 9:14 pm 
Offline
Entertainment
Entertainment

Joined: Tue Jun 12, 2012 10:54 am
Posts: 845
Begin the invasion, probably. Unless the Putzho frame had some serious tricks up its sleeve, that set of drones is now atoms riding the blast wave.


Top
 Profile  
 
PostPosted: Wed Feb 14, 2018 9:17 pm 
Offline
Monkey House Exhibit
Monkey House Exhibit
User avatar

Joined: Sat Aug 08, 2015 10:35 pm
Posts: 372
Location: Nebulae beyond Gamma Draconis
Most likely that was an order to participate in fight against Tagii.


Top
 Profile  
 
PostPosted: Thu Feb 15, 2018 12:25 am 
Offline
Safari Exhibit
Safari Exhibit

Joined: Sun Aug 19, 2012 3:36 pm
Posts: 107
Well someone finally learned from the past and is willing to actually use (edit:: some, ok one of) their tools properly.


Top
 Profile  
 
PostPosted: Thu Feb 15, 2018 12:34 am 
Offline
Safari Exhibit
Safari Exhibit

Joined: Sun Aug 19, 2012 3:36 pm
Posts: 107
Going OT, sorry

Properly using their tools would be learning to fork and merge "self streams" to get rid of so many of these problems before they come up. Meat-think not fast enough? Run on a bit of substrate designed to be thinky and fast for a bit.


As for the stupid 24h or so without backups.. That's still just stupid. Every person who regularly excretes waste should have backing up regularly for the punning of "dropping a log" alone.


Top
 Profile  
 
PostPosted: Thu Feb 15, 2018 3:33 am 
Offline
Carnie
Carnie
User avatar

Joined: Fri Jun 22, 2012 5:44 pm
Posts: 2588
DrCron wrote:
Every person who regularly excretes waste should have backing up regularly for the punning of "dropping a log" alone.

Ohohoho.

Of course then anyone brought back from a back-up would naturally be 'Number 2'.


Top
 Profile  
 
PostPosted: Thu Feb 15, 2018 5:57 am 
Offline
Monkey House Exhibit
Monkey House Exhibit

Joined: Tue Feb 05, 2013 9:55 pm
Posts: 397
DrCron wrote:
Going OT, sorry

Properly using their tools would be learning to fork and merge "self streams" to get rid of so many of these problems before they come up. Meat-think not fast enough? Run on a bit of substrate designed to be thinky and fast for a bit.


As for the stupid 24h or so without backups.. That's still just stupid. Every person who regularly excretes waste should have backing up regularly for the punning of "dropping a log" alone.

Except that would still be about once per 24 hours


Top
 Profile  
 
PostPosted: Thu Feb 15, 2018 2:36 pm 
Offline
Monkey House Exhibit
Monkey House Exhibit

Joined: Fri Jul 01, 2016 8:10 am
Posts: 478
sotanaht wrote:
DrCron wrote:
Going OT, sorry

Properly using their tools would be learning to fork and merge "self streams" to get rid of so many of these problems before they come up. Meat-think not fast enough? Run on a bit of substrate designed to be thinky and fast for a bit.


As for the stupid 24h or so without backups.. That's still just stupid. Every person who regularly excretes waste should have backing up regularly for the punning of "dropping a log" alone.

Except that would still be about once per 24 hours


And in this case, it wouldn't help much unless the systems were in constant contact ANYWAY, because the more up to date backups would have been atomized with the ship.

It's not a factor of HOW it's done, it's a factor of how often and how much bandwidth it uses. Also how easy it is to track and hack and jam said transfer.

Considering how easy it seems to be to trace hypernet access, even heavily encrypted, the burst method every 24 hours would seem to be the most reasonable measure between security and having recent backups.

That said, scheduling everyone's for the same time would seem to defeat the purpose of the security. SOMEBODY is going to notice all that hypernet bandwidth going somewhere. Unless its compiled into a single burst by the local system before being sent back to Eina-Afa and from there to whatever backup systems they have.


Top
 Profile  
 
PostPosted: Thu Feb 15, 2018 4:32 pm 
Offline
Safari Exhibit
Safari Exhibit

Joined: Sat Dec 29, 2012 1:35 am
Posts: 110
Kendrakirai wrote:
sotanaht wrote:
DrCron wrote:
Going OT, sorry

Properly using their tools would be learning to fork and merge "self streams" to get rid of so many of these problems before they come up. Meat-think not fast enough? Run on a bit of substrate designed to be thinky and fast for a bit.


As for the stupid 24h or so without backups.. That's still just stupid. Every person who regularly excretes waste should have backing up regularly for the punning of "dropping a log" alone.

Except that would still be about once per 24 hours


And in this case, it wouldn't help much unless the systems were in constant contact ANYWAY, because the more up to date backups would have been atomized with the ship.

It's not a factor of HOW it's done, it's a factor of how often and how much bandwidth it uses. Also how easy it is to track and hack and jam said transfer.

Considering how easy it seems to be to trace hypernet access, even heavily encrypted, the burst method every 24 hours would seem to be the most reasonable measure between security and having recent backups.

That said, scheduling everyone's for the same time would seem to defeat the purpose of the security. SOMEBODY is going to notice all that hypernet bandwidth going somewhere. Unless its compiled into a single burst by the local system before being sent back to Eina-Afa and from there to whatever backup systems they have.

And now you have me wondering whether the targets of the long guns are being traced by those backup traffic bursts.

_________________
Proud driver of the Gruel-Retriever LVSR and uncertified gruel thief.


Top
 Profile  
 
PostPosted: Thu Feb 15, 2018 4:42 pm 
Offline
Monkey House Exhibit
Monkey House Exhibit

Joined: Sat May 14, 2011 10:10 pm
Posts: 455
Kendrakirai wrote:
sotanaht wrote:
DrCron wrote:
Going OT, sorry

Properly using their tools would be learning to fork and merge "self streams" to get rid of so many of these problems before they come up. Meat-think not fast enough? Run on a bit of substrate designed to be thinky and fast for a bit.


As for the stupid 24h or so without backups.. That's still just stupid. Every person who regularly excretes waste should have backing up regularly for the punning of "dropping a log" alone.

Except that would still be about once per 24 hours


And in this case, it wouldn't help much unless the systems were in constant contact ANYWAY, because the more up to date backups would have been atomized with the ship.

It's not a factor of HOW it's done, it's a factor of how often and how much bandwidth it uses. Also how easy it is to track and hack and jam said transfer.

Considering how easy it seems to be to trace hypernet access, even heavily encrypted, the burst method every 24 hours would seem to be the most reasonable measure between security and having recent backups.

That said, scheduling everyone's for the same time would seem to defeat the purpose of the security. SOMEBODY is going to notice all that hypernet bandwidth going somewhere. Unless its compiled into a single burst by the local system before being sent back to Eina-Afa and from there to whatever backup systems they have.


Tailor did offer Tagon a running backup, once.


Top
 Profile  
 
PostPosted: Thu Feb 15, 2018 10:26 pm 
Offline
Monkey House Exhibit
Monkey House Exhibit

Joined: Fri Jul 01, 2016 8:10 am
Posts: 478
I believe what he offered was to move up his scheduled backup rather than a stream, but point. :)


Top
 Profile  
 
PostPosted: Fri Feb 16, 2018 12:53 pm 
Offline
Monkey House Exhibit
Monkey House Exhibit

Joined: Sat May 14, 2011 10:10 pm
Posts: 455
Kendrakirai wrote:
I believe what he offered was to move up his scheduled backup rather than a stream, but point. :)


Not a stream, and not a rescheduling, but I forgot the term and didn't search long enough to find the referenced strip.
An incremental backup, which is basically just a partial backup that contains only that which has changed since the last full backup. Basically, he offered to run a backup on just the last couple-few hours, since Kaff Tagon's last backup was only a couple-few hours old at that point.


Top
 Profile  
 
PostPosted: Fri Feb 16, 2018 2:32 pm 
Offline
Concession Worker
Concession Worker
User avatar

Joined: Mon Jun 29, 2015 9:52 pm
Posts: 1302
Sean wrote:
Kendrakirai wrote:
I believe what he offered was to move up his scheduled backup rather than a stream, but point. :)


Not a stream, and not a rescheduling, but I forgot the term and didn't search long enough to find the referenced strip.
An incremental backup, which is basically just a partial backup that contains only that which has changed since the last full backup. Basically, he offered to run a backup on just the last couple-few hours, since Kaff Tagon's last backup was only a couple-few hours old at that point.

...differential /incremental?

_________________
Rule of thumb is that if you need to use a squeegee, they're at least Laz-4.


Top
 Profile  
 
PostPosted: Fri Feb 16, 2018 7:34 pm 
Offline
Monkey House Exhibit
Monkey House Exhibit

Joined: Fri Jul 01, 2016 8:10 am
Posts: 478
Sean wrote:
Kendrakirai wrote:
I believe what he offered was to move up his scheduled backup rather than a stream, but point. :)


Not a stream, and not a rescheduling, but I forgot the term and didn't search long enough to find the referenced strip.
An incremental backup, which is basically just a partial backup that contains only that which has changed since the last full backup. Basically, he offered to run a backup on just the last couple-few hours, since Kaff Tagon's last backup was only a couple-few hours old at that point.


Ah yes, an incremental backup. Not as big a packet, but still a pretty big packet, and if done continuously, or even on a schedule, still detectable and potentially traceable.


Top
 Profile  
 
PostPosted: Sat Feb 17, 2018 11:41 am 
Offline
Monkey House Exhibit
Monkey House Exhibit

Joined: Sat May 14, 2011 10:10 pm
Posts: 455
Kendrakirai wrote:

Ah yes, an incremental backup. Not as big a packet, but still a pretty big packet, and if done continuously, or even on a schedule, still detectable and potentially traceable.


You're overlooking the teraport in all this. If you have both backup technology, a teraport system that you can use freely, and a OTP with your backup server, a OTP that includes location coordinates, you can put your backup in a probe, teraport that probe as many times as you wish to feel safe, so long as the last jump landed your probe at the pre-determined, single-use set of coordinates, where your backup providers probe would meet yours for a data transfer, and return. Again, by a circuitous route.

In the same way, you would presumably communicate. Regularly scheduled dead-drops to points deep in space far from listening stations. A new schedule of dead-drop locations would be provided in the same way.

Not a live video stream, but about as fast as email.


Top
 Profile  
 
PostPosted: Sat Feb 17, 2018 11:55 am 
Offline
Entertainment
Entertainment

Joined: Tue Jun 12, 2012 10:54 am
Posts: 845
I'd been thinking about that, as related to my "Terraport as heat sink" system. I guess it depends on your energy budget? I don't think anybody's commented on the energy cost of a terraport, but I can imagine it being expensive enough that you couldn't send an update once a second or so. Still a reasonable way to handle static backups though.


Top
 Profile  
 
PostPosted: Sat Feb 17, 2018 1:54 pm 
Offline
Monkey House Exhibit
Monkey House Exhibit

Joined: Fri Jul 01, 2016 8:10 am
Posts: 478
Sean wrote:
Kendrakirai wrote:

Ah yes, an incremental backup. Not as big a packet, but still a pretty big packet, and if done continuously, or even on a schedule, still detectable and potentially traceable.


You're overlooking the teraport in all this. If you have both backup technology, a teraport system that you can use freely, and a OTP with your backup server, a OTP that includes location coordinates, you can put your backup in a probe, teraport that probe as many times as you wish to feel safe, so long as the last jump landed your probe at the pre-determined, single-use set of coordinates, where your backup providers probe would meet yours for a data transfer, and return. Again, by a circuitous route.

In the same way, you would presumably communicate. Regularly scheduled dead-drops to points deep in space far from listening stations. A new schedule of dead-drop locations would be provided in the same way.

Not a live video stream, but about as fast as email.


That's extreme paranoia levels of security, and it's SUPER easy to kill without anybody ever knowing you've lost your last eight months of backups because somebody swatted your probe while it was leaving TAD-interdicted space.

And it makes it even MORE possible to hack because instead of a live stream of data, it's just sitting in some forage medium or other, static, with no method of checking against the original for errors or alterations.


Top
 Profile  
 
PostPosted: Sat Feb 17, 2018 2:31 pm 
Offline
Monkey House Exhibit
Monkey House Exhibit

Joined: Sat May 14, 2011 10:10 pm
Posts: 455
Kendrakirai wrote:
Sean wrote:
Kendrakirai wrote:

Ah yes, an incremental backup. Not as big a packet, but still a pretty big packet, and if done continuously, or even on a schedule, still detectable and potentially traceable.


You're overlooking the teraport in all this. If you have both backup technology, a teraport system that you can use freely, and a OTP with your backup server, a OTP that includes location coordinates, you can put your backup in a probe, teraport that probe as many times as you wish to feel safe, so long as the last jump landed your probe at the pre-determined, single-use set of coordinates, where your backup providers probe would meet yours for a data transfer, and return. Again, by a circuitous route.

In the same way, you would presumably communicate. Regularly scheduled dead-drops to points deep in space far from listening stations. A new schedule of dead-drop locations would be provided in the same way.

Not a live video stream, but about as fast as email.


That's extreme paranoia levels of security, and it's SUPER easy to kill without anybody ever knowing you've lost your last eight months of backups because somebody swatted your probe while it was leaving TAD-interdicted space.

And it makes it even MORE possible to hack because instead of a live stream of data, it's just sitting in some forage medium or other, static, with no method of checking against the original for errors or alterations.


Except, if it's also your method of staying in touch, your probe comes back, also via a circuitous route, with the latest news and the digital mailbag.
Further, you'd know if your probe left TAD interdicted space, because the only time it'd seriously risk leaving TAD interdicted space would be the two endpoints. On one end, you are a witness, and on the other, the middle-of-the-road meeting between your probe and your upstream contact. If it dies there, the upstream contact is compromised, at least to a certain extent, since that means the upstream contact leaked the rendezvous location.

And, again, your probe doesn't return, so you know something is up.

The middle hops would be so out of the way that only by pure, terrible luck would it hop out somewhere where anyone would be set up and care.

Really, the real risk would be the same ones that hit TOR occasionally. An incoming packet that tricks your system into squawking from its current location, rather than going through a pair of multi-jump intermediaries. Or one that infects your system just enough to encrypt and stego your itinerary into the outgoing mail.

Yes, if your communication was all one-way, then you could be losing all your outgoing information without ever realizing it.

Another risk, that occurs to me, would be if the mid-point rendezvous was compromised, and someone didn't swat your probe, but scooped it...and gained the return-track coordinates from it. This applies to both sides. Both sides need to trust the other not to scoop their drones and get the destination from them.
To mitigate this, it might be worth having the probe return half-way, rendezvous with a SECOND probe, that has the rest of the route directions, but which is enabled enough to self destruct rather than return, if the probe didn't return, alone.
Use an air gap long enough that communications can be effected, and weapons fire might be effected, but capture attempts would be ineffective. If the drone might be anywhere within a light-second on arrival, it can communicate a packet of data while being as difficult to predict exactly where it will pop up.
Both probes, in any exchange, would also need to jam superluminal coms, so neither side could call in reinforcements to the exact spot the probe landed.

And I don't consider it too paranoid, if it works, and if the probes can, under normal successful circumstances, be recovered and reused.

So that now makes three midpoint transactions. One in the middle between two organizations. One on either side, to ensure neither mid-point probe had a tail, or a doppelganger.
And yes, once the first drone came back, alone, and could be vetted, it could be fed the remaining information on how to get there itself. Be walked in, rather than hand off the data and go back. Or go away.


Top
 Profile  
 
PostPosted: Sat Feb 17, 2018 3:19 pm 
Offline
Monkey House Exhibit
Monkey House Exhibit

Joined: Fri Jul 01, 2016 8:10 am
Posts: 478
Sorry, I man space that's interdicted by anybody BUT you. Some of those TAD wells are a week across at the apparently typical cruising speed of about .3c. That gives anybody who sees you launch one, or just finds it in space, plenty of time to dick with the probe and it's payload. I always assumed the probe would be destroyed or reused at either end. It's getting the probe someplace it's POSSIBLE to Teraport in the first place that's the dangerous part.

And if you rely exclusively on this, your backup is going to be a week old if you're in one of those deep TAD systems, like Sol. And the probe is also going to have the meet coordinates in its computer to boot.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 19 posts ] 

All times are UTC - 6 hours [ DST ]


Who is online

Users browsing this forum: Bing [Bot] and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group