Recent Comments

Jan 3, 2021
1/3/21, 5:25 PM
Very hot induction and story!
nycboot
1/3/21, 5:24 PM
Wow - that scene with Malik hiding was really thrilling! Good luck on producing more!
Leo
1/3/21, 4:46 PM
You should make the dad/king become his obedient slave
1/3/21, 4:38 PM
This was a fantastic story.
SMC2710
1/3/21, 4:21 PM
Great work. Please continue. i look forward to meeting the new Ben and his soon to also be transformed frat brother Jaden.
1/3/21, 3:51 PM
A quick shout-out to jockbear, Bound_Up-Boy, and DannyStorm -- Thank you for all your kind comments! And Bound_Up_Boy -- I'll go and see if it lets me add that tag like you suggest!
nycboot
1/3/21, 2:37 PM
Whoa! Twist ending of this chapter. Of course that makes us want to see what happens. :) Your writing keeps the tension going - good job!!
1/3/21, 2:34 PM
The experience of editing Lexorius's two "Empire" stories helped to inspire my own story, "[Empire Days](https://www.gayspiralstories.com/story/show/203457)." I wouldn't say it's set in exactly the same fictional universe, but it uses some similar concepts.
1/3/21, 2:06 PM
I am loving the series so far.. Really good chapters and set ups. I'm not fussed about the woman.. Call me an asshole.. You could just make them lesbians
1/3/21, 12:42 PM
I can't help but break my suspension of disbelief when I see characters completely misrepresent computer science when they should know better. And while this story had plenty of that (a file doesn't have "defenses" by itself, it's the OS that imposes permissions on the filesystem!), I'm going to address the biggest one: Computers not having personal agency and autonomy doesn't make computing "absolute". Unless you're writing a program that will run with absolutely no layers of abstraction below it (not even the bootloader!), your program will be affected by things outside of your control. For example: a core of a computer can only run one instruction at a time, and most programming languages assume that each "[thread of execution](https://en.wikipedia.org/wiki/Thread_(computing))" in the program has a core all to itself. But if you look at the amount of threads running in a system, they tend to dwarf out the number of cores. So the OS has to "timeshare" each core across different threads by [stopping the thread every so often and then resuming it](https://en.wikipedia.org/wiki/Context_switch). This means you can't know whether a thread did something before or after another thread did something else, unless you explicitly [make either thread wait for the other](https://en.wikipedia.org/wiki/Lock_(computer_science)). That can lead to things working right most of the time but failing inexplicably once in a while, or to things working reliably on your beefy development machine but not on lower-end computers with fewer cores. And that's assuming the computer is the only thing in the universe. Although far less common nowadays, it's still possible for some ionizing radiation to [flip a bit in memory](https://en.wikipedia.org/wiki/Single-event_upset). So yeah, computing isn't all that absolute.