code logs -> 2019 -> Sun, 23 Jun 2019< code.20190622.log - code.20190624.log >
--- Log opened Sun Jun 23 00:00:59 2019
02:51
<&Reiver>
ToxicFrog: Oh dear. Is this a 'It will recover in time' or a 'welp, broke now'?
03:11
<&ToxicFrog>
Reiver: the former.
03:11 * Reiver nods
03:12
<&ToxicFrog>
Even if you completely lose all your money, have somehow managed to drain all the servers you can hack, and have no hacknet nodes, you can always get a job in the city and leave that idling for a bit.
03:12
<&Reiver>
LOL
03:13
<&Reiver>
Well, fair enough then :)
03:13
<&Reiver>
I love that the failure mode is "Go get a job", though
03:38
<&ToxicFrog>
Ok, I finally have my master control program up and running!
03:38
<&ToxicFrog>
It scans for rootable and hackable systems; every rootable system has a worker automatically installed on it.
03:38
<&ToxicFrog>
Hackable systems are prioritized based on what needs to be done to them and workers are assigned to them accordingly.
03:38
<&ToxicFrog>
I do wonder if I should set some upper bound on the number of workers I can have tied up in weaken(), though.
03:39
<&ToxicFrog>
At the moment all of them are trying to weaken() the same very high-level server and most of them won't even return for another work assignment for half an hour.
03:40
<&Reiver>
Perhaps a percentage?
03:40
<&Reiver>
Or scan for, eg, half a dozen and target the softest?
03:41
<&ToxicFrog>
The current behaviour is that if any servers need to be weaken()ed it prioritizes that first, since that gives the best long-term results
03:41
<&ToxicFrog>
(since every weaken() makes subsequent runs of hacking tools against that server faster)
03:41
<&ToxicFrog>
But the unforseen problem here is that if a really hard target shows up, the entire swarm will get tied up working on it and income from the swarm drops to 0 until they're done.
03:42
<&ToxicFrog>
I don't want to set a cap on what percentage of the swarm can be weaken()ing because there are legitimate uses for having all of them doing that, but I may set a limit on how many can be targeting the same server at once.
03:43
<&Reiver>
Oh, I meant "No more than X% should target one server at a time"
03:43
<&Reiver>
Also, is it a swarm or a botnet?~
03:45
<&ToxicFrog>
It's totally a botnet
03:56
<&ToxicFrog>
https://gist.github.com/ToxicFrog/d5829e3c0d6d0b68d59b10a32bf85de1
04:00
<&ToxicFrog>
Reiver: that's what the startup sequence looks like.
04:42 celticminstrel [celticminst@Nightstar-6an2qt.dsl.bell.ca] has quit [[NS] Quit: And lo! The computer falls into a deep sleep, to awake again some other day!]
05:11 Vorntastic [uid293981@Nightstar-6br85t.irccloud.com] has joined #code
05:11 mode/#code [+qo Vorntastic Vorntastic] by ChanServ
07:12
<&Reiver>
https://www.zdnet.com/article/nasa-hacked-because-of-unauthorized-raspberry-pi-connected-to-its-network/
07:33
<&McMartin>
https://pbs.twimg.com/media/D9tdNb_XYAADeHd.jpg
07:51
<&Reiver>
Sidenote to your link: I have now clicked on your link four times. >_<
07:53
<&McMartin>
Were they at least different copies >_>
07:56
<&Reiver>
They were not!
07:56
<&Reiver>
They were right here!
07:57
<&McMartin>
OK
07:57
<&McMartin>
Be warned that I have pasted it in multiple channels we are both in~
08:03 * Vorntastic grumps at the inaccuracy of the graph
08:12 * Vorntastic sets about mathing in Python once more. This is annoying on mobile but he's got a thought
08:15 Degi_ [Degi@Nightstar-rt69t3.dyn.telefonica.de] has joined #code
08:45
<&McMartin>
Hahahahaha
08:45
<&McMartin>
POSIX!
08:45
<&McMartin>
https://twitter.com/cperciva/status/1141852451756105729
08:52 * McMartin gets the core of his disassembler working, which involves handling some super-dumb corner cases that the smoke test smoked out.
08:56 Kindamoody[zZz] is now known as Kindamoody
09:43
<~Vorntastic>
Whee, terrible stackoids
10:07
<~Vorntastic>
Hooray
10:07
<~Vorntastic>
1,6,90,2040
10:08
<~Vorntastic>
http://oeis.org/A001499
10:10 Degi_ [Degi@Nightstar-rt69t3.dyn.telefonica.de] has quit [Ping timeout: 121 seconds]
10:10
<@TheWatcher>
Huh
10:20 Degi_ [Degi@Nightstar-rt69t3.dyn.telefonica.de] has joined #code
10:58 Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has joined #code
11:31
<&ToxicFrog>
oh my god, part of the problem was that it wasn't ignoring targets that I didn't actually have enough skill to hack
11:36
<~Vorntastic>
I should poke at this game
11:46
<&ToxicFrog>
I have now written something like 500 lines of code for it
12:33 * TheWatcher eyes that bitburner game
12:58 celticminstrel [celticminst@Nightstar-6an2qt.dsl.bell.ca] has joined #code
12:58 mode/#code [+o celticminstrel] by ChanServ
13:32 Degi_ [Degi@Nightstar-rt69t3.dyn.telefonica.de] has quit [Connection closed]
14:48 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has joined #code
14:48 mode/#code [+qo Vornicus Vornicus] by ChanServ
17:29 * Vornicus examines the legacy vornonoi code with references, tries to figure out why he needed certain checks
17:31
<~Vornicus>
So - I have a thing that checks whether an edge needs correction. Basically it has to check whether the "far" point is inside the circumcircle of the other three. ...for some reason, I have here that I am checking convexity first.
17:32
<~Vornicus>
But if the quadrilateral is not convex, then either 1. the far point is outside of the circumcircle naturally, or 2. we've lost the handedness invariant somewhere
17:37
<~Vornicus>
So either 1. this is a test that never succeeds or 2. this is dealing with a freaky edge case involving the points at infinity.
17:37
<~Vornicus>
But I don't have anything beyond "-- I need to check whether the quadrilateral is convex. If not, then the edge is unavoidably legal!
17:37
<~Vornicus>
"
17:38
<~Vornicus>
The psychopath with anger issues has discovered where I live.
18:01 Vorntastic [uid293981@Nightstar-6br85t.irccloud.com] has quit [[NS] Quit: Connection closed for inactivity]
18:35 Kindamoody is now known as Kindamoody|afk
19:17
<~Vornicus>
Ugh. Goddamn hate geometry.
19:31
<&[R]>
I hate hate-geometry as well. Why can't we just have love-geometry instead
19:33
<~Vornicus>
Small irony: this thing is for löve
20:33 Vorntastic [uid293981@Nightstar-6br85t.irccloud.com] has joined #code
20:33 mode/#code [+qo Vorntastic Vorntastic] by ChanServ
20:35
<&ToxicFrog>
Goddamn async/await
20:35
<&ToxicFrog>
It's like coroutines except awful
20:56
<&McMartin>
Yeah, not a fan
20:56
<&McMartin>
Though I have to admit that most of my objections to it sound exactly the objections made in the 1960s regarding symbolic assemblers
21:06
<~Vorntastic>
Pff
21:08
<&[R]>
What arguments were there?
21:09
<&McMartin>
"You don't really know what it's doing behind your back", "You're thinking about a system that isn't actually what the computer will be doing"
21:11
<&McMartin>
With the first also being "I *do* really know what it's doing behind my back and it terrifies me, why should I trust it"
21:25 McMartin [mcmartin@Nightstar-ipm463.ca.comcast.net] has quit [[NS] Quit: brb]
21:28 McMartin [mcmartin@Nightstar-ipm463.ca.comcast.net] has joined #code
21:28 mode/#code [+ao McMartin McMartin] by ChanServ
21:34 Kindamoody|afk is now known as Kindamoody
22:06 Degi [Degi@Nightstar-rt69t3.dyn.telefonica.de] has joined #code
22:49 himi [sjjf@Nightstar-v37cpe.internode.on.net] has quit [Ping timeout: 121 seconds]
23:21
<&ToxicFrog>
I mean, in my case, I know what it's doing behind my back, and it doesn't terrify me, it's just a gigantic boilerplate-laden pain in the ass
23:22
<&ToxicFrog>
"what if we had coroutines, but every function that can (transitively) ever call a coroutine needs to be annotated as such, and every call of such a function also needs to be annotated in ways that restrict where, syntactically, you can call them"
23:22
<&ToxicFrog>
(I realize that they aren't coroutines as such, but from a programmer's perspective they can be treated as if they were apart from the annotations)
23:23 Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has quit [Ping timeout: 121 seconds]
23:29 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has quit [Connection closed]
23:29
<&McMartin>
ToxicFrog: Right, see, the behind my back here is "translating what looks like a linear function into a state machine and associated invisible fields for location within it"
23:42 Kindamoody is now known as Kindamoody[zZz]
--- Log closed Mon Jun 24 00:00:00 2019
code logs -> 2019 -> Sun, 23 Jun 2019< code.20190622.log - code.20190624.log >

[ Latest log file ]