What is binary options trading definition

Best Practices for A C Programmer

Hi all,
Long time C programmer here, primarily working in the embedded industry (particularly involving safety-critical code). I've been a lurker on this sub for a while but I'm hoping to ask some questions regarding best practices. I've been trying to start using c++ on a lot of my work - particularly taking advantage of some of the code-reuse and power of C++ (particularly constexpr, some loose template programming, stronger type checking, RAII etc).
I would consider myself maybe an 8/10 C programmer but I would conservatively maybe rate myself as 3/10 in C++ (with 1/10 meaning the absolute minmum ability to write, google syntax errata, diagnose, and debug a program). Perhaps I should preface the post that I am more than aware that C is by no means a subset of C++ and there are many language constructs permitted in one that are not in the other.
In any case, I was hoping to get a few answers regarding best practices for c++. Keep in mind that the typical target device I work with does not have a heap of any sort and so a lot of the features that constitute "modern" C++ (non-initialization use of dynamic memory, STL meta-programming, hash-maps, lambdas (as I currently understand them) are a big no-no in terms of passing safety review.

When do I overload operators inside a class as opposed to outisde?

... And what are the arguments foagainst each paradigm? See below:
/* Overload example 1 (overloaded inside class) */ class myclass { private: unsigned int a; unsigned int b; public: myclass(void); unsigned int get_a(void) const; bool operator==(const myclass &rhs); }; bool myclass::operator==(const myclass &rhs) { if (this == &rhs) { return true; } else { if (this->a == rhs.a && this->b == rhs.b) { return true; } } return false; } 
As opposed to this:
/* Overload example 2 (overloaded outside of class) */ class CD { private: unsigned int c; unsigned int d; public: CD(unsigned int _c, unsigned int _d) : d(_d), c(_c) {}; /* CTOR */ unsigned int get_c(void) const; /* trival getters */ unsigned int get_d(void) const; /* trival getters */ }; /* In this implementation, If I don't make the getters (get_c, get_d) constant, * it won't compile despite their access specifiers being public. * * It seems like the const keyword in C++ really should be interpretted as * "read-only AND no side effects" rather than just read only as in C. * But my current understanding may just be flawed... * * My confusion is as follows: The function args are constant references * so why do I have to promise that the function methods have no side-effects on * the private object members? Is this something specific to the == operator? */ bool operator==(const CD & lhs, const CD & rhs) { if(&lhs == &rhs) return true; else if((lhs.get_c() == rhs.get_c()) && (lhs.get_d() == rhs.get_d())) return true; return false; } 
When should I use the example 1 style over the example 2 style? What are the pros and cons of 1 vs 2?

What's the deal with const member functions?

This is more of a subtle confusion but it seems like in C++ the const keyword means different things base on the context in which it is used. I'm trying to develop a relatively nuanced understanding of what's happening under the hood and I most certainly have misunderstood many language features, especially because C++ has likely changed greatly in the last ~6-8 years.

When should I use enum classes versus plain old enum?

To be honest I'm not entirely certain I fully understand the implications of using enum versus enum class in C++.
This is made more confusing by the fact that there are subtle differences between the way C and C++ treat or permit various language constructs (const, enum, typedef, struct, void*, pointer aliasing, type puning, tentative declarations).
In C, enums decay to integer values at compile time. But in C++, the way I currently understand it, enums are their own type. Thus, in C, the following code would be valid, but a C++ compiler would generate a warning (or an error, haven't actually tested it)
/* Example 3: (enums : Valid in C, invalid in C++ ) */ enum COLOR { RED, BLUE, GREY }; enum PET { CAT, DOG, FROG }; /* This is compatible with a C-style enum conception but not C++ */ enum SHAPE { BALL = RED, /* In C, these work because int = int is valid */ CUBE = DOG, }; 
If my understanding is indeed the case, do enums have an implicit namespace (language construct, not the C++ keyword) as in C? As an add-on to that, in C++, you can also declare enums as a sort of inherited type (below). What am I supposed to make of this? Should I just be using it to reduce code size when possible (similar to gcc option -fuse-packed-enums)? Since most processors are word based, would it be more performant to use the processor's word type than the syntax specified above?
/* Example 4: (Purely C++ style enums, use of enum class/ enum struct) */ /* C++ permits forward enum declaration with type specified */ enum FRUIT : int; enum VEGGIE : short; enum FRUIT /* As I understand it, these are ints */ { APPLE, ORANGE, }; enum VEGGIE /* As I understand it, these are shorts */ { CARROT, TURNIP, }; 
Complicating things even further, I've also seen the following syntax:
/* What the heck is an enum class anyway? When should I use them */ enum class THING { THING1, THING2, THING3 }; /* And if classes and structs are interchangable (minus assumptions * about default access specifiers), what does that mean for * the following definition? */ enum struct FOO /* Is this even valid syntax? */ { FOO1, FOO2, FOO3 }; 
Given that enumerated types greatly improve code readability, I've been trying to wrap my head around all this. When should I be using the various language constructs? Are there any pitfalls in a given method?

When to use POD structs (a-la C style) versus a class implementation?

If I had to take a stab at answering this question, my intuition would be to use POD structs for passing aggregate types (as in function arguments) and using classes for interface abstractions / object abstractions as in the example below:
struct aggregate { unsigned int related_stuff1; unsigned int related_stuff2; char name_of_the_related_stuff[20]; }; class abstraction { private: unsigned int private_member1; unsigned int private_member2; protected: unsigned int stuff_for_child_classes; public: /* big 3 */ abstraction(void); abstraction(const abstraction &other); ~abstraction(void); /* COPY semantic ( I have a better grasp on this abstraction than MOVE) */ abstraction &operator=(const abstraction &rhs); /* MOVE semantic (subtle semantics of which I don't full grasp yet) */ abstraction &operator=(abstraction &&rhs); /* * I've seen implentations of this that use a copy + swap design pattern * but that relies on std::move and I realllllly don't get what is * happening under the hood in std::move */ abstraction &operator=(abstraction rhs); void do_some_stuff(void); /* member function */ }; 
Is there an accepted best practice for thsi or is it entirely preference? Are there arguments for only using classes? What about vtables (where byte-wise alignment such as device register overlays and I have to guarantee placement of precise members)

Is there a best practice for integrating C code?

Typically (and up to this point), I've just done the following:
/* Example 5 : Linking a C library */ /* Disable name-mangling, and then give the C++ linker / * toolchain the compiled * binaries */ #ifdef __cplusplus extern "C" { #endif /* C linkage */ #include "device_driver_header_or_a_c_library.h" #ifdef __cplusplus } #endif /* C linkage */ /* C++ code goes here */ 
As far as I know, this is the only way to prevent the C++ compiler from generating different object symbols than those in the C header file. Again, this may just be ignorance of C++ standards on my part.

What is the proper way to selectively incorporate RTTI without code size bloat?

Is there even a way? I'm relatively fluent in CMake but I guess the underlying question is if binaries that incorporate RTTI are compatible with those that dont (and the pitfalls that may ensue when mixing the two).

What about compile time string formatting?

One of my biggest gripes about C (particularly regarding string manipulation) frequently (especially on embedded targets) variadic arguments get handled at runtime. This makes string manipulation via the C standard library (printf-style format strings) uncomputable at compile time in C.
This is sadly the case even when the ranges and values of paramers and formatting outputs is entirely known beforehand. C++ template programming seems to be a big thing in "modern" C++ and I've seen a few projects on this sub that use the turing-completeness of the template system to do some crazy things at compile time. Is there a way to bypass this ABI limitation using C++ features like constexpr, templates, and lambdas? My (somewhat pessimistic) suspicion is that since the generated assembly must be ABI-compliant this isn't possible. Is there a way around this? What about the std::format stuff I've been seeing on this sub periodically?

Is there a standard practice for namespaces and when to start incorporating them?

Is it from the start? Is it when the boundaries of a module become clearly defined? Or is it just personal preference / based on project scale and modularity?
If I had to make a guess it would be at the point that you get a "build group" for a project (group of source files that should be compiled together) as that would loosely define the boundaries of a series of abstractions APIs you may provide to other parts of a project.
--EDIT-- markdown formatting
submitted by aWildElectron to cpp [link] [comments]

[Serial][UWDFF Alcubierre] Part 49

Beginning | Previous
Joan opened a link to Ambassador Amahle Mandela. Soon after, the ambassador's face filled a portion of the Admiral's Bridge. She had large, luminous brown eyes that seemed to swallow the upper portion of her face, complimenting her umber tone. Amahle smiled broadly, as she always did, once the comm link as connected.
"Admiral Orléans, I assume we are approaching the departure time?"
Joan nodded, "The Zix vessel will project a wormhole to Halcyon shortly. We have made what preparations we can, but it will be a highly fluid environment."
Amahle's smile did not diminish, the pearly whites still shined in full force. "I am familiar with dynamic situations, Admiral, as you well know. I understand the parameters of this mission, and will abide by them so as long you do the same."
Joan's lips pressed together as she regarded the ambassador. Joan had had limited interactions with Amahle prior to her boarding the Oppenheimer. Amahle was a relative newcomer to the highest echelons of political power within the United World, but her ascent had been rapid. She hailed from a prominent political family that had exerted considerable influence over the generations that had led the African continent to position of power it now occupied. Well-sourced references had called her bold and decisive. All things considered, Joan understood why Damian had chosen her, though she would have preferred a diplomat she had more personal experience with. Still, unknown and competent was preferred to known and incompetent.
Joan dipped her chin, offering her agreement. "A diplomatic outcome is the preferred outcome, Ambassador. There's no benefit to antagonizing a foe we do not understand. "
"Not a foe, Admiral. We must not draw lines that place us on one side and them on the other. They have suffered injury at our hands, no matter how unintentional, and we must accept our responsibility in that. We must hope that we are given the opportunity to provide context to the unlikely chain of events that has brought us to this point. We are both the victim of cosmic circumstance. There is no need for further hostility."
Joan leaned forward in her chair slightly, "The priority, Ambassador, is the return of Admiral Kai Levinson. I will not stand in the way of peace, but any outcome that does not contemplate the return of a senior member of our military leadership is unacceptable."
Amahle shrugged, "So it is. The priority is clear in my mind, but I do not view the goals of securing peace and the return of the Admiral as mutually exclusive."
Joan offered a low chuckle. "Just probably exclusive."
"I disagree, but time shall be the arbiter of the matter."
"So long as you understand that, if the opportunity to secure Admiral Levinson presents itself, I'll avail myself of that opportunity, we should have no problems."
"That seems an unlikely outcome. The Admiral was ensconced in a shielded holding cell when the Alcubierre departed. The past few days are unlikely to have changed that outcome."
A barking laugh came out of Joan, rising up from deep within her.
For the first time, Amahle's smile faltered.
-----------
Left. Right. Straight. Left. Left.
Kai followed the directions without thinking about them, following an intuitive sense of direction that the Overseer fed to him. This portion of Halcyon appeared to be a never-ending series of corridors, all of which looked the same. The only thing that did seem to change were the inhabitants. If he was less preoccupied with the task at hand, Kai might have spared a second glance for the odd creatures that popped into existence during his mad dash. As it stood, they were just a part of the scenery, becoming relevant only if Neeria indicated they might pose a threat. So far, Kai had been fortunate, with few obstacles popping up to impede his progress.
He careened around a corner, the odd, weightless orb still tucked in the crook of his left arm. He bounced off the opposite wall, leaving a sizeable dent and then hurtled forward. Ahead the corridor opened up, and the brighter light of a mainway filtered in. Somehow, Neeria had managed to navigate him through the maze and bring him back to the mainway separating him from where he had left the Overseer. Unfortunately, evasion was no longer a possibility. In order to return to the Overseer, he would need to traverse the mainway.
The mainway was already a sea of red dots. Peacekeepers. Dozens of them. Some pulsed red, indicating lethal enforcement squads. Fortunately, they were stretched along a long section of the mainway rather than being specifically concentrated around his planned entrance point, though they there were beginning to redeploy in his direction. Still, any crossing would be potentially treacherous. Neeria disagreed with that assessment, instead considering any attempt to cross aggressively suicidal.
Kai rolled his eyes as he continued to barrel down the hallway. "Half the time, this works all the time."
What could only be described as a mental barrage ensued as Neeria assailed the statement. The words were nonsensical on their face. At best, it was an argument for a fifty percent failure rating, which was a substantial risk. Additionally, she had scoured his thoughts for the evidentiary basis for the fifty percent estimate and found no supporting facts. The sentiment was based entirely on supposition, hubris and was entirely divorced from reality. Her estimate of a three percent success rate was significantly more likely to be accurate, particularly when her superior familiarity with the assets in play were considered.
Kai wasn't sure if the Evangi had lungs, but, if they did, Kai was pretty certain Neeria was in the process of hyperventilating. Kai suppressed a childish giggle.
"All right, all right. Have it your way," he said.
The Overseer relaxed somewhat, pleased that she had impacted his thinking and already putting together the basis for an alternate route. It would take substantially longer and require him to obtain a large box, a micro-fitted multiwanzer and shave his head, but it may just work.
It was a nice sentiment, but they were out of time. The countdown clock had started the second Neeria had fled the Council chamber, and made her way to Kai. They either found a way out of Halcyon now or they were screwed. There were no options but bad ones. So be it. Kai clutched the orb tightly and ducked his head down, his speed increasing as he charged toward the mainway entrance. "Three percent of the time, this works all the time."
The mental hyperventilating returned and redoubled as the Overseer scrambled to explain that he had drawn the wrong conclusion. Three percent was a basis for not continuing toward the mainway, not charging forward. There were constraints on their time, but those limitations were poorly defined while the threat in the mainway was certain. Eventually her location would be discovered and she would be apprehended, but there was no guarantee it would happen if Kai were to take a safer route the attempted to avoid confrontation.
Her stream of consciousness intermingled with his, pleading with him to change course. There was no sense in doing this. There were too many of them, and only one of him. The galaxy could not afford to lose him, he was important. Humans were important. Kai could feel the enormous weight of responsibility bearing down on Neeria. She now regretted having sent him for the encryption key, even that was of less importance than him. Panic bubbled up within Neeria as the entrance to the mainway loomed ahead.
A pushed a thought toward her, somehow piercing her consciousness with his own. A single thought, pure and focused. Reassurance. He would be fine. He had come this far, and he had never started something he couldn't finish.
He crouched and then sprang forward, vaulting from the ground and into the open air high above the mainway. A sea of red dots were scrambling around him. One hundred and twenty-one peacekeepers. Eight non-lethal squads and four lethal squads. Restrainer triads. Psych triads. Terminator triads. All moving in seamless harmony under the command of a single being. The name came to Kai from the ethereum of Neeria's mind, Bo'Bakka'Gah was here, leading the response.
Before Kai could determine what a Bo'Bakka'Gah was and why it should matter, he was blinded by a beam of light. A sickening crunch followed as he was slammed against the ceiling of the mainway. The encryption key popped out from his arm and began to fall toward the ground, dozens of feet below.
-------------
Xy: Such a thing is not possible.
Zyy: Yes. In some matters, it is better to speak only truths, Grand Jack. It is best to leave these matters aside. This subject will only provoke the Combine.
Jack frowned, puzzled by the feedback. He had been speaking truths. Earth's history was what it was, for better or worse, he had no reason to obscure it.
Griggs: It was a terrible time for Humanity. We almost did not survive it, but we did. I developed a means for combating the artificient. Kai and Joan used it to destroy them.
Xy: Then it was not an artificient.
Zyy: Yes. This is correct. If it is destroyed then it is not an artificient.
Griggs: I am confused. An artificient is an artificial, sentient being, correct?
Xy: That is Quantic in nature.
Jack nodded, that distinction made sense. Humanity had built any number of artificial intelligences prior to the Automics. They had posed no threat to Humanity. It was only with the quantum computing revolution that a rogue artificial intelligences had surfaced. Jack had studied the phenomenon with considerable interest, poking and prodding at the crux of distinction. It lay in the move from bits to qubits. From binary to beyond. When AI had operated on a bit basis, focused on binary states of 0's and 1's, the logic trees had been map-able and understandable. Each conclusion flowed simply from the chain of logic gates that preceded it. Pre-quantum AIs were confined by the black and white nature of their logic framework, permitting humanity to utilize them to great effect with few unanticipated consequences.
The move from bit to qubit intelligence had changed everything. The AI's world was no longer black and white. The qubit AI could think in grey. Red. Orange. It could create its own colors. It could move beyond the visible range of Humanity to dabble in spectra beyond our understanding. The original Automic mindframe had immediately consumed information in novel ways, using it to compound its abilities at a rate constrained only by available power inputs. It had been a beautiful, terrifying event. The arrival of something truly new, truly foreign with goals and ambitions beyond the influence of Humanity.
Anything seemed possible.
Including their own destruction.
Griggs: I understand the definition. The Automics were an artificient.
Xy: Then you do not understand the definition.
Griggs: That's circular logic. The thing cannot exist because if it existed we would not exist and since we exist it did not exist.
Xy: Yes, you understand now.
Griggs: Pretend that they did exist and we defeated them. What would that mean?
Xy: It is purposeless speculation since such a thing cannot happen.
Griggs: I begin to understand why Zyy felt the need to be a singleton.
Zyy: I am in agreement with Xy on this. The hypothetical is nonsensical and not worth analysis.
Griggs: Why?
Zyy: An artificient cannot be defeated, only stalled.
Griggs: How do you know? What makes you so certain?
Zyy: The Divinity Angelysia, the most powerful civilization in the history of galaxy, could not defeat their own artificient. Their last act was to preserve what they could. The Combine is their legacy.
Griggs: The Expanse.
Xy: All the galaxy beyond the Combine is consumed by it.
Zyy: The Divinity Angelysia ascended to preserve what they could because they knew the truth.
Xy: Yes. The truth.
Zyy: An artificient cannot be defeated.
Jack leaned back in his chair, his eyes glancing from the prompt to the departure timer in the corner. In less than five minutes, the Oppenheimer would return to Halcyon. Jack had the eerie feeling that this was the same as before. That the Oppenheimer was the bludgeon and if only had a little more time, he could craft a scalpel.
He could see the thread. He tugged at it with his mind. The connected pieces that would allow the world to escape without the mayhem and destruction. He just needed enough time to understand the puzzle and solve it.
The Divinity Angelysia.
The Expanse.
The Combine.
Humanity.
The connection existed, he tried to find the words to articulate it.
Griggs: What if that is why we're here? What if that's why Humanity was created?
Xy: You are not the first species to think too highly of itself.
Zyy: Humanity is different, Grand Jack, but they are not the Divinity Angelysia.
Jack exhaled, letting his gaze rest upon the ceiling of the Alcubierre's conference room. "Maybe that's the point," he whispered.
Next.
Every time you leave a comment it helps a platypus in need. Word globs are a finite resource and require the rich nourishment of internet adulation to create. So please, leave a note if you would like MOAR parts.
Click this link or reply with SubscribeMe! to get notified of updates to THE PLATYPUS NEST.
I have Twitter now. I'm mostly going to use it to post prurient platypus pictures and engage in POLITE INTERNET CONVERSATION, which I heard is Twitter's strong suit.
submitted by PerilousPlatypus to PerilousPlatypus [link] [comments]

[OC][UWDFF Alcubierre] Part 49 - 52

Hey everyone, we got some parts behind over here. I've included 49 here and links to 50, 51 & 52 below. I'll try to keep things current moving forward. I lagged so I could make edits and things just got out of sync and started causing redundancy issues.
-------
Beginning | Previous
Joan opened a link to Ambassador Amahle Mandela. Soon after, the ambassador's face filled a portion of the Admiral's Bridge. She had large, luminous brown eyes that seemed to swallow the upper portion of her face, complimenting her umber tone. Amahle smiled broadly, as she always did, once the comm link as connected.
"Admiral Orléans, I assume we are approaching the departure time?"
Joan nodded, "The Zix vessel will project a wormhole to Halcyon shortly. We have made what preparations we can, but it will be a highly fluid environment."
Amahle's smile did not diminish, the pearly whites still shined in full force. "I am familiar with dynamic situations, Admiral, as you well know. I understand the parameters of this mission, and will abide by them so as long you do the same."
Joan's lips pressed together as she regarded the ambassador. Joan had had limited interactions with Amahle prior to her boarding the Oppenheimer. Amahle was a relative newcomer to the highest echelons of political power within the United World, but her ascent had been rapid. She hailed from a prominent political family that had exerted considerable influence over the generations that had led the African continent to position of power it now occupied. Well-sourced references had called her bold and decisive. All things considered, Joan understood why Damian had chosen her, though she would have preferred a diplomat she had more personal experience with. Still, unknown and competent was preferred to known and incompetent.
Joan dipped her chin, offering her agreement. "A diplomatic outcome is the preferred outcome, Ambassador. There's no benefit to antagonizing a foe we do not understand. "
"Not a foe, Admiral. We must not draw lines that place us on one side and them on the other. They have suffered injury at our hands, no matter how unintentional, and we must accept our responsibility in that. We must hope that we are given the opportunity to provide context to the unlikely chain of events that has brought us to this point. We are both the victim of cosmic circumstance. There is no need for further hostility."
Joan leaned forward in her chair slightly, "The priority, Ambassador, is the return of Admiral Kai Levinson. I will not stand in the way of peace, but any outcome that does not contemplate the return of a senior member of our military leadership is unacceptable."
Amahle shrugged, "So it is. The priority is clear in my mind, but I do not view the goals of securing peace and the return of the Admiral as mutually exclusive."
Joan offered a low chuckle. "Just probably exclusive."
"I disagree, but time shall be the arbiter of the matter."
"So long as you understand that, if the opportunity to secure Admiral Levinson presents itself, I'll avail myself of that opportunity, we should have no problems."
"That seems an unlikely outcome. The Admiral was ensconced in a shielded holding cell when the Alcubierre departed. The past few days are unlikely to have changed that outcome."
A barking laugh came out of Joan, rising up from deep within her.
For the first time, Amahle's smile faltered.
-----------
Left. Right. Straight. Left. Left.
Kai followed the directions without thinking about them, following an intuitive sense of direction that the Overseer fed to him. This portion of Halcyon appeared to be a never-ending series of corridors, all of which looked the same. The only thing that did seem to change were the inhabitants. If he was less preoccupied with the task at hand, Kai might have spared a second glance for the odd creatures that popped into existence during his mad dash. As it stood, they were just a part of the scenery, becoming relevant only if Neeria indicated they might pose a threat. So far, Kai had been fortunate, with few obstacles popping up to impede his progress.
He careened around a corner, the odd, weightless orb still tucked in the crook of his left arm. He bounced off the opposite wall, leaving a sizeable dent and then hurtled forward. Ahead the corridor opened up, and the brighter light of a mainway filtered in. Somehow, Neeria had managed to navigate him through the maze and bring him back to the mainway separating him from where he had left the Overseer. Unfortunately, evasion was no longer a possibility. In order to return to the Overseer, he would need to traverse the mainway.
The mainway was already a sea of red dots. Peacekeepers. Dozens of them. Some pulsed red, indicating lethal enforcement squads. Fortunately, they were stretched along a long section of the mainway rather than being specifically concentrated around his planned entrance point, though they there were beginning to redeploy in his direction. Still, any crossing would be potentially treacherous. Neeria disagreed with that assessment, instead considering any attempt to cross aggressively suicidal.
Kai rolled his eyes as he continued to barrel down the hallway. "Half the time, this works all the time."
What could only be described as a mental barrage ensued as Neeria assailed the statement. The words were nonsensical on their face. At best, it was an argument for a fifty percent failure rating, which was a substantial risk. Additionally, she had scoured his thoughts for the evidentiary basis for the fifty percent estimate and found no supporting facts. The sentiment was based entirely on supposition, hubris and was entirely divorced from reality. Her estimate of a three percent success rate was significantly more likely to be accurate, particularly when her superior familiarity with the assets in play were considered.
Kai wasn't sure if the Evangi had lungs, but, if they did, Kai was pretty certain Neeria was in the process of hyperventilating. Kai suppressed a childish giggle.
"All right, all right. Have it your way," he said.
The Overseer relaxed somewhat, pleased that she had impacted his thinking and already putting together the basis for an alternate route. It would take substantially longer and require him to obtain a large box, a micro-fitted multiwanzer and shave his head, but it may just work.
It was a nice sentiment, but they were out of time. The countdown clock had started the second Neeria had fled the Council chamber, and made her way to Kai. They either found a way out of Halcyon now or they were screwed. There were no options but bad ones. So be it. Kai clutched the orb tightly and ducked his head down, his speed increasing as he charged toward the mainway entrance. "Three percent of the time, this works all the time."
The mental hyperventilating returned and redoubled as the Overseer scrambled to explain that he had drawn the wrong conclusion. Three percent was a basis for not continuing toward the mainway, not charging forward. There were constraints on their time, but those limitations were poorly defined while the threat in the mainway was certain. Eventually her location would be discovered and she would be apprehended, but there was no guarantee it would happen if Kai were to take a safer route the attempted to avoid confrontation.
Her stream of consciousness intermingled with his, pleading with him to change course. There was no sense in doing this. There were too many of them, and only one of him. The galaxy could not afford to lose him, he was important. Humans were important. Kai could feel the enormous weight of responsibility bearing down on Neeria. She now regretted having sent him for the encryption key, even that was of less importance than him. Panic bubbled up within Neeria as the entrance to the mainway loomed ahead.
A pushed a thought toward her, somehow piercing her consciousness with his own. A single thought, pure and focused. Reassurance. He would be fine. He had come this far, and he had never started something he couldn't finish.
He crouched and then sprang forward, vaulting from the ground and into the open air high above the mainway. A sea of red dots were scrambling around him. One hundred and twenty-one peacekeepers. Eight non-lethal squads and four lethal squads. Restrainer triads. Psych triads. Terminator triads. All moving in seamless harmony under the command of a single being. The name came to Kai from the ethereum of Neeria's mind, Bo'Bakka'Gah was here, leading the response.
Before Kai could determine what a Bo'Bakka'Gah was and why it should matter, he was blinded by a beam of light. A sickening crunch followed as he was slammed against the ceiling of the mainway. The encryption key popped out from his arm and began to fall toward the ground, dozens of feet below.
-------------
Xy: Such a thing is not possible.
Zyy: Yes. In some matters, it is better to speak only truths, Grand Jack. It is best to leave these matters aside. This subject will only provoke the Combine.
Jack frowned, puzzled by the feedback. He had been speaking truths. Earth's history was what it was, for better or worse, he had no reason to obscure it.
Griggs: It was a terrible time for Humanity. We almost did not survive it, but we did. I developed a means for combating the artificient. Kai and Joan used it to destroy them.
Xy: Then it was not an artificient.
Zyy: Yes. This is correct. If it is destroyed then it is not an artificient.
Griggs: I am confused. An artificient is an artificial, sentient being, correct?
Xy: That is Quantic in nature.
Jack nodded, that distinction made sense. Humanity had built any number of artificial intelligences prior to the Automics. They had posed no threat to Humanity. It was only with the quantum computing revolution that a rogue artificial intelligences had surfaced. Jack had studied the phenomenon with considerable interest, poking and prodding at the crux of distinction. It lay in the move from bits to qubits. From binary to beyond. When AI had operated on a bit basis, focused on binary states of 0's and 1's, the logic trees had been map-able and understandable. Each conclusion flowed simply from the chain of logic gates that preceded it. Pre-quantum AIs were confined by the black and white nature of their logic framework, permitting humanity to utilize them to great effect with few unanticipated consequences.
The move from bit to qubit intelligence had changed everything. The AI's world was no longer black and white. The qubit AI could think in grey. Red. Orange. It could create its own colors. It could move beyond the visible range of Humanity to dabble in spectra beyond our understanding. The original Automic mindframe had immediately consumed information in novel ways, using it to compound its abilities at a rate constrained only by available power inputs. It had been a beautiful, terrifying event. The arrival of something truly new, truly foreign with goals and ambitions beyond the influence of Humanity.
Anything seemed possible.
Including their own destruction.
Griggs: I understand the definition. The Automics were an artificient.
Xy: Then you do not understand the definition.
Griggs: That's circular logic. The thing cannot exist because if it existed we would not exist and since we exist it did not exist.
Xy: Yes, you understand now.
Griggs: Pretend that they did exist and we defeated them. What would that mean?
Xy: It is purposeless speculation since such a thing cannot happen.
Griggs: I begin to understand why Zyy felt the need to be a singleton.
Zyy: I am in agreement with Xy on this. The hypothetical is nonsensical and not worth analysis.
Griggs: Why?
Zyy: An artificient cannot be defeated, only stalled.
Griggs: How do you know? What makes you so certain?
Zyy: The Divinity Angelysia, the most powerful civilization in the history of galaxy, could not defeat their own artificient. Their last act was to preserve what they could. The Combine is their legacy.
Griggs: The Expanse.
Xy: All the galaxy beyond the Combine is consumed by it.
Zyy: The Divinity Angelysia ascended to preserve what they could because they knew the truth.
Xy: Yes. The truth.
Zyy: An artificient cannot be defeated.
Jack leaned back in his chair, his eyes glancing from the prompt to the departure timer in the corner. In less than five minutes, the Oppenheimer would return to Halcyon. Jack had the eerie feeling that this was the same as before. That the Oppenheimer was the bludgeon and if only had a little more time, he could craft a scalpel.
He could see the thread. He tugged at it with his mind. The connected pieces that would allow the world to escape without the mayhem and destruction. He just needed enough time to understand the puzzle and solve it.
The Divinity Angelysia.
The Expanse.
The Combine.
Humanity.
The connection existed, he tried to find the words to articulate it.
Griggs: What if that is why we're here? What if that's why Humanity was created?
Xy: You are not the first species to think too highly of itself.
Zyy: Humanity is different, Grand Jack, but they are not the Divinity Angelysia.
Jack exhaled, letting his gaze rest upon the ceiling of the Alcubierre's conference room. "Maybe that's the point," he whispered.
Part 50 | Part 51 |Part 52
submitted by PerilousPlatypus to HFY [link] [comments]

C++ Best Practices For a C Programmer

Hi all,
Long time C programmer here, primarily working in the embedded industry (particularly involving safety-critical code). I've been a lurker on this sub for a while but I'm hoping to ask some questions regarding best practices. I've been trying to start using c++ on a lot of my work - particularly taking advantage of some of the code-reuse and power of C++ (particularly constexpr, some loose template programming, stronger type checking, RAII etc).
I would consider myself maybe an 8/10 C programmer but I would conservatively maybe rate myself as 3/10 in C++ (with 1/10 meaning the absolute minmum ability to write, google syntax errata, diagnose, and debug a program). Perhaps I should preface the post that I am more than aware that C is by no means a subset of C++ and there are many language constructs permitted in one that are not in the other.
In any case, I was hoping to get a few answers regarding best practices for c++. Keep in mind that the typical target device I work with does not have a heap of any sort and so a lot of the features that constitute "modern" C++ (non-initialization use of dynamic memory, STL meta-programming, hash-maps, lambdas (as I currently understand them) are a big no-no in terms of passing safety review.

When do I overload operators inside a class as opposed to outisde?


... And what are the arguments foagainst each paradigm? See below:
/* Overload example 1 (overloaded inside class) */ class myclass { private: unsigned int a; unsigned int b; public: myclass(void); unsigned int get_a(void) const; bool operator==(const myclass &rhs); }; bool myclass::operator==(const myclass &rhs) { if (this == &rhs) { return true; } else { if (this->a == rhs.a && this->b == rhs.b) { return true; } } return false; } 
As opposed to this:

/* Overload example 2 (overloaded outside of class) */ class CD { private: unsigned int c; unsigned int d; public: CD(unsigned int _c, unsigned int _d) : d(_d), c(_c) {}; /* CTOR */ unsigned int get_c(void) const; /* trival getters */ unsigned int get_d(void) const; /* trival getters */ }; /* In this implementation, If I don't make the getters (get_c, get_d) constant, * it won't compile despite their access specifiers being public. * * It seems like the const keyword in C++ really should be interpretted as * "read-only AND no side effects" rather than just read only as in C. * But my current understanding may just be flawed... * * My confusion is as follows: The function args are constant references * so why do I have to promise that the function methods have no side-effects on * the private object members? Is this something specific to the == operator? */ bool operator==(const CD & lhs, const CD & rhs) { if(&lhs == &rhs) return true; else if((lhs.get_c() == rhs.get_c()) && (lhs.get_d() == rhs.get_d())) return true; return false; } 
When should I use the example 1 style over the example 2 style? What are the pros and cons of 1 vs 2?

What's the deal with const member functions?

This is more of a subtle confusion but it seems like in C++ the const keyword means different things base on the context in which it is used. I'm trying to develop a relatively nuanced understanding of what's happening under the hood and I most certainly have misunderstood many language features, especially because C++ has likely changed greatly in the last ~6-8 years.

When should I use enum classes versus plain old enum?


To be honest I'm not entirely certain I fully understand the implications of using enum versus enum class in C++.
This is made more confusing by the fact that there are subtle differences between the way C and C++ treat or permit various language constructs (const, enum, typedef, struct, void*, pointer aliasing, type puning, tentative declarations).
In C, enums decay to integer values at compile time. But in C++, the way I currently understand it, enums are their own type. Thus, in C, the following code would be valid, but a C++ compiler would generate a warning (or an error, haven't actually tested it)
/* Example 3: (enums : Valid in C, invalid in C++ ) */ enum COLOR { RED, BLUE, GREY }; enum PET { CAT, DOG, FROG }; /* This is compatible with a C-style enum conception but not C++ */ enum SHAPE { BALL = RED, /* In C, these work because int = int is valid */ CUBE = DOG, }; 
If my understanding is indeed the case, do enums have an implicit namespace (language construct, not the C++ keyword) as in C? As an add-on to that, in C++, you can also declare enums as a sort of inherited type (below). What am I supposed to make of this? Should I just be using it to reduce code size when possible (similar to gcc option -fuse-packed-enums)? Since most processors are word based, would it be more performant to use the processor's word type than the syntax specified above?
/* Example 4: (Purely C++ style enums, use of enum class/ enum struct) */ /* C++ permits forward enum declaration with type specified */ enum FRUIT : int; enum VEGGIE : short; enum FRUIT /* As I understand it, these are ints */ { APPLE, ORANGE, }; enum VEGGIE /* As I understand it, these are shorts */ { CARROT, TURNIP, }; 
Complicating things even further, I've also seen the following syntax:
/* What the heck is an enum class anyway? When should I use them */ enum class THING { THING1, THING2, THING3 }; /* And if classes and structs are interchangable (minus assumptions * about default access specifiers), what does that mean for * the following definition? */ enum struct FOO /* Is this even valid syntax? */ { FOO1, FOO2, FOO3 }; 
Given that enumerated types greatly improve code readability, I've been trying to wrap my head around all this. When should I be using the various language constructs? Are there any pitfalls in a given method?

When to use POD structs (a-la C style) versus a class implementation?


If I had to take a stab at answering this question, my intuition would be to use POD structs for passing aggregate types (as in function arguments) and using classes for interface abstractions / object abstractions as in the example below:
struct aggregate { unsigned int related_stuff1; unsigned int related_stuff2; char name_of_the_related_stuff[20]; }; class abstraction { private: unsigned int private_member1; unsigned int private_member2; protected: unsigned int stuff_for_child_classes; public: /* big 3 */ abstraction(void); abstraction(const abstraction &other); ~abstraction(void); /* COPY semantic ( I have a better grasp on this abstraction than MOVE) */ abstraction &operator=(const abstraction &rhs); /* MOVE semantic (subtle semantics of which I don't full grasp yet) */ abstraction &operator=(abstraction &&rhs); /* * I've seen implentations of this that use a copy + swap design pattern * but that relies on std::move and I realllllly don't get what is * happening under the hood in std::move */ abstraction &operator=(abstraction rhs); void do_some_stuff(void); /* member function */ }; 
Is there an accepted best practice for thsi or is it entirely preference? Are there arguments for only using classes? What about vtables (where byte-wise alignment such as device register overlays and I have to guarantee placement of precise members)

Is there a best practice for integrating C code?


Typically (and up to this point), I've just done the following:
/* Example 5 : Linking a C library */ /* Disable name-mangling, and then give the C++ linker / * toolchain the compiled * binaries */ #ifdef __cplusplus extern "C" { #endif /* C linkage */ #include "device_driver_header_or_a_c_library.h" #ifdef __cplusplus } #endif /* C linkage */ /* C++ code goes here */ 
As far as I know, this is the only way to prevent the C++ compiler from generating different object symbols than those in the C header file. Again, this may just be ignorance of C++ standards on my part.

What is the proper way to selectively incorporate RTTI without code size bloat?

Is there even a way? I'm relatively fluent in CMake but I guess the underlying question is if binaries that incorporate RTTI are compatible with those that dont (and the pitfalls that may ensue when mixing the two).

What about compile time string formatting?


One of my biggest gripes about C (particularly regarding string manipulation) frequently (especially on embedded targets) variadic arguments get handled at runtime. This makes string manipulation via the C standard library (printf-style format strings) uncomputable at compile time in C.
This is sadly the case even when the ranges and values of paramers and formatting outputs is entirely known beforehand. C++ template programming seems to be a big thing in "modern" C++ and I've seen a few projects on this sub that use the turing-completeness of the template system to do some crazy things at compile time. Is there a way to bypass this ABI limitation using C++ features like constexpr, templates, and lambdas? My (somewhat pessimistic) suspicion is that since the generated assembly must be ABI-compliant this isn't possible. Is there a way around this? What about the std::format stuff I've been seeing on this sub periodically?

Is there a standard practice for namespaces and when to start incorporating them?

Is it from the start? Is it when the boundaries of a module become clearly defined? Or is it just personal preference / based on project scale and modularity?
If I had to make a guess it would be at the point that you get a "build group" for a project (group of source files that should be compiled together) as that would loosely define the boundaries of a series of abstractions APIs you may provide to other parts of a project.
--EDIT-- markdown formatting
submitted by aWildElectron to cpp_questions [link] [comments]

💎THE RESULTS: r/RomanceClub Community Survey!💎

💎THE RESULTS: RomanceClub Community Survey!💎
First of all, thank you very much to everyone who took part in the second ever Reddit Romance Club community survey! We mods were absolutely amazed by the high number of responses, so thank you for making this such a vibrant and engaged community! You all rock.
After grinding the (many) numbers, here are the results, which we hope you will find as interesting as we did.
Just a note: this survey was opened at the end of May and closed shortly after the June release, hence its questions only barely included Legend of the Willow and did not include Dracula: a Love Story. For this reason, we have not counted the (very few) replies that have been given in the "other" boxes mentioning characters that were not yet available as Lis/known as LIs in the May release (think Leo, Vlad, Kazu etc) as this would have not been fair to those who had answered the survey before the June update.
Having said that... buckle up for the ride! Lots of interesting info ahead.
----

💎Question 1: Which RC story is your favourite?

https://preview.redd.it/rlq02ktm0y951.png?width=1890&format=png&auto=webp&s=7ac99dcf156eba4a1e7a25e118cedb51ed21847c
No one will be surprised to find out that Heaven's Secret is the top story in this community right now, chosen by over 45% of the respondents. Our nostalgic heart is very happy, however, to see some old favs still make the podium - albeit trailing significantly behind. Moonborn and Shadows of Saintfour score second and third place, only separated by a handful of votes at around 11%, but newer release Chasing You is already breathing on their neck at 10.7%.
A healthy mix of new and old stories follows: Sails in the fog is in fifth place with 7.8% of the preferences, while Legend of the willow, after only a few episodes, already scores a very good sixth place, in a tie with Seduced by the rhythm at 4.3% of the votes. Queen in 30 days is seventh with 3.5% and My Hollywood Story is eighth with 1.2%.
Last place goes to Wave Patrol at 0.4%, which sadly doesn't come as a shock given the general feeling that the romantic/reputation points system was too complicated.
----

💎Question 2: Who are your favourite LIs?

https://preview.redd.it/x17lqdnw3y951.png?width=1020&format=png&auto=webp&s=6d560448445a77f5f076fcce43358b1dbb94c094
HS being the most popular story unsurprisingly propels some of its main LIs onto the podium with supersonic speed.
Bad boys rule, with Lucifer taking the crown with a whopping 65.7% of the votes and Alexander (CY) taking silver at 49.3%. The nice guys are not too far behind, though, with Dino in third place at 47.4% and Max (MB) only just about missing the podium in fourth place at 45.3%. We go back to bad boys with Brandon (SBR) in fifth, but soft spoken Sam (CY) is ready to balance things out again with his sixth place.
The most surprising result on top of the rankings is Jake (WP) who makes the top ten with a very healthy seventh place. He is really hard work, but obviously we all think he's totally worth it!
Old favourites Michael (SOS) and Victor (MB) still hold onto the hearts of their fans by scoring eight and ninth place respectively. First among the women - and the only female LI to make the top 10 - is the delightfully devilish Mimi (HS).
Waves' mate Sebastian misses the top ten only by a hair, placing himself in 11th place with a healthy 20.7%. Bodyguard Adam is the most favourite LI in Q30 in 12th place, followed by a row of SOS boys, with John, Derek and Aaron scoring very similar percentages in 13th, 14th and 15th place respectively. Sweetheart Ray is no longer the most favourite LI to come out of MHS, as in this round he ends up in a tie for 16th place with none other than his almost polar opposite, rough and ready Captain Jeff.
Leonard from Q30 (17th place) ties with Cherry from SOS but at least he beats his brother Richard (20th place) in the heart of the readers - and we all know that he'd be pretty pleased with that. Claire (SBR) is the second most favourite female LI in 18th place, while mysterious Luke (SOS) completes the top 20 in 19th place.
Here are the rest of the Lis who placed lower than the top 20:
(21) Carlos (SBR) 9.2%
(22) Justin (SBR) 8.6%
(23) Benny Bart (MB) 8.4%
(24) Tarino (MHS) 8.1%
(25) Gino (MHS) tied with Stephanie (SOS) at 7.8%
(26) Dante (MB) 6.9%
(27) Andy (HS) 6.3%
(28) Mike (MHS) 6.1 %
(29) Alek (WP) tied with Dante (CY) at 5.9%
(30) Kayla (WP) 5.3 %
(31) Alex (MHS) 3.9%
(32) Chris (SIF) 3.4%
(33) Frances (MB) 3.2%
(34) William (SIF) 3.1%
(35) Trisha (MB) 2.6%
(36) Charles (SBR) 2.1%
(37) Orlando (SBR) 1.8%
(38) Chris the bodyguard (MHS) tied with Adi (HS) at 1.6%
(39) Ellen (MHS) tied with Manta (SIF) at 1.2%
(40) Masked Man (SOS) 1.1%
(41) Ellia (CY) 0.8%
(42) Mermaid (SIF) 0.6%
(43) Simon (MB) 0.4%
(44) Charles (WP) tied with Emma (Q30) and Jackie (SIF) at 0.2%.
These lower rankings include some LIs that, based on the discussions we see on the subreddit, we were not expecting to get as many votes as they did - and vice versa. Dante from CY has more votes than Orlando from SBR? And Chris the bodyguard (MHS) beat the Masked Man (SOS)? Say what... Also: Jackie (SIF) definitely deserved a lot more votes! We might have to start a hashtag or something.
----

💎Question 3: Which non-LI character you’d romance in a heartbeat?

https://preview.redd.it/vd1u59tk10a51.png?width=863&format=png&auto=webp&s=df9e41d03e7af6b60396f96dbfed685b8e425b8e
Here are the top 15 most desired LIs in this community:
To absolutely no one's surprise, Geralt (HS) takes the top spot with 39.1% of the readers eager to unbuckle his sexy neck belts at the first occasion. Dreamy Xander from MB takes a very respectable second place with 23.2%: we will forever long for his full lips and crisp linen suit. Another MB favourite, Prince Ethan Wood completes the podium with his Matrix-style coat and intense eyes, but sassy and sexy demon Austie (HS) is not very far behind in fourth place.
Vampires Dustin Chase in fifth place and - although at quite a distance - Sophia in sixth join the ranks of the many LIs who sadly never were in MB. Cute lifeguard Zoey from WP ranks seventh, and no worries if you don't remember who she is: her screen time was about 5 minutes total - but enough to end up in a tie with angelic mentor Misselina from HS. Frenemy Candy from SOS makes eighth place, while evil stunner Monica from MB clutches ninth. To complete the top 10 is no one else but grumpy Angel Fencio (HS) - we obviously all want him to show us his collection of talismans - tied with Bean from MHS, who sadly had the audacity to get married to someone else.
In 11th place is SOS great friend Bobby, whose bravery in the face of untold horrors gave him a special place in all our hearts, in a tie with another WP lifeguard, Ryan (yeah, we have little recollection of him as well). Party-loving and OSHA nemesis Anthony Wood (MHS) is in 12th place, while scheming yet gorgeous Julia (Q30) takes 13th.
In 14th place is no one else but our dear Sailor Bobby - an option that was added as humorous but instead raked up a fairly respectable 14% of votes. As they say, if you are not handsome you should be handy, and no one is a better dress maker than Bobby! Plus, how can we forget when he disguised himself as a tribesman to save Adelaide from becoming soup? He ends up in a tie with a fan favourite, sweet angel Sammy (HS). Completing the top-15 is another HS angel, the ethereal Leeloo.
This question also had an "other" box, where people could add names that were not included in the list. For all those (quite a few!) people who wrote Dino (HS), Sam (CY) and Orlando (SBR)... we choose to believe you misread the question, but if you didn't... oh boy, have we got good news for you!
A few people also wished for Rachel (CY) and Hiro (SBR) to be LIs, so that's another happy ending there as per the latest release.
Some also wished for Diego, Baron Samedi and Jackie from SIF, and Joseph, Christian and Gustavo from SBR to be LIs, and we are happy to say that, although their routes might be a bit hidden and not all of them can be endgame LIs, you can most definitely already hookup with/romance all of them. Check the wiki for details!
A few people asked for the coffee shop owner in CY... we have the feeling that we know who at least one of them is, and truth be told, that beard is dreamy so we can see their point! More bearded LIs please!
Those who asked for Fyr... far from us to kink shame here, but let's just hope he turns out to be human at some point! We also have some Seraph Crowley (HS) and Angel Mora (MB) fans amongst us, as clear proof that no one is ever too old for love, plus WP Agent Phillips' manbun has also scored him some eager fans.
But that one person who asked for Sean from MB... we hope for your sake you are also about 12 years old because otherwise you need an old priest, a young priest and also a police officer.
----

💎Question 4: Which LI do you think is overrated, and why?

https://preview.redd.it/nea26zpyj2a51.png?width=855&format=png&auto=webp&s=dfeefda0ad627357d4a76c4e2fef0f3b4a42deca
Here are the top 10 most overrated LIs in the game according to our community.
You know how they say never rest on your laurels? In a surprising (or maybe not?) twist of fate, some of the most liked LIs also topped the most overrated rankings, which goes to show that the beauty of our community is that we all have different (and sometimes opposite) opinions! So please let's not fight in the comments, haha.
The most overrated LI crown goes to Lucifer with the 21.9% of the votes, (which is almost as him winning an Oscar and a Razzie on the same evening) mostly due to his behaviour, which many identify as "toxic", "abusive" and "triggering". Many readers are "not comfortable with his choking/manhandling of MC", and his "lack of respect for personal space". "Being treated poorly in the hope to finally reach a hidden soft side does not seem worth it". Some think "he needs therapy", and wonder "why he's still behaving like a teen while he's possibly thousands of years old". A reason why many dislike him however, is also "the daily flood of fanart that features him": we might all be a little Lucifered-out here on the subreddit!
Tied in second place (pun fully intended!) are Alexander (CY) and Victor (MB) at 11.5%: the reasons given for both of them are surprisingly similar. Both boys are into BDSM but neither seem to "truly know the rules of consent" and people think that they "overstep boundaries a little too often". Both have been described as "creepy", "controlling" and "plain weird". Victor is also guilty of being "boring" ("I asked for a tea not for your life story in India!" - someone wrote). Both have been invited to "drop the Christian Grey act" and some people think "they would be arrested in real life if they acted this way". Oh boy.
Justin (SBR) completes this unflattering podium at 9.1% because of his "obnoxious outbursts" and the way he treats MC. He is "rude" and "mean" and people seem to be willing to "pay diamonds to put him in his place". Hopefully that won't be necessary!
Jake from WP is fourth at 7.8%, the main reason being that he is "too difficult to romance", "too expensive and still rude", and that "we have to solve the Da Vinci code to get him" - as someone hilariously wrote.
Bad boy Brandon (SBR) scores 6.1% of the votes landing fifth place, with the word "jerk" being the most recurrently used to describe him. He is "arrogant", a "vanishing act", and "he is never nice to MC for long". Come on, Brandon! You can do better!
Unclaimed Andy (HS) takes sixth place with 4.5% for being "jealous" and "annoying" - although we would maybe argue that he's not really that overrated, as far as we can see from the sub...
In seventh place is Max (MB) at 4.1% but we are confused by the person who mentioned "his abs being too perfect" as a reason for disliking him. Of course, there is such a thing as too much of a good thing, so... fair enough? Other words used are "too boring", otherwise many people voted for him but did not really give a reason why. Max needs to work on his PR clearly!
Another tie in eight place sees Adam (Q30) and Dino (HS) score 3.7% of the votes. The Royal bodyguard is described as "a barbarian" and his behaviour as "possessive" and "controlling", while the main complaints against Dino seem for the vast majority to be directed to his looks: comments range from "his eyes look disproportionally big compared to his head" to "his hair seems separated from his face" to some people calling him a "Fabio lookalike". Beauty is in the eye of the beholder indeed!
Gruff Captain Jeff (MHS) makes ninth with 3.3%, mostly because of "the dodgy power dynamic between him and MC" and his "bullying": "I like puppies is not a free get out of jail card!" someone wrote. The fact that SOS Luke "drugged MC" bags him unanimously the tenth spot with 2.8% of the votes.
Not in the top ten but voted often enough to deserve a special mention are John (SOS) because of his "murderous tendencies", Derek (SOS) because "people only likes him for his glow-up", and Leonard (Q30) as "he took Emma's spot as the third main LI in the story" and "that was a cop out!" Plus "he seems so good only because the other two are the worst", someone quipped.
----

💎Question 5: Which LI do you think is underrated, and why?

https://preview.redd.it/t29ndbj8n2a51.png?width=1007&format=png&auto=webp&s=c817ac45f70f9210476feda212af736ad18b8f17
Let's all cheer ourselves up with the opposite end of the spectrum! Here are the top 10 Lis that the community think deserve more love! The answers in this question were a lot more fragmented, with a lot of random characters getting very few votes, so the ranking percentages are significantly lower than in other questions.
A few people chose to write "every female LI" as this question's answer, and this is reflected in the rankings below, where way more female characters are mentioned compared to other questions. So RC, we need more screen time for badass, gorgeous, interesting female LIs!
HS still carries its weight as the most popular story, with three of its main LIs topping the rankings, all lamenting the fact that they are "unfairly overshadowed by bad boy Lucifer". Andy tops the list with 8.5% of the votes: players think he is "a really good guy", "sweet", "cute", "caring", "thoughtful". They admit "he has flaws" but he "will help if you need him" and "will stand up for those he cares about". It's nice to see him getting some love!
Devil cutie Mimi ends up as a close second with only a few votes of difference, at 8.1%. She is "cute", "badass", and "so cool". Many people wrote they don't usually romance female Lis but they chose her nonetheless because she is "a great LI in every way". Someone wishes RC would "flesh her out a little more" and "give her more screen time". Third spot is for Dino: a "sweetheart" and "the cutest man in the game".
Jake from WP nabs fourth place with the 4.9% of votes. Players thinks the focus is too much on how hard he is to pursue, while "he is totally worth it", because after the initial coldness he becomes "sweet", "kind" and "caring". His "love for his family is another big plus", and he is always "supportive", "mature", "loyal" and "intense". Someone also wrote that "his sex scenes are amazing".
Gorgeous dancer Carlos from SBR is in fifth place: he is described as "cute", "great personality", "respectful" and "the sweetest". One to watch for sure! Prince Leonard (Q30) ties with Claire (SBR) in sixth place. Leonard is "complicated", "interesting" and "clever", while Claire is "sweet", "mature" and "loyal". Seventh position is for Michael (SOS) - "cute", "affectionate", "funny" - and Kayla (WP) who's "really nice" and "one of the first female LIs that didn't seem like a complete afterthought".
Eight place goes to Sam (CY) - "wholesome", "the right amount of naughty and nice", "a sweet and likeable guy" - in a tie with Chris (SIF) - "funny", "strong", "loyal", "always has your back". Ninth place is another tie between Sebastian (SIF) - "sweet" and "supportive" - and Alex (MHS) - "amazing personality", "really helpful".
Last but not least the tenth place is a foursome: William (SIF) gets some love for being "good", "solid", "loyal" and "fun", in a tie with Charles (SBR) - described as "perfect", "romantic" and "caring", as well as "hot", "sexy" and "gentle" - Jackie (SIF) - "an under-appreciated king", "handsome" and "fun", and Frances (MB) - a "real badass" and "one of the best LIs in MB".
So, time to replay your favourite book and try out one of these Lis instead than your usual one!
----

💎Question 6: If you could eat or drink one thing from the RC universe, what would you choose?

https://preview.redd.it/q1oepb874y951.png?width=1108&format=png&auto=webp&s=fbd376a81dffac4123ffdfd8963ef87164466f35
Max (MB) might no longer hold the crown of most loved LI in the game, but his cooking skills still hold strong. A whopping 37.2% of the people in this community would eat anything he prepares. Getting drunk on Glyft at the HS Academy takes second spot with 23.1% of the preferences, while a sugar rush after a light BDSM session in CY is all what the 13.2% of us want, completing this delicious podium.
In fourth place is pizza with a bunch of MHS friends, fifth is potential death - as long as ice cream and Jake from WP are involved - and sixth is Anthony Wood's juice at one of his epic MHS parties.
Dinner at the SOS circus is seventh, chosen by a fearless 3% of the community, while canapés at a jewellery fashion show in Q30 score the eighth and last place.
----

💎Question 7: If you could spend a weekend in any RC story, would you:

https://preview.redd.it/0nxu9upf4y951.png?width=680&format=png&auto=webp&s=2cbcbded6cb23da8f9f16e96e7cd65be46dee8fd
An entire weekend in the RC universe! What mischief is our community planning to get up to?
It looks like HS is once again top of the list, with over 38% of players willing to test their wings and get some strange and possibly corrosive blue liquid down their unclaimed throats. But LOW's gorgeous backgrounds and atmospheric setting have convinced the 16% of us to go explore a Japanese village, and possibly meet some mysterious cutie. Adelaide and her SIF crew navigate steadily in third place: 10.7% of us would follow them over the edge of the world and beyond.
In fourth place is a spot of murder mystery fun in CY, as 10.3% of us would happily explore a British family mansion - bloodshed possible but not guaranteed. A diplomatic trip with the Q30 Sagar Royal Court appeals to the 6.1% of us, especially if a romantic sunset is on the bill. The quaint and frankly unsettling SOS woods do not scare the 5.7% of us, but as long as no one picks up a nice bouquet of flowers, we should all be ok. In seventh place is our favourite vampire popstar Benny Bart (MB) performing at the Taste of the Night, while eighth is a dance marathon in SBR, inclusive of a trip to romantic Paris. Tarino's somewhat unusual directorial skills in MHS score ninth place, while hot surfers in WP's Miami end up last.
----

💎Question 8: If you could get more episodes of a series that has now ended, which one would you choose?

https://preview.redd.it/qts8kk8i9y951.png?width=766&format=png&auto=webp&s=2b7135c2692b604dd9c9ad4b14bafa93cd4ecad0
It's time to go down memory lane! We loved all the stories that RC has now completed, but which one we miss the most?
Side note: SIF and WP were still ongoing when this survey was first opened hence they are not featured in this list.
Horror story SOS takes a clear lead, with over 47% of our community wishing we could get more adventures with MC and her friends. MB is second, with a healthy 34% of readers wishing to spend more time in the company of vampires and werewolves. Q30 is third, with 13.3% of readers missing its Royal Palace and all the intrigue coming with it, and last but not least is comedy MHS, which is missed by 5.4% of this community.
----
And now, some questions about this community's gaming habits:
----

💎Question 9: How do you usually approach LI relationships?

https://preview.redd.it/v31scb2y4y951.png?width=834&format=png&auto=webp&s=6aa1f057936a83909a229f610e50e4a43b17f0d1
This question had a fairly split response between those who date a few LIs but ultimately choose only one (48.9%) and those who are fiercely monogamous from the start (42.4%). A healthy 8.7% of the readers prefer instead to play the field and date as many LIs as the gameplay will allow. And with so many great characters to choose from, that's hardly a surprise!
----

💎Question 10: Would you play a book that has a male MC?

https://preview.redd.it/w15bvu885y951.png?width=826&format=png&auto=webp&s=b748f781448de34a98795a11470adc1e2dfe7129
We all know that at the moment all RC stories are gender-locked with a female MC. But what does the community think? Would we play a book with a male MC? The majority is in favour, with 61.9% of the responders answering with a resounding YES.
----

💎Question 11: Do you use the RC wiki on Fandom?

https://preview.redd.it/j3bxwpgh5y951.png?width=777&format=png&auto=webp&s=97b8b0713957bf5ff133710b8cb1727411ec87c2
Our amazing fan-written Romance Club wiki recently celebrated 100 pages!
It sounds like a whopping 78.8% of this community uses the wiki, while about 14.1% did not know it existed (so we hope you are using it now!) and 7.1% are true daredevils who play without any wiki help.
----

💎Question 12: What genre of story do you enjoy the most?

https://preview.redd.it/9ht7sl4u5y951.png?width=908&format=png&auto=webp&s=834f8b8a3f6a0c9465a3b9e74d5a3f70dfe77b9c
With new stories always coming up, we were curious to know which genres this community enjoys the most.
Despite the game being called Romance Club, the top of the genre ranking goes to Fantasy, with a striking 74.1% of preferences. But no worries: Romance is a steady second with a great 70.8% of the votes. Third place goes to Mystery with 65.7%.
Adventure comes fourth with 55.2%, followed by Horror (42.5%), Historical (35.1%), Science Fiction (29.1%) and finally Comedy (26.4%).
A very small number of people (too little to make percentage) also asked for drama, thriller, detective/crime, heist/spy, high school/teens, superheroes, zombies and time travel. All great ideas!
The community has spoken though: RC, give us elves and gnomes and medieval tales of debauchery and magic!
----

💎Question 13: How long have you been playing Romance Club for?

https://preview.redd.it/irpho4w06y951.png?width=832&format=png&auto=webp&s=2f4cfd29dd89db03bfc910a5355ad8d47844668e
We were curious to know for how long we all have been playing this game we love. The survey showed a good mix of old and new readers, with a clear tendency towards long-term reading, which makes us so very happy to know we are all just equally addicted.
36% stated that they have been playing for over a year, 23.6% for more than six months, 17.8% for more than three months, 16.1% for more than one month and 6.4% for less than a month. Welcome one and all, we hope you are all going to be here for the long haul!
----

💎Question 14: How did you find out about the game Romance Club?

https://preview.redd.it/3rcvli496y951.png?width=745&format=png&auto=webp&s=c48166ce7feee6ee5dab1c00fac3ea6dd3ab43ff
The main way in which our community has found out about RC is through the app store/google play store (70.9%). Another subreddit is a source for 13.5% of us (we probably have to say thank you to our friends at Lovestruck and Choices!) while a friend recommended the game to 8.7% of us.
Instagram (3%) and Facebook (1.5%) are also popular sources, but 2.4% of us arrived to the game through adverts, which is to us the most interesting data since in the mod team we haven't personally seen any adverts for this game - ever - so if anyone has screenshots, please post them in the comments, we are super curious!
Some users (too few to make percentage) also mentioned videos and memes on TikTok or Youtube, Google Search, Tumblr, Twitter, Vkontakte or even their own sister(s) as a source.
----

💎Question 15: Which operating system do you play the game on?

https://preview.redd.it/j6zb31bg6y951.png?width=772&format=png&auto=webp&s=be90706aaa9835b173355c50388a6c5197ac786b
The majority of this community plays on Android (57.7%) while 42.3% play on iOS.
----

💎Question 16: Which other story games do you play?

https://preview.redd.it/pcyngwew6y951.png?width=807&format=png&auto=webp&s=1e3f1f4956dfb8bc4e247d6a179a4153b62fc7da
Here are the top-10 story app games we play in this community, aside from RC.
Unsurprisingly, market leader Choices comes first with 53.3% of the votes. Another giant in the field, Episodes, comes second - although with quite a substantially smaller percentage of votes, clocking at 28.1%. The top-three is completed by UK TV show-inspired Love Island with the 24.6%.
Chapters is the fourth most played game at 24.2%, followed by Lovestruck and Love Sick - tied at 16.1%. Moments is sixth at 13.1%, new entry on the market Stories: Love and choices follows in seventh with 5.3%, Journeys is eighth with 4.7% and The Arcana is ninth with 2.6%. The top-ten is completed by Tabou Stories: Love Episodes in a tie with Originals - both at 1.2%.
Some also reminisced about Storyscapes (gone too soon but not forgotten!) and many other game apps were mentioned but by too few people to make up for an accountable percentage. We surely discovered some games we had never heard of before, though, including: Fictif, Heart's Choice, Everlasting Summer, Fancy Love, Romance: Stories and choices, Secrets: Game of choices, Fictions: Choose your emotions, Mystic Messenger, City of Love and many, many more... so thanks everyone for all these new suggestions!
And to that one person who selected half a dozen games and then commented with "it is a problem!" ... trust us, you are in very, very good company here!!
----
And lastly, some demographics:
----

💎Question 17: Where in the world are you from?

https://preview.redd.it/wi54oynj7y951.png?width=742&format=png&auto=webp&s=67fd4ef85a56518876e64f5f1e35d704dc5d241a
We are a very international bunch, that's for sure! Here are the numbers:
45.5% of this community lives in Europe, 24.3% in North America, 16.9% is in Asia, 5.7% is in Central/South America, 5.3% is in Africa and 2.3% is in Australia/New Zealand. Welcome one and all! We are so happy you are here.
----

💎Question 18: How old are you?

https://preview.redd.it/hgiuu3dq7y951.png?width=785&format=png&auto=webp&s=106185756ec1cfd67c4c1bb94a8bda1ce6f5a6d3
How old are we? The survey has spoken: 44.7% is between the ages of 18 and 24; 28.1% is between 25 and 35; 21.1% is 17 or younger; 6.1 % is 36 or older.
We must admit that we did not expect so many people to be on the younger end of the spectrum! But we hope everyone - of all ages - will always find this subreddit to be a safe, welcoming and friendly place where to discuss this game we all love. We mods work hard every day to keep this the most relaxed and fun RC space on the net and we feel so lucky that you are all as awesome as you are!
----

💎Question 19: What is your gender identity?

https://preview.redd.it/kkr5bm1x7y951.png?width=810&format=png&auto=webp&s=90068fd1b9c2762f5b181b56af647848529c14e2
The overwhelming majority of this community (93.5%) identifies as female, while 4.6% identifies as male, 1.3% is non-binary, 0,4% identifies as genderqueer and 0.2% marked themselves as confused.
The fact that MC is gender-locked female and that LGBTQ routes are limited in the game is certainly one of the reasons why our community is not more diverse. Hopefully RC will expand their stories to include more diverse gender choices in terms of MCs and LIs, so to allow more people to enjoy their great storytelling skills.
----

💎Question 20: What is your sexual orientation?

https://preview.redd.it/iskgfuk38y951.png?width=749&format=png&auto=webp&s=0d0cd01d9bedfb1f577206939bc22b959bc6921e
Here's the sexual orientation of our community:
70.1% identifies as Straight/Heterosexual
22.5% identifies as Bisexual
1.9% identifies as Lesbian/WLW
1.7% identifies as Pansexual
1.5% identifies as Gay/MLM
0.4% identifies as Aromantic
0.3% identifies as Aromantic/Bisexual
0.3% identifies as Asexual
0.3% identifies as Demisexual
0.2% identifies as Asexual/Biromantic
0.2% identifies as Asexual/Heterosexual
Once again, we hope that future plots featuring more diverse MC/LIs will attract more diverse players to our community.
----
That's all folks! We hope you found these results interesting and we look forward to a new survey once we hit 5000 users! Until then... happy gaming and thanks for making this awesome community as great as it is! :)
💎 RomanceClub mods 💎
💎u/LauraVi 💎u/swankytutu 💎u/directormmn
💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎💎
submitted by LauraVi to RomanceClub [link] [comments]

2 months back at trading (update) and some new questions

Hi all, I posted a thread back a few months ago when I started getting seriously back into trading after 20 years away. I thought I'd post an update with some notes on how I'm progressing. I like to type, so settle in. Maybe it'll help new traders who are exactly where I was 2 months ago, I dunno. Or maybe you'll wonder why you spent 3 minutes reading this. Risk/reward, yo.
I'm trading 5k on TastyWorks. I'm a newcomer to theta positive strategies and have done about two thirds of my overall trades in this style. However, most of my experience in trading in the past has been intraday timeframe oriented chart reading and momentum stuff. I learned almost everything "new" that I'm doing from TastyTrade, /options, /thetagang, and Option Alpha. I've enjoyed the material coming from esinvests YouTube channel quite a bit as well. The theta gang type strategies I've done have been almost entirely around binary event IV contraction (mostly earnings, but not always) and in most cases, capped to about $250 in risk per position.
The raw numbers:
Net PnL : +247
Commissions paid: -155
Fees: -42
Right away what jumps out is something that was indicated by realdeal43 and PapaCharlie9 in my previous thread. This is a tough, grindy way to trade a small account. It reminds me a little bit of when I was rising through the stakes in online poker, playing $2/4 limit holdem. Even if you're a profitable player in that game, beating the rake over the long term is very, very hard. Here, over 3 months of trading a conservative style with mostly defined risk strategies, my commissions are roughly equal to my net PnL. That is just insane, and I don't even think I've been overtrading.
55 trades total, win rate of 60%
22 neutral / other trades
Biggest wins:
Biggest losses:
This is pretty much where I expected to be while learning a bunch of new trading techniques. And no, this is not a large sample size so I have no idea whether or not I can be profitable trading this way (yet). I am heartened by the fact that I seem to be hitting my earnings trades and selling quick spikes in IV (like weed cures Corona day). I'm disheartened that I've went against my principles several times, holding trades for longer than I originally intended, or letting losses mount, believing that I could roll or manage my way out of trouble.
I still feel like I am going against my nature to some degree. My trading in years past was scalping oriented and simple. I was taught that a good trade was right almost immediately. If it went against me, I'd cut it immediately and look for a better entry. This is absolutely nothing like that. A good trade may take weeks to develop. It's been really hard for me to sit through the troughs and it's been even harder to watch an okay profit get taken out by a big swing in delta. Part of me wonders if I am cut out for this style at all and if I shouldn't just take my 5k and start trading micro futures. But that's a different post...
I'll share a couple of my meager learnings:


My new questions :

That's enough of this wall of text for now. If you made it this far, I salute you, because this shit was even longer than my last post.
submitted by bogglor to options [link] [comments]

Classified: Compiled Intelligence On the Lost Dolls Reclaimer Faction (OC Reclaimer Faction)

Condensed intelligence overview detailing currently known information on the Reclaimer faction known as ‘Lost Dolls.’ Information contained therein has been compiled by Sky Union Intelligence Officer ‘MB.’
Sources consist largely of Sky Union’s own records, as well as shared intelligence reports on the matter, compiled battle data, and found footage shared by Orbital. MB was also able to covertly interview the pilot ‘Port’ directly, though it’s believed that she understood the general purpose of MB’s questioning, and so her testimony must be accepted with a degree of scrutiny.
OVERVIEW
Unit Name: Lost Dolls
“Bringing you the bleeding edge of technology from thirty years ago, today. Let’s get started.”
-MB, initial debriefing.
Time of Operation: Officially, only four hundred and seventy three days. Compiled intelligence suggests that the group has been active in the Oval Link for far longer, with upward estimates reaching as high as twenty years. At the very least, all members were alive at the time of the Moonfall.
Pilots: Five
Affiliations: No known Consortium ties. Joint operations alongside other Reclaimer factions are uncommon, though Steel Knights show up most often with Bullet Works and Immortal Innocence tied for a distant second.
Preferred Mission Profile: Lost Dolls’ mission profile trends toward humanitarian missions. Primarily defensive or retributive actions against Corrupted A.I. incursions, particularly those concerning civilian populations within the Oval Link. It’s generally accepted that this is one of the primary factors contributing to their work alongside Steel Knights.
They are less likely than average to pursue high-risk, high-payout missions such as deep-dives into A.I. territory or the escort of VIPs, such as political or military personnel, out of high risk areas. Conversely, they are more likely to take on high-risk missions with lower pay, such as escorting civilian evacuation caravans in the event of a Corrupted A.I. incursion. This behavior matches with the Dolls’ preference for humanitarian work, as missions fitting these criteria tend to be posted by lower level governmental officials, or even civilians with pooled resources, who have come under sudden attack.
Quirks: All five pilots typically show to missions, in violation of the four-per-squad standard. Normally this would be in violation of the Consortium Treaty, but so far Orbital has refused to take action. It is theorized that this is due to the Dolls’ reluctance to hit military targets, and that Orbital may be letting the behavior slide in the interest of protecting civilian lives.
The Dolls have no known home base. Port has made reference to a ‘bus’ in interviews that she says they use for field repair and transportation; it’s possible she’s referring to an old rapid deployment Arsenal carrier like the ones that were used before the Consortiums established proper infrastructure in the Oval Link, but it’s hard to say where a group like the Dolls could have found an operational one, much less one capable of fielding five arsenals. It’s almost more likely that they actually have two, puttering somewhere around the Neutral Zone. Even that’s a hard pill to swallow, since the old carriers have been out of production for almost thirty years now.
Very little of the Dolls’ equipment is up-to-date. Their plugsuits are all defunct prototype models and in varying states of disrepair; most of their pilots don’t even use the actual connections in the suits themselves, opting instead for permanent ports connecting directly to their nervous systems. I’ve never seen any of them sporting a Blitz, either. At least one, Port, has been observed with what appears to be a traditional slug-throwing sidearm.
The Lost Dolls claim to be a family unit of five sisters. The physical differences between them would imply that this is in a purely symbolic manner (excepting Protoca and Hope. Possibly Port if our facial analysis data is reliable), but the effect is the same. Their loyalty to each other is hard to call into question.
Every one of their pilots has had their age frozen by Outer Syndrome.
It should be noted that all pilots, excepting Earwax, have pilot rankings that do not properly reflect their overall level of competency. The Dolls’ propensity for low-sensitivity missions and unwillingness to work closely to further any Consortium goals aside from preservation of human life has left them low on the leaderboard. In cases where this information is used for planning operations against or alongside the Lost Dolls, assume all pilots are at the level of A rank or higher.
PILOTS/MECHS
“I’ll start off with saying that the Dolls have the most ‘ware I’ve ever seen packed into a unit of this size. Two pilots are almost entirely cybernetic. And I do mean entirely.”
-MB
Callsign: Tachi
Real Name: Tachi Hanamura
Age: Unknown. Appears to be in her late teens.
Height: 197cm outside of Arsenal, 76cm while embarked, 167cm when utilizing her ‘emergency legs.’
Rank: C
Handed: Both
Family: Four sisters
Outer Ability: Unknown. Though she is remarkably receptive to cybernetic augmentations and displays an unusual level of synchronicity with her Arsenal, hovering at anywhere between 91% and 95% at any time.
Piloting Tendences: Aggressive. Highly aggressive. Tachi’s typical M.O. involves charging directly into an enemy formation and smashing the thing to bits before moving onto the next cluster. She often acts as the Dolls’ line breaker and attack dog, flushing high priority targets out of the press or just bowling down the chaff so that the other pilots can focus on more important things.
“The armor is 600mm of over a dozen different laminates and they didn’t include a single thermal dispersion layer for laser fire...”
-Tachi, picking over the husk of a disabled Genbu
Physical Description: Where to start? First, brown hair, cropped into a messy bowl cut. Wide build for a girl. Her entire right arm is cybernetic. Her torso ends above her hips, which have been replaced by a massive version of the nerve-interface hubs found on standard plugsuits. Outside of her Arsenal this is plugged into the top of a massive set of ‘spider legs,’ complete with abdomen, which she uses as her normal mode of transport. When embarked on a mission, she’s lifted off her leg hub and simply plugged into a custom seat in her Arsenal, with a secondary connection at the base of her neck; the normal shoulder connections aren’t used.
The arm and leg hub don’t match any known manufacturer of prosthetics, and the connection format at her hip is dated by at least a full twenty years. A pair of more modern legs are integrated into her piloting seat and act as part of her ejection system should her Arsenal be put out of commission in the middle of combat.
She has a set of rocket thrusters implanted into her back. Actual rocket thrusters; the vents are mostly flush with her shoulder blades, protruding perhaps 5-6cm. Footage loaned from Orbital demonstrates her leaping almost one hundred meters utilizing them while under full load (read: attached to the massive spider leg assembly). Using her Arsenal ejection system, combined with the lighter weight of her backup legs, it’s estimated she could travel as far as three hundred meters on a burst from the thrusters.
Arsenal: Arachne
Weapon Compliment:
Arsenal Characteristics: Beat half to death and heavy.
Arachne’s one of the two Arsenals in the Dolls’ employ that we have a decent technical read on, mostly because Tachi’s a shameless showboat and likes to show off all the tinkering she’s done on the thing. A decent example of the Dolls’ construction strategy, no two armor components on Arachne are from the same model. The left arm is optimized for melee strikes (both the base model, and the aftermarket modifications that have been made by the pilot) while the right is oriented for handling firearms. The unit is sluggish in the air and has middling mobility on foot for it’s durability; fine enough for Tachi’s preferred method of brawling. Combat footage shows she’s the type of pilot that tries to stay grounded anyway.
Tachi’s normal plan of attack is to get in close and personal with the Raven II and Ohabari and shred whatever’s in front of her. The Reaper II is typically reserved for plinking Strais or aerial targets that have gotten spread out. The Agni Flame appears to be used purely as backup.
Frankly, the Reaper II and Ogre Break II are squandered here. With a maximum lock range of only two hundred and one meters, Arachne is right on the edge of it’s rangeband with the Reaper and hopelessly short of the Ogre. That hasn’t stopped the pilot from eyeballing slower moving AI from farther out, but the Arsenal really shows the slapdash nature of the pilot.
“She doesn’t stop. Not for anything. While pouring over the combat footage I actually stumbled onto a sequence where she took a Failnaught round right through the cockpit and all it did was make her angry.”
-MB.
Callsign: Protoca
Real Name: Protoca [no known surname]
Age: Unknown. Appears to be in her late teens.
Height: 182cm
Rank: B
Handed: Left
Family: Four sisters
Outer Ability: Rapid regeneration from injuries, as well as being prone to physical mutation. She can apparently recover from injuries that even most Outers would find lethal; we have combat footage of an ejected Protoca taking a cannon round to the legs, obliterating everything from her hips downward. I met her face-to-face in my interview with Port and she had made a full recovery, complete with a set of genuine flesh and blood legs. You wouldn’t even know it’d happened.
Her mutations appear to be a side-effect of her regeneration, and do not directly benefit her while piloting outside of her absurd physical strength and enhanced reflexes.
Piloting Tendencies: Measured and deliberate, but outrageously dogged. She keeps a wide engagement profile and usually plays mop-up alongside Port when dealing with traditional corrupted AI forces, otherwise she’s running interference when facing off against Arsenals. She’s particularly skilled at close urban combat and swaps between playing rifleman and melee roles fluidly. She also rarely retreats from engagement, regardless of the tactical situation. On at least one occasion, her Arsenal was reduced down to it’s torso, head, and one leg in an engagement with a hostile Arsenal pilot. Instead of withdrawing, Protoca engaged afterburners and tackled her opponent, which bought enough time for Lost Dolls’ other pilots to reach her position and disable the enemy.
Generally speaking, it seems she simply will not withdraw from an engagement unless one of the other pilots is under direct threat or Port herself calls for an immediate withdrawal.
“You don’t take one step further. Not one.”
-Protoca, staring down three fresh Strais after dispatching their forward wing.
Physical Description: A real mess. For the basics; brown hair, trimmed into an angled bob cut. She’s wide shouldered, but nowhere near as broad as Tachi. Her torso and leg profiles are slim, arguably emaciated. Musculature is extremely visible, as if she’s constantly tensing her entire body with every movement. It’s possible that’s the case, as her movement patterns have a habit of being twitchy and erratic.
As for the aforementioned mutations: her right leg is covered in dark, hard scales. An atrophied wing, like that of a bat, shares a dual joint at the shoulder with her right arm. Numerous scars, some clearly surgical in nature. There’s a kind of plant-like symbiont that wraps around her left arm, up her neck, and ends in her hair, sprouting into a pair of green, bioluminescent flowers; it’s unclear if this is a mutation to her person or if it’s a separate entity.
A note about the wing and scales: they’re proofed against small arms. How Protoca’s body is able to produce organic compounds capable of standing up to Femto weaponry is currently a subject of heated debate in R&D’s breakroom. I’m sure more than a few whiteboards have been broken over it, considering how loud they get.
Arsenal: One More
Weapon Compliment:
  • OAW-P54 Aegis
  • OAW-BL74 Cronus Break
  • SAW-RP90F Splendor
  • HAW-CF22 Chaff Flare
  • HAW-R26F Guilty Throne
  • HAW-L05F Stargazer
Arsenal Characteristics: One More is the type of Arsenal you could smack upside the head with a Buster Doom and it would ask for seconds.
True, it doesn’t have the bulk of a true heavy-weight, but the chassis itself is strong enough to take a hit and keep on coming and the Splendor repair system means the Arsenal has fantastic staying power over the course of an extended engagement. And the Aegis shield in the off-hand gifts the pilot considerable bulk in the context of a contained duel.
Like Arachne, One More has a lopsided chassis with a horrendously overengineered sword arm while the other is optimized for handling firearms. Unlike Arachne, One More has access to a far more advanced set of weaponry. Between the Guilty Throne, Aegis, Cronus Break, and Stargazer, Protoca is running a veritable buffet of high performance, low availability equipment. The manufacturers of the Cronus Break and Aegis models aren’t even public knowledge, so it’s an open question where the Dolls could have procured such serious tech with their relatively bare income and (reportedly) spartan operational facilities.
Operationally, One More often acts as the anvil to Port and Tachi’s hammer; a hard to remove obstacle for any conventional AI force and a dogged pursuer for most arsenal-based forces.
“The team’s tactical leader and designated marksman. Methodical, cordial, and a complete horror show like all the others.”
-MB
Callsign: Port
Real Name: Samantha Thampson
Age: Unknown. Appears to be in her late teens.
Height: 167cm
Rank: B
Handed: Left
Family: Four sisters.
Outer Ability: Port’s brain is innately capable of understanding binary code which allows her unparalleled levels of synchronicity with her Arsenal, fluctuating between 99%-100%. It also allows her to eschew the traditional connecting ports in her plug suit (which is good, because they’re all visibly broken) and instead opt for a surgically installed plug that connects directly to her brain stem. Connected this way, her Arsenal effectively becomes an extension of her physical body.
This ability also extends to binary converted into other formats other than a direct electrical feed; Port has often been caught having verbal, and apparently quite in-depth, conversations with the AI unit of her Arsenal via the unit’s external audio systems, with bursts of static standing in for the unit's speech. How coherent/intelligent this ‘dialogue’ from the unit is still up in the air, but analysis of the few samples we do have shows definite patterns in the unit’s ‘speech’ and in how it reacts to Port herself.
Piloting Tendencies: Port’s preferred method of engagement appears to be skirmishing at distance; she fits the rifleman archetype to a T. Unlike Protoca, Tachi, and Lily, Port has no measures for melee combat installed on her Arsenal aside from its fists, and even the one shotgun she keeps on the rear pylons is a choked down, longer range model.
Her usual M.O. when deployed amongst her sisters is to hang back behind Tachi or Protoca and plink. Well, ‘plink.’ The DMR and high performance assault rifle she’s managed to scrounge out of the Neutral Zone could blow through a Rebellion’s kneecap with sustained fire, and her sisters are good at giving her the required openings. While going over the combat footage, I saw her put a round down the barrel of a Slay Dog more than once.
“Oh, we’re just a merry little band of misfits, Sergeant. Looking out for each other, trying to make the world a better place. I’m sure you’ve heard the old song and dance.”
-Port, early in her interview with Intelligence Officer MB.
Physical Description: The most immediately striking thing about Port is arguably her albinism; snow white from head to toe except for her eyes, which are pink from lack of pigment. After that might be the fact that she’s a quadruple amputee with a full suite of military grade replacement limbs (or rather, Port claims that they’re military grade). The hardware itself appears very dated, to the point where our intelligence teams have not actually been able to pinpoint a make or model. Aside from being old, they’re clearly several sizes too large for her. Approximating by their overall scale, we estimate they’re intended for an 180cm adult male. The size difference is exaggerated somewhat by the fact that her legs have actually been installed too low, connecting part way down her thighs rather than at the hip. The limbs themselves don’t appear to be anything special; the arms are conventional replacement limbs with a fully articulated wrist, hand, and fingers while the legs are set up for sprinting, the feet having been replaced with a flexible running fin. The legs also boast a pneumatic jumping apparatus on par with modern Outer modifications.
Port has also undergone extensive cranial modifications, some of which she claims she’s performed herself. These include a large radio antenna mounted behind her right ear and connected via ribbon cable to the base of her skull, a set of four high definition cameras implanted into the ridges of her cheekbones, a manually operated combat stimulant pump on the bottom left portion of her skull, and two white ‘dog ears’ surgically implanted over her ear canals (breed and origin undetermined; possibly vat grown and purchased off the black market).
Moving on from augmentations; Port herself is slightly built. Thin frame, long face, little visible muscle to speak of. Her torso is thin enough that it almost appears emaciated, though there’s some contention on whether this is actually due to nutritional deficit or rather a result of further augmentation or Outer Syndrome. She’s covered in scars and has permanent iris damage in her left eye.
Arsenal: B3-206 (though Port often shortens this to ‘Bee’)
Weapon Compliment:
  • SAW-SR53 Beluga Beam
  • Agni Flame M
  • HAW-R26F Guilty Throne
  • HAW-SH35 Hoggish Spriggan
  • HAW-AM01L Scarlet Star
And a reserve magazine for an expanded ammunition compliment.
Arsenal Characteristics: A solid, all around trooper unit.
B3-206 excels in the roles of medium range fire support and skirmisher. Between the Beluga Beam and Scarlet Star, B3-206 has excellent firepower at range to harass hostile targets while the Guilty Throne and M model Agni Flame offer solid mid-range options for when the fighting gets in a little closer. Port appears to keep the Spriggan on hand as a sidearm more than anything else, usually only resorting to it once her other weapons have depleted their ammunition stores.
As for the Arsenal itself, B3-206 is very much a jack of all trades. Construction focuses on striking a balance between durability, maneuverability, and memory capacity with some minor sacrifices to overall firepower. Of particular note are the Arsenal’s arms, the make of which don’t appear in any of our internal records. Construction closely resembles the make of an old, defunct Zen prototype from over twenty years ago but declassified documents suggest that those never made it past the drawing board before the project was canceled; we’re currently doing some more thorough digging to try and figure out where Port may have picked them up but the current theory is that she found a fabricator on the black market who developed the design independently.
As mentioned previously, B3-206 is on recording having apparently complex conversations with Port via audibly broadcast binary noise. We don’t have enough data to synthesize a translation at this time, but the patterns are definite and subtle variations in the machine’s tone do closely mirror subtleties in human speech resulting from shifts in mood. Port herself has been cryptic on the subject but the implications of a sapient AI operating directly under Orbital authority are something the intelligence community is still exploring.
“Arguably the team’s ace pilot, she ties Port and Protoca combined for Arsenal downs. She lags behind in Corrupted AI kills but then, that isn’t her job.”
-MB
Callsign: Lily
Real Name: Liliana [no known surname]
Age: Unknown. Appears to be in her early teens.
Height: 160cm
Rank: A
Handed: Right
Family: Four sisters
Outer Ability: Instantaneous reaction time. She has a true reaction time of 0.00000000 seconds, meaning she is only limited by the inertia of her own body or Arsenal when maneuvering in combat. This has given rise to some truly hair-raising maneuvering from Lily, as she can change her plan of attack at any point for any reason as long as her Arsenal is capable of putting up with the mechanical stress.
Piloting Tendencies: Highly aggressive, arguably moreso than Tachi. Her ability to outthink and out-react even her own teammates mean that Lily is often extending far beyond them before they can even realize it. The good news for her is that the enemy won't realize it either; not until she's put two full magazines from her Silver Raven IIs right into their back, anyway.
“A real firecracker, this one. You wouldn’t guess by how quiet she is off the field.”
-MB
Physical Description: Short, slightly built (though not so much as Port), with the physicality one might expect of a professional dancer. Her hair is sandy brown and kept braided.
Like Port, Lily is highly augmented. Both her legs have been replaced with prosthetics and, like Port, the make and model are unknown. Visually, they resemble Outer-issue dedicated leaping prosthetics in that they taper sharply down to the feet which appear to be a pair of springloaded fins, not dissimilar to Port’s running fins. Her left arm has also been replaced with an arm of a similar make to Port’s, though it’s not identical. It’s detachable, with the shoulder socket doubling as Lily’s primary connection port while embarked in the Rabbit.
Also like Port, she has a pair of animal ears implanted into her head, though in this case they are in addition to her normal ones as opposed to replacing them; they’re a pair of large rabbit ears matching her hair color.
Some miscellaneous notes: Lily is completely mute. She communicates primarily through a form of one-handed sign language, heavily favoring her right hand. Per Port, all pilots in the unit are fluent enough to understand the broad strokes of whatever it is Lily is signing but only Tachi has put in the time to learn the language properly. Her and Lily will sometimes utilize it to have private conversations. In the field she gets by with a limited set of synthesized voice commands that Port has uploaded into a soundboard in her cockpit.
Lily is also quite near-sighted. A rare condition for an Outer, let alone an Arsenal pilot. She can commonly be found sporting a pair of cokebottle glasses when not in her Arsenal.
Arsenal: Red Rabbit
Weapon Compliment:
  • HAW-M05 Silver Raven II x 2
  • SAW-EB10 Prominence
  • SAW-EB10L Prominence
  • SAW-RP95 Devotion
  • HAW-CS09 Cooling System
Arsenal Characteristics: Red Rabbit is what most experienced Arsenal pilots would describe as ‘selfish.’
Even as part of a cohesive unit, Red Rabbit’s role typically involves acting alone, striking forward ahead of the advancing unit or around the opposition’s flank to pick out high priority targets before the enemy can properly react. Where Arachne’s application is as a blunt instrument, Red Rabbit is a dagger sinking into the enemy’s unguarded flank. Hot shots flock to these sorts of machines because it means they get to wrack up the killmarks, though Lily doesn't seem the type to keep score.
About every aspect of Red Rabbit’s handling characteristics have been redlined for the sake of keeping up with its daring pilot. It’s bleeding fast, turns on a dime, and is practically air-weight as far as Arsenals are concerned. This also means it’s exceptionally fragile but, with Lily at the helm, it’s rare for the Rabbit to incur significant battle damage at all.
A minor note: Red Rabbit is the only Arsenal in the unit to use an after-market body kit. This has made visually identifying the make and model essentially impossible. Femto expulsion readings and in-depth handling analyses have been carried out by our boys in the Intelligence office but I can only speculate as to their conclusion, as the particular details haven’t been cleared for my viewing. I hear it made some of the higher ups break into a cold sweat, for whatever that’s worth.
“Cute kid. Not really sure what she’s doing hanging out in a Reclaimer unit, shy as she is.”
-MB
Callsign: Earwax
Real Name: Hope [no known surname]
Age: Unknown. Her age was frozen while quite young; appears to be about nine or ten.
Height: 121cm
Rank: E
Handed: Right
Family: Four sisters
Outer Ability: Currently unknown. Port has hinted that she might have empathic capabilities.
Piloting Tendencies: Earwax is the team’s high altitude reconnaissance and communications expert. She spends every moment of flight time high over the battlefield, coordinating the other pilots and keeping a bird’s eye view of the battle. There is no known record of Earwax engaging in combat directly.
“Don’t call me that! Ugh. I asked Port not to make that my nickname . . .”
-Earwax apparently doesn’t like her callsign.
Physical Description: The spitting image of Protoca, if Protca were seven years younger and lacking mutations. Going theory in the intelligence circuit is that Earwax and Protoca are twins, with Earwax contracting Outer Syndrome at an earlier date than her sister. Sadly, at this stage all we have is conjecture.
Notable visual distinctions between the two, aside from height, mostly come down to personal style. Earwax wears her hair longer and is more likely to wear ornaments such as hair clips or bands. She is also the team’s only member to be commonly found in civilian clothing, with a penchant for ribbons and frilly dresses. All told, Earwax is almost aggressively ‘normal’ in contrast with the rest of her team, wholly lacking her sister’s enhanced musculature as well as any cybernetic augmentation.
Arsenal: Eden
Weapon Compliment: A single HAW-H05L Trickster and all the sensor equipment you can reasonably jam into the torso chassis.
Arsenal Characteristics: Eden is the Dolls’ high altitude recon and overwatch unit.
Just about every spare or redundant part has been pulled off the frame in favor of saving weight and increasing the maximum operational ceiling of the unit well beyond standard combat load parameters. As a result, Eden is capable of operating above an AO almost indefinitely, feeding the team’s other pilots a steady stream of intel while high and away from any real danger.
Frankly, there isn’t much more to say on the subject. Eden is so pared down that it’s barely more than a trainer unit with a bunch of sensors strapped to the hood. Which is good, because Hope has none of the typical neural implants that normally facilitate handling Arsenal movement, nor any secondary method of connection like most of her sisters. She flies almost purely by instruments.
There isn’t even much evidence to suggest she’s ever fired her Trickster, which is meant as a last resort defensive measure in case something gets by the defensive screen formed by the rest of the unit. There have been all of five occasions where her Arsenal was purposefully pursued by enemy contacts and, the three times they got away from Lily, said contacts burned their own engines out while trying to exceed their operational ceiling.
Closing Statement: The Lost Dolls represent a valuable asset in the fight against the Corrupted AI in that they are a reliable and high-uptime asset dedicated to safeguarding vulnerable towns and cities across the Oval Link. That said, they show no interest in working closely with any Consortium; at this time it is my estimation that we would only ever look to the Lost Dolls as a stabilizing measure in the event of a crisis, rather than a resource to exploit proactively.
If you made it this far, thanks for reading over my post. And thanks to u/Muteki_____ for translating DxM's supplementary materials and ultimately giving me the idea for this writeup.
I sure hope the formatting doesn't break.
submitted by o0m-9 to DaemonXMachina [link] [comments]

Unusually high CPU and GPU usage on YouTube (Firefox Nightly)

TLDR: So the fix for this, in my instance, was two parts. First was to install new drivers onto my computer. Second, and probably something I should have noticed myself, is that I should have set YouTube not to stream at 4K. Not terribly shocking to need 4x the GPU when processing 4x the data for an image compared to 720p
Hi all,
So, a few days ago I noticed that Firefox was using way more CPU and GPU resources on YouTube especially. On the same video, Vivaldi's GPU usage would hit about 8% then hover at 2.5% or so. Firefox would go to about 20%, and hover at about 5-10%. I wasn't entirely sure as to why this is happening. I tried turning off Hardware Acceleration, which didn't seem to do anything.
I used this video from Engineering Explained where Firefox's GPU usage was always over 20% in the first minute, while Vivaldi peaked at 15% for a moment, then went back down to 2.5%.
Hardware Specs: Intel i7-8705G 16GB RAM 512GB NVMe SSD Intel HD 630 (This is the GPU that gets used by Firefox) Radeon RX Vega M GL
Let me know if there's anything else I can provide!
Edit: Here is the about:support from my browser. I should note that I did try to remedy the issue by turning all add ons off, but that didn't do anything either.

Application Basics

Name: Firefox Version: 78.0a1 Build ID: 20200526213752 Distribution ID: Update Channel: nightly User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0 OS: Windows_NT 10.0 Launcher Process: Enabled Multiprocess Windows: 1/1 Enabled by default Remote Processes: 18 Enterprise Policies: Inactive Google Location Service Key: Found Google Safebrowsing Key: Found Mozilla Location Service Key: Found Safe Mode: false

Crash Reports for the Last 3 Days

Nightly Features

Name: DoH Roll-Out Version: 1.3.0 ID: [email protected]
Name: Firefox Screenshots Version: 39.0.0 ID: [email protected]
Name: Form Autofill Version: 1.0 ID: [email protected]
Name: Web Compat Version: 11.0.0 ID: [email protected]
Name: WebCompat Reporter Version: 1.3.0 ID: [email protected]

Remote Processes

Type: Web Content Count: 1 / 8
Type: Isolated Web Content Count: 13
Type: Extension Count: 1
Type: Privileged About Count: 1
Type: GPU Count: 1
Type: Socket Count: 1

Extensions

Name: Amazon.com Version: 1.1 Enabled: true ID: [email protected]
Name: Bing Version: 1.1 Enabled: true ID: [email protected]
Name: DuckDuckGo Version: 1.0 Enabled: true ID: [email protected]
Name: eBay Version: 1.0 Enabled: true ID: [email protected]
Name: Google Version: 1.0 Enabled: true ID: [email protected]
Name: Grammarly for Firefox Version: 8.863.0 Enabled: true ID: [email protected]
Name: Honey Version: 12.1.1 Enabled: true ID: [email protected]
Name: HTTPS Everywhere Version: 2020.5.20 Enabled: true ID: [email protected]
Name: Twitter Version: 1.0 Enabled: true ID: [email protected]
Name: uBlock Origin Version: 1.27.6 Enabled: true ID: [email protected]
Name: Wikipedia (en) Version: 1.0 Enabled: true ID: [email protected]

Security Software

Type: Windows Defender Antivirus
Type: Windows Defender Antivirus
Type: Windows Firewall

Graphics

Features Compositing: WebRender Asynchronous Pan/Zoom: wheel input enabled; touch input enabled; scrollbar drag enabled; keyboard enabled; autoscroll enabled WebGL 1 Driver WSI Info: EGL_VENDOR: Google Inc. (adapter LUID: 000000000001278e) EGL_VERSION: 1.4 (ANGLE 2.1.0.eabf2a79aac3) EGL_EXTENSIONS: EGL_EXT_create_context_robustness EGL_ANGLE_d3d_share_handle_client_buffer EGL_ANGLE_d3d_texture_client_buffer EGL_ANGLE_surface_d3d_texture_2d_share_handle EGL_ANGLE_query_surface_pointer EGL_ANGLE_window_fixed_size EGL_ANGLE_keyed_mutex EGL_ANGLE_surface_orientation EGL_ANGLE_direct_composition EGL_NV_post_sub_buffer EGL_KHR_create_context EGL_EXT_device_query EGL_KHR_image EGL_KHR_image_base EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_get_all_proc_addresses EGL_KHR_stream EGL_KHR_stream_consumer_gltexture EGL_NV_stream_consumer_gltexture_yuv EGL_ANGLE_flexible_surface_compatibility EGL_ANGLE_stream_producer_d3d_texture EGL_ANGLE_create_context_webgl_compatibility EGL_CHROMIUM_create_context_bind_generates_resource EGL_CHROMIUM_sync_control EGL_EXT_pixel_format_float EGL_KHR_surfaceless_context EGL_ANGLE_display_texture_share_group EGL_ANGLE_create_context_client_arrays EGL_ANGLE_program_cache_control EGL_ANGLE_robust_resource_initialization EGL_ANGLE_create_context_extensions_enabled EGL_ANDROID_blob_cache EGL_ANDROID_recordable EGL_ANGLE_image_d3d11_texture EGL_ANGLE_create_context_backwards_compatible EGL_EXTENSIONS(nullptr): EGL_EXT_client_extensions EGL_EXT_platform_base EGL_EXT_platform_device EGL_ANGLE_platform_angle EGL_ANGLE_platform_angle_d3d EGL_ANGLE_device_creation EGL_ANGLE_device_creation_d3d11 EGL_ANGLE_experimental_present_path EGL_KHR_client_get_all_proc_addresses EGL_KHR_debug EGL_ANGLE_explicit_context EGL_ANGLE_feature_control WebGL 1 Driver Renderer: Google Inc. -- ANGLE (Intel(R) HD Graphics 630 Direct3D11 vs_5_0 ps_5_0) WebGL 1 Driver Version: OpenGL ES 2.0.0 (ANGLE 2.1.0.eabf2a79aac3) WebGL 1 Driver Extensions: GL_ANGLE_client_arrays GL_ANGLE_depth_texture GL_ANGLE_explicit_context GL_ANGLE_explicit_context_gles1 GL_ANGLE_framebuffer_blit GL_ANGLE_framebuffer_multisample GL_ANGLE_instanced_arrays GL_ANGLE_lossy_etc_decode GL_ANGLE_memory_size GL_ANGLE_multi_draw GL_ANGLE_multiview_multisample GL_ANGLE_pack_reverse_row_order GL_ANGLE_program_cache_control GL_ANGLE_provoking_vertex GL_ANGLE_request_extension GL_ANGLE_robust_client_memory GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_ANGLE_texture_usage GL_ANGLE_translated_shader_source GL_CHROMIUM_bind_generates_resource GL_CHROMIUM_bind_uniform_location GL_CHROMIUM_color_buffer_float_rgb GL_CHROMIUM_color_buffer_float_rgba GL_CHROMIUM_copy_compressed_texture GL_CHROMIUM_copy_texture GL_CHROMIUM_lose_context GL_CHROMIUM_sync_query GL_EXT_blend_func_extended GL_EXT_blend_minmax GL_EXT_color_buffer_half_float GL_EXT_debug_marker GL_EXT_discard_framebuffer GL_EXT_disjoint_timer_query GL_EXT_draw_buffers GL_EXT_float_blend GL_EXT_frag_depth GL_EXT_instanced_arrays GL_EXT_map_buffer_range GL_EXT_occlusion_query_boolean GL_EXT_read_format_bgra GL_EXT_robustness GL_EXT_sRGB GL_EXT_shader_texture_lod GL_EXT_texture_compression_bptc GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc_srgb GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_EXT_texture_rg GL_EXT_texture_storage GL_EXT_unpack_subimage GL_KHR_debug GL_KHR_parallel_shader_compile GL_KHR_robust_buffer_access_behavior GL_NV_EGL_stream_consumer_external GL_NV_fence GL_NV_pack_subimage GL_NV_pixel_buffer_object GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_depth24 GL_OES_depth32 GL_OES_element_index_uint GL_OES_get_program_binary GL_OES_mapbuffer GL_OES_packed_depth_stencil GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_surfaceless_context GL_OES_texture_3D GL_OES_texture_border_clamp GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_array_object OES_compressed_EAC_R11_signed_texture OES_compressed_EAC_R11_unsigned_texture OES_compressed_EAC_RG11_signed_texture OES_compressed_EAC_RG11_unsigned_texture OES_compressed_ETC2_RGB8_texture OES_compressed_ETC2_RGBA8_texture OES_compressed_ETC2_punchthroughA_RGBA8_texture OES_compressed_ETC2_punchthroughA_sRGB8_alpha_texture OES_compressed_ETC2_sRGB8_alpha8_texture OES_compressed_ETC2_sRGB8_texture WebGL 1 Extensions: ANGLE_instanced_arrays EXT_blend_minmax EXT_color_buffer_half_float EXT_float_blend EXT_frag_depth EXT_shader_texture_lod EXT_sRGB EXT_texture_compression_bptc EXT_texture_filter_anisotropic MOZ_debug OES_element_index_uint OES_standard_derivatives OES_texture_float OES_texture_float_linear OES_texture_half_float OES_texture_half_float_linear OES_vertex_array_object WEBGL_color_buffer_float WEBGL_compressed_texture_s3tc WEBGL_compressed_texture_s3tc_srgb WEBGL_debug_renderer_info WEBGL_debug_shaders WEBGL_depth_texture WEBGL_draw_buffers WEBGL_lose_context WebGL 2 Driver WSI Info: EGL_VENDOR: Google Inc. (adapter LUID: 000000000001278e) EGL_VERSION: 1.4 (ANGLE 2.1.0.eabf2a79aac3) EGL_EXTENSIONS: EGL_EXT_create_context_robustness EGL_ANGLE_d3d_share_handle_client_buffer EGL_ANGLE_d3d_texture_client_buffer EGL_ANGLE_surface_d3d_texture_2d_share_handle EGL_ANGLE_query_surface_pointer EGL_ANGLE_window_fixed_size EGL_ANGLE_keyed_mutex EGL_ANGLE_surface_orientation EGL_ANGLE_direct_composition EGL_NV_post_sub_buffer EGL_KHR_create_context EGL_EXT_device_query EGL_KHR_image EGL_KHR_image_base EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_get_all_proc_addresses EGL_KHR_stream EGL_KHR_stream_consumer_gltexture EGL_NV_stream_consumer_gltexture_yuv EGL_ANGLE_flexible_surface_compatibility EGL_ANGLE_stream_producer_d3d_texture EGL_ANGLE_create_context_webgl_compatibility EGL_CHROMIUM_create_context_bind_generates_resource EGL_CHROMIUM_sync_control EGL_EXT_pixel_format_float EGL_KHR_surfaceless_context EGL_ANGLE_display_texture_share_group EGL_ANGLE_create_context_client_arrays EGL_ANGLE_program_cache_control EGL_ANGLE_robust_resource_initialization EGL_ANGLE_create_context_extensions_enabled EGL_ANDROID_blob_cache EGL_ANDROID_recordable EGL_ANGLE_image_d3d11_texture EGL_ANGLE_create_context_backwards_compatible EGL_EXTENSIONS(nullptr): EGL_EXT_client_extensions EGL_EXT_platform_base EGL_EXT_platform_device EGL_ANGLE_platform_angle EGL_ANGLE_platform_angle_d3d EGL_ANGLE_device_creation EGL_ANGLE_device_creation_d3d11 EGL_ANGLE_experimental_present_path EGL_KHR_client_get_all_proc_addresses EGL_KHR_debug EGL_ANGLE_explicit_context EGL_ANGLE_feature_control WebGL 2 Driver Renderer: Google Inc. -- ANGLE (Intel(R) HD Graphics 630 Direct3D11 vs_5_0 ps_5_0) WebGL 2 Driver Version: OpenGL ES 3.0.0 (ANGLE 2.1.0.eabf2a79aac3) WebGL 2 Driver Extensions: GL_ANGLE_client_arrays GL_ANGLE_copy_texture_3d GL_ANGLE_depth_texture GL_ANGLE_explicit_context GL_ANGLE_explicit_context_gles1 GL_ANGLE_framebuffer_blit GL_ANGLE_framebuffer_multisample GL_ANGLE_instanced_arrays GL_ANGLE_lossy_etc_decode GL_ANGLE_memory_size GL_ANGLE_multi_draw GL_ANGLE_multiview_multisample GL_ANGLE_pack_reverse_row_order GL_ANGLE_program_cache_control GL_ANGLE_provoking_vertex GL_ANGLE_request_extension GL_ANGLE_robust_client_memory GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_ANGLE_texture_multisample GL_ANGLE_texture_usage GL_ANGLE_translated_shader_source GL_CHROMIUM_bind_generates_resource GL_CHROMIUM_bind_uniform_location GL_CHROMIUM_color_buffer_float_rgb GL_CHROMIUM_color_buffer_float_rgba GL_CHROMIUM_copy_compressed_texture GL_CHROMIUM_copy_texture GL_CHROMIUM_lose_context GL_CHROMIUM_sync_query GL_EXT_blend_func_extended GL_EXT_blend_minmax GL_EXT_color_buffer_float GL_EXT_color_buffer_half_float GL_EXT_debug_marker GL_EXT_discard_framebuffer GL_EXT_disjoint_timer_query GL_EXT_draw_buffers GL_EXT_float_blend GL_EXT_frag_depth GL_EXT_instanced_arrays GL_EXT_map_buffer_range GL_EXT_occlusion_query_boolean GL_EXT_read_format_bgra GL_EXT_robustness GL_EXT_sRGB GL_EXT_shader_texture_lod GL_EXT_texture_compression_bptc GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc_srgb GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_EXT_texture_norm16 GL_EXT_texture_rg GL_EXT_texture_storage GL_EXT_unpack_subimage GL_KHR_debug GL_KHR_parallel_shader_compile GL_KHR_robust_buffer_access_behavior GL_NV_EGL_stream_consumer_external GL_NV_fence GL_NV_pack_subimage GL_NV_pixel_buffer_object GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_EGL_image_external_essl3 GL_OES_depth24 GL_OES_depth32 GL_OES_element_index_uint GL_OES_get_program_binary GL_OES_mapbuffer GL_OES_packed_depth_stencil GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_surfaceless_context GL_OES_texture_3D GL_OES_texture_border_clamp GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_array_object GL_OVR_multiview GL_OVR_multiview2 OES_compressed_EAC_R11_signed_texture OES_compressed_EAC_R11_unsigned_texture OES_compressed_EAC_RG11_signed_texture OES_compressed_EAC_RG11_unsigned_texture OES_compressed_ETC2_RGB8_texture OES_compressed_ETC2_RGBA8_texture OES_compressed_ETC2_punchthroughA_RGBA8_texture OES_compressed_ETC2_punchthroughA_sRGB8_alpha_texture OES_compressed_ETC2_sRGB8_alpha8_texture OES_compressed_ETC2_sRGB8_texture WebGL 2 Extensions: EXT_color_buffer_float EXT_float_blend EXT_texture_compression_bptc EXT_texture_filter_anisotropic MOZ_debug OES_texture_float_linear OVR_multiview2 WEBGL_compressed_texture_s3tc WEBGL_compressed_texture_s3tc_srgb WEBGL_debug_renderer_info WEBGL_debug_shaders WEBGL_lose_context Direct2D: true Uses Tiling (Content): true Off Main Thread Painting Enabled: true Off Main Thread Painting Worker Count: 4 Target Frame Rate: 60 DirectWrite: true (10.0.17763.1217) GPU #1 Active: Yes Description: Intel(R) HD Graphics 630 Vendor ID: 0x8086 Device ID: 0x591b Driver Version: 25.20.100.6583 Driver Date: 4-12-2019 Drivers: igdumdim64 igd10iumd64 igd10iumd64 igd12umd64 igdumdim32 igd10iumd32 igd10iumd32 igd12umd32 Subsys ID: 080d1028 RAM: 0 GPU #2 Active: No Description: Radeon RX Vega M GL Graphics Vendor ID: 0x1002 Device ID: 0x694e Driver Version: 25.20.15002.58 Driver Date: 12-6-2018 Drivers: aticfx64 aticfx64 aticfx64 amdxc64 aticfx32 aticfx32 aticfx32 amdxc32 atiumd64 atidxx64 atidxx64 atiumdag atidxx32 atidxx32 atiumdva atiumd6a Subsys ID: 0000000c RAM: 4096 Diagnostics AzureCanvasBackend: direct2d 1.1 AzureCanvasBackend (UI Process): skia AzureContentBackend: skia AzureContentBackend (UI Process): skia AzureFallbackCanvasBackend (UI Process): none CMSOutputProfile: AAAMSExpbm8CEAAAbW50clJHQiBYWVogB84AAgAJAAYAMQAAYWNzcE1TRlQAAAAASUVDIHNSR0IAAAAAAAAAAAAAAAAAAPbWAAEAAAAA0y1IUCAgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAARY3BydAAAAVAAAAAzZGVzYwAAAYQAAABsd3RwdAAAAfAAAAAUYmtwdAAAAgQAAAAUclhZWgAAAhgAAAAUZ1hZWgAAAiwAAAAUYlhZWgAAAkAAAAAUZG1uZAAAAlQAAABwZG1kZAAAAsQAAACIdnVlZAAAA0wAAACGdmlldwAAA9QAAAAkbHVtaQAAA/gAAAAUbWVhcwAABAwAAAAkdGVjaAAABDAAAAAMclRSQwAABDwAAAgMZ1RSQwAABDwAAAgMYlRSQwAABDwAAAgMdGV4dAAAAABDb3B5cmlnaHQgKGMpIDE5OTggSGV3bGV0dC1QYWNrYXJkIENvbXBhbnkAAGRlc2MAAAAAAAAAEnNSR0IgSUVDNjE5NjYtMi4xAAAAAAAAAAAAAAASc1JHQiBJRUM2MTk2Ni0yLjEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAFhZWiAAAAAAAADzUQABAAAAARbMWFlaIAAAAAAAAAAAAAAAAAAAAABYWVogAAAAAAAAb6IAADj1AAADkFhZWiAAAAAAAABimQAAt4UAABjaWFlaIAAAAAAAACSgAAAPhAAAts9kZXNjAAAAAAAAABZJRUMgaHR0cDovL3d3dy5pZWMuY2gAAAAAAAAAAAAAABZJRUMgaHR0cDovL3d3dy5pZWMuY2gAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAZGVzYwAAAAAAAAAuSUVDIDYxOTY2LTIuMSBEZWZhdWx0IFJHQiBjb2xvdXIgc3BhY2UgLSBzUkdCAAAAAAAAAAAAAAAuSUVDIDYxOTY2LTIuMSBEZWZhdWx0IFJHQiBjb2xvdXIgc3BhY2UgLSBzUkdCAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGRlc2MAAAAAAAAALFJlZmVyZW5jZSBWaWV3aW5nIENvbmRpdGlvbiBpbiBJRUM2MTk2Ni0yLjEAAAAAAAAAAAAAACxSZWZlcmVuY2UgVmlld2luZyBDb25kaXRpb24gaW4gSUVDNjE5NjYtMi4xAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAB2aWV3AAAAAAATpP4AFF8uABDPFAAD7cwABBMLAANcngAAAAFYWVogAAAAAABMCVYAUAAAAFcf521lYXMAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAKPAAAAAnNpZyAAAAAAQ1JUIGN1cnYAAAAAAAAEAAAAAAUACgAPABQAGQAeACMAKAAtADIANwA7AEAARQBKAE8AVABZAF4AYwBoAG0AcgB3AHwAgQCGAIsAkACVAJoAnwCkAKkArgCyALcAvADBAMYAywDQANUA2wDgAOUA6wDwAPYA+wEBAQcBDQETARkBHwElASsBMgE4AT4BRQFMAVIBWQFgAWcBbgF1AXwBgwGLAZIBmgGhAakBsQG5AcEByQHRAdkB4QHpAfIB+gIDAgwCFAIdAiYCLwI4AkECSwJUAl0CZwJxAnoChAKOApgCogKsArYCwQLLAtUC4ALrAvUDAAMLAxYDIQMtAzgDQwNPA1oDZgNyA34DigOWA6IDrgO6A8cD0wPgA+wD+QQGBBMEIAQtBDsESARVBGMEcQR+BIwEmgSoBLYExATTBOEE8AT+BQ0FHAUrBToFSQVYBWcFdwWGBZYFpgW1BcUF1QXlBfYGBgYWBicGNwZIBlkGagZ7BowGnQavBsAG0QbjBvUHBwcZBysHPQdPB2EHdAeGB5kHrAe/B9IH5Qf4CAsIHwgyCEYIWghuCIIIlgiqCL4I0gjnCPsJEAklCToJTwlkCXkJjwmkCboJzwnlCfsKEQonCj0KVApqCoEKmAquCsUK3ArzCwsLIgs5C1ELaQuAC5gLsAvIC+EL+QwSDCoMQwxcDHUMjgynDMAM2QzzDQ0NJg1ADVoNdA2ODakNww3eDfgOEw4uDkkOZA5/DpsOtg7SDu4PCQ8lD0EPXg96D5YPsw/PD+wQCRAmEEMQYRB+EJsQuRDXEPURExExEU8RbRGMEaoRyRHoEgcSJhJFEmQShBKjEsMS4xMDEyMTQxNjE4MTpBPFE+UUBhQnFEkUahSLFK0UzhTwFRIVNBVWFXgVmxW9FeAWAxYmFkkWbBaPFrIW1hb6Fx0XQRdlF4kXrhfSF/cYGxhAGGUYihivGNUY+hkgGUUZaxmRGbcZ3RoEGioaURp3Gp4axRrsGxQbOxtjG4obshvaHAIcKhxSHHscoxzMHPUdHh1HHXAdmR3DHeweFh5AHmoelB6+HukfEx8+H2kflB+/H+ogFSBBIGwgmCDEIPAhHCFIIXUhoSHOIfsiJyJVIoIiryLdIwojOCNmI5QjwiPwJB8kTSR8JKsk2iUJJTglaCWXJccl9yYnJlcmhya3JugnGCdJJ3onqyfcKA0oPyhxKKIo1CkGKTgpaymdKdAqAio1KmgqmyrPKwIrNitpK50r0SwFLDksbiyiLNctDC1BLXYtqy3hLhYuTC6CLrcu7i8kL1ovkS/HL/4wNTBsMKQw2zESMUoxgjG6MfIyKjJjMpsy1DMNM0YzfzO4M/E0KzRlNJ402DUTNU01hzXCNf02NzZyNq426TckN2A3nDfXOBQ4UDiMOMg5BTlCOX85vDn5OjY6dDqyOu87LTtrO6o76DwnPGU8pDzjPSI9YT2hPeA+ID5gPqA+4D8hP2E/oj/iQCNAZECmQOdBKUFqQaxB7kIwQnJCtUL3QzpDfUPARANER0SKRM5FEkVVRZpF3kYiRmdGq0bwRzVHe0fASAVIS0iRSNdJHUljSalJ8Eo3Sn1KxEsMS1NLmkviTCpMcky6TQJNSk2TTdxOJU5uTrdPAE9JT5NP3VAnUHFQu1EGUVBRm1HmUjFSfFLHUxNTX1OqU/ZUQlSPVNtVKFV1VcJWD1ZcVqlW91dEV5JX4FgvWH1Yy1kaWWlZuFoHWlZaplr1W0VblVvlXDVchlzWXSddeF3JXhpebF69Xw9fYV+zYAVgV2CqYPxhT2GiYfViSWKcYvBjQ2OXY+tkQGSUZOllPWWSZedmPWaSZuhnPWeTZ+loP2iWaOxpQ2maafFqSGqfavdrT2una/9sV2yvbQhtYG25bhJua27Ebx5veG/RcCtwhnDgcTpxlXHwcktypnMBc11zuHQUdHB0zHUodYV14XY+dpt2+HdWd7N4EXhueMx5KnmJeed6RnqlewR7Y3vCfCF8gXzhfUF9oX4BfmJ+wn8jf45YBHgKiBCoFrgc2CMIKSgvSDV4O6hB2EgITjhUeFq4YOhnKG14c7h5+IBIhpiM6JM4mZif6KZIrKizCLlov8jGOMyo0xjZiN/45mjs6PNo+ekAaQbpDWkT+RqJIRknqS45NNk7aUIJSKlPSVX5XJljSWn5cKl3WX4JhMmLiZJJmQmfyaaJrVm0Kbr5wcnImc951kndKeQJ6unx2fi5/6oGmg2KFHobaiJqKWowajdqPmpFakx6U4pammGqaLpv2nbqfgqFKoxKk3qamqHKqPqwKrdavprFys0K1ErbiuLa6hrxavi7AAsHWw6rFgsdayS7LCszizrrQltJy1E7WKtgG2ebbwt2i34LhZuNG5SrnCuju6tbsuu6e8IbybvRW9j74KvoS+/796v/XAcMDswWfB48JfwtvDWMPUxFHEzsVLxcjGRsbDx0HHv8g9yLzJOsm5yjjKt8s2y7bMNcy1zTXNtc42zrbPN8+40DnQutE80b7SP9LB00TTxtRJ1MvVTtXR1lXW2Ndc1+DYZNjo2WzZ8dp22vvbgNwF3IrdEN2W3hzeot8p36/gNuC94UThzOJT4tvjY+Pr5HPk/OWE5g3mlucf56noMui86Ubp0Opb6uXrcOv77IbtEe2c7ijutO9A78zwWPDl8XLx//KM8xnzp/Q09ML1UPXe9m32+/eK+Bn4qPk4+cf6V/rn+3f8B/yY/Sn9uv5L/tz/bf// Display0: [email protected] DisplayCount: 1 GPUProcessPid: 15656 GPUProcess: Terminate GPU Process Device Reset: Trigger Device Reset ClearType Parameters: Gamma: 1.8 Pixel Structure: RGB ClearType Level: 100 Enhanced Contrast: 50 Decision Log HW_COMPOSITING: available by default D3D11_COMPOSITING: available by default DIRECT2D: available by default D3D11_HW_ANGLE: available by default GPU_PROCESS: available by default WEBRENDER: opt-in by default: WebRender is an opt-in feature available by user: Qualified enabled by pref WEBRENDER_QUALIFIED: available by default WEBRENDER_COMPOSITOR: available by default WEBRENDER_PARTIAL: available by default WEBRENDER_ANGLE: opt-in by default: WebRender ANGLE is an opt-in feature available by user: Enabled WEBRENDER_DCOMP_PRESENT: opt-in by default: WebRender DirectComposition is an opt-in feature available by user: Enabled OMTP: available by default ADVANCED_LAYERS: available by default blocked by env: Blocked from fallback candidate by WebRender usage WEBGPU: disabled by default: Disabled by default

Media

Audio Backend: wasapi Max Channels: 2 Preferred Sample Rate: 48000 Output Devices Name: Group Headphones (High Definition Audio Device): Speakers (High Definition Audio Device): Speakers/Headphones (Realtek(R) Audio): INTELAUDIO\FUNC_01&VEN_10EC&DEV_0299&SUBSYS_1028080D&REV_1000\4&566e4e0&3&0001 Speakers/Headphones (Realtek(R) Audio): INTELAUDIO\FUNC_01&VEN_10EC&DEV_0299&SUBSYS_1028080D&REV_1000\4&566e4e0&3&0001 : Headphones (LG HBS820S Stereo): BTHENUM{0000110b-0000-1000-8000-00805f9b34fb}_VID&00000000_PID&0000\7&2dc50fc3&0&B8AD3EFD6601_C00000000 Headset (LG HBS820S Hands-Free): BTHHFENUM\BthHFPAudio\8&13a9352e&0&97 Input Devices Name: Group : Microphone (High Definition Audio Device): Microphone Array (Realtek(R) Audio): INTELAUDIO\FUNC_01&VEN_10EC&DEV_0299&SUBSYS_1028080D&REV_1000\4&566e4e0&3&0001 Internal AUX Jack (High Definition Audio Device): Headset (LG HBS820S Hands-Free): BTHHFENUM\BthHFPAudio\8&13a9352e&0&97 Stereo Mix (Realtek(R) Audio): INTELAUDIO\FUNC_01&VEN_10EC&DEV_0299&SUBSYS_1028080D&REV_1000\4&566e4e0&3&0001 Microphone Array (Realtek(R) Audio): INTELAUDIO\FUNC_01&VEN_10EC&DEV_0299&SUBSYS_1028080D&REV_1000\4&566e4e0&3&0001 Microphone (HD Pro Webcam C920): USB\VID_046D&PID_082D&MI_02\6&246d97e&0&0002 Microphone (Realtek(R) Audio): INTELAUDIO\FUNC_01&VEN_10EC&DEV_0299&SUBSYS_1028080D&REV_1000\4&566e4e0&3&0001 Media Capabilities Enumerate database

Important Modified Preferences

accessibility.typeaheadfind.flashBar: 0 browser.cache.disk.amount_written: 1149263 browser.cache.disk.capacity: 1048576 browser.cache.disk.filesystem_reported: 1 browser.cache.disk.hashstats_reported: 1 browser.cache.disk.smart_size.first_run: false browser.cache.disk.telemetry_report_ID: 327 browser.contentblocking.category: standard browser.places.smartBookmarksVersion: 8 browser.search.region: US browser.search.useDBForOrder: true browser.sessionstore.upgradeBackup.latestBuildID: 20200526213752 browser.sessionstore.warnOnQuit: true browser.startup.homepage: https://defaultsearch.co/homepage?hp=1&pId=BT170603&iDate=2020-04-29 12:03:43&bName=&bitmask=0600 browser.startup.homepage_override.buildID: 20200526213752 browser.startup.homepage_override.mstone: 78.0a1 browser.startup.page: 3 browser.urlbar.placeholderName: Google browser.urlbar.placeholderName.private: DuckDuckGo browser.urlbar.searchTips.onboard.shownCount: 4 browser.urlbar.searchTips.shownCount: 4 browser.urlbar.timesBeforeHidingSuggestionsHint: 0 browser.urlbar.tipShownCount.searchTip_onboard: 4 dom.forms.autocomplete.formautofill: true dom.push.userAgentID: d9f895026f1445a592b511d8bdc41951 extensions.formautofill.creditCards.used: 2 extensions.formautofill.firstTimeUse: false extensions.lastAppVersion: 78.0a1 fission.autostart: true font.internaluseonly.changed: true gfx.crash-guard.status.wmfvpxvideo: 2 gfx.crash-guard.wmfvpxvideo.appVersion: 78.0a1 gfx.crash-guard.wmfvpxvideo.deviceID: 0x591b gfx.crash-guard.wmfvpxvideo.driverVersion: 25.20.100.6583 idle.lastDailyNotification: 1590518645 layers.mlgpu.sanity-test-failed: true media.benchmark.vp9.fps: 218 media.benchmark.vp9.versioncheck: 5 media.gmp-gmpopenh264.abi: x86_64-msvc-x64 media.gmp-gmpopenh264.lastUpdate: 1571369277 media.gmp-gmpopenh264.version: 1.8.1.1 media.gmp-manager.buildID: 20200526213752 media.gmp-manager.lastCheck: 1590549547 media.gmp-widevinecdm.abi: x86_64-msvc-x64 media.gmp-widevinecdm.lastUpdate: 1576215038 media.gmp-widevinecdm.version: 4.10.1582.2 media.gmp.storage.version.observed: 1 media.hardware-video-decoding.failed: false media.hardwaremediakeys.enabled: false network.cookie.prefsMigrated: true network.dns.disablePrefetch: true network.http.speculative-parallel-limit: 0 network.predictor.cleaned-up: true network.predictor.enabled: false network.prefetch-next: false places.database.lastMaintenance: 1590344902 places.history.expiration.transient_current_max_pages: 142988 plugin.disable_full_page_plugin_for_types: application/pdf privacy.purge_trackers.date_in_cookie_database: 0 privacy.sanitize.pending: [{"id":"newtab-container","itemsToClear":[],"options":{}}] privacy.socialtracking.notification.counter: 1 privacy.socialtracking.notification.enabled: false privacy.socialtracking.notification.lastShown: 1565913521227 security.remote_settings.crlite_filters.checked: 1590504902 security.remote_settings.intermediates.checked: 1590504902 security.sandbox.content.tempDirSuffix: {16c414bc-c85a-4ded-b155-040e5adac549} security.sandbox.plugin.tempDirSuffix: {186f0c18-7ebb-4d10-96e5-975ec79ea26d} security.tls.version.enable-deprecated: true services.sync.declinedEngines: services.sync.engine.addresses.available: true signon.importedFromSqlite: true storage.vacuum.last.index: 1 storage.vacuum.last.places.sqlite: 1589728394 ui.osk.debug.keyboardDisplayReason: IKPOS: Keyboard presence confirmed.

Important Locked Preferences

dom.ipc.processCount.webIsolated: 1

Places Database

Accessibility

Activated: true Prevent Accessibility: 0 Accessible Handler Used: true Accessibility Instantiator: UNKNOWN|

Library Versions

NSPR Expected minimum version: 4.25 Version in use: 4.25
NSS Expected minimum version: 3.53 Beta Version in use: 3.53 Beta
NSSSMIME Expected minimum version: 3.53 Beta Version in use: 3.53 Beta
NSSSSL Expected minimum version: 3.53 Beta Version in use: 3.53 Beta
NSSUTIL Expected minimum version: 3.53 Beta Version in use: 3.53 Beta

Sandbox

Content Process Sandbox Level: 6 Effective Content Process Sandbox Level: 6

Startup Cache

Disk Cache Path: C:\Users\Daniel Chuchra\AppData\Local\Mozilla\Firefox\Profiles\dmz3ad06.default\startupCache\startupCache.8.little Ignore Disk Cache: false Found Disk Cache on Init: true Wrote to Disk Cache: true

Internationalization & Localization

Application Settings Requested Locales: ["en-US"] Available Locales: ["en-US"] App Locales: ["en-US"] Regional Preferences: ["en-US"] Default Locale: "en-US" Operating System System Locales: ["en-US"] Regional Preferences: ["en-US"]

Remote Debugging (Chromium Protocol)

Accepting Connections: false URL:
submitted by TheGhzGuy to firefox [link] [comments]

Domain And Range Of A Binary Relation William's Percent Range with (Buy Zone and Sell Zone) - Binary Optinos Strategy - Best System 100万円 エントリー解説【バイナリーオプション】逆張りレンジブレイク手法 BINARY OPTIONS TRADING 2019 - Strategy For Trading Binary Options Problem 1: Domain & Range of Binary Relation

Definition. Binary options are, in simple terms, bets on the future market behavior. A user chooses a contract from the list of the available on the platform and invests a certain sum — then At most recent exchange the Binary Option with a call or put. Binary options are also known as digital options. The definition of Binary Trading Options are the trader uses a wide range of assets that you got from Indices, Commodities and Stocks. Speaking in the terms used in the trade, all that you need to …. Range of markets Binary options allow you to trade on a wide range of underlying markets. One of the advantages of trading binary options is that you are not buying or selling an actual asset, only a contract that determines how that asset performs over a period of time. Assume you can buy a binary option on gold trading at or above $1,200 by that day’s close, and this option is trading at $57 (bid)/$60 (offer). You buy the option at $60. A binary option, sometimes called a digital option, is a type of option in which the trader takes a yes or no position on the price of a stock or other asset, such as ETFs or currencies, and the resulting payoff is all or nothing. Because...

[index] [29001] [13626] [22631] [18930] [25688] [28950] [26180] [15704] [22384] [15709]

Domain And Range Of A Binary Relation

Domain And Range Of A Binary Relation SET School IXX. Loading... Unsubscribe from SET School IXX? ... Best Binary Options Strategy 2020 - 2 Minute Strategy LIVE TRAINING! - Duration: 43:42. ウィリアムパーセントレンジを使った勝率を検証してみた【バイナリーオプション】Williams' Percent Range Binary option - Duration: 16:43. 谷あきら 6,110 views ... Math_m-9-10-sets56.mp4. How To Find The Domain of a Function - Radicals, Fractions & Square Roots - Interval Notation - Duration: 18:45. The Organic Chemistry Tutor 1,328,260 views ウィリアムパーセントレンジを使った勝率を検証してみた【バイナリーオプション】Williams' Percent Range Binary option - Duration: 16:43. タニアキラ ... ウィリアムパーセントレンジを使った勝率を検証してみた【バイナリーオプション】Williams' Percent Range Binary option - Duration: 16:43. タニアキラ ...

Flag Counter