text:
Shedded Soul
[01:51] Day 41, Attempt 17. How quickly mortal volition erodes.
A part of Valcen had watched his own mental progression with a certain detached interest. Neither the count of days nor the count of attempts were near triple digits and he was already considering turning today's scheduled meeting into an ultimatum.
Already willing to undermine the reason you're going through this ritual at all? Weak.
He was disappointed in himself. He was disappointed in the biology that wrought these emotions. It amplified how fragile he felt. It made it frightfully clear how fleshy morals were, how tied to his biological machinery. A construct of the mind no more than hunger or exhaustion. Far too easy to get sick and tired of. A burden.
[01:52] He wasn't willing to give up on his just yet. He had sternly told himself he would at least try to make it to the count of fifty, but if the trend continued, realistically, he would be lucky to make it to thirty. Stubborn willpower would only get him so far.
He weighed the dim, glowing orb in his left forepaw, observing how useless it was in the bright light of the corridor. He'd convinced the Nayabaru to turn off the lights in the cell, although they promised there would be hell to pay if he ever let go of the orb while in it, more so if he dared to vanish into the darkness for even a moment.
[01:53] Their cameras would be nearly blind, but they wanted to be sure they could at least identify Valcen – that Valcen could be held accountable.
And so it was dark in the captive's cell when Valcen slipped into it, cradling just enough light to his chest that his thin mane was tainted with dull gold, and the right edge of his jaw was awash in an odd, warm glow.
Reh:
[03:08] Before the door to his cell had even opened, the captive was jerked into alertness by the sudden, blissful darkness. Something unusual was happening. Nayabaru never shut off the lights in his cell — or anywhere else, as far as he could tell. He wasn't even aware they could be shut off until now. Was this some kind of trick? Sabotage? Or — possibly — a rescue attempt?
He knew that such things did happen occasionally. That they could happen, that they were possible. He'd never heard a story of such a thing happening in Katal, though. Given the size and complexity of this place, though — and given its reputation — he couldn't imagine anyone being reckless enough to try. But hope seldom bothers listening to reality, and his had somehow refused to die in the — months? — it's been since he was dragged in here.
[03:09] And so, when the door to his cell opened, permitting entry not to a Hesh but to a fellow kavkem, there was a jolt of surprise. He immediately tried to stand, before the metal collar fastened around his neck and the deceptively short chain attaching it to the floor reminded him precisely why that was a bad idea. He scrabbled his dulled claws against the chain in frustration, then turned his attention back to his potential savior.
"Shyilun?" he whispered hoarsely, a hopeful pleading in his expression.
[03:21] The phrase cut across his chest like a blade, part spike of frustration, part mangled empathy crying out in silence. It took him a moment to gather himself, to realign himself with the strategy of the day, inasmuch as it could still be called that.
Might as well.
Finally: "No." A single deep breath, clearly audible in the eerie silence of the cell. "Not anything like that, not for a long time, I don't think. No, I only have some questionable privileges.
"The good news is that one of the privileges is the ability to extend the privileges, although not for wholly arbitrary reasons.
[03:22] "No, rather, I am here to offer you a shocking degree of autonomy and far less of the poking, prodding and bored Hesh torture you would otherwise suffer – for the low, low price of your absolute obedience to me personally, whenever I choose to invoke it."
[04:22] The reply drove a blade into his gut, puncturing the hopeful narrative. Naive, foolish, shameful. He squeezed his eyes shut, trying to bury the remains of his ideas about what sort of interaction this was and instead focus on the words coming from his visitor's mouth.
Not that those words painted a picture that made much sense. It was odd that he was speaking Naya. It was odd that he spoke of having 'privileges'. And the offer — the offer drove a shiver down his spine, sounding entirely unlike something a kavkem would ever request. Enough to make him question. The whole thing felt confusing and dangerous.
For a long moment, he simply stared at the visitor, as if studying his shape could impart knowledge of his motives. He was kind of mangy, with an uneven coat of feathers; evidence of prior dealings with Hesha? "What... do you mean, 'privileges'? How does a kavkem get 'privileges' in Katal?" If a kavkem is even what you are...
[04:32] "Presumably," Valcen quipped, drily. "A kavkem would get privileges in much the same way I've gotten them – by helping the Nayabaru innovate technology they desire but lack the intelligence to create."
[04:33] Leaving the implication that he was not a kavkem to dangle, he let his gaze drop down to the orb of light he was still clutching to his chest, directing a moment of resentment at the inanimate object in the form of a glare. He twisted the device a little, as though it were a crystal ball he might scry the future out of, then brought his attention back to the captive.
Sweetly intoned: "Do you know what a qidravem is?" Somewhere in Valcen's mind, he considered the various interpretations a kavkem might have of that mythological concept, musing on one of them: Dealing out potential threats now, are you?
[08:36] Not a kavkem. Or one so far removed from the ordinary to both speak in such a manner and to offer help to the Nayabaru. His mind began constructing other possibilities. A yirh? Possible, though unlikely. A kiikam? Perhaps. Nateh? ... If a god was helping the Nayabaru, it was probably one of the Havnateha, so hopefully not that. ...Or it was Tkanetar, though if that were the case, he'd probably be on fire and begging for a swift death by now, right?
The next question prompted a panicked jolt from the captive kavkem, accompanied by a wide-eyed stare at his unlikely visitor. A havnateh wants to use your body. A mental image of his soul torn to shreds, of his body hollowed out to make room for a malicious divinity, lodged itself in his psyche. As if his body language hadn't already answered Valcen's question, a nervous voice replied: "I'm aware of what such a thing does. And what its purpose is." ...But if you wanted to take my body, surely you would have done so already? Unless... "I... take it that's the alternative to your offer?"
[22:29] Panic was perhaps not what he had expected. A little strong. He watched the cowering kavkem with curiosity, taunted by the invisible thought processes in a skull only a very countable number of inches away from him. He could reach out and touch it. It wouldn't tell him anything about what the captive was thinking; not yet. Not for a while.
As the captive uttered a nervous question of his own, Valcen tilted his muzzle and his facial expression adopted a subtle disappointment. There really hadn't been any cause to believe this dabbling in a mysterious air would work, had there? But what else was there, but to vary the themes?
He resisted the immediate urge to simply end the conversation prematurely, even if it was only a single step not taken. Instead, he showed the way: "The alternative is that we simply forget about it. Nothing changes. You stay here; I move on."
Meanwhile, Valcen's fingers lodged themselves into the irregularities that made up the surface of the orb and he let it dangle from his wrist a little, as though considering casting it aside.
No. A thought like a whiplash. His attention swerved back up, a hard gaze latching onto the kavkem. The grip on the orb tightened, then flared into brightness purely by vicinity alone as he stepped across to the chained bundle until he was looming over the captive, tongue running along unblemished teeth.
[22:30] "Listen," Valcen leant down in disregard for any damage the captive might cause him, hiding the resultant nervous flutter of his mortal heartbeat. "The qidravem will shackle me, not you. But while it's one thing to craft one, it's another to ensure it has adequate hosts. I cannot do latter on my own.
"So I ask you now: Do you want to make a difference for your people? Or do you want to be the number the Nayabaru designate you as?" Or the number seventeen. You can be the number seventeen as well, if you prefer.
[05:42] Valcen's initial answer seemed to calm the captive somewhat, enough to let him consider his options. There wasn't any immediate danger here — at least, not yet. Though that did raise the question: Why would he bring up qidravema at all?
Before he had much time to ponder that question, his visitor was advancing threateningly, wielding the glowing orb like one might a sacred artifact. ...For all he knew, it could be one. An arm twisted up to partially shield his eyes from the glare, as his gaze shot back and forth between the orb and the kavkem-shaped visitor, attention focused on every word.
So many subtle, critically important things in so few words. So many questions raised. His mind struggled to put them all into some kind of order. The being looming over him knew how to craft qidravema. It also sounded like he didn't have one — yet. He needed a host — 'hosts', plural? What did that mean? How was he going to be involved? Not reincarnated by the qidravem, but possibly still with his body as a host. Possibly not, though.
And then, of course, that question. The answer was so obvious that he couldn't help but parse it as rhetorical, but there was an enormous gap between 'Sort-of-freeing one kavkem and demanding obedience and possibly a body in return' and 'Making a difference'. (Not to mention a worthy distinction between 'Making a difference' and 'Making things better'.) "Are you... Does that mean you're going to help?" A moment later, as if
realizing the ambiguity of his question: "Help the kavkema? Help Tamachelu? After you make your qidravem, and... have your hosts?"
Even after the words had left his throat, a part of him chastised himself: Did the answer even matter? What was the alternative? A lifetime of torment by the Hesha. Worse, a lifetime of torment by the thought that here was a chance, a moment when he could have taken the next step. A quest, a purpose, and all he had to do was reach out and take it.
Any Dynasharigadech worth his soul ought to leap at this opportunity. Why was he hesitating? Fear of the unknown? Fear of annihilation by a qidravem? Fear that whatever this being was, it might not have Tamachelu's or the kavkema's best interests at heart? If he could learn what it knew, if he could use or transmit that knowledge, if he could influence it...?
[20:29] Valcen's mind was cast into a sharp detour, parsing the question as orthogonal. He lingered in his posture – as if paused but for his breath and strictly physiological processes. Perhaps too long.
The truth was seductively close. It would be easy to give yet another neutered explanation of what he was hoping to achieve in the long term. An explanation that had in its previous sixteen variants gotten him precisely nowhere.
But lie? Could he lie yet? Had his patience eroded to the point where he was willing to say anything at all? It might have been a more appealing option, had he known what to say – what the magic words were that would yield enlightenment in the captive, that would yield what he wanted.
The theme du jour came back to him – mystery. There was no mystery in the hard statistics. 'There are too many variables in this equation as that I could give you any guarantees, but I am taking measures that I hope will have positive effects in the long run,' hardly fit today's narrative.
[20:30] With a mixture of nausea and aggravation coiled in his gut, Valcen offered: "I plan to live a very long time – but right now, in the immediate future, I am going to make matters worse."
[01:30] The response drove a spike of nausea into the captive's gut. "I see," he responded quietly, letting his gaze fall from the visitor's face to a spot on the opposite wall. Of course. Of course it wasn't going to help in the short-term; it was helping the Nayabaru after all.
And yet... it really wasn't the short-term he was as concerned about. 'Making a difference', if that difference could be felt in the distant future — that still counted. A part of him sought to clarify, to ask yet more questions. But what good would that do? Hadn't a part of him already made up his mind? Wasn't every additional question just an opportunity to dissuade him from the only true path forward?
Eventually, his caution and curiosity managed to win out over his devotion to his ideals. "...You spoke of making a difference for the kavkema. What kind of difference are you promising?" His eyes struggled to fix on the kavkem face looming above him. "Are you going to help us? Eventually?"
[01:55] There it was, the inevitable hurdle of statistics. Mortals always used that word – eventually – without really grasping what it meant and what a diluting force the progression of time was, a constant gnawing on carefully made plans.
[01:56] Valcen took a small step back, although the cell didn't leave so much room behind him as that he had all that much choice in the length of his stride, making the variation mostly meaningless. "If you want a promise, I can't give you one. Timescales, circumstances, events... they complicate things.
"Right now, I don't have a qidravem, and if you decline, then I will ask the next kavkem, and if they in turn decline, and this chain of events continues..." – ...then I'll probably just stop caring about your consent. – "...eventually, I die, and belie any promise I made.
"My interest is in Tamachelu, not in the kavkema. But if I can affect the status quo in your people's favour, this would please me." And if it means qasaia, so be it.
[03:17] With that, the pieces finally started to fall into place, laying his worst fears and misgivings to rest. This wasn't a havnateh — at least, not yet. Some other sort of shari in a kavkem's form, one who knew how to make a qidravem and — in spite of helping the Nayabaru, at least seemed to want to help the kavkema and Tamachelu. The earlier statement that things would become worse in the near future at least painted him as honest. What more could he ask for?
His nervousness wasn't entirely gone, of course — there was still the chance this could end horribly. There was still a chance he was making a preposterously huge mistake. But the unknown always held these terrors, and it always would. Instead, he focused on the alternative, the hopelessness if he refused, the lost opportunities he'd never have a chance to reclaim. Squeezing his eyes shut and taking a deep breath, he exhales the words: "I accept your offer."
[03:36] For a moment, Valcen's mind simply went blank. With a supreme mental effort, he stopped himself from uttering a 'What?' out loud. His earlier frustrations slammed into his confusion and melded into a brief spike of anger. He fought that down as well.
A strange hollowness invaded him. "Great," he said, politely and with a positive undertone that bore no relation to anything he was feeling. Fingers tapped against the glowing orb-light in a casual rhythm, expressing a disembodied excitement.
[03:37] Then it caught up to him as a surge of relief and elation. He let his eyes close, taking a deep breath, scolding and mocking himself lightly for having doubted, scolding and mocking himself equally lightly for the scolding and mocking, then dipped down his muzzle well below the height of Baishar's in gratitude.
The top of his head bumped deliberately against Baishar's shoulder and collarbone, contact softened by the mane. Sound partly muffled by the strange posture, Valcen murmured: "Okay."
He repeated it more softly, before withdrawing and gathering himself into a more professional posture, guiding all of his giddiness into a carefully arranged tension. "My name is Valcen," he introduced himself, as if all of this had come in reverse conversational order. "Let's get you out of here."
[09:13] There was a long moment of silence — long enough that he was wondering if he should repeat himself a bit louder, before his visitor finally replied. The initially simple-sounding response gave way to something else, a deep bow of gratitude, a sense of relief. It was puzzling — mostly for how little it fit with his earlier behavior. It felt deeply kavkem.
Finally, a name to place on his... whatever this relationship was. Savior? Mentor? Master? Guardian? ...Time would tell. "Valcen," he repeated, testing the sound. Like 'valcee'? an internal voice offered. Perhaps, even if he didn't look particularly strong. "My name is Baishar."
[18:16] "Well, thank you, Baishar," Valcen half-mumbled the near-platitude, meaning it as a gesture of appreciation, his mind wandering off. In a fleeting, absent-minded gesture, his free forepaw brushed against Baishar's muzzle near its tip, like an aborted petting gesture, and then he was turning.
A moment later saw him facing the entrance of the cell, reaching up with his free forepaw, then thumping against it a few times. "I have my volunteer," Valcen said loudly, although it was unlikely it could be heard outside – perhaps as a very soft mumbling.
Indeed, for a while, nothing happened. He was just about to repeat both gesture and call when the light came back on – abruptly, without transition, biting in his eyes, prompting a soft hiss. He staggered back from the door, mostly in an intentional motion, to leave space for whatever—
[18:17] It snapped open, and a Nayabaru, standard Hesh weapon in hand, stepped first in, then past Valcen with a snort, leering at Baishar. The wicked spike at the end of the spear-hook hybrid swerved dangerously, coming to rest near Baishar's muzzle, as though intent on gauging his eye out.
But instead, the Nayabaru had crouched, though casting suspicious glances back at Valcen occasionally, clearly tense. Baishar was less of a threat, of course, claws and teeth blunted as they were. "Make us any trouble," the Nayabaru growled. "And we stop caring about your privileges." The tone made it clear us referred to the Hesha, not Valcen.
One arm roughly pushed into Baishar's side, brushing him aside to tend to the anchors of the shackles.
Valcen had crowded away from the Nayabaru as much as the cell's size allowed, pressed into a thin corner, but effectively still in the way. The orb of light was presumably still lit – but with the regular light back on, it just seemed like some kind of ball he'd been carrying, devoid of any mysticism.
[20:54] The brief affectionate gesture felt unexpectedly nice, after what must have been at least a month of captivity and the anxiety of their introduction. It had been a while since he'd last experienced something resembling kindness.
As Valcen banged on the door and shouted to whoever was listening, thoughts began to coalesce around the recent shift in behavior. Something Valcen had said began to stand out: 'If you decline, then I will ask the next kavkem, and if they in turn decline....' It was very unlikely he was the first kavkem Valcen had asked. Cautiously, quietly, driven by curiosity, he asked, "How many—?"
Before he could finish that thought, the world returned to its familiar blinding brightness. There was a yelp of distress from Baishar as he covered his eyes with his forepaws, the required posture making the edges of his restraints dig into his skin.
He felt the Hesh's motion before his eyes could adjust, instinctively tensing up as it entered his cell, halfway convinced that despite his mysterious benefactor's 'privileges', this would only end in more pain. The other half clamped down on his fear, focusing it. Don't fight. Don't make any sudden motions. His eyes squinted open, and he was greeted with the sight of a familiar spike, dangerously close to his face.
The Hesh spoke, unclear which of them it was addressing, but it didn't really matter. If they even bothered to speak to a kavkem, it was always the same promise of torment, even if they used different words. A massive arm shoved into his side, pushing him into an even more awkward position to a muffled sound of protest; but he did everything he could not to complain, trying to make the Hesh's work as easy as possible. Just a little longer, and then you won't have to worry about this so much.
[22:04] The chain anchors came loose with a snort from the Nayabaru. Before Baishar could fully appreciate the freedom of movement, a smack struck him – no doubt light from the perspective of the Nayabaru, but reverberating through Baishar's body. "Get up and out of my sight," it bellowed. Well, apparently 'respect' was not part of his new set of privileges.
In a motion frightfully quick for a creature the size and weight of a Nayabaru, the Hesh veered to look at Valcen, slamming the weapon to trap him against the wall, one end of the metal implement clanging against the wall, the prongs caught against the door's frame.
"We're done," the Hesh grunted at him. "Two." His free paw raised to gesture with two fingers. "Not a single one more."
"Yes, yes," Valcen assured, a nervous arrogance to his voice. "Two is fine and all I need."
The Hesh glared. "Not a single—"
"Yesssyesyes," Valcen assured, trying and failing to shrink a little further into the corner.
[22:05] The Hesh snorted, its aggravation somewhat soothed. "I trust you won't be needing access to the Pens any more," it concluded, tone suspended between scepticism and command.
"Sure," Valcen responded. "That's fine."
[22:29] Baishar winced at the smack, curbing an instinct to hiss and bare his teeth — it wouldn't do him any good. A few moments later, he began scrambling to his feet, trying to navigate through the crowded space while dealing with cramped muscles. The Hesh had told him to leave, and he didn't need to be told twice. He slunk out as surreptitiously as he could, taking care not to as much as brush the Hesh with a wayward feather.
Then he was free of the cell, in a broad hallway, lights still too bright but his eyes were beginning to adjust. For a moment, he considered running — but that would be a fool's errand, surely. There were Hesha everywhere in Katal; running would net him a dart, followed by a loss of anything he'd hoped to gain in this encounter, followed by more torture by a Hesh with nothing better to do than to make his life miserable.
Instead, he took a few cautious steps from the door and flattened himself against the outer wall of his former cell, hoping this was good enough to be considered 'out of the Hesh's sight'. It seemed a strange request from one who was presumably supposed to keep an eye on the kavkema, but he knew better than to argue.
[22:30] Meanwhile, the overheard conversation granted him some additional context. Two kavkema — so there was another Valcen had already found. Why did he need two? 'Hosts', plural — but a qidravem only needed one. At least, all the stories suggested as much. Perhaps there was something he didn't know. (Of course, there were many things he didn't know. Soon, he would be able to fix that.)
[22:43] There was a Hesh immediately beside the outer door – as soon as Baishar's aching eyes were aware of that Nayabaru, it was also clear that those were the eyes that were going to linger on him. It seemed as though that were all the Hesh was meant to do, however – there were no words, no poking or prodding, no demands.
Apparently he'd chosen a spot that had this one's approval.
It took a few more arduous moments for Valcen to resurface – sans orb. He kept his posture low, although there was still a certain grace to his motions – the mark of a kavkem who had freedom of movement. "Come," he prompted, softly – but still in Naya, shooting a glance back over his shoulder at the door-guarding Hesh.
And then they were walking through the corridors – already a partial freedom, a space many times greater than Baishar's cell had been, if greatly subdued by the presence of the Nayabaru they encountered on the way. Not yet anything one would call privacy, but surprisingly devoid of active oppression, the remnant chains dangling from him notwithstanding.
[23:08] Once he noticed the second Nayabaru, there was a moment of terror that he'd done something to earn their ire — perhaps simply existing in their general vicinity. For a few tense moments, his eyes darted between the second Hesh and its weapon, halfway expecting some punishment — but as none came, he allowed himself to relax a tiny bit, eyes coming to rest on the weapon.
As Valcen emerged from the cell and bade him to follow, he took a single step to follow, then glanced briefly in the direction of the Nayabaru, as if seeking some secondary confirmation that this was acceptable. When there was no obvious motion to stop him, he turned and followed Valcen nervously down the corridor.
It was strange, walking through the hallways of Katal without a Nayabaru dragging him along. His gait had a bit of a limp to it at first, owing to extended poor posture in a too-small cell; it took some time for his tail to realize it had its full freedom of movement and didn't have to stay awkwardly angled to one side. He tried to mimic Valcen's posture, staying as low as he could while they were still in full view of the Hesha, trying not to enjoy his newfound freedom of movement too visibly. Short of the sounds of footfalls and the soft chinking of chains, he remained silent.
[23:21] It's quiet enough that he can hear Valcen breathing whenever he's close by, smothering their route in an eerie air. Valcen at least seems to be very sure where he's going – perhaps to a cell that 'belongs' to him, although if so, hopefully larger than the one Baishar had been crammed into.
At some point, Valcen slows, approaching a larger doorway, the guard of which glances at him with only passing interest – used to his presence?
[23:22] Without that words are exchanged, the Nayabaru twists to the side, tending toward the magic needed to open the door; nothing Baishar understood. They evidently had technology that could identify Nayabaru – perhaps from their markings? – and opened only in their presence.
Beyond the door was a stairway with two right angles, leading further down.
Further down. Baishar had been lucid enough of his incarceration here to know that they were underground – that true freedom lay in the opposite direction.
"<We can safely switch to Kendaneivash now,>" Valcen commented as they had meandered halfway down the broad stairs, designed for Nayabaru as they had been.
[00:01] Baishar glanced nervously up at the Nayabaru guarding the door to what he presumed was Valcen's cell — as he'd glanced nervously to essentially every other Nayabaru they'd passed along the way. The fact he was being escorted by a kavkem — or by a shari in a kavkem's shape, rather — touched the entire journey with a surreal, eerie air.
The door opened — through the same mysterious means all other doors in this place operated — revealing a surprisingly large space, with broad stairs leading downwards. Deeper into the earth. For creatures so fond of sunlight, the Nayabaru seemed to enjoy making their Pens as far from the outdoors as possible. How much dirt and stone lay above them even now?
There was a sigh of relief from Baishar at the switch to a more intimately familiar tongue. "<Thank you,>" he replied, tone one of deep gratitude. The Nayabaru couldn't stand the ancient language, for reasons he still did not fully understand. It wasn't as if they ever listened to what the kavkema said, regardless of whose language it was in. The switch signalled that, for now, they were safe from the Hesha.
A moment later, he added: "<...And... thank you for freeing me from there.>" It felt like a premature thanks, as if he wasn't really free of the Hesha, as if he might yet wake up to discover this all a dream. He considered a third aspect of this to be thankful for, but he should probably save that for when he actually learned some of the secrets Valcen knew.
Instead, given the freedom to speak, it seemed a good time to ask one of the many questions he still had. "<I... am curious. You mentioned to the Hesh that you needed two kavkema? Why?>"
[00:15] Valcen made as though to respond, but was cut off before the first syllable. "The community grows!" A Nayabaru lingered near the base of the stairs, glancing up at the two of them, wearing an expression awkwardly mixing respect and mockery.
"Tanak," Valcen addressed the Nayabaru, weaving a sigh into the syllables. "This is Baishar. Baishar, this is Tanak. You can think of him as my supervisor. He won't touch you without my consent." The inherent threat was so subtle as to be easily missed. Valcen's consent, not Baishar's.
"Are you sure you want to promise something you can't directly enforce?" Tanak asked, although without any malicious leering that Baishar might have otherwise expected of a Nayabaru – it seemed more as if he were casting an intellectual exercise at Valcen.
"Positive," Valcen dismissed it flatly, paying no detailed heed to the Nayabaru as he continued along his way.
[00:36] The sudden sound of booming Naya was enough to make Baishar jump, skittering to the back of his current stair-platform. Eyes darted back and forth between the Nayabaru and Valcen, a twinge of betrayal in his expression. You said it was safe. Even here, there were Hesha. Or, at least one.
Introductions were exchanged. Tanak. This one had a name. Presumably the others did too, but their shifts changed often enough that he'd never bothered to learn any. The promise of safety from this 'supervisor' felt dangerously tenuous — there was never safety from Nayabaru, as Tanak himself seemed eager to point out. Though the jovial attitude was unusual. Which was probably not a good sign.
Valcen was already walking past the Nayabaru without giving him a second glance. Baishar hurried to catch up, keeping low but not letting his eyes leave Tanak until he was past him. Don't confront the Hesh.
[00:57] Tanak seemed to eye Baishar curiously, but kept his distance, only loosely tailing after them. "It may be counter-intuitive," Valcen commented, seeming much more relaxed now that they were down here – wherever here was. "But Tanak has been assigned to me as a body guard.
"As you might have noticed from what happened in the Pens, there are quite a few Nayabaru that are driven by their prejudices and, amongst those, quite a few that don't necessarily trust I intend to stay true to my word. Any benefits I reap before I've proven my worth increases the chance that someone will override the Karesejat's word.
"So the Nayabaru that best understand the Karesejat decided that Tanak was to watch my back for me." He sighs at the absurdity of a Nayabaru protecting a kavkem. Flatly: "Which is why I get to enjoy the fantastic luxury of Tanak's presence."
[01:36] Tanak's gaze was far from comforting, but as long as he was simply watching from a distance, he was presumably not in any immediate danger. He quickly caught up to Valcen, happy to keep his distance from the unexpected Nayabaru.
The revelation that Tanak was a bodyguard for Valcen, of all things, was surprising. Especially since that might have been helpful in the Pens. Why had he been staying he—
At the mention of the word 'Karesejat', Baishar stopped dead in his tracks. Surely he must have misheard...? No, there it was again. "I... I'm sorry, but... the Karesejat?" His eyes, wide in fear with a mix of concern, found Valcen's. A moment later, his voice lowered to a whisper, as if afraid speaking the name might summon her: "... Terenyira?"
[01:39] "The Karesejat," Valcen confirmed, biting down any urge to quip that there was only one and the deduction was entirely logical. He bit up the follow-up remark of 'Was there a question in there?' and instead tried to guess at what Baishar was baffled by that would be helped by some explanation. With some amusement: "How do you think one gets privileges around here?"
[02:03] Baishar's mind balked at how flippant Valcen was being. Was he even aware of what he was dealing with? Was he aware, and simply ignoring the consequences? Was he reckless? Was he mad? "...I would think," he began, cautiously, all too aware of the heartbeat racing in his chest, "That one who sought to build a qidravem, would do well to avoid the attention of— of—" His grasp of Naya failed him. Glancing nervously back at Tanak, hoping that Valcen's earlier comments were truthful — "juna havnateh yria'is," he concluded. "That there would be some other way."
[02:22] Valcen chuckled drily. "<Now if only I could impart those words of wisdom unto my past self,>" he observed, letting Baishar's phrase nudge him back into Kendaneivash mode. "<It really doesn't matter now,> Baishar. Terenyira <and I, we understand each other, in the way close enemies do.>
"<We trust each other exactly to the degree it makes logical sense for us to cooperate and not a single inch further. She expects that I'll inevitably betray her, I expect she'll try to make my eradication complete and permanent shortly before I manage to do anything of the sort, and we both patiently wait to see how it all plays out.>"
[03:44] The switch back to Kendaneivash resolved one source of his anxiety, while the contents of Valcen's response added several more. What have I gotten myself into? From the sounds of it, Valcen had already made the mistake of getting involved with the Karesejat, possibly without realizing what a mistake it was. There was enmity between them — but also an alliance? A delicate balance that could only tip in the wrong direction.
There were hints at a deeper truth, as well. 'Make my eradication complete and permanent' was an unusual phrase that raised a lot of questions, all connected to the mystery of what exactly Valcen was. Perhaps he should just ask, once the pit of dread in his gut had subsided, once he had the strength he suspected he'd need to understand the answer.
Eventually, he managed to string more words together. "<I hope — for your sake, and mine — that you know what you're doing.>" His eyes locked onto Valcen's for a long moment, unblinking, concerned, as if gazing deep enough could grant him insight. Do you know what you're doing? Do you understand the magnitude of what you're dealing with? It sounded like he did, and whether through arrogance or skill, believed himself up to the challenge.
[04:07] "<Unfortunately, I do,>" Valcen remarked, even as he led Baishar into a spacious, circular room.
In the tradition of Nayabaru-designed spaces, it was too bright by far, although something like a tent of dark drapes had been set up near one end of it, with pillows peering out of the construct, with two or three having spilt out. The fabric otherwise gave no indication of what was behind it – it seemed quite suited for the task of keeping the light out.
[04:08] Near the other end of the room was some kind of desk, currently decorated with scattered, cryptic metal shrapnel, some kind of magnifying glass, and various items that even from a distance could only be a craftsman's tools (albeit far more advanced than wild kavkema had to contend with).
The room was divided into thirds by currently withdrawn sliding panes, potentially isolating the area Valcen presumably used for sleeping from both the 'office' and the thus far empty centre of the room.
The 'tent' stirred. The tip of a muzzle wiggled under the edge of the fabric, then eased it up, revealing the vague impression of another kavkem. For a moment, it kept itself still, staring directly at Baishar as if in scrutiny (although the glare of the room made it difficult, as well as no doubt the imagined scrutiny).
Then the person pushed forward and upward, dragging the tip of the fabric with themselves for a few inches, before the structure had enough and began to unravel from the soft shoulders, gradually revealing the rest of the body to the light.
It took her coming close enough for him to guess at the narrow whites of her eyes for her expression to register fully. She was sizing him up, as though trying to gauge his fitness for a particular purpose.
"<He's a little stiff-limbed, but I suppose that's to be expected; he looks healthy enough,>" she commented to Valcen, before dipping her muzzle in a brief greeting. With a meticulously polite tone: "<Welcome, thanks for joining us. I go by Ryrha.>"
[08:51] More frustratingly cryptic statements. Surely knowing what one is doing was better than the alternative...? Or was this a puzzle he was meant to untangle? If it was the latter, it would have to wait — he was still reeling from the shock of the last revelation.
He attempted to pick apart the knot of anxiety in his gut, trying to place his feelings in some kind of context. He had promised obedience to a shari of unknown power and provenance. This shari had already allied itself with Terenyira (yet had intentions to betray her), intended in the long term to help Tamachelu but would make things worse for both her and the kavkema in the short term, wanted to construct a qidravem (and knew how to do so), and needed him for... some purpose related to acquiring hosts. Possibly even using his own body as one. He still hadn't entirely ruled that possibility out.
When he put it like that... the pang of nausea didn't change at all. It's too much, a part of him insisted. He clenched his teeth. No. This was a Quest. He had to remember that — keep the goal fixed in his mind. You're going to help. You're going to make things better. All other concerns were transient, ephemeral, finite things. So long as he kept the goal in sight, The Progression would drag him along, panting and screaming, inexorably into the future.
It took a few moments for him to notice the change in surroundings, the contrast near the far wall catching his eye and pulling him from his contemplations. Blessed shade! A comforting sight amid all the upheaval. He resisted the urge to cling to that comfort — it could wait.
Instead, his gaze explored the space. Yet another massive room in comparison to what he'd just left behind. The toolbench caught his attention — he took a step towards it, trying to parse the scattered objects on it in the glare. Some were recognizable as tools — though they mostly looked Nayabaru-sized. Others seemed like random junk. How does one construct a qidravem? Surely not from metal.
Motion from the tent tugged at his gaze, where he saw someone emerge — another kavkem. The other kavkem. He studied her as she approached, not quite managing to place her expression in the glare until she was close. Studying him. Gauging him. Then she spoke, first to Valcen, commenting — oddly — on his health, then greeted him. "<Thank you, Ryrha,>" he replied, lowering his muzzle in return. "<I am called Baishar. You must be the other kavkem.>" His gaze turned back to Valcen, questioningly. "<Speaking of which, you never answered my question. Why two?>"
[13:39] Baishar's question led instantly into a part stern, part confused glance from Ryrha toward Valcen. Valcen shrugged. "<We were interrupted,>" he remarked, thumbing across to Tanak, who had now grabbed a lonely chair near the entrance of the room – outside it, but in good view of everything in it – and was settling down.
[13:40] "<What did you ask of this one?>" Ryrha countered, somewhat incredulously.
"<Complete obedience,>" Valcen summarised.
Ryrha glanced back at Baishar. With a motherly patience, she admonished the newcomer: "<You're an idiot for agreeing to that.>" There's no worry or distress in her voice – presumably, she means that it was an idiotic thing to agree to in theory, not in practise. Her next words confirm: "<You're lucky> Valcen <doesn't need you for that much.>"
"<I might,>" Valcen interrupts, briefly. "<Having a general-purpose kavkem might simplify some things.>"
[13:41] "<You already have a general-purpose kavkem,>" Ryrha shot an irritated glare at Valcen.
"<Oh,>" Valcen mused, seemingly pleasantly surprised by this revelation – Ryrha must previously not have made it explicit. "<...well, now I have two.>"
A sound halfway between a snort and a sigh escaped Ryrha, then she flicked her muzzle to dismiss that line of thought. To Baishar, she said: "<Thanks to his mother's care,> Valcen <is sterile, so he can't contribute to making> yemmysaa. <He has been told, by the likes of> Tanak, <to simply subcontract the Seklushia, but he considers this cruel.>
"<Hence our volunteer work.>"
[21:14] Baishar responded to Ryrha's admonishment with a soft snort. "<Given the alternative of rotting in a cell for the rest of my life, I would have been an idiot not to.>" Strictly speaking, not a contradiction of her earlier statement, but at least a justification for his actions. Not that a justification was necessary, but it might be helpful for whatever would come next.
Listening to Ryrha's explanation, he noticed a piece of interesting data: Valcen had a mother. Something to keep in mind. At her mention of eggs, things began to click. "<Hosts,>" he said, as if understanding the meaning of that word for the first time.
This wasn't what he'd been expecting. What exactly had you been expecting? If this was indeed his Quest, there should be physicalities to transcend; this seemed like the opposite. His gut couldn't quite decide whether to feel relieved or subtly horrified. On one hand, it wasn't his soul at risk of being eviscerated. On the other, the thought of bringing life into this place....
[21:15] Things would get worse before they got better. And it wasn't as if he had much choice in the matter; merely the choice of how he would feel about it. "<I see,>" he replied, tone suspended between stoic acceptance and disappointment. Did he? Really? "<How... many do you need?>" The wrong question. But maybe it would still lead him to the answer to the right one.
[21:48] "<However many it takes,>" Valcen responded. "<Ultimately, what I need is a biology that's suitable amenable to the technologies needed to transfer a mind – a soul, if you will – from one host to another, ideally without having a consciousness of its own that needs any subverting at the adult stage, but without dying from the lack of intellectual stimulation.>
"<The eggs will let me explore these genetic underpinnings. Most of them will die – given the broad swaths of changes I'll be making, their average viability will drop sharply. Once I have a genetic basis, once I know which chromosomes to tweak to make hosts a useful reality, I may still need Ryrha, but your participation would become optional.>"
...well, some of those words made sense.
[22:12] Valcen's response was... almost comprehensible. Several of the words he'd never heard before. Baishar glanced to Ryrha, briefly, wondering if she understood more than he did. He tried to summarize what he could grasp from that in words he understood. "<You need to experiment with the eggs themselves, to make them... receptive?>" It was a valiant attempt. A moment later, he frowned. "<...Why? A qidravem is a qidravem; does the nature of the host matter?>" There was a burning curiosity in that question, a level of fascination Valcen hadn't yet seen from this particular kavkem.
[22:16] Valcen glanced back at Baishar with a certain degree of dispassionate confusion. Then: "<Maybe you missed a part of the narrative, so let me stress it again: I have no interest in destroying a functioning consciousness. Nevermind that a body not designed for my mind would be far more difficult to control.>
"<See, for example, all motions you make with your limbs? They're controlled by your mind. But the pathways running into your limbs are subtly different than mine. If I were to put my current mind into your body in its entirety, I would have to learn how to walk all over again.>"
[22:50] Baishar bristled slightly. "<No, I... understand why you'd use eggs,>" he replied, trying to sort out where he'd miscommunicated. A moment later, he added, "<And I appreciate that you're not planning to take my body, or anyone else's.>" He shut his eyes, blocking out the glare to help him think; his tongue idly ran across blunted teeth. "<But... I still don't understand why you need to... design a body.> Nateha <do not have this problem with their> qidravema, <do they?>" His eyes opened, gaze finding Valcen again. "<...And that is what you intend to become, is it not?>"
[00:08] Valcen flicked his muzzle in dismissal. "<Resume being,>" he corrected, with a loose smile and intense stare. "<As for the design question,>" he continued. "<The mind of a> nateh <is very, very different to that of a kavkem.>
"<If Tamachelu decided to take you as an avatar, most of her mind would not reside inside your skull. On the other hand, my skull is all that's left of me.>
"<Normally, when a> nateh <dies, their body, bereft of all thinking apparatus, ceases to function. If it does survive the death of the> nateh, <it will be an imbecile, a doddering idiot, likely incapable of as much as simple language, often incapable of hunting and sustaining itself.>
"<That I'm talking to you at all is a miracle. It's a carefully designed miracle, planned and executed with great caution. I am only a fraction of my designer, though I continue to carry ver name, and enjoy a certain... continuity of thought. But I am a carefully selected fraction, self-sufficient and intellectually capable of continuing what ve came here for.>"
[18:57] Those first two words rammed into his thoughts like a charging Rheshjere, splintering everything. Resume being? He stared at Valcen, dumbfounded, hearing his words but not entirely processing them. You were a god. A former god. The idea at first sounded like an oxymoron, a paradox, a sick joke. But as Valcen spoke, it began to make a certain kind of sense.
If a kavkem could, under the right circumstances, with the right tools and the right knowledge, transcend mortal flesh, then there was no reason to believe the reverse could not happen as well. That a god — or rather, a shard of a god, a piece that could fit fully into a mortal-shaped vessel — could become mortal.
The very concept of it made him nauseous. Had this happened willingly? Unlikely; what god would do this to itself? And yet it had been carefully designed. Why? And if Valcen was merely a piece of a god, where was the rest? His earlier comments — 'the Karesejat will try to make my eradication complete and permanent' — hinted at the horrifying truth.
Baishar was dimly aware of his body's posture, sunk down on all fours, gaze turned down toward his shadow, blunted claws seeking purchase on a surface that offered none. He was dimly aware of the moisture clouding his vision, making the overwhelming brightness of the room that much worse. "Siigu—" he began, but the question was stopped short by the lump in his throat. "Zetu ta'—" The phrase was aborted by a whine of distress, his resolve buckling under the weight of it all.
[18:58] A long, tense moment later, Baishar's gaze snapped up to Valcen. "<How can you bear it?>" he sobbed, voice raised and as filled with emotion as Valcen had ever heard him speak. "<Everything you've lost, for— for this, this miserable finite existence!>"
[19:39] The empathy was unexpected, visibly startling Valcen. Muted, he stared back at Baishar, his expression and body language cycling through confusion, disgust and appreciation, feathers puffing out in irregular intervals, jaw working.
Of course Baishar couldn't know what it was like, couldn't fathom it, but here he was, willing to try. Thinking to try. The words struck Valcen as hollow and subtly false, a painful mockery of the whole process, but it was clear it was unintentional.
Then he shook himself as if to rid his feathers of water, eyes fluttering briefly as he composed himself. Softly: "<In the first shock of the moment, for better or worse, I didn't have the luxury of dwelling on it.>" His tongue probed across his thin lips for a moment's pause, before he added, audibly trying to keep his tone meticulously matter-of-fact: "<The worst is the... erosion.>
"<Every day is a mental decline. The... format of a kavkem mind, of any nyaqen mind, does not lend itself to any permanence. When you come from a format that allows perfect recall, where you can choose what to remember and what to discard, it's...>"
He trailed off, blinking – to suppress tears? The topic seemed to have shaken him; his voice was subtly frayed at the edges. But when he spoke again, it was an almost aloof finality: "<No matter. Such musings won't help you help me.>"
[21:25] Baishar watched Valcen's expression with uncertainty, the silence feeling eternal. Have I gone too far? At moments it felt that way, like he must have upset Valcen in some way, but it seemed like Valcen himself wasn't entirely sure how to feel about his question. Has no one ever asked you this? some part of him wondered. Am I the first person to care? A second thread of thought, split off from the first: How long have you been in this state?
The first few words of Valcen's reply only made the circumstances of his mortality more mysterious. What caused this? How was it both planned and sudden? Was the havnateh Terenyira involved? He had no desire to know the answers to these questions — not now, not at this very moment. He would need time to process all of this. Hopefully that was a luxury he'd be able to afford.
As Valcen expanded on what he meant by 'erosion', a sense of awe mixed itself in with the horror in his gut. To choose what to remember and what to discard. He could just barely imagine it — impossibly distant, comprehensible only as an abstraction; he couldn't make it visceral, real. He could imagine what it was like to lose it only by analogy. Was it like losing all sense of memory, living with only an understanding of the present, devoid of context? Of course not; any metaphor could only be a sketch of what it must be like, a drawing of a kavkem in the dust compared to the real, living thing.
Of course, he had the real, living thing here, before him. He didn't entirely have to imagine what it was like; from what he could gauge of Valcen's manner, the answer was 'traumatic'. There was something fragile there, well-hidden at most times but briefly exposed. He could reach out and grasp it, pull it close, do what he could to protect it—
Valcen's final words had a cold edge to them. They didn't sound defensive, but that was one purpose Baishar was certain they had. Something constricted in his chest. He inhaled sharply, then let his breath out slowly. "<Of course.>" His mind scrounged together the bits of debris, the broken thoughts and hopes and fears. He would deal with them separately. "<Of course,>" he repeated, softer, pushing himself into a stand, squeezing eyes shut and shaking away what remained of his tears. Another inhale, slower this time. The Progression beckoned to him, hooks sunken into him, dragging him forward. "<...Is there anything you require of me at this time?>"
[21:38] Valcen seemed to consider the question for a moment, as though rolling options around in his head – or perhaps merely pondering the curiosity that it had been asked at all. Finally, he flicked his muzzle upward in a light dismissal. "<Come to terms with your new situation; spend time with Ryrha, exchange ideas. If you need anything, summon Tanak. I'll approach when I need your assistance.>"
[22:25] Baishar glanced over in Ryrha's direction when her name was mentioned, his mind having been so preoccupied that he'd nearly forgotten about her presence. There was a hint of concern in his expression, but she seemed to be unfazed by his recent outburst. His gaze turned back to Valcen, and he lowered his muzzle deeply in gratitude. "<Thank you.>"
His gaze turned to the makeshift tent on the far side of the room, the darkness within inviting. Come to terms with your new situation. He was not expected to be ready yet. He could allow himself a modicum of comfort as he did so. He was permitted to take his time. He was obliged to take his time.
He paused there for a moment, indecisive, then turned his attention to Ryrha. "<May I enter your home?>" he asked, tone polite, if mildly uncertain that he was asking precisely the right question. 'May I enter the makeshift pile of furniture that looks like the only decently habitable space I've seen in over a month' felt like it lacked a certain tactfulness.
[22:37] Ryrha twitched her muzzle back in the kavkem equivalent of a quirked brow. "<Such a strange question, given we're supposed to be mates,>" she commented, bemused; glancing instead to Valcen to assess if he needed anything unspoken. As the nateh-sunates turned his attention away, she, too, broke off, and gestured for Baishar to follow.


How cool is it to be the photographer of wedding and then shoot the pregnancy of the their first born??? Extremely cool, can thank you enough Grace and Joseph for letting me capture this moments in your life. I enjoy seeing the magic of love on a different stage, enjoy your picture. Keep loving going!!!!


text:
package com.twitter.util.tunable

import com.fasterxml.jackson.core.JsonParser
import com.fasterxml.jackson.databind.DeserializationContext
import com.fasterxml.jackson.databind.deser.std.StdDeserializer
import com.twitter.util

/**
 * Deserializers for Deserializing a JSON [[com.twitter.util.tunable.Tunable]] value
 */
private[twitter] object json {

  /**
   * Deserialize a String representation of a [[com.twitter.util.Duration]] using
   * [[com.twitter.util.Duration.parse]]
   */
  val DurationFromString = new StdDeserializer[util.Duration](classOf[util.Duration]) {
    override def deserialize(
      jsonParser: JsonParser,
      deserializationContext: DeserializationContext
    ): util.Duration = util.Duration.parse(jsonParser.getText)
  }
}

redpajama_set_name: RedPajamaGithub


Simply skf nup 215 ecp bearing in Cambodia are widely used in industrial drive, agriculture, compressors, motors and generators, construction, industrial fan, industrial transmission and other fields. Simply skf nup 215 ecp bearing in Cambodia can ensure high quality for more than 80% raw material of Simply skf nup 215 ecp bearing in Cambodia provided by the steel plant.
Explorer series bearing of Simply skf nup 215 ecp bearing in Cambodia are better than any brand bearings currently in bearing performance , lifetime, design, and the use of performance. Explorer series bearings of Simply skf nup 215 ecp bearing in Cambodia have more advantages ,such as higher meet rated , lower noise, reducing warranty costs greatly, increasing running time of the machine.
SKF NUP 215 ECP, We as a reputable supplier for the superior quality ,quick delivery , buy SKF NUP 215 ECP from bestskfbearings will be your rational choice.
We guarantee to provide you with the best SKF NUP 215 ECP Bearings,At the same time to provide you with the SKF NUP 215 ECP types,price,size chart,cross reference,CAD.
If a problem does arise, we do our best to rectify the situation. | eBay!
Cylindrical roller bearings, single row; NUP, NJ + HJ Seat tolerances for standard conditions NU 215 ECP SKF Explorer.


text:
Journal of a Programmer
Short notes and essays about stuff that interests me (mostly technical stuff).
Yes. Yes. Yes. Yes. Yes.
5 Things That Will Make Blood and Wine Great
Although originally given a tentative release for the first quarter of 2016, like all good ambiguously dated things Witcher 3's second and more sizable expansion, Blood and Wine, has been pushed back to the first half of 2016. Which does technically still include the first quarter, but come on. They wouldn't be giving themselves those extra three months of leeway if they didn't think they needed it.
So while we may have to wait a bit longer for our next and seemingly final foray in to the life of Geralt of Rivia, we've still got enough nuggets of information to dive in, Scrooge McDuck style, and swim on the oceans of speculation until CD Projekt Red lock down dates, deadlines, and details for us all. To that end, and knowing what we know, here are five things that could be done in Blood and Wine that would make it great.
Must. Find. Time. To. Complete. Pillars. Of. Eternity. And. Firewatch. Soon.
Posted by Bryan Pendleton at 6:45 PM No comments:
Alameda Point's Spirits Alley featured on Roads & Kingdoms
A little local coverage from one of my favorite websites: The Point of Diminishing Returns for Adult-Beverage Enthusiasts
Once the fog deepens, nearly covering the western span of the Bay Bridge, the deserted base looks more like the abandoned movie set it was than the burgeoning home of alcohol innovation it has become.
Posted by Bryan Pendleton at 10:46 AM No comments:
Stuff I'm reading, late February edition
The rain is over. Bummer. It was good while it lasted.
Disks for Data Centers: White paper for FAST 2016
We believe it is time to develop, jointly with the industry and academia, a new line of disks that are specifically designed for large scale data centers and services.
Not-quite-so-broken TLS: lessons in re-engineering a security protocol specification and implementation
On the surface this is a paper about a TLS implementation, but the really interesting story to me is the attempt to 'do it right,' and the techniques and considerations involved in that process. The IT landscape is littered with bug-ridden and vulnerable software – surely we can do better? And if we're going to make a serious attempt at that, where better than something like a TLS stack – because bugs and vulnerabilities there also expose everything that relies on it – i.e. pretty much the whole of the internet.
A Critique of ANSI SQL Isolation Levels
The ANSI SQL isolation levels were originally defined in prose, in terms of three specific anomalies that they were designed to prevent. Unsurprisingly, it turns out that those original definitions are somewhat ambiguous and open to both a strict and a broad interpretation. It also turns out that they are not sufficient, since there is one even more basic anomaly not mentioned in the standard that needs to be prevented in order to be able to implement rollback and recovery. Looking even more deeply, the paper uncovers eight different phenomena (anomalies) that can occur, and six different isolation levels.
Google's Transition from Single Datacenter, to Failover, to a Native Multihomed Architecture
The main idea of the paper is that the typical failover architecture used when moving from a single datacenter to multiple datacenters doesn't work well in practice. What does work, where work means using fewer resources while providing high availability and consistency, is a natively multihomed architecture
The Deactivation of the American Worker
The job terminations, like the bulk of the media outlet's work, were first experienced by most Gawker employees in digital, rather than physical space. Deleting the accounts was merely the company's attempt to assert control of its office space, and Slack's role in the layoffs simply exemplified where work was actually being done; it also serves as an indicator of, for many employees in the coming years, where it will end.
The Absurdity of What Investors See Each Day
What happened is when NYSE first allowed [traders] to collocate in the [same building], people started to get into pissing matches over the length of their cables. Just to give you an idea, a foot of cable equates to one nanosecond, which is a billionth of a second. People were getting into pissing matches over a billionth of a second.
NYSE measured the distance to the furthest cabinet, which is where people put their servers. It was 185 yards. So they gave every [high-frequency trader] a cable of 185 yards.
Then, traders who were previously closer to the [exchange server] asked to move to the farthest end of the building. Why? Because when a cable is coiled up, there's a light dispersion that is slightly greater than when the cable is straight.
President Obama Announces His Intent to Nominate Carla D. Hayden as Librarian of Congress
She began her career with the Chicago Public Library as the Young Adult Services Coordinator from 1979 to 1982 and as a Library Associate and Children's Librarian from 1973 to 1979.
The story of CVE-2015-7547
I don't believe there is a Pulitzer Prize for software.
But if there was such a prize, it should be given to the teams from RedHat and from Google who worked on CVE-2015-7547.
Let's start the roundup by looking a bit at Dan Kaminsky's essay: A Skeleton Key of Unknown Strength
The glibc DNS bug (CVE-2015-7547) is unusually bad. Even Shellshock and Heartbleed tended to affect things we knew were on the network and knew we had to defend. This affects a universally used library (glibc) at a universally used protocol (DNS). Generic tools that we didn't even know had network surface (sudo) are thus exposed, as is software written in programming languages designed explicitly to be safe.
Kaminsky goes on to give a high-level summary of how the bug allows attacks:
Somewhat simplified, the attacks depend on:.
A buffer being filled with about 2048 bytes of data from a DNS response
The stub retrying, for whatever reason
Two responses ultimately getting stacked into the same buffer, with over 2048 bytes from the wire
The flaw is linked to the fact that the stack has two outstanding requests at the same time – one for IPv4 addresses, and one for IPv6 addresses. Furthermore DNS can operate over both UDP and TCP, with the ability to upgrade from the former to the latter. There is error handling in DNS, but most errors and retries are handled by the caching resolver, not the stub. That means any weird errors just cause the (safer, more properly written) middlebox to handle the complexity, reducing degrees of freedom for hitting glibc.
An interesting thing about this bug is that it was more-or-less concurrently studied by two separate security analysis teams. Here's how the Google team summarize the issue in their article: CVE-2015-7547: glibc getaddrinfo stack-based buffer overflow
glibc reserves 2048 bytes in the stack through alloca() for the DNS answer at _nss_dns_gethostbyname4_r() for hosting responses to a DNS query.
Later on, at send_dg() and send_vc(), if the response is larger than 2048 bytes, a new buffer is allocated from the heap and all the information (buffer pointer, new buffer size and response size) is updated.
Under certain conditions a mismatch between the stack buffer and the new heap allocation will happen. The final effect is that the stack buffer will be used to store the DNS response, even though the response is larger than the stack buffer and a heap buffer was allocated. This behavior leads to the stack buffer overflow.
The vectors to trigger this buffer overflow are very common and can include ssh, sudo, and curl. We are confident that the exploitation vectors are diverse and widespread; we have not attempted to enumerate these vectors further.
That last paragraph is a doozy.
Still, both of the above articles, although fascinating and informative, pale beside the epic, encyclopedic, exhaustive, and fascinating treatise written by Carlos O'Donell of RedHat and posted to the GNU C Library mailing list: [PATCH] CVE-2015-7547 --- glibc getaddrinfo() stack-based buffer overflow.
O'Donell's explication of the bug is perhaps the greatest debugging/diagnosis/post-mortem write-up of a bug that I think I've ever read.
If you've ever tried to precisely describe a bug, and how it can cause a security vulnerability, you'll know how hard it is to do that both exactly and clearly. Here's how O'Donell does it:
The defect is located in the glibc sources in the following file:
- resolv/res_send.c
as part of the send_dg and send_vc functions which are part of the
__libc_res_nsend (res_nsend) interface which  is used by many of the
higher level interfaces including getaddrinfo (indirectly via the DNS
NSS module.)
One way to trigger the buffer mismanagement is like this:
* Have the target attempt a DNS resolution for a domain you control.
- Need to get A and AAAA queries.
* First response is 2048 bytes.
- Fills the alloca buffer entirely with 0 left over.
- send_dg attemps to reuse the user buffer but can't.
- New buffer created but due to bug old alloca buffer is used with new
size of 65535 (size of the malloc'd buffer).
- Response should be valid.
* Send second response.
- This response should be flawed in such a way that it forces
__libc_res_nsend to retry the query. It is sufficient for example to
pick any of the listed failure modes in the code which return zero.
* Send third response.
- The third response can contain 2048 bytes of valid response.
- The remaining 63487 bytes of the response are the attack payload and
the recvfrom smashes the stack with it.
The flaw happens because when send_dg is retried it restarts the query,
but the second time around the answer buffer points to the alloca'd
buffer but with the wrong size.
O'Donell then proceeds to walk you through the bug, line by line, showing how the code in question proceeds, inexorably, down the path to destruction, until it commits the fatal mistake:
So we allocate a new buffer, set *anssizp to MAXPACKET, but fail to set *ansp to the new buffer, and fail to update *thisanssizp to the new size.
And, therefore:
So now in __libc_res_nsend the first answer buffer has a recorded size of MAXPACKET bytes, but is still the same alloca'd space that is only 2048 bytes long.
The send_dg function exits, and we loop in __libc_res_nsend looking for an answer with the next resolver. The buffers are reused and send_dg is called again and this time it results in `MAXPACKET - 2048` bytes being overflowed from the response directly onto the stack.
There's more, too, and O'Donell takes you through all of it, including several other bugs that were much less severe which they uncovered while tracking this down and studying it using tools like valgrind.
O'Donell's patch is very precise, very clearly explained, very thoroughly studied.
But, as Kaminsky points out in today's follow-up, it's still not clear that we understand the extent of the danger of this bug: I Might Be Afraid Of This Ghost
A few people have privately asked me how this particular flaw compares to last year's issue, dubbed "Ghost" by its finders at Qualys.
the constraints on CVE-2015-7547 are "IPv6 compatible getaddrinfo". That ain't much. The bug doesn't even care about the payload, only how much is delivered and if it had to retry.
It's also a much larger malicious payload we get to work with. Ghost was four bytes (not that that's not enough, but still).
In Ghost's defense, we know that flaw can traverse caches, requiring far less access for attackers. CVE-2015-7547 is weird enough that we're just not sure.
It's fascinating that, apparently due to complete coincidence, the teams at Google and at RedHat uncovered this behavior independently. Better, they figured out a way to coordinate their work:
In the course of our investigation, and to our surprise, we learned that the glibc maintainers had previously been alerted of the issue via their bug tracker in July, 2015. (bug). We couldn't immediately tell whether the bug fix was underway, so we worked hard to make sure we understood the issue and then reached out to the glibc maintainers. To our delight, Florian Weimer and Carlos O'Donell of Red Hat had also been studying the bug's impact, albeit completely independently! Due to the sensitive nature of the issue, the investigation, patch creation, and regression tests performed primarily by Florian and Carlos had continued "off-bug."
This was an amazing coincidence, and thanks to their hard work and cooperation, we were able to translate both teams' knowledge into a comprehensive patch and regression test to protect glibc users.
It was very interesting to read these articles, and I'm glad that the various teams took the time to share them, and even more glad that companies like RedHat and Google are continuing to fund work like this, because, in the end, this is how software becomes better, painful though that process might be.
I am like you. You are like me.
Read this story.
Read it over and over and over.
And smile, and be glad.
Posted by Bryan Pendleton at 10:34 PM No comments:
Blind injection
Obviously, the gravitational wave discovery was extremely, extremely cool.
But what I thought was in a lot of ways much cooler was the technique the team used to build in a process which ensured that they were extremely careful in their analysis, and weren't easily fooled: LIGO-Virgo Blind Injection
The LIGO Scientific Collaboration and the Virgo Collaboration conducted their latest joint observation run (using the LIGO Hanford, LIGO Livingston, Virgo and GEO 600 detectors) from July, 2009 through October 2010, and are jointly searching through the resulting data for gravitational wave signals standing above the detector noise levels. To make sure they get it right, they train and test their search procedures with many simulated signals that are injected into the detectors, or directly into the data streams. The data analysts agreed in advance to a "blind" test: a few carefully-selected members of the collaborations would secretly inject some (zero, one, or maybe more) signals into the data without telling anyone. The secret goes into a "Blind Injection Envelope", to be opened when the searches are complete. Such a "mock data challenge" has the potential to stress-test the full procedure and uncover problems that could not be found in other ways.
It must be really pleasing, in that what-makes-an-engineer-deeply-satisfied sort of way, to open up the Blind Injection Envelope and discover that your analysis was in fact correct.
It isn't a perfect comparison, but I am strongly reminded of the Netflix engineering team's approach to building in fault tolerance and reliability in their systems by intentionally provoking failures: The Netflix Simian Army
Imagine getting a flat tire. Even if you have a spare tire in your trunk, do you know if it is inflated? Do you have the tools to change it? And, most importantly, do you remember how to do it right? One way to make sure you can deal with a flat tire on the freeway, in the rain, in the middle of the night is to poke a hole in your tire once a week in your driveway on a Sunday afternoon and go through the drill of replacing it. This is expensive and time-consuming in the real world, but can be (almost) free and automated in the cloud.
This was our philosophy when we built Chaos Monkey, a tool that randomly disables our production instances to make sure we can survive this common type of failure without any customer impact. The name comes from the idea of unleashing a wild monkey with a weapon in your data center (or cloud region) to randomly shoot down instances and chew through cables -- all the while we continue serving our customers without interruption. By running Chaos Monkey in the middle of a business day, in a carefully monitored environment with engineers standing by to address any problems, we can still learn the lessons about the weaknesses of our system, and build automatic recovery mechanisms to deal with them. So next time an instance fails at 3 am on a Sunday, we won't even notice.
In computing circles, this sort of thing is often gathered under the term Recovery Oriented Computing, but I really like the term "blind injection."
I'm going to remember that, and keep my eye out for places to take advantage of that technique.
Saving the desert
Here's some wonderful news to pick me up after what was, for totally unrelated reasons, an extremely rough week.
Volcanic spires and Joshua trees: Obama protects 1.8 million acres in California's desert
President Obama designated three new national monuments in the California desert Thursday, expanding federal protection to 1.8 million acres of landscapes that have retained their natural beauty despite decades of heavy mining, cattle ranching and off-roading.
Photos: Obama Declares 3 New National Monuments In California Desert
All three areas lie east of Los Angeles. Two of the new monuments — Castle Mountains and Mojave Trails — are near California's border with Nevada.
And crucially, "the new monuments will link already protected lands, including Joshua Tree National Park, Mojave National Preserve, and fifteen congressionally-designated Wilderness areas, permanently protecting key wildlife corridors and providing plants and animals with the space and elevation range that they will need in order to adapt to the impacts of climate change," the release says.
With 3 new monuments, Obama creates world's second-largest desert preserve
The designations under the 1906 Antiquities Act connect an array of existing protected areas, including Joshua Tree National Park, Mojave National Preserve and 15 wilderness areas, creating a nearly 10 million-acre arid land reserve that is surpassed only by Namibia's Namib-Naukluft National Park.
Obama Just Added Three More National Monuments
Mojave Trails National Monument
This is the largest of the newly protected areas and spans 1.6 million acres, over 350,000 of which were already protected. The area includes ancient Native American trading routes, a long stretch of Route 66, and World War II training camps. Natural highlights include the Pisgah Crater lava flows, Marble Mountains Fossil Beds, and the Amboy Crater.
Mojave Trails boasts stunning springs of underground water, like diamonds in the rough, teaming with desert life, and shifting sand dunes that hum in the wind - havens for kit foxes.
Other national treasures in the proposed monument include:
The scenic lava flows of Amboy Crater—North America's youngest volcano and a National Natural Landmark;
The 550 million-year-old trilobite fossil beds of the Marble Mountains;
Sleeping Beauty Valley—the last intact valley representing the West Mojave plant ecosystem; and
The Cady Mountains—one of the best areas in the Mojave to see bighorn sheep.
1:248,000
Press Release: Historic Designation of New California Desert National Monuments Celebrated by Local Communities
The Mojave Trails National Monument links the Mojave National Preserve to Joshua Tree National Park and existing Wilderness Areas, and includes vital wildlife habitat, desert vistas and important Native American cultural sites. Sand to Snow offers some of the most biologically diverse habitats in the country, linking the San Gorgonio Wilderness to Joshua Tree National Park and the San Bernardino National Forest. Some of the finest Joshua tree, piñon pine, and juniper forests in the desert grow in the Castle Mountains National Monument. Given the exceptional historical, ecological, and geological features found in each area – from Route 66 to the Marble Mountains Fossil Beds to desert tortoise and bighorn sheep habitat – these lands are well-deserving of their new national monument status.
"Along with over 100 historians, archaeologists, and other experts, I enthusiastically welcome the designation of the Mojave Trails, Sand to Snow and Castle Mountains National Monuments," said Dr. Clifford E. Trafzer, Rupert Costo Chair in American Indian Affairs, University of California, Riverside. "President Obama has taken a step forward to preserve not only the beauty of these lands, but also our shared history. Now these places will be better protected against theft and damage of Native American objects and artifacts. With respect and good stewardship, these public lands are repositories of knowledge, just waiting to be understood."
This is the land of my childhood (well, my middle-school childhood, anyway). It is as harsh and unforgiving a place as exists on the planet, but my oh my is it a treasure for those who take the time to get to know and appreciate it.
Thank you, Mr. President.
Stuff I'm reading, President's Day edition
El Nino is apparently over, as the rain has completely stopped. Sigh.
Gas leak at Porter Ranch well is stopped -- at least temporarily
The leaking well is one of 115 injection wells at the 80-year-old, 3,600-acre Aliso Canyon facility, which stores 86 billion cubic feet of gas that serves 11 million people in the Los Angeles basin. Many of those wells are corroded and mechanically damaged, the gas company said.
Yet it is the only field in a distribution area stretching from Porter Ranch 60 miles south to Santa Ana that can ensure reliability in both winter, when homes and businesses use significant amounts of natural gas for heating, and summer, when gas-fired generators supply power to air conditioners.
Efforts to kill the well are being conducted under new orders imposed by the Safety and Enforcement Division of the California Public Utilities Commission in consultation with the state Department of Conservation's Division of Oil, Gas and Geothermal Resources.
The Princeton Bitcoin textbook is now freely available
If you're looking to truly understand how Bitcoin works at a technical level and have a basic familiarity with computer science and programming, this book is for you. Researchers and advanced students will find the book useful as well — starting around Chapter 5, most chapters have novel intellectual contributions.
Transitioning from SPDY to HTTP/2
HTTP/2 is the next-generation protocol for transferring information on the web, improving upon HTTP/1.1 with more features leading to better performance. Since then we've seen huge adoption of HTTP/2 from both web servers and browsers, with most now supporting HTTP/2. Over 25% of resources in Chrome are currently served over HTTP/2, compared to less than 5% over SPDY. Based on such strong adoption, starting on May 15th — the anniversary of the HTTP/2 RFC — Chrome will no longer support SPDY.
The Malware Museum
The Malware Museum is a collection of malware programs, usually viruses, that were distributed in the 1980s and 1990s on home computers. Once they infected a system, they would sometimes show animation or messages that you had been infected. Through the use of emulations, and additionally removing any destructive routines within the viruses, this collection allows you to experience virus infection of decades ago with safety.
Planning for Disaster
I'm not optimistic that, as a group, computer scientists and computing professionals can prevent this disaster from happening: the economic forces driving automation and system integration are too strong. But of course we should try. We also need to think about what we're going to do if, all of a sudden, a lot of people suddenly expect us to start producing computer systems that actually work, and perhaps hold us accountable when we fail to do so.
The Moral Hazard of Complexity-Theoretic Assumptions
Computational-complexity theory focuses on classifying computational problems according to their inherent difficulty. The theory relies on some fundamental abstractions, including that it is useful to classify algorithms according to their worst-case complexity, as it gives us a universal performance guarantee, and that polynomial functions display moderate growth.
Jepsen: RethinkDB 2.2.3 reconfiguration
I offered the team a more aggressive failure model: we'd dynamically reconfigure the cluster membership during the test. This is a harder problem than consensus with fixed membership: both old and new nodes must gracefully agree on the membership change, ensure that both sets of nodes will agree on any operations performed during the handover, and finally transition to normal consensus on the new set of nodes. The delicate handoff of operations from old nodes to new provides ample opportunities for mistakes.
Einstein's gravitational waves 'seen' from black holes
Expected signals are extremely subtle, and disturb the machines, known as interferometers, by just fractions of the width of an atom.
But the black hole merger was picked up by two widely separated LIGO facilities in the US.
The merger radiated three times the mass of the sun in pure gravitational energy.
Top 5 Targets of a Gravity Wave Observatory
an instrument called LIGO (the Laser Interferometer Gravitational-Wave Observatory) had apparently observed a "spectacular" direct gravitational wave signal, minute ripples in the fabric of spacetime created by distant and very massive objects—in this case, the collision and merger of two black holes, one 36 times the mass of our Sun, the other 29 times. Einstein first theorized that gravitational waves should exist in 1915, but evidence for them has been indirect so far. LIGO may be the first instrument to ever see them directly, by measuring the slight contraction and expansion of the distance separating distant mirrors.
We asked physicists what they'd be most excited to observe with a fully functioning gravitational wave observatory. Here are their top 5 favorite targets.
The Resetting of the Startup Industry
The startup industry may be "resetting," which doesn't mean a "crash" but rather just a resetting of valuations, timescales, winners/losers, capital sources and the relative emphasis of growth rates vs. burn rates.
Was Black Friday A DiSaaSter Or Simply Reversion To The Mean?
Last Friday, LinkedIn, Salesforce and Workday lost $18B in market capitalization. To put that in perspective, these three SaaS companies lost more in market cap on Friday than 15 current SaaS leaders are worth…combined.
How can this be possible? LinkedIn, Salesforce and Workday are growing revenue with sticky customers and they are targeting large addressable markets. Are they now suddenly undesirable companies?
Founders – Use Your Down Round To Clean Up Your Cap Table
I learned this lesson 127 times between 2000 and 2005. I started investing in 1994 and while there was some bumpiness in 1997 and again in 1999, the real pain happened between 2000 and 2005. I watched, participated, and suffered through every type of creative financing as companies were struggling to raise capital in this time frame. I've seen every imaginable type of liquidation preference structure, pay-to-play dynamic, preferred return, ratchet, share/option bonus, option repricing, and carveout. I suffered through the next financing after implementing a complex structure, or a sale of the company, or a liquidation. I've spent way too much time with lawyers, rights offerings, liquidation waterfalls, and angry/frustrated people who are calculating share ownership by class to see if they can exert pressure on an outcome that they really can't impact anyway, and certainly haven't been constructively contributing to.
Why Commons Should Not Have Ideological Litmus Tests
The final point I want to bring up here is how codes of conduct should be used. These are not things which should be seen as pseudo-legal or process-oriented documents. If you go this way, people will abuse the system. It is better in my experience to vest responsibility with the maintainers in keeping the peace, not dispensing out justice, and to have codes of conduct aimed at the former, not the latter. Justice is a thorny issue, one philosophers around the world have been arguing about for millennia with no clear resolution.
Things that happen when your city hosts a Super Bowl:
There's a fair amount of extra traffic on the roads.
The one-hour trek on Highway 101 down the Peninsula to the South Bay might stretch to two hours next week. The Embarcadero and Market Street closures near Super Bowl City, the fan village, are causing painfully slow trips around San Francisco's Ferry Building. Already-jammed BART and Caltrain parking lots could fill by 6 a.m. And 600 or more charter buses will be used to carry fans to the Feb. 7 game at Levi's Stadium in Santa Clara.
Everybody is visiting San Francisco, even though the game isn't played there.
While the game is in Santa Clara, nine days of activities leading up to the game are in San Francisco. That means transportation impacts from January 23 to February 12. Whether you're visiting, working or a resident, plan ahead, pack your patience and take transit, bike or walk where you need to go.
There are special events, both free, and paid, which you can go to.
Super Bowl City presented by Verizon is the Host Committee's free-to-the-public fan village designed to celebrate the milestone Super Bowl 50 and to highlight its unique place in the Bay Area.
The NFL Experience driven by Hyundai, pro football's interactive theme park, will be hosted by the Bay Area during Super Bowl Week. To be located at the Moscone Center in San Francisco, the NFL Experience celebrates the sport's history and electrifying atmosphere of Super Bowl.
Some of the events are so popular that you can't get in.
San Francisco police turned away thousands of people from Super Bowl City late Friday when the event reached maximum capacity.
It's hard to find a hotel room.
"We're starting at $1,500 for the regular rooms, suites go up to $10,000 a night and we have a four day minimum that we require," said Roger Huldi, the General Manager at the W Hotel.
But maybe you can rent somebody's spare bedroom, cheap.
There are simply too many rooms and not enough guests. "You get a flood of people listing their places and nobody looks at it," says Ian McHenry, a co-founder of research firm Beyond Pricing, which sells rental hosts a service to help calculate how much they should charge. "There's way too much supply in the market." Of the nearly 10,000 currently active Airbnb listings in the Bay Area this weekend, around 60 percent are still available, according to the San Jose Mercury News.
There's been a significantly-noticable increase in the number of private charter jets flying in and out.
Private jet companies say this year's game could near or top records for previous Super Bowls, given the attractive location, large number of private jet airports in the area and the excitement over the game.
Companies say business is up between 10 and 20 percent over last year. And while consolidated numbers are hard to come by, experts estimate between 1,000 and 1,500 jets could arrive at Oakland, San Jose, Hayward and other California airports.
But, uhm, don't try to fly your drone.
"Temporary Flight Restrictions will prohibit certain aircraft operations, including unmanned aircraft operations, within a 32-mile radius of the stadium in Santa Clara, Calif. on game day," reads a statement from the Federal Aviation Administration.
Everyone who's anyone will be there: Jet-setters swooping into Bay Area for Super Bowl 50.
Usually, about a half-dozen private jets might use Panico's facility at any one time. This weekend, there could be as many as 200. While their owners are attending the modest little sporting event just down the Nimitz Freeway, the planes will be parked wingtip to wingtip. So many $50 million jets will be slumming it in Hayward that the airport will shut down one runway and turn it into a temporary parking lot.
The weather cooperates, and is just unbelievably nice.
Plentiful sunshine. High 73F. Winds NW at 5 to 10 mph.
There's plenty of other entertainment. (My co-worker's son is the drummer for the Latin Youth Jazz Ensemble!)
For the musically inclined, there are several acts lined up in the Bay Area to get you ready for the game. Performing at the City Stage in San Francisco on Sunday will be the Latin Youth Jazz Ensemble (3 p.m. ET), John Brothers Piano Company (3:45 p.m. ET) and the Glide Ensemble (5 p.m. ET).
All the media companies have been busy crafting their advertisements.
Super Bowl ads are practically an event unto themselves. And when they unfold on the screen this Sunday, viewers will see a reflection of America's diversity.
While Hollywood faces a backlash over an all-white slate of acting nominees for this year's Oscars, several of the TV spots airing during the big game will feature actors, athletes and characters who represent a range of ethnicity, generations, and sexual orientations.
The Goodyear Blimp spends all week flying around the area.
"We're getting the beauty shots for the networks," said the photographer. "You know, downtown, sunsets."
And what do they get in exchange? Priceless advertising seen by millions of fans from the ground and from their living rooms.
And, of course, at some point during the day there will be a football game of sorts.
Have fun, everyone! I think I'll be reading my newspaper and grilling ribs, although I'm sure I'll tune it for the ads.
It's not just a game, ...
... it's LARPing at Moszna Castle: The Witcher School
The Witcher School is a LARP for adults inspired by "The Witcher" series and the fantasy book series by Andrzej Sapkowski.
During the game you will become an apprentice going through a rigorous witcher training: you will learn fencing, archery and alchemy; you will hunt monsters, unveil secrets and intrigues; and finally, you will face tough choices and discover the consequences the hard way. You will move to Moszna Castle in Poland, redecorated for our needs and transformed into a real witchers' abode where you will meet famous characters known from "The Witcher" books and games.
The "Design Document" goes on to elaborate:
Up to this point, you could only read about this or see this on the screen of your TV or PC. But here... if you want to slash your enemy with a sword you do not have to imagine doing that, or push a button on your controller. What you have to do here is to do it for real. You will learn how to brew potions using real ingredients, and what gestures are needed to use witcher signs. And these are only a few of the things you will be able to learn. You will be an integral part of the live action. This will be an opportunity to immerse yourself in a well-known setting of The Witcher and live your own unforgettable adventure.
Some links on large object support in git
Storing large binary files in git repositories
there are multiple 3rd party implementations that will try to solve the problem, many of them using similar paradigm as a solution. In this blog post I will go through seven alternative approaches for handling large binary files in Git repositories with respective their pros and cons.
Git Annex vs. Git LFS
my experience with Annex is that it's full-featured and a bit less focused in its approach. It's easy enough to check in files and sync them among various locations, but there are also testing tools, a web-based GUI, and lots of options you can use in different situations. The git-annex project site reveals a lot: plenty of features, updates, discussions, and enough threads that some sort of trail off.
Git LFS is at the other end of things: a bit nicer-looking, a bit more straightforward, and significantly simpler. Tack it on to your repository, tell it what kind of files to watch, and then pretty much forget about it. If you check in a file (with a normal git add whatever.mp4), the magic happens via a pre-push hook where LFS will check your watch list and spring into action if needed. It otherwise blends in after minimal configuration.
git-annex v6
This new unlocked file mode uses git's smudge/clean filters, and I was busy developing it all through December. It started out playing catch-up with git-lfs somewhat, but has significantly surpassed it now in several ways.
So, if you had tried git-annex before, but found it didn't meet your needs, you may want to give it another look now.
Stuff I'm reading, early February edition
If the groundhog were to look today, she would DEFINITELY see her shadow, at least here in my neighborhood.
All Change Please
The combined changes in networking, memory, storage, and processors that are heading towards our data centers will bring about profound changes to the way we design and build distributed systems, and our understanding of what is possible. Today I'd like to take a moment to summarise what we've been learning over the past few weeks and months about these advances and their implications.
High-Availability at Massive Scale: Building Google's Data Infrastructure for Ads
While most distributed systems handle machine-level failures well, handling datacenter-level failures is less common. In our experience, handling datacenter-level failures is critical for running true high availability systems. Most of our systems (e.g. Photon, F1, Mesa) now support multi-homing as a fundamental design property. Multi-homed systems run live in multiple datacenters all the time, adaptively moving load between datacenters, with the ability to handle outages of any scale completely transparently. This paper focuses primarily on stream processing systems, and describes our general approaches for building high availability multi-homed systems, discusses common challenges and solutions, and shares what we have learned in building and running these large-scale systems for over ten years.
Immutability Changes Everything
It wasn't that long ago that computation was expensive, disk storage was expensive, DRAM (dynamic random access memory) was expensive, but coordination with latches was cheap. Now all these have changed using cheap computation (with many-core), cheap commodity disks, and cheap DRAM and SSDs (solid-state drives), while coordination with latches has become harder because latch latency loses lots of instruction opportunities. Keeping immutable copies of lots of data is now affordable, and one payoff is reduced coordination challenges.
To Trie or not to Trie – a comparison of efficient data structures
I have been reading up a bit by bit on efficient data structures, primarily from the perspective of memory utilization. Data structures that provide constant lookup time with minimal memory utilization can give a significant performance boost since access to CPU cache is considerably faster than access to RAM. This post is a compendium of a few data structures I came across and salient aspects about them
POPL 2016
Last month saw the 43rd edition of the ACM SIGPLAN-SIGACT Symposium on the Principles of Programming Languages (POPL). Gabriel Scherer did a wonderful job of gathering links to all of the accepted papers in a GitHub repo. For this week, I've chosen five papers from the conference that caught my eye.
NSA's top hacking boss explains how to protect your network from his attack squads
NSA tiger teams follow a six-stage process when attempting to crack a target, he explained. These are reconnaissance, initial exploitation, establish persistence, install tools, move laterally, and then collect, exfiltrate and exploit the data.
Amazon's Experiment with Profitability
Amazon Chief Executive Officer Jeff Bezos has spent more than two decades reinvesting earnings back into the company. That steadfast refusal to strive for profitability never seemed to hurt the company or its stock price, and Amazon's market value (now about $275 billion) passed Wal-Mart's last year. All the cash it generated went into infrastructure development, logistics and technology; it experimented with new products and services, entered new markets, tried out new retail segments, all while capturing a sizable share of the market for e-commerce.
I Hate the Lord of the Rings
A software developer explains why the Lord of the Rings is too much like work, and why Middle Earth exists in every office.
Startup Interviewing is (redacted)
Silicon Valley is full of startups who fetishize the candidate that comes into the interview, answers a few clever fantasy coding challenges, and ultimately ends up the award-winning hire that will surely implement the elusive algorithm that will herald a new era of profitability for the fledging VC-backed company.
Inverting Binary Trees Considered Harmful
he was like - wait a minute I read this really cute puzzle last week and I must ask you this - there are n sailors and m beer bottles and something to do with bottles being passed around and one of the bottles containing a poison and one of the sailors being dishonest and something about identifying that dishonest sailor before you consume the poison and die. I truly wished I had consumed the poison instead of laboring through that mess.
"Can you solve this problem for me on the whiteboard?"
Programmers use computers. It's what we do and where we spend our time. If you can't at least give me a text editor and the toolchain for the language(s) you're interested in me using, you're wasting both our time. While I'm not afraid of using a whiteboard to help illustrate general problems, if you're asking me to write code on a whiteboard and judging me based on that, you're taking me out of my element and I'm not giving you a representative picture of who I am or how I code.
Don't get me wrong, whiteboards can be a great interview tool. Some of the best questions I've been asked have been presented to me on a whiteboard, but a whiteboard was used to explain the concept, the interviewer wrote down what I said and used that to help frame a solution to the problem. It was a very different situation than "write code for me on the whiteboard."
Bryan Pendleton
Alameda Point's Spirits Alley featured on Roads & ...
My Backpacking Trips with Mike

redpajama_set_name: RedPajamaCommonCrawl


Li, TJ ; Nanopoulos, DV; Li, TJ (reprint author), Chinese Acad Sci, Inst Theoret Phys, Key Lab Frontiers Theoret Phys, Beijing 100190, Peoples R China.
Abstract To explain both the possible superluminal neutrino propagation and all the known phenomenological constraints/observations on Lorentz violation, the Background-Dependent Lorentz Violation (BDLV) has been proposed. We study the BDLV in a model-independent way. Assuming that the Lorentz violation on the Earth is much larger than those on the interstellar scale, we automatically escape all the astrophysical constraints on Lorentz violation. For the BDLV from the effective field theory, we present a simple model and discuss the possible solutions to the theoretical challenges of the superluminal neutrino propagation such as the Bremsstrahlung effects for muon neutrinos and the pion decays. Also, we address the Lorentz violation constraints from the LEP and KamLAMD experiments. For the BDLV from the Type IIB string theory with D3-branes and D7-branes, we point out that the D3-branes are flavour blind, and all the SM particles are the conventional particles as in the traditional SM when they do not interact with the D3-branes. Thus, we not only can naturally avoid all the known phenomenological constraints on Lorentz violation, but also can naturally explain all the theoretical challenges. Interestingly, the energy-dependent photon velocities may be tested at the experiments.
GB/T 7714 Li, TJ,Nanopoulos, DV,Li, TJ . Background-dependent Lorentz violation: natural solutions to the theoretical challenges of the superluminal neutrino propagation[J]. EUROPEAN PHYSICAL JOURNAL C,2012,72(6):2044.
APA Li, TJ,Nanopoulos, DV,&Li, TJ .(2012).Background-dependent Lorentz violation: natural solutions to the theoretical challenges of the superluminal neutrino propagation.EUROPEAN PHYSICAL JOURNAL C,72(6),2044.
MLA Li, TJ,et al."Background-dependent Lorentz violation: natural solutions to the theoretical challenges of the superluminal neutrino propagation".EUROPEAN PHYSICAL JOURNAL C 72.6(2012):2044.