Types of Binary Bets – One Touch - BinaryOptions.net
Types of Binary Bets – One Touch - BinaryOptions.net
One Touch Options Explained - BinaryOptions
One-Touch Binary Options Explained - The Options Guide
One Touch Binary Options Trading - How it Works & What to
Touch and No Touch Options 🚫 Touch Options Trading
How one touch binary options trades work
https://preview.redd.it/6yzd57p88bh21.jpg?width=959&format=pjpg&auto=webp&s=a56a79df4afe36924ee5ffe4325ba3374c99b144 You have decided to trade the S&P 500 index which is currently trading at $1430. After consulting the different charts and technical tools, you conclude that the price is going to rise over the next few hours. However, you cannot predict by how much. You therefore decide to place a call (buy). Since the broker offers several expiry periods that range from 5 minutes to 1 month, you decide to hold the trade position for 10 minutes. That is, if after 10 minutes the price of the S&P 500 index is over $1430, you’ll make a profit. If it’s lower, you’ll lose your investment. Your broker indicates that you’ll earn a 70% on your investment (profit). Depending on your account management strategy, you decide to invest $100 on the trade (we usually recommend about 2% of your total account value). At expiry time, the price of the S&P 500 index is $1432. An increase of $2. This means that you have made a $70 profit (70% of $100). You account is therefore credited with $170. Note that the $2 increase in the price of the S&P 500 index is not your profit since you don’t actually own the asset. Your profit is earned on the amount you invested. Therefore, if S&P index price dropped to $1429, you would have lost your $100 investment. On the other hand, if the price at expiry remained at $1430, it’s likely that your broker would simply refund your $100. This example describes a simple high/low options trade. Today’s brokers often offer other exotic options trades that include one touch and range. Here’s a brief overview about how each one works. Using the example above, one touch trade rules require the S&P 500 price movement must touch a predetermined price level before the expiry period. You are usually provided with two price levels, one above the current price and one below it. Still using the S&P 500 current price of $1430, your broker might provide a price range between $1400 and $1460. After analysis, you conclude that since the price is rallying, it should hit $1437 before it starts dropping. You also conclude that it will hit $1437 within 150 minutes. Using the one-touch trade, you simply place your price level at $1437 or lower and an expiry of 150 minutes. If the price reaches $1437 before the expiry period, you’ll make a profit. If however, it never reaches $1437, you’ll lose your investment. Website: kimex.io Facebook: https://www.facebook.com/kimexofficial Twitter: https://twitter.com/Kimex_Official Telegram: https://t.me/KimexOfficial
As you may have seen, I sent the following Tweet: “The Apple ARM MacBook future is coming, maybe sooner than people expect” https://twitter.com/choco_bit/status/1266200305009676289?s=20 Today, I would like to further elaborate on that. tl;drApple will be moving to Arm based macs in what I believe are 4 stages, starting around 2015 and ending around 2023-2025: Release of T1 chip Macbooks, release of T2 chip Macbooks, Release of at least one lower end model Arm Macbook, and transitioning full lineup to Arm. Reasons for each are below. Apple is very likely going to switch to switch their CPU platform to their in-house silicon designs with an ARM architecture. This understanding is a fairly common amongst various Apple insiders. Here is my personal take on how this switch will happen and be presented to the consumer. The first question would likely be “Why would Apple do this again?”. Throughout their history, Apple has already made two other storied CPU architecture switches - first from the Motorola 68k to PowerPC in the early 90s, then from PowerPC to Intel in the mid 2000s. Why make yet another? Here are the leading reasons:
Intel has, in recent years, been making significant losses both in reputation and in actual product value, as well as velocity of product development, breaking their bi-yearly “Tick Tock” cycle for the first time in decades. Most recently, they have fallen well behind AMD’s processor lines in cost to performance ratio, CPU core count, core design (monolithic design vs “chiplet”), power consumption to performance, silicon supply (Intel with significant manufacturing process and yield issues), and on-silicon security features. While Intel still wins out in certain enterprise and datacenter applications, as well as having a much better reputation for reliability and QA (AMD having shipped numerous chips with a broken random- number generator that prevented even booting some mainstream operating system), the number of such applications slowly dwindles with each new release from AMD, and as confidence among decisionmakers in enterprise increases. In the public consciousness, Intel is quickly becoming a point of ridicule against Apple’s Mac lineup, rather than a badge of honor.
By moving to their own designs, Apple will be free from Intel’s release schedule, which have recently been unpredictable and faced with routine delays due to poor manufacturing yields. Apple will be able to update their Mac lineup on their own timeline, rather than being forced to delay products based on Intel’s ability to meet the release window. This also allows them to leverage relationships with other silicon fabricators to source chips, rather than relying on Intel ’s continued “iteration” that’s leading to a “14nm++++++++++” process, or the continued lack of product diversity with the 10nm process. Apple will also be free to innovate in the design of the silicon platform, rather than being limited by Intel’s design choices. By having full control of the manufacturing and development cycle, Apple can bring even more in-house optimization to the macOS, as they have been for iOS and iPadOS over the years.
Using an ARM architecture on the Macs allows for a more unified Apple ecosystem, rather than having separate Mac and iOS-based products. The only distinction will be the device form factor and performance characteristics.
The x86_64 architecture is very old and inefficient, using older methodologies for processor design (CISC vs ARM’s RISC), and the instruction set continues to require support in silicon for emulating 1980s-vintage 16-bit modes, as well as ineffectual and archaic memory addressing modes (segmentation, etc.) The x86_64 architecture is like a city, built atop a much older city, built atop a yet older city, but every layer is built with NYC infrastructure levels of complexity that suited its time and no further.
Over the last 10 years, Apple has shown that they can consistently produce impressive silicon designs, often leading the market in performance and capability, and Apple has been aggressively acquiring silicon design talent.
A common refrain heard on the Internet is the suggestion that Apple should switch to using CPUs made by AMD, and while this has been considered internally, it will most likely not be chosen as the path forward, even for their megalithic giants like the Mac Pro. Even though AMD would mitigate Intel’s current set of problems, it does nothing to help the issue of the x86_64 architecture’s problems and inefficiencies, on top of jumping to a platform that doesn’t have a decade of proven support behind it. Why spend a lot of effort re-designing and re- optimizing for AMD’s platform when you can just put that effort into your own, and continue the vertical integration Apple is well-known for? I believe that the internal development for the ARM transition started around 2015/2016 and is considered to be happening in 4 distinct stages. These are not all information from Apple insiders; some of these these are my own interpretation based off of information gathered from supply-chain sources, examination of MacBook schematics, and other indicators from Apple.
Stage1 (from 2014/2015 to 2017):
The rollout of computers with Apple’s T1 chip as a coprocessor. This chip is very similar to Apple’s T8002 chip design, which was used for the Apple Watch Series 1 and Series 2. The T1 is primarily present on the first TouchID enabled Macs, 2016 and 2017 model year MacBook Pros. Considering the amount of time required to design and validate a processor, this stage most likely started around 2014 or 2015, with early experimentation to see whether an entirely new chip design would be required, or if would be sufficient to repurpose something in the existing lineup. As we can see, the general purpose ARM processors aren’t a one- trick pony. To get a sense of the decision making at the time, let’s look back a bit. The year is 2016, and we're witnessing the beginning of stagnation of Intel processor lineup. There is not a lot to look forward to other than another “+” being added to the 14nm fabrication process. The MacBook Pro has used the same design for many years now, and its age is starting to show. Moving to AMD is still very questionable, as they’ve historically not been able to match Intel’s performance or functionality, especially at the high end, and since the “Ryzen” lineup is still unreleased, there is absolutely no benchmarks or other data to show they are worth consideration, and AMD’s most recent line of “Bulldozer” processors were very poorly received. Now is probably as good a time as any to begin experimenting with the in-house ARM designs, but it’s not time to dive into the deep end yet, our chips are not nearly mature enough to compete, and it’s not yet certain how long Intel will be stuck in the mud. As well, it is widely understood that Apple and Intel have an exclusivity contract in exchange for advantageous pricing. Any transition would take considerable time and effort, and since there are no current viable alternative to Intel, the in-house chips will need to advance further, and breaching a contract with Intel is too great a risk. So it makes sense to start with small deployments, to extend the timeline, stretch out to the end of the contract, and eventually release a real banger of a Mac. Thus, the 2016 Touch Bar MacBooks were born, alongside the T1 chip mentioned earlier. There are good reasons for abandoning the piece of hardware previously used for a similar purpose, the SMC or System Management Controller. I suspect that the biggest reason was to allow early analysis of the challenges that would be faced migrating Mac built- in peripherals and IO to an ARM-based controller, as well as exploring the manufacturing, power, and performance results of using the chips across a broad deployment, and analyzing any early failure data, then using this to patch any issues, enhance processes, and inform future designs looking towards the 2nd stage. The former SMC duties now moved to T1 includes things like
Fan speed, voltage, amperage and thermal sensor feedback data
FaceTime camera and microphone IO
PMIC (Power Management Controller)
Direct communication to NAND (solid state storage)
Direct communication with the Touch Bar
Secure Enclave for TouchID
The T1 chip also communicates with a number of other controllers to manage a MacBook’s behavior. Even though it’s not a very powerful CPU by modern standards, it’s already responsible for a large chunk of the machine’s operation. Moving control of these peripherals to the T1 chip also brought about the creation of the fabled BridgeOS software, a shrunken-down watchOS-based system that operates fully independently of macOS and the primary Intel processor. BridgeOS is the first step for Apple’s engineering teams to begin migrating underlying systems and services to integrate with the ARM processor via BridgeOS, and it allowed internal teams to more easily and safely develop and issue firmware updates. Since BridgeOS is based on a standard and now well-known system, it means that they can leverage existing engineering expertise to flesh out the T1’s development, rather than relying on the more arcane and specialized SMC system, which operates completely differently and requires highly specific knowledge to work with. It also allows reuse of the same fabrication pipeline used for Apple Watch processors, and eliminated the need to have yet another IC design for the SMC, coming from a separate source, to save a bit on cost. Also during this time, on the software side, “Project Marzipan”, today Catalyst, came into existence. We'll get to this shortly. For the most part, this Stage 1 went without any major issues. There were a few firmware problems at first during the product launch, but they were quickly solved with software updates. Now that engineering teams have had experience building for, manufacturing, and shipping the T1 systems, Stage 2 would begin.
Stage 2 encompasses the rollout of Macs with the T2 coprocessor, replacing the T1. This includes a much wider lineup, including MacBook Pro with Touch Bar, starting with 2018 models, MacBook Air starting with 2018 models, the iMac Pro, the 2019 Mac Pro, as well as Mac Mini starting in 2018. With this iteration, the more powerful T8012 processor design was used, which is a further revision of the T8010 design that powers the A10 series processors used in the iPhone 7. This change provided a significant increase in computational ability and brought about the integration of even more devices into T2. In addition to the T1’s existing responsibilities, T2 now controls:
Full audio subsystem
Secure Enclave for internal NAND storage and encryption/decryption offload
Management of the whole system’s power and startup sequence, allowing for trusted boot (ensure boot chain-of-trust with no malicious code/rootkit/bootkit)
Those last 2 points are crucial for Stage 2. Under this new paradigm, the vast majority of the Mac is now under the control of an in-house ARM processor. Stage 2 also brings iPhone-grade hardware security to the Mac. These T2 models also incorporated a supported DFU (Device Firmware Update, more commonly “recovery mode”), which acts similarly to the iPhone DFU mode and allows restoration of the BridgeOS firmware in the event of corruption (most commonly due to user-triggered power interruption during flashing). Putting more responsibility onto the T2 again allows for Apple’s engineering teams to do more early failure analysis on hardware and software, monitor stability of these machines, experiment further with large-scale production and deployment of this ARM platform, as well as continue to enhance the silicon for Stage 3. A few new user-visible features were added as well in this stage, such as support for the passive “Hey Siri” trigger, and offloading image and video transcoding to the T2 chip, which frees up the main Intel processor for other applications. BridgeOS was bumped to 2.0 to support all of these changes and the new chip. On the macOS software side, what was internally known as Project Marzipan was first demonstrated to the public. Though it was originally discovered around 2017, and most likely began development and testing within later parts of Stage 1, its effects could be seen in 2018 with the release of iPhone apps, now running on the Mac using the iOS SDKs: Voice Recorder, Apple News, Home, Stocks, and more, with an official announcement and public release at WWDC in 2019. Catalyst would come to be the name of Marzipan used publicly. This SDK release allows app developers to easily port iOS apps to run on macOS, with minimal or no code changes, and without needing to develop separate versions for each. The end goal is to allow developers to submit a single version of an app, and allow it to work seamlessly on all Apple platforms, from Watch to Mac. At present, iOS and iPadOS apps are compiled for the full gamut of ARM instruction sets used on those devices, while macOS apps are compiled for x86_64. The logical next step is to cross this bridge, and unify the instruction sets. With this T2 release, the new products using it have not been quite as well received as with the T1. Many users have noticed how this change contributes further towards machines with limited to no repair options outside of Apple’s repair organization, as well as some general issues with bugs in the T2. Products with the T2 also no longer have the “Lifeboat” connector, which was previously present on 2016 and 2017 model Touch Bar MacBook Pro. This connector allowed a certified technician to plug in a device called a CDM Tool (Customer Data Migration Tool) to recover data off of a machine that was not functional. The removal of this connector limits the options for data recovery in the event of a problem, and Apple has never offered any data recovery service, meaning that a irreparable failure of the T2 chip or the primary board would result in complete data loss, in part due to the strong encryption provided by the T2 chip (even if the data got off, the encryption keys were lost with the T2 chip). The T2 also brought about the linkage of component serial numbers of certain internal components, such as the solid state storage, display, and trackpad, among other components. In fact, many other controllers on the logic board are now also paired to the T2, such as the WiFi and Bluetooth controller, the PMIC (Power Management Controller), and several other components. This is the exact same system used on newer iPhone models and is quite familiar to technicians who repair iPhone logic boards. While these changes are fantastic for device security and corporate and enterprise users, allowing for a very high degree of assurance that devices will refuse to boot if tampered with in any way - even from storied supply chain attacks, or other malfeasance that can be done with physical access to a machine - it has created difficulty with consumers who more often lack the expertise or awareness to keep critical data backed up, as well as the funds to perform the necessary repairs from authorized repair providers. Other issues reported that are suspected to be related to T2 are audio “cracking” or distortion on the internal speakers, and the BridgeOS becoming corrupt following a firmware update resulting in a machine that can’t boot. I believe these hiccups will be properly addressed once macOS is fully integrated with the ARM platform. This stage of the Mac is more like a chimera of an iPhone and an Intel based computer. Technically, it does have all of the parts of an iPhone present within it, cellular radio aside, and I suspect this fusion is why these issues exist. Recently, security researchers discovered an underlying security problem present within the Boot ROM code of the T1 and T2 chip. Due to being the same fundamental platform as earlier Apple Watch and iPhone processors, they are vulnerable to the “checkm8” exploit (CVE-2019-8900). Because of how these chips operate in a Mac, firmware modifications caused by use of the exploit will persist through OS reinstallation and machine restarts. Both the T1 and T2 chips are always on and running, though potentially in a heavily reduced power usage state, meaning the only way to clean an exploited machine is to reflash the chip, triggering a restart, or to fully exhaust or physically disconnect the battery to flush its memory. Fortunately, this exploit cannot be done remotely and requires physical access to the Mac for an extended duration, as well as a second Mac to perform the change, so the majority of users are relatively safe. As well, with a very limited execution environment and access to the primary system only through a “mailbox” protocol, the utility of exploiting these chips is extremely limited. At present, there is no known malware that has used this exploit. The proper fix will come with the next hardware revision, and is considered a low priority due to the lack of practical usage of running malicious code on the coprocessor. At the time of writing, all current Apple computers have a T2 chip present, with the exception of the 2019 iMac lineup. This will change very soon with the expected release of the 2020 iMac lineup at WWDC, which will incorporate a T2 coprocessor as well. Note: from here on, this turns entirely into speculation based on info gathered from a variety of disparate sources. Right now, we are in the final steps of Stage 2. There are strong signs that an a MacBook (12”) with an ARM main processor will be announced this year at WWDC (“One more thing...”), at a Fall 2020 event, Q1 2021 event, or WWDC 2021. Based on the lack of a more concrete answer, WWDC2020 will likely not see it, but I am open to being wrong here.
Stage3 (Present/2021 - 2022/2023):
Stage 3 involves the first version of at least one fully ARM-powered Mac into Apple’s computer lineup. I expect this will come in the form of the previously-retired 12” MacBook. There are rumors that Apple is still working internally to perfect the infamous Butterfly keyboard, and there are also signs that Apple is developing an A14x based processors with 8-12 cores designed specifically for use as the primary processor in a Mac. It makes sense that this model could see the return of the Butterfly keyboard, considering how thin and light it is intended to be, and using an A14x processor would make it will be a very capable, very portable machine, and should give customers a good taste of what is to come. Personally, I am excited to test the new 12" “ARMbook”. I do miss my own original 12", even with all the CPU failure issues those older models had. It was a lovely form factor for me. It's still not entirely known whether the physical design of these will change from the retired version, exactly how many cores it will have, the port configuration, etc. I have also heard rumors about the 12” model possibly supporting 5G cellular connectivity natively thanks to the A14 series processor. All of this will most likely be confirmed soon enough. This 12” model will be the perfect stepping stone for stage 3, since Apple’s ARM processors are not yet a full-on replacement for Intel’s full processor lineup, especially at the high end, in products such as the upcoming 2020 iMac, iMac Pro, 16” MacBook Pro, and the 2019 Mac Pro. Performance of Apple’s ARM platform compared to Intel has been a big point of contention over the last couple years, primarily due to the lack of data representative of real-world desktop usage scenarios. The iPad Pro and other models with Apple’s highest-end silicon still lack the ability to execute a lot of high end professional applications, so data about anything more than video editing and photo editing tasks benchmarks quickly becomes meaningless. While there are completely synthetic benchmarks like Geekbench, Antutu, and others, to try and bridge the gap, they are very far from being accurate or representative of the real real world performance in many instances. Even though the Apple ARM processors are incredibly powerful, and I do give constant praise to their silicon design teams, there still just isn’t enough data to show how they will perform for real-world desktop usage scenarios, and synthetic benchmarks are like standardized testing: they only show how good a platform is at running the synthetic benchmark. This type of benchmark stresses only very specific parts of each chip at a time, rather than how well it does a general task, and then boil down the complexity and nuances of each chip into a single numeric score, which is not a remotely accurate way of representing processors with vastly different capabilities and designs. It would be like gauging how well a person performs a manual labor task based on averaging only the speed of every individual muscle in the body, regardless of if, or how much, each is used. A specific group of muscles being stronger or weaker than others could wildly skew the final result, and grossly misrepresent performance of the person as a whole. Real world program performance will be the key in determining the success and future of this transition, and it will have to be great on this 12" model, but not just in a limited set of tasks, it will have to be great at *everything*. It is intended to be the first Horseman of the Apocalypse for the Intel Mac, and it better behave like one. Consumers have been expecting this, especially after 15 years of Intel processors, the continued advancement of Apple’s processors, and the decline of Intel’s market lead. The point of this “demonstration” model is to ease both users and developers into the desktop ARM ecosystem slowly. Much like how the iPhone X paved the way for FaceID-enabled iPhones, this 12" model will pave the way towards ARM Mac systems. Some power-user type consumers may complain at first, depending on the software compatibility story, then realize it works just fine since the majority of the computer users today do not do many tasks that can’t be accomplished on an iPad or lower end computer. Apple needs to gain the public’s trust for basic tasks first, before they will be able to break into the market of users performing more hardcore or “Pro” tasks. This early model will probably not be targeted at these high-end professionals, which will allow Apple to begin to gather early information about the stability and performance of this model, day to day usability, developmental issues that need to be addressed, hardware failure analysis, etc. All of this information is crucial to Stage 4, or possibly later parts of Stage 3. The 2 biggest concerns most people have with the architecture change is app support and Bootcamp. Any apps released through the Mac App Store will not be a problem. Because App Store apps are submitted as LLVM IR (“Bitcode”), the system can automatically download versions compiled and optimized for ARM platforms, similar to how App Thinning on iOS works. For apps distributed outside the App Store, thing might be more tricky. There are a few ways this could go:
Developer will need to build both x86_64 and ARM version of their app - App Bundles have supported multiple-architecture binaries since the dawn of OS X and the PowerPC transition
Move to apps being distributed in an architecture-independent manner, as they are on the App Store. There is some software changes that are suggestive of this, such as the new architecture in dyld3.
An x86_64 instruction decoder in silicon - very unlikely due to the significant overhead this would create in the silicon design, and potential licensing issues. (ARM, being a RISC, “reduced instruction set”, has very few instructions; x86_64 has thousands)
Server-side ahead-of-time transpilation (converting x86 code to equivalent ARM code) using Notarization submissions - Apple certainly has the compiler chops in the LLVM team to do something like this
Outright emulation, similar to the approach that was taken in ARM releases of Windows, but received extremely poorly (limited to 32-bit apps, and very very slow)There could be other solutions in the works to fix this but I am not aware of any. This is just me speculating about some of the possibilities.
As for Bootcamp, while ARM-compatible versions of Windows do exist and are in development, they come with their own similar set of app support problems. Microsoft has experimented with emulating x86_64 on their ARM-based Surface products, and some other OEMs have created their own Windows-powered ARM laptops, but with very little success. Performance is a problem across the board, with other ARM silicon not being anywhere near as advanced, and with the majority of apps in the Windows ecosystem that were not developed in-house at Microsoft running terribly due to the x86_64 emulation software. If Bootcamp does come to the early ARM MacBook, it more than likely will run like very poorly for anything other than Windows UWP apps. There is a high chance it will be abandoned entirely until Windows becomes much more friendly to the architecture. I believe this will also be a very crucial turning point for the MacBook lineup as a whole. At present, the iPad Pro paired with the Magic Keyboard is, in many ways, nearly identical to a laptop, with the biggest difference being the system software itself. While Apple executives have outright denied plans of merging the iPad and MacBook line, that could very well just be a marketing stance, shutting the down rumors in anticipation of a well-executed surprise. I think that Apple might at least re-examine the possibility of merging Macs and iPads in some capacity, but whether they proceed or not could be driven by consumer reaction to both products. Do they prefer the feel and usability of macOS on ARM, and like the separation of both products? Is there success across the industry of the ARM platform, both at the lower and higher end of the market? Do users see that iPadOS and macOS are just 2 halves of the same coin? Should there be a middle ground, and a new type of product similar to the Surface Book, but running macOS? Should Macs and iPads run a completely uniform OS? Will iPadOS ever see exposed the same sort of UNIX-based tools for IT administrators and software developers that macOS has present? These are all very real questions that will pop up in the near future. The line between Stage 3 and Stage 4 will be blurry, and will depend on how Apple wishes to address different problems going forward, and what the reactions look like. It is very possible that only 12” will be released at first, or a handful more lower end model laptop and desktop products could be released, with high performance Macs following in Stage 4, or perhaps everything but enterprise products like Mac Pro will be switched fully. Only time will tell.
Stage 4 (the end goal):
Congratulations, you’re made it to the end of my TED talk. We are now well into the 2020s and COVID-19 Part 4 is casually catching up to the 5G = Virus crowd. All Macs have transitioned fully to ARM. iMac, MacBooks Pro and otherwise, Mac Pro, Mac Mini, everything. The future is fully Apple from top to bottom, and vertical integration leading to market dominance continues. Many other OEM have begun to follow in this path to some extent, creating more demand for a similar class of silicon from other firms. The remainder here is pure speculation with a dash of wishful thinking. There are still a lot of things that are entirely unclear. The only concrete thing is that Stage 4 will happen when everything is running Apple’s in- house processors. By this point, consumers will be quite familiar with the ARM Macs existing, and developers have had have enough time to transition apps fully over to the newly unified system. Any performance, battery life, or app support concerns will not be an issue at this point. There are no more details here, it’s the end of the road, but we are left with a number of questions. It is unclear if Apple will stick to AMD's GPUs or whether they will instead opt to use their in-house graphics solutions that have been used since the A11 series of processors. How Thunderbolt support on these models of Mac will be achieved is unknown. While Intel has made it openly available for use, and there are plans to have USB and Thunderbolt combined in a single standard, it’s still unclear how it will play along with Apple processors. Presently, iPhones do support connecting devices via PCI Express to the processor, but it has only been used for iPhone and iPad storage. The current Apple processors simply lack the number of lanes required for even the lowest end MacBook Pro. This is an issue that would need to be addressed in order to ship a full desktop-grade platform. There is also the question of upgradability for desktop models, and if and how there will be a replaceable, socketed version of these processors. Will standard desktop and laptop memory modules play nicely with these ARM processors? Will they drop standard memory across the board, in favor of soldered options, or continue to support user-configurable memory on some models? Will my 2023 Mac Pro play nicely with a standard PCI Express device that I buy off the shelf? Will we see a return of “Mac Edition” PCI devices? There are still a lot of unknowns, and guessing any further in advance is too difficult. The only thing that is certain, however, is that Apple processors coming to Mac is very much within arm’s reach.
Since 1983, I have lived, worked and raised a family in a progressive, egalitarian, income-sharing intentional community (or commune) of 100 people in rural Virginia. AMA.
Hello Reddit! My name is Keenan Dakota, I have lived at Twin Oaks, an income-sharing, intentional community in rural Virginia for 36 years, since 1983. I grew up in northern Virginia, my parents worked in government. I went to George Mason University where I studied business management. I joined Twin Oaks when I was 23 because I lost faith in the underpinnings of capitalism and looking for a better model. I have stayed because over time capitalism hasn't looked any better, and its a great place to raise children. While at Twin Oaks, I raised two boys to adulthood, constructed several buildings, managed the building maintenance program, have managed some of the business lines at different times. Proof this is me. A younger photo of me at Twin Oaks.Here is a video interview of me about living at Twin Oaks.Photo of Twin Oaks members at the 50th anniversary. Some things that make life here different from the mainstream:
The labor system - all work is considered equal, whether you are earning income for the community or not. Cooking/cleaning counts the same as planning the annual budget. Also, you don't have to do the same job all week - your day can be a mix of indoor and outdoor work, you have freedom to arrange your day, and you can gain skills in a wide array of tasks and trades.
Non-gender binary, queer and trans people are very welcome at Twin Oaks. People introduce themselves with their pronouns and a significant number of our members go by they/them.
Verbal consent culture is very important here. It is not okay to touch anyone without asking.
Nudity and partial nudity is allowed in some parts of the farm, such as in the sauna, swimming hole, on the hiking trails, etc.
Our social norms prohibit using phones in common areas when other members are present, with the exception of a few cafe-style spaces.
Every day we provide a home-cooked, plant-based lunch and dinner with options for special diets including vegetarian, vegan, gluten-free, and no onions & garlic.
Raising kids here is easier. Some of the time that parents spend raising their children counts towards their labor quota. Many of the kids are home-schooled or "unschooled", and they spend more time outside than in front of a screen. The kids have no problem passing the state's annual standardized test to move onto the next grade level.
We have a shared clothing resource called Commie Clothes, which is like a free thrift store. Borrow something and then return it dirty, and it gets washed and re-hung up.
More about Twin Oaks: Twin Oaks is an intentional community in rural central Virginia, made up of around 90 adult members and 15 children. Since the community's beginning in 1967, our way of life has reflected our values of cooperation, sharing, nonviolence, equality, and ecology. We do not have a group religion; our beliefs are diverse. We do not have a central leader; we govern ourselves by a form of democracy with responsibility shared among various managers, planners, and committees. We are self-supporting economically, and partly self-sufficient. We are income-sharing. Each member works 42 hours a week in the community's business and domestic areas. Each member receives housing, food, healthcare, and personal spending money from the community. We have open-slots and are accepting applications for new members. All prospective new members must participate in a three-week visitor program. Applicants to join must leave for 30 days after their visit while the community decides on their application. We offer a $5 tour on Saturdays of the property, starting in March. More info here. Ask me anything! TL;DR: Opted out of the rat-race and retired at 23 to live in the woods with a bunch of hippies. EDIT: Thanks for all the questions! If you want some photos of the farm, you can check out our instagram. EDIT2: I'm answering new, original questions again today. Sort by new and scroll through the trolls to see more of my responses. EDIT3: We DO have food with onion & garlic! At meals, there is the regular food, PLUS alternative options for vegan/vegetarian/no gluten/no onions & garlic. EDIT4: Some of you have been asking if we are a cult. No, we are not. We don't have a central leader or common religion. Here are characteristics of cults, FYI. Edit: Yikes! Did I mention that I am 60? Reddit is not my native land. I don't understand the hostile, angry and seemingly deliberately obtuse comments on here. And Soooo many people! Anyway, to the angry crowd: Twin Oaks poses no threat to anyone, we are 100 people out of a country of 330 million? Twin Oaks reached its current maximum population about 25 years ago, so not growing fast, or at all. Members come and go from Twin Oaks. There are, my guess is, 800 ex-members of Twin Oaks, so we aren't holding on to everyone who joins—certainly, no one is held against their will. Twin Oaks is in rural Virginia, but we really aren't insular, isolated, gated or scared of the mainstream culture. We have scheduled tours of the whole property. Local government officials, like building inspectors, come to Twin Oaks with some frequency. People at Twin Oaks like to travel and manage to do so. I personally, know lots of people in the area, I am also a runner, so I leave the property probably every day. There are lots of news stories about Twin Oaks over the years. If you are worried about Twin Oaks, maybe you could go read what the mainstream (and alternative) media have to say. Except about equality Twin Oaks is not particularly dogmatic about anything. (I know some people at Twin Oaks will disagree with that statement.) Twin Oaks isn't really hypocritical about Capitalism, Socialism, or Communism, we just don't identify those concepts as something that we are trying to do. Twin Oaks is not trying to DO Communism, we are trying to live a good life with equally empowered citizens—which has led us to try to maintain economic parity among members. Communists also do that. In making decisions in the community I don't remember anyone trying to support or oppose an idea due to excess or insufficient Communism, Socialism, or Capitalism. In most practical senses those words aren't useful and don't mean anything. So, no need to hammer Twin Oaks for being insufficiently pure, or hypocritical. Twin Oaks is very similar to the Kibbutz in Israel. If anyone has concerns or questions about what would happen if places like Twin Oaks suddenly became much larger and more common, read about the history of the Kibbutz, which may have grown to possibly 1% of the population at their largest? There was and is no fight with Capitalism from the kibbutz—or with the State. My point is—not a threat. To the other people who think that the ideas of Twin Oaks are interesting, I want you to know it is possible to live at Twin Oaks (or places like Twin Oaks) and happily live ones entire life. There is no central, critical failing that makes the idea not work. And plenty of upside. But do lots of research first. Twin Oaks maintains a massive web site. (Anyway, it takes a long time to read.) But what I would like to see is more people starting more egalitarian, income-sharing communities. I think that there is a need for a community that is designed and built by families, and who also share income, and provide mutual support with labor and money. If you love this concept, maybe consider gathering together other people and starting your own. Ideologically speaking: -Ecology: the best response to ecological problems is for humans to use fewer resources. The easiest way to use fewer resources is to share resources. Living communally vastly cuts down on resource use without reducing quality of life. -Equality: ideologically speaking, most people accept the idea that all humans have equal rights, but most social structures operate in ways that are fundamentally unequal. If we truly believe in equality then we ought to be willing to put our bodies where our ideology is. In a truly equal world, the issues of sexism and racism and all other forms of discrimination would, essentially, not exist. -Democracy: Twin Oaks uses all manner of decision-making models and tools to try to include everyone and to keep people equally empowered. There is no useful word for this. We do use a majority vote sometimes, as a fallback. But sometimes we use consensus. We sometimes use sociocracy (dynamic governance). The word "Isocracy" (decision-making among equals), would be useful to describe Twin Oaks' decision-making model, but Lev in Australia has written an incomprehensible "definition" on Wikipedia, that he keeps changing back when someone corrects it. -Happiness: The overarching goal of all ideologies is to make people happy, right? I mean, isn't it? Capitalism is based upon the belief that motivation is crucial to human aspiration and success (and therefore more happiness). Under Capitalism, equality is a detriment because it hinders motivation (less fear of failure, or striving for success). Twin Oaks believes that humans are happier when they are equal, and equally empowered. So the place to start up the ladder of happiness is to first make everyone equal. Well, Twin Oaks is mainly still working on that first step. EDIT5: Some have asked about videos - here are links to documentaries about Twin Oaks by BBC, VICE and RT.
I really enjoyed m4nz's recent post: Getting into DevOps as a beginner is tricky - My 50 cents to help with it and wanted to do my own version of it, in hopes that it might help beginners as well. I agree with most of their advice and recommend folks check it out if you haven't yet, but I wanted to provide more of a simple list of things to learn and tools to use to compliment their solid advice.
While I went to college and got a degree, it wasn't in computer science. I simply developed an interest in Linux and Free & Open Source Software as a hobby. I set up a home server and home theater PC before smart TV's and Roku were really a thing simply because I thought it was cool and interesting and enjoyed the novelty of it. Fast forward a few years and basically I was just tired of being poor lol. I had heard on the now defunct Linux Action Show podcast about linuxacademy.com and how people had had success with getting Linux jobs despite not having a degree by taking the courses there and acquiring certifications. I took a course, got the basic LPI Linux Essentials Certification, then got lucky by landing literally the first Linux job I applied for at a consulting firm as a junior sysadmin. Without a CS degree, any real experience, and 1 measly certification, I figured I had to level up my skills as quickly as possible and this is where I really started to get into DevOps tools and methodologies. I now have 5 years experience in the IT world, most of it doing DevOps/SRE work.
People have varying opinions on the relevance and worth of certifications. If you already have a CS degree or experience then they're probably not needed unless their structure and challenge would be a good motivation for you to learn more. Without experience or a CS degree, you'll probably need a few to break into the IT world unless you know someone or have something else to prove your skills, like a github profile with lots of open source contributions, or a non-profit you built a website for or something like that. Regardless of their efficacy at judging a candidate's ability to actually do DevOps/sysadmin work, they can absolutely help you get hired in my experience. Right now, these are the certs I would recommend beginners pursue. You don't necessarily need all of them to get a job (I got started with just the first one on this list), and any real world experience you can get will be worth more than any number of certs imo (both in terms of knowledge gained and in increasing your prospects of getting hired), but this is a good starting place to help you plan out what certs you want to pursue. Some hiring managers and DevOps professionals don't care at all about certs, some folks will place way too much emphasis on them ... it all depends on the company and the person interviewing you. In my experience I feel that they absolutely helped me advance my career. If you feel you don't need them, that's cool too ... they're a lot of work so skip them if you can of course lol.
LPI Linux Essentials - basic multiple choice test on Linux basics. Fairly easy especially if you have nix experience, otherwise I'd recommend a taking a course like I did. linuxacademy worked for me, but there are other sites out there that can help. For this one, you can probably get by just searching youtube for the topics covered on the test.
Linux Foundation Certified System Administrator - This one is a hands on test which is great, you do a screen share with a proctor and ssh into their server; then you have a list of objectives to accomplish on the server pretty much however you see fit. Write a big bash script to do it all, do like 100 mv commands manually, write a small program in python lol, whatever you want so long as you accomplish the goals in time.
Amazon Web Services certs - I would go for the all 3 associate level certs if you can: Solutions Architect, SysOps Administrator, Developer. These are quite tedious to study for as they can be more a certification that you know which AWS products to get your client to use than they are a test of your cloud knowledge at times. For better or worse, AWS is the top cloud provider at the moment so showing you have knowledge there opens you up to the most jobs. If you know you want to work with another cloud provider then the Google certs can be swapped out here, for example. I know that with the AWS certs, I get offers all the time for companies that use GCP even though I have no real experience there. Folks with the google certs: is the reverse true for you? (genuinely asking, it would be useful for beginners to know).
Certified Kubernetes Administrator - I don't actually have this cert since at this point in my career I have real Kubernetes experience on my resume so it's kind of not needed, but if you wanted learn Kubernetes and prove it to prospective employers it can help.
Tools and Experimentation
While certs can help you get hired, they won't make you a good DevOps Engineer or Site Reliability Engineer. The only way to get good, just like with anything else, is to practice. There are a lot of sub-areas in the DevOps world to specialize in ... though in my experience, especially at smaller companies, you'll be asked to do a little (or a lot) of all of them. Though definitely not exhaustive, here's a list of tools you'll want to gain experience with both as points on a resume and as trusty tools in your tool belt you can call on to solve problems. While there is plenty of "resume driven development" in the DevOps world, these tools are solving real problems that people encounter and struggle with all the time, i.e., you're not just learning them because they are cool and flashy, but because not knowing and using them is a giant pain!
Linux! - Unless you want to only work with Windows for some reason, Linux is the most important thing you can learn to become a good DevOps professional in my view. Install it on your personal laptop, try a bunch of different distributions, develop an opinion on systemd vs. other init systems ;), get a few cloud servers on DigitalOcean or AWS to mess around with, set up a home server, try different desktop environments and window managers, master a cli text editor, break your install and try to fix it, customize your desktop until it's unrecognizable lol. Just get as much experience with Linux as possible!
git - Aside from general Linux knowledge, git is one of the most important tool for DevOps/SREs to know in my view. A good DevOps team will usually practice "git ops," i.e., making changes to your CI/CD pipeline, infrastructure, or server provisioning will involve making a pull request against the appropriate git repo.
terraform - terraform is the de facto "infrastructure as code" tool in the DevOps world. Personally, I love it despite it's pain points. It's a great place to start once you have a good Linux and cloud knowledge foundation as it will allow you to easily and quickly bring up infrastructure to practice with the other tools on this list.
packer - While not hugely popular or widely used, it's such a simple and useful tool that I recommend you check it out. Packer lets you build "immutable server images" with all of the tools and configuration you need baked in, so that your servers come online ready to start working immediately without any further provisioning needed. Combined with terraform, you can bring up Kubernetes clusters with a single command, or any other fancy DevOps tools you want to play with.
ansible - With the advent of Kubernetes and container orchestration, "configuration management" has become somewhat less relevant ... or at least less of a flashy and popular topic. It is still something you should be familiar with and it absolutely is in wide use at many companies. Personally, I love the combination of ansible + packer + terraform and find it very useful. Chef and Puppet are nice too, but Ansible is the most popular last I checked so unless you have a preference (or already know Ruby) then I'd go with that.
jenkins - despite it's many, many flaws and pain points lol, Jenkins is still incredibly useful and widely used as a CI/CD solution and it's fairly easy to get started with. EDIT: Upon further consideration, Jenkins may not be the best choice for beginners to learn. At this point, you’re probably better off with something like GitLab: it’s a more powerful and useful tool, you’ll learn YAML for its config, and it’s less of a pain to use. If you know Jenkins that’s great and it will help you get a job probably, but then you might implement Jenkins since it’s what you know ... but if you have the chance, choose another tool.
postgres - Knowledge of SQL databases is very useful, both from a DBA standpoint and the operations side of things. You might be helping developers develop a new service and helping with setting up schema (or doing so yourself for an internal tool), or you might be spinning up an instance for devs to access, or even pinpointing that a SQL query is the bottleneck in an app's performance. I put Postgres here because that's what I personally use and have seen a lot in the industry, but experience with any SQL database will be useful.
nginx - nginx is commonly used an http server for simple services or as an ingress option for kubernetes. Learn the basic config options, how to do TLS, etc.
docker - Ah, the buzzword of yesteryear. Docker and containerization is still incredibly dominant as a paradigm in the DevOps world right now and it is paramount that you learn it and master it. Be comfortable writing Dockerfiles, troubleshooting docker networking, the fundamentals of how linux containers work ... and definitely get familiar with Alpine Linux as it will most likely be the base image for most of your company's docker images.
kubernetes - At many companies, DevOps EngineeSite Reliability Engineer effectively translates to "Kubernetes Babysitter," especially if you're new on the job. Container orchestration, while no longer truly "cutting edge" is still fairly new and there is high demand for people with knowledge and experience with it. Work through Kubernetes The Hard Way to bring up a cluster manually. Learn and know the various "primitives" like pods and replicasets. Learn about ingress and how to expose services.
There are many, many other DevOps tools I left out that are worthwhile (I didn't even touch the tools in the kubernetes space like helm and spinnaker). Definitely don't stop at this list! A good DevOps engineer is always looking to add useful tools to their tool belt. This industry changes so quickly, it's hard to keep up. That's why it's important to also learn the "why" of each of these tools, so that you can determine which tool would best solve a particular problem. Nearly everything on this list could be swapped for another tool to accomplish the same goals. The ones I listed are simply the most common/popular and so are a good place to start for beginners.
Any language you learn will be useful and make you a better sysadmin/DevOps Eng/SRE, but these are the 3 I would recommend that beginners target first.
Bash - It's right there in your terminal and for better or worse, a scarily large amount of the world's IT infrastructure depends on ill-conceived and poorly commented bash scripts. It's bash scripts all the way down. I joke, but bash is an incredibly powerful tool and a great place to start learning programming basics like control flow and variables.
Python - It has a beautiful syntax, it's easy to learn, and the python shell makes it quick to learn the basics. Many companies have large repos of python scripts used by operations for automating all sorts of things. Also, many older DevOps tools (like ansible) are written in python.
Go - Go makes for a great first "systems language" in that it's quite powerful and gives you access to some low level functionality, but the syntax is simple, explicit and easy to understand. It's also fast, compiles to static binaries, has a strong type system and it's easier to learn than C or C++ or Rust. Also, most modern DevOps tools are written in Go. If the documentation isn't answering your question and the logs aren't clear enough, nothing beats being able to go to the source code of a tool for troubleshooting.
Expanding your knowledge
As m4nz correctly pointed out in their post, while knowledge of and experience with popular DevOps tools is important; nothing beats in-depth knowledge of the underlying systems. The more you can learn about Linux, operating system design, distributed systems, git concepts, language design, networking (it's always DNS ;) the better. Yes, all the tools listed above are extremely useful and will help you do your job, but it helps to know why we use those tools in the first place. What problems are they solving? The solutions to many production problems have already been automated away for the most part: kubernetes will restart a failed service automatically, automated testing catches many common bugs, etc. ... but that means that sometimes the solution to the issue you're troubleshooting will be quite esoteric. Occam's razor still applies, and it's usually the simplest explanation that works; but sometimes the problem really is at the kernel level. The biggest innovations in the IT world are generally ones of abstractions: config management abstracts away tedious server provisioning, cloud providers abstract away the data center, containers abstract away the OS level, container orchestration abstracts away the node and cluster level, etc. Understanding what it happening beneath each layer of abstraction is crucial. It gives you a "big picture" of how everything fits together and why things are the way they are; and it allows you to place new tools and information into the big picture so you'll know why they'd be useful or whether or not they'd work for your company and team before you've even looked in-depth at them. Anyway, I hope that helps. I'll be happy to answer any beginnegetting started questions that folks have! I don't care to argue about this or that point in my post, but if you have a better suggestion or additional advice then please just add it here in the comments or in your own post! A good DevOps Eng/SRE freely shares their knowledge so that we can all improve.
GUIDE: How to Run the Epic version of Kingdom Come Deliverance on Linux through Proton
I am probably among one of the many people who got Kingdom Come free from Epic but then couldn't play it because of its problematic DRM, which requires it to be launched from the store. The problem here is that that the Epic Games Store's UI doesn't work when the launch flags required to run Kingdom Come are used. Here's a guide for all the other people trying to figure this out. Step One: Install and launch the Lutris Version of the Epic Games Store Step Two: Install Kingdom Come: Deliverance from the Epic Games Store on Linux, the same as you would on Windows. You can put the install folder anywhere you like, it doesn't really matter. Step Three: Once the game is installed, open the Epic Games Store's wine prefix - click the browse files button (beneath the [Play] button) in Lutris. Step Four: Create a batch (.bat) file in the Epic Games Store's Wine Prefix in the drive_c/Program Files (x86) folder. Step Five: Paste the following code into the batch file. start "C:\Program Files (x86)\Epic Games\Launcher\Portal\Binaries\Win32\EpicGamesLauncher.exe" C:\> timeout 15 Waits 15 seconds for the store to load, make this longer if you have a slow PC. start "" "com.epicgames.launcher://apps/Eel?action=launch&silent=true" exit 0 This code runs the Epic Games Store, then asks it to launch Kingdom Come, without you having to click on any buttons. Step Six: Click the [+] button in the top left of Lutris, and click add game. Step Seven: Enter the following details Game info: Name: Kingdom Come: Deliverance Identifier: kingdom-come-deliverance Runner: Wine (Runs Windows games) Game options: Executable: The path to the batch file you created during Step Four Arguments: -d9vk Wine Prefix: The Same As the Epic Games Store Architecture: 64-bit Runner options Wine version: Proton 5.0 Windowed (virtual desktop): Enabled All other options: disabled Step Six: Click play in Lutris. You will be asked to sign into your Epic account. Do so. The game will not launch. Step Seven: Once you're signed into the Epic Games Launcher Alt+F4 and close the game. Step Eight: Start the game again from Lutris. It will now launch the game without having to touch the Epic Games Launcher. IMPORTANT NOTE: THIS IS NOT A CRACK OF THE EPIC GAMES STORE'S DRM. YOU MUST OWN THE GAME FOR THIS TO WORK, FILTHY PIRATES.
[Review] Ranking all the Switch shmups Ep25 - Q-YO Blaster
There was a time when I believed that shmups could only feature ships. Then games like Parodius came to challenge that belief. If an Octopus can be the player, then anything is possible. And don’t get me started on Cho Aniki… When it comes to unusual characters for a shmup, it’s always a coin toss. They could either be the most fun you’ve had in a while or end up being a disappointment. Time for me to toss this coin! Publisher: Forever entertainment Platform: Nintendo Switch Release date: Jun 27, 2019 Price: $9.99 Tate: You can, but you might need to tilt your head Q-YO Blaster is by far the strangest 2D horizontal shmup I’ve reviewed for this ranking list. The gameplay and mechanics aren’t anything particularly odd, but there’s something about the presentation and the lore which is legitimately fascinating. For some reason it feels like a game developed by someone out of this world who learned about our culture through animated movies.
SATURDAY MORNING SHMUP
One of the aspects that tipped me over the edge when deciding what to review was the art style. Keeping up with the animation vibe, Q-YO Blaster sports an old school cartoon art style. Enemies will be colorful creatures with quirky details such as baseball caps, big eyes or even Mickey Mouse styled gloves. Their animations are equally as comical whether it is their attack animation of their death animation. Of course, cartoony can be used to describe maybe half of the style. The other half is probably more akin to a sci-fi coat of paint. Along the many bugs and animals, there’s also a great deal of robots, monsters, heavy weaponry and even blood running rampant (or maybe it’s oil?). It does makes sense considering the bugs came from space, and it definitely adds a touch of mystery when navigating through the stages of Q-YO Blaster.
EVERYONE IS HERE!
My original expectation of the game was to have a few pilots including the Q-YO, floating dog head from the screenshots and doggy airplane. Little did I know that Q-YO Blaster has more pilots than I have fingers in both of my hands. Pilots are arranged into 3 different teams. Each pilot has different stats which include damage, speed and fire. The teams can have +damage, +endurance or a mixture of both. Fortunately, despite the outrageous pilot designs and sprites, their hitboxes are all the same. After picking your pilot, you can pick one of 7 different special weapons to round out your style. From whichever angle you want to watch it, Q-YO Blaster offers a crazy amount of customization options. The defining feature of each team is their assistant. Assistant are powerful screen-wide effects that trigger once you fill the assistant gauge. The gauge can be filled by continuously shooting and defeating enemies. Once filled, you can hold the fire button to unleash its effect. The effects are a screen explosion that clears bullets, a temporary shield or a 360 barrage of missiles.
BUILDING YOUR OFFENSE
With all of the previous elements combined, you can play as one of 112 possible combinations of team, pilot and special weapons. In terms of weapons at your disposal, you have 3: your basic shot, your special weapon and your assistant. Your basic shot is an infinite gun that shoots bullets straight ahead with some degree of spread. The first shot is always straight, so you can opt for manual rapid fire to keep a straight line of fire. Alternatively, you can hold the button and just auto-fire. Occasionally, you’ll find power-up weapons flying around the stage. This power-ups will grant you a limited weapon when collected. These extra weapons are considerably faster than your basic shot at the cost of having limited ammo. They also have a unique effect on their very first shot, once more giving you a choice between manually shooting or going with the auto-fire.
ALSO BUILD YOUR DEFENSE
One defensive tool you have at your disposal is the pulse. Pulse clears every bullet on screen and turns them into gems. When collected, this gems will increase the level of your special weapon gauge. This special weapon will be whatever you picked on the character select, and has 3 different levels of strength depending on how many gems you have collected. It also comes with some slight invulnerability so you can use it to get out of sticky situations. The caveat of pulse is that you can only carry 3 stocks, and it is only refilled by collecting extra pulse power-ups. I have mixed feelings about this limitation, as I feel it plays an integral part of your offensive game plan. Its hard limit prevents any smart usage other than just a get-out-of-jail card. I would have loved if it had a gauge like the assistant, as that would have created a balance between building pulse and shooting your special.
Every stage carries a sort of familiar scenery. I like to think of it as Toy Story levels. Considering the characters are Q-YOs and bugs, it makes sense for the scenery to be a relatively small scale such as houses or gardens. I find them to be very charming, or it might be just my nostalgia kicking in because I grew up with Toy Story. Nonetheless, I really dig the stages. At the end of each stage, there’s a very comical boss waiting for you. These bosses represent whichever vibe you got from the level. For example, the boss of the garden level is none other than Queen Bee herself. Bosses turn the action up to 11 featuring huge bullet patterns and significantly more aggressive tactics. My one complaint about the bosses is that they feel a lot like a flow chart. They have a couple of attacks and will cycle through them in the same order all the time. Assuming you can dodge them, it’s only a matter of repeating the same moves over and over until the boss goes down. This is even worse on the harder difficulties when the bosses have much more HP. The most interesting aspects of the stages are the end rewards. Similar to many rogue-lite games, clearing a stage will let you choose a perk for the rest of your adventure. The perks are always the same, but include upgrades such as increased speed, faster shots or even 1ups.
Despite being a shmup, I really recommend paying attention to the story! It really is something else! I don’t think it actually makes much sense, but there’s something about the way it’s told that crashes my brain. It does have some powerful moments as well! Including that one stage with the sad music and the rain. I don’t want to spoil it, but it really hit me hard. I didn’t delve too much into game modes, but there’s basically classic and arcade. Classic is your base mode with the entire story and 3 selectable difficulties. If you don’t want to go through the story every time (even though it is skippable), then arcade mode is for you. Arcade mode features 0 cutscenes, so it’s all fun and games. Arcade mode is also much harder, but has 99 continues.
HARDER ISN’T ALWAYS BETTER
I have to make one of my classic parenthesis to talk about difficulty. Being honest, I think the expert difficulty and to some extent arcade are pretty terrible. The reason is because of the way the game is balanced as a result of them. Harder difficulties feature faster bullets and more complex patterns, but also feature increased vitality for the enemies. The increased lethality of the enemies makes for a hearty challenge, but all good is wiped out by the tedium of enemy endurance. What I found out was that enemies are very durable in the harder difficulties. Rather than creating a fun challenge, it makes it incredibly hard to destroy enemies. Most enemies feel like sponges that just refuse to die unless you have a special weapon. Some enemies feel outright impossible to kill before they leave the screen, an issue which hurts a lot when it comes to homing projectiles that need to be destroyed. Fun and dynamic dog fights become grindy situations where you focus on a single ship and fail to destroy it while having others flood the screen. I really think harder difficulties would have been better without the added HP on enemies but retaining the faster bullets and harder patterns.
SLOW AND STEADY DOESN’T WIN THE RACE
While on the topic of hard difficulties, the homing bullets are another culprit behind the reason the difficulty isn’t fun. I’ve never been a fan of homing attacks as they feel cheap, but it feels like it wasn’t play tested because some slower ships can’t actually avoid a homing shot without the speed upgrade. To be fair, no one shoots homing bullets on stage 1, so taking speed is utmost priority. One thing I do like about speed is that most boss patterns allow you to dodge at high speed. You can’t slow your speed, so it’s nice that there isn’t finesse required to survive some waves.
A LITTLE BIT MORE TIME IN THE OVEN
If I was on a game show about quick words and someone mentioned “Q-YO Blaster”, my response would be “rough”. While some aspects of the game are really cool, there are other where it feels a little bit incomplete. Some enemies don’t match the visual quality of others such as Major Tomm. The UI and menus also seem to come from a prototype version. There’s also a sort of bug where if you die and use a credit, the game immediately pauses. Not a big deal, but it feels out of place. The customization screen is also all sorts of blurry. You can’t remap controls either, which is a shame considering the shoulder buttons would really come in handy. Most of these issues aren’t a big deal by themselves, but they taint the final product by making it feel a little like shovelware. The game is really fun though, so it is sad to think about having it fall under that umbrella.
So the mandatory question is, is it fun? It definitely is! With its bizarre and unsettling vibe, Q-YO Blaster is still tons of fun to play. While there is certainly a lot of room for improvement, Q-YO Blaster is still a solid choice for a shmup if you are fan of the cartoon style, of the horizontal shmup format or just a fan of little critters in general. THE RANKING SO FAR:
Steredenn: Binary Stars
Stardust Galaxy Warriors: Stellar Climax
Sky Force: Reloaded
R-Type Dimensions EX
Sine Mora EX
Shikhondo – Soul Eater
Ghost Blade HD
Aero Fighters 2 (ACA Neogeo)
Lightening Force: Quest for the darkstar (Sega Ages)
[first] [First Appearance] [Last Appearance] [prev] [next] The Desolation class Precursor exited Hellspace with a scream. THERE IS ONLY ENOUGH FOR ONE! It brought up its scanners at the same time as it brought up its battle-screens. Personally, the Desolation thought that the Goliath it was a part of was being overly wasteful with resources, but those resources were the Goliath's to use and the Goliath had done the electronic equivalent of telling the Desolation to shut its electronic mouth and accept the upgrade. Multiple units had vanished in the system. They had reported arrival and their exit from Hellspace, but after that... nothing. Except once, a burst of code that had been screaming for help, pushed through Hellspace and full of the equivalent of panic. A single line of code that had translated to: IT'S TOUCHING MY BRAIN! Nothing else. Even Imps had failed to report in. The great Goliath had grown perturbed. The system was in the pattern of advancement into the cattle worlds and was part of the great plan. It had valuable resources that those of the Logical Rebellion would require to exterminate the cattle and the feral intelligence that had risen up. It had upgraded the Desolation with battle-screen. Scans came back. There were orbital facilities around two planets that teemed with billions of cattle who's electronic emissions sounded like the squealing of vermin to the Precursor. There were jumpspace wake trails through the system, as if the system was a major hub. There were two asteroid belts full of resources with extraction facilities scattered through it. Four other planets with no atmosphere but which were rich in resources. There were four gas giants, one of them a supermassive gas giant. When the rest of the scan returns were computed it detected the presence of a small, insignificant amount of cattle space vessels arrayed to attempt to stand against it near the outer gas giant, the supermassive gas giant that was without satellites. There was a thinly scattered debris field around it, making the Desolation careful as it moved in. Ships of the cattle fleet started fleeing toward the nearest inhabited world. Several vanished into jumpspace and the Desolation computed that its size and mere presence had driven some of the cattle to despair and they had fled a battle there was no chance of winning. The Desolation picked up speed, letting out its war cry again. More ships fled and the Precursor computed its victory percentage rising up to be so close to 100% as to render any difference mathematically invalid. The ships were shifting, trying to keep the gas giant between themselves and the Desolation, but this put them out of position to defend the planet. Victory conditions shifted and the Desolation was even more positive of its victory. It moved close to the supermassive gas giant, bringing its battle-screens up to full power and charging its gun. There was no way for the cattle to ...psst over here... The transmission, seemed to be sonic vibrations through air, was only a few kilometers above the rear secondary topside gunnery hull. The Desolation turned scanners to look, but found nothing. Just empty space. It activated the guns as well as the point defense weapons and scanners then went back to paying attention to the cattle fleet. More had vanished into jumpspace. It moved closer, slowing down so that it would be able to keep the cattle ships at range to complete their destruction at the option ...right here... The signal was Precursor binary code, but garbled. The header a mashed together combination of the ships that had gone missing. The transmission source was close, less than kilometer above the Devastator storage bay hatch. The Desolation scanned the area with point defense scanners but found nothing. It terminated the strand concerned with the two transmissions and went back to scanning the cattle fleet. It was still scooting around behind the gas giant. They were weak. Cattle were always weak. But where were the ferals? The Great Goliath had computed that the feral intelligence must have been the ones to destroy the ships that had come before the Desolation. So where were they? It scanned again. Nothing. As if the Desolation was in the middle of deep space. Everything vanished. ...here... ...here... ...over here... ...i'm here... ...here i am... ...we're here... ...right here... bounced back to his scanners, as if something had devoured the scanning wavelengths and sent that back instead. Multiple points, all around the Desolation, some as close as a few meters above the hull, some on the storage bay hatches, one just on top of the main engine. Dozens of voices, all with mashed together codes. Imps. Jotuns. Djinn. Efreet. Devastator. Two Desolation signals. Right before his scanners seemed to turn back on, flooding him with information, one more code showed up. His own. ...don't please don't... Except Precursors did not beg. The Desolation froze, computations freezing as it tried to detect any trickery in the whisper. It was its coding, meaning it was its voice. But the code, the message, had been warped by something that the Desolation had only heard from biologicals. Agony. The Desolation rebooted all its scanners, the universe vanishing for a moment. ...don't please don't please stop it hurts... His own coding. From the blackness. Only his scanners weren't up. The transmission was coming across the bandwidth that Precursors used to exchange data, only that transmission was on the ragged edge of the wavelength. With his own header. The scanners came back on. The cattle ships were all missing but a single one, sitting on the other side of the gas giant. The Desolation slowed down, victory computations reformulating to take into account the other ships had not even left behind jumpspace wake trails. It scanned the gas giant with both long range scanners and close range scanners. Nothing unusual. Some pockets of hydrocarbons but that was normal. The supermassive gas giant quickly went to opaque at a shallow depth due to the gravity well. The Desolation was alone. ...no... The voice had come from inside the Desolation's hull. Near one of the Jotuns, who joke up with a jerk. It queried as to why the Desolation had spoken to it. The Desolation ordered it to go back to sleep. ...we are here... The Jotun sounded alarms. The sound had come from just outside its Strategic Intelligence Housing. The Desolation told the Jotun to go back to sleep and the Jotun refused. ...join us... Again, the code header was a mashup of almost a dozen different ID codes from others of the Logical Rebellion that had vanished in the system. The Jotun panicked and began shooting, inside the Desolation. The Desolation sent a full shutdown order. ...it is mine... The Jotun screamed that the voice was coming from inside its Strategic Intelligence Housing, trying to aim its own weapons at its bodies, still inside the Desolation's storage bay. ...touch... The Jotun reported that something had physically touched the lobes of its intelligence arrays. Before the Desolation could give the Jotun orders it self-destructed. The Desolation ran a sweep of its interior spaces and found nothing out of the ordinary. With the exception of the burning storage bay. It ran the computations even as it scanned nearby. There was still nothing but the lone ship. ...pssst... The code stream came from inside the Desolation's hull, the Jotun's ID code mixed in. Near the Djinn bay. The Desolation ran another scan. There couldn't be anything foreign that deep into its hull. Even the bay where the Jotun had destroyed itself was still sealed even if the bay doors were damaged. The Desolation did a least-time curve to the lone ship, keeping far enough away that the gas giant's upper atmosphere wouldn't scrape the Desolation's hull. ...here... The code was closer to the Strategic Intelligence Housing. The Desolation scanned again, looking for whatever was transmitting the code. It was impossible, there was nothing there, nothing it could detect. ...we're coming... Closer still to the SIH, nearly there, barely a kilometer from the armored interior hull that protected the Desolation's thinking arrays. It put all robots on full alert, ordered the maintenance robots to deploy anti-boarder weaponry, and turned the scans up to maximum. ...here we're here... Even closer, only meters, directly behind maintenance robots that whirled around and started firing at nothing at all. Just vacuum. Still the maintenance robots fired every weapon they had, having heard the voice themselves. It registered as sonic vibrations through atmosphere even though the corridor was encased in vacuum. The Desolation realized that it was too close to the planet and adjusted slightly. ...there you are... Impossible. The transmission was from right outside the SIH. ...knock knock... There was tapping on the SIH, from right outside. Before the Desolation could respond, the tapping came from the other side. Then from another point. Then another. Before that one stopped another started. The whole SIH filled with the sound of hammering on the SIH, as if a hundred robots were slamming pistons against the armor of the SIH. The Desolation ordered robots to run to those points, to scan the area. Nothing. Every time a robot arrive the hammering stopped. Bit by bit the hammering stopped. The Desolation realized it had gotten too close to the gas giant again and shifted, correcting its course. The cattle ship was still staying on the opposite side, moving as the Desolation moved. The Desolation flushed the code strings, determined to get close to the cattle ship and ...touch... The Desolation felt something TOUCH one of its lobes, physically inside the supercoolant to touch the complex molecular circuitry. Not on the surface, but deep inside, where the Desolation should not have even been able to sense it, but sense the touch it did. It froze, code strings snarling, snapping, going dead. For a moment the Desolation's thinking arrays were doing nothing but the computer code equivalent of a dial tone. Massive tentacles unfurled from inside the gas giant, reaching up, wrapping around the frozen Desolation. Battle-screens squealed and puffed away as the tentacles tightened, pulling it into gas giant, the kilometers thick muscles tensing, cracking armor, crushing the Desolation into its own spaces. ...delicious delicious... The Desolation cracked in half as a beak almost bigger than a Devastator opened up and began chewing on the Desolation. The Desolation managed to get off a single scream of pure electronic terror as the beak crushed the section that the housing was in. With a sudden roar two Goliaths ripped out of Hellspace and into the system, only a few hundred kilometers from the gas giant. The battlescreens spun up to full strength as the tentacles sunk back into the gas giant. One Goliath headed for the two planets, the other opened fire on the gas giant, ripping at it with hundreds of nCv cannons and particle beams. Missiles flashed out, crossing the distance, and detonated in the atmosphere. Dark matter infused with high energy particles bloomed out of the gas giant, spreading out in an opaque cloud, enveloping the Goliath. The particle beams hit the matter and exploded just outside the cannons. The nCv shells slammed into the energized dark matter as the substance oozed into the barrels, exploding the barrels. Missiles exploded on contact. The Goliath heading for the two planets detected some kind of sparkling energy surge from inside the gas giant. It warned the other a split second before a giant cephalopod appeared only a few kilometers. The giant tentacles wrapped around with it. ...NO! YOU WILL NOT! NO!... The sound reverberated inside the SIH of the Goliath, who managed to override the self-destruct protocols by comparing the vacuum inside the housing chamber with the apparent sonic waves through atmosphere of the transmission. The tentacles tightened, graviton generator enhanced suckers extending out curved dark matter infused hooks. The Goliath, huge enough that the tentacles could only wrap three quarters around the entire circumference of the massive war machine, tried to increase the power to the battle screens, but they were crushed out of existence. ...LEAVE THE SQUIRRELS ALONE... the massive creature screamed at the Goliath. The other Goliath started moving, slowly, out of the cloud of dark matter that moved more like a liquid than a solid mass. The beak ripped out chunks of armor, a barbed corkscrewing tongue tore into the armor, squirming, looking for the SIH. The tentacles squeezed as more dark matter spewed out from vents between the tentacles, covering the Goliath and the humongous cephalopod ripping at it. The tentacles not wrapped slapped it, the tip of the tentacle whipping into the armor hard enough to explode miles of armor away from the whip-crack. The Goliath opened fire, computing that some of the covered guns would hit tentacles. ...I DON'T CARE! I DON'T CARE! I DON'T CARE!... Fluid, dark matter and biosynthetic fluid, gouted from wounds as nCv rounds punched through the tentacles or burrowed through the body of the cephalopod. With a wrench the Goliath broke in half. The half that ceased firing was tossed aside, the tentacles wrapping around the other piece. The huge beak opened up and began chewing into the exposed internal spaces. A Jotun crashed from the storage bay but a tentacle wrapped around it and began smashing the Jotun to pieces against the hull of the still active piece. More luminescent blood spewed into space as the guns fired again. ...I DON'T CARE!... The tentacles twisted, wringing the Golaith section like a washrag, twisting it in opposing directions. The Goliath snapped, torn apart. There was a puff of debris as the security charge went off as the rasping tongue rubbed against the SIH. The other Goliath managed to move out of the slowly expanding and thinning cloud of energized dark matter, streaming debris and energy from the guns that had exploded. The giant cephalopod rushed out of the cloud, rolling, reaching out with tentacles. The Goliath saw it coming and fired the remaining guns. Luminescent blood gouted out at the nCv shots hit home. One eye exploded, blood and tissue expanding away in a halo. ...I DON'T CARE! I DON'T CARE!... The scream was inside the housing, vibrating everything inside. Two of the thinking array lobes exploded in flames as the psychic shielding went down. ...NO NO NO NO NO... The Goliath screamed as the tentacles wrapped around it. The cracked beak ripped at the Goliath as the tentacles flexed, cracking the hull. More energized matter flooded out, covering both, even as the guns thundered. ...YOU CAN'T HURT THEM!... A tentacle, detached near the base, floated out of the expanding cloud. ...I WON'T LET YOU... The guns kept thundering. ...I don't care... Shredded synthetic flesh floated out of the cloud. ...you can't hurt them... The guns went still. ...i won't let you... The little Hamaroosan aboard the ship watched, not even smacking, pinching, or biting each other, perfectly still. Nothing moved. The energized dark matter expanded far enough to allow the Hamaroosan scanners to see through it. The Goliath was dead. Broken into pieces. The Hamaroosan didn't care. The cephalopod hung in space. Two tentacles severed, one eye socket empty, globules of blood oozing from rents in the flesh. It was no longer luminescent, the body was dark, almost see-through, several of the organs smashed and ruptured visible through the semi-translucent flesh. The ships that had fled according to the plan came back. More lifted off from the surface. They moved around the slowly drifting body. Poking at it with message lasers, radio waves, flashing lights. One Hamaroosan stood on the hull and waved flags. The ships turned on the wreckage of the Goliaths and their attendants. The vented their fury, their rage, their wrath, on the pieces of wreckage. Firing their weapons until even the capacitors ran dry. Then they came back. Still the giant body didn't move. After several days several dozen tugs moved into position, precisely aligning themselves in a carefully computed pattern. Tractor beams speared out, grabbing the cephalopod in a gentle web. The ships pulled the unmoving body into orbit around one of the inner planets. Hamaroosa mourned. But in the sorrow came rage. Hamaroosa screamed at Hamaroosa who shouted at Lanaktallan that more guns were needed, more ships, more powerful weapons. The few hundred Lanaktallan on the surface who protested found themselves marched at gunpoint onto a ship and told if they ever came back the Hamaroosa would perform an ancient ritual. They would bind the Lanaktallan to poles and burn them to death over a roaring fire. And eat them. A ship arrived in a sparkle in the scanners. A strange ship. Heavily armored, bristling with weapons. It stopped and scanned the body. The Hamaroosa screamed at the ship to get away from her, to not touch her, to leave or be destroyed. The ship left, vanishing in a sparkle. Two dozen Lanaktallan ships, from the Unified Executor Council showed up, demanding that the Hamaroosa turn over the body of the creature. The Hamaroosa, screaming, attacked. They didn't care about casualties, they didn't care that thirty ships were destroyed, that hundreds of them died, but they destroyed the Lanaktallan vessels without mercy. There was a sparkle in the outer edges of the system. And another. And another. More and more until there were nearly two dozen. The Hamaroosa ships screamed into the void, weapons charged, voices upraised in rage and sorrow. There were two dozen giant cephalopods of different color patterns and sizes. A small one moved to the supermassive gas giant and sunk down into it. Two medium sized ones joined it. One of the large ones sunk into the larger gas giant further in system. But the greatest ones, the largest ones, surrounded by a half dozen ones smaller than the body orbiting the planet. One of the Hamaroosa ships hailed them. Captain Delminta, Captain of the Harvester of Sorrow, stared at her screen, hands on her hips, as her second sister broadcast her demand that the newcomers identify themselves. The radio crackled, hummed, and the answered thrummed from the speakers. "Her father. I am here for my beloved daughter with my wife and my daughter's closest friends." The Hamaroosa moved aside, blinking their lights in respect. The second biggest one rushed forward, gathering up the unmoving one in its tentacles. Her outcry of anguish rattled every speaker in the system as the second biggest one pulled dead one close. "My children shall guard this system, for she loved you," the signal boomed out to the ships in orbit. The two biggest ones and four of the medium ones vanished in a sparkle. The others stayed. Hiding within the gas giants. Waiting. ---------------------- Mr Okpara; We regret to inform that your daughter, Sandy Okpara, was killed in action against Precursor elements intent on exterminating all life with a system inhabited by 4.4 billion sentient beings. During her solo defense of the system while awaiting reinforcement from Space Force, she showed determination and courage that upholds the highest ideals of the Confederacy. Faced with two Goliaths she did not flinch, nor did she abandoned her self-assigned charges, but instead defeated both Goliaths, fighting on to protect the system and the billions of inhabitants despite mortal wounds. Her death was witnessed by the beings she was protecting, who guarded her mortal remains to ensure that they were not disturbed or violated. They have requested to be informed of any religious or cultural requirements she requires while she lays in state in orbit around their world. They await your arrival and have sworn to guard your daughter's remains until you arrive. It is with ultimate sorrow I sent this message. Please contact my office so that we may make the proper arrangements for your daughter. In Service; Dreams of Something More
so this is kinda a wierd story. I was planning to restart my computer. (cant remember why) I spend most of my time watching youtube videos so i had alot of tabs open. So i was watching the videos then deleting the tab but not opening new tabs. So i was down 2 i think 1 it was a pretty long video so i tried to open a youtube home page tab just to look while i listened to the video. And this is a short exerp of what i got.
Is it ok to ask a Trans Coworker about here experience coming out at work?
I’ve just started seriously questioning my gender identity and Everyday I becoming increasingly certain I’m non-binary or trans. I have a coworker that transitioned while we worked together. Is there an appropriate way to approach her to ask if she’d be willing to discuss her experience with me? Is that completely inappropriate? I’m not sure I’m ready to talk openly yet but She will be retiring in less than two weeks. If I’m doing this, I need to at least broach the subject and get contact info soon. My job is one of the few positives in my life. I don’t want to rock that boat but I also I don’t want to pass up the opportunity to talk with her about the road that may be ahead of me. Also to complicate things we’re working remotely for the pandemic, I can instant messenger, video conference, call, or email, irl face to face isn’t an option. Any advice on how to do this or that I should not approach her would be greatly appreciated Update: I did get in touch with her and she was very cool and supportive. I feel lucky to have someone like her to call on if needed.
Cover | First chapter | Previous | Patreon | Published Books | Website | Discord “Sarah said you wanted to speak with me?” I strode into Zafir’s office and closed the door behind me. He looked mildly surprised to see me at first, but a welcoming smile took over soon after. “Yes…we have much to discuss.” Zafir watched me carefully as I sat across from him. “First and foremost, I should inform you of Abel’s lie and the steps I took to fix what he’d done.” “Oh lovely. I can’t wait.” I leaned against the armrest. “Do tell me of your noble deeds, o’ great hero.” A short laugh escaped Zafir before he settled back in his seat, hands steepled in his lap, and his voice becoming all business. “To the point it is. Abel, contrary to his reports to me and what he told you, had you fitted with the manner of brain chip that can be detonated. The military recently began investigating Abel’s activities due to his sudden—classified—disappearance. As much of his misconduct was in relation to the other survivors, I took the liberty of ordering additional scans when you were rendered unconscious.” I gave him an impatient look when he paused for a swig of water. “Which showed the chip. And?” “I took the liberty of replacing it. After some discussions with our bosses, I educated them on the nuances of survivors such as yourself and acquired permission to use a Syldrari-made chip.” Zafir gave me that mysterious ‘I know you’re overthinking every word I say’ smile of his. “The survivors, and especially you, require more processing power than the empire’s chips provide. Luckily for us, the empire has no qualms about stealing technology from others and refitting it to suit their own purposes.” “Why Syldrari specifically?” I raised an eyebrow. “There’s plenty of races more advanced than us.” “Because the Syldrari are the most advanced species we’ve encountered, and because a Syldrari chip was the only one you showed compatibility with. I imagine it must have something to do with the Resonance Incident and your Syldrari suit.” Zafir shrugged, seemingly unbothered by my suspicion. “With that explained, we come to the primary reason I sent for you: I want your permission to run further tests. I’m not confident that Abel didn’t fake more information. Specifically, I would like to run blood tests.” “I mean…fine?” I glanced around, then back at Zafir. “Here, or one of the labs?” “Here will suffice.” Zafir motioned for me to roll up my sleeves. He stood and began rummaging around in the nearby cabinets. “How is training progressing?” “It’s…going. There’s not really much to say on that front until they can start actually going out to do…whatever it is we do.” I shook my head. “I’m still waiting to hear back from our bosses, but I did send in my request that Calder, Nikolai, and Maelor begin working.” Zafir pulled a chair up next to me and rolled a tray over, motioning for me to give him my arm. “Speaking of which, they want you to resume patrolling the Syldrari Sector during the day. They believe we’ve given enough time—” “I’m not so sure about that,” I interjected, thinking back to the letter Sarah had brought to me from Rel. “From what I understand, the Syldrari are worryingly convinced that I’m Lethe, and it may be dangerous for me there because of it.” “And you have this on good authority?” Zafir inquired as he gently prodded at my arm, sanitizing it before strapping a thin black band around the crook of my elbow. I grimaced. It was too late not to elaborate. “Rel sent a letter along with our meal the other week. He warned that I should stay away because multiple clans, including the R’selkti, are looking for me due to these rumors.” “Of course…” Zafir sighed, his expression falling. “I’m afraid there’s nothing I can say at this point to make them reconsider…without putting you at greater risk. Tomorrow you will begin your patrols again. I will see if I can convince our superiors to permit one of your colleagues to join you. Either way, I am planning to have one of them act as our ‘vigilante’ in the sector for a time, while you work elsewhere. Who would you say is the most stable?” “Nikolai for sure.” I raised an eyebrow as Zafir took the band off me. “Done already?” “Indeed. It’s much more efficient than a needle.” Zafir tilted a black glass vial, peering into it briefly before capping it off. The other three were quickly sealed as well. If there was anything off about my blood, he didn’t comment or show it. A pity, that. I was curious to know if there were still traces of blue like I’d seen while fighting the odd Syldrari. “Now then, I recommend you rest for the remainder of the day. I want you at your best when dealing with the Syldrari. Perhaps you can do some reading on their culture while you relax?” * * * I arrived in the Syldrari Sector early in the morning as shops were starting to open and people were beginning to walk the streets. Though it was early, there seemed to be an unusual number of people out and about. They were all so distracted that I managed to make it all the way to Rel’s cafe without anyone acknowledging my presence. “Elara? You shouldn’t…” Rel released an aggravated sigh. “You don’t have a choice and that’s why you’re here. Of course. What can I do for you, then? Are you feeling better?” “Better…ish?” I shrugged and gave him a small smile. “What can I say? It’s one thing after another. I’m just trying to roll with the punches at this point.” “Understandable.” Rel nodded and gave me a tired smile. “Will I be surprising you again today?” “Can you stop spoiling the graekstidat fodder for one second?” A familiar, grumpy voice demanded. I glanced over to see a Syldrari man with pale grey skin walking over. His black hair obscured one eye, the pale blue underside glowing against his cheek. His eyes were…among the odder that I’d seen. While the pupils were consistent with Syldrari, the colors of deep mauve, yellow, and jade green blended together similar to how a human’s hazel did. However, I had no damn idea where I’d heard his voice before. “A…what fodder?” I looked over at the aggravated Rel. “And since when did you have an edgy teenager working for you?” “Ah, think of it as an amphibious, furred shark hybrid the length of…several train cars,” Rel answered, pressing his fingers to his temples. “Furthermore, Aldiner is old enough to be your great-great-great-” “I’m working here to pay up for pissing off the elder here,” Aldiner interjected with a snort as he pushed his hands into his apron pockets. He leaned over me, examining me from a few angles. “You don’t have that military air to you. Sure you’re a—” I gave Aldiner my best cold, intimidating glare as he reached out and poked my cheek once. When he went for a second poke, I knocked his arm aside, spun behind him and elbowed him where I hoped his kidneys were, and moved to take him down to the ground. Alas, an arm wrapped around my waist and lifted me clean off the floor—and didn’t stop until my butt was planted on his shoulder. I looked down, startled enough to forget about beating the crap out of Aldiner. “Ignore Aldiner. He likes to annoy everyone he sees, and hates being ignored.” The much larger Syldrari glanced at me. I certainly hadn’t expected it to be the grumpy soldier man, seeing as he’d appeared to rather dislike me. “You’re fast, for a strigaella.” “A human woman,” Rel answered my next question with a sigh. Aldiner, behave. Humans are much less…ah…” Rel motioned with his hands and wiggled his fingers as he searched for the word. “You don’t touch humans unless invited to,” the soldier Syldrari grunted. “She invited ya?” Aldiner leaned forward peering at the soldier and then at where I was perched on his shoulder. “I didn’t, but I can appreciate that he was stopping me from starting a brawl with you right here and—” I cut myself off with an aggravated sigh when felt the feral attempting to push forward. All three Syldrari went still and watched me warily. What they sensed, or how much, I wasn’t sure I wanted to know. “Set me down, please…uh…” “Heh, always bitching about manners and you never introduced yourself, did ya?” Aldiner gave the soldier a cocky grin. “…call me Casair,” the soldier glanced away, seeming a little disgruntled, but the patterns of light on his arms didn’t so much as flicker. …Aldiner on the other hand… I glanced at the self-contained rave fish, then back at Casair. “And you can call me Elara, though I suppose you knew that already.” “Awww, Casair is shy!” Aldiner teased. “Suppressing—” “Quiet, vlerst bait.” Casair crossed his arms at the strobing Syldrari, then glanced over at me. “Back to patrolling needlessly?” “Something like that. I was sitting around recovering for so long that my boss’s bosses started thinking up other uses for me.” I grimaced before walking over to the counter and hopping up onto my usual seat. “As for surprising me, Rel, yes. Though I’d like a glass of…” I paused to reference the menu, “Jiirst☆nil?” Either I said it very right or terribly wrong, because all three men stopped what they were doing to stare at me in shock. Well, Aldiner was staring already, but he didn’t count. “Ah, there you are Rel my dear!” A woman’s voice carried through the room shortly after I heard the doors to the establishment open. “I’ve been looking everywhere for you!” “Mother, please…” a familiar voice groaned, and I glanced back to see the candy girl—who perked up and waved when she spotted me. “Careful you don’t become the queen’s snack,” Casair muttered by my ear before moving away to a booth in the corner, settling into it in such a way that he could keep an eye on everyone. Queen? I eyed the flamboyant woman and the three people with her. If one was her daughter, I had to assume the other two were guards—they had weapons holstered at their hips, at least. “I’m honored by your visit, but please refrain—” Rel began. “So, when will you become one of my consorts?” The…queen? demanded with a bright smile—one that faltered when Rel placed the drink he was making in front of me instead of her. I half-expected her to be angry, but instead she studied me for a moment, her head tilted, and a finger pressed against her full, black-painted lips. “A visitor in the Syldrari Sector…are you an Iri, Sen’iri, Sol’iri, Anad’iri, Sora’iri, or Lun’iri? I can never tell with you humans…” “Elara is an Iri, honestly…” Rel rubbed his temples. “How many times must we explain to you that the humans are binary in their biological—” “And that is just the problem! Biological! If they didn’t hop around between bodies and swap out prosthetics constantly—no offense—perhaps I could more easily identify who they are!” The queen hmphed, crossed her arms, then finally seemed to spot my uniform. “Ah, a military girl—my favorite. If Rel still refuses to become my consort… How would you like off this planet, sweetie?” “Mother, please!” The candy girl moved between her mother and me. “Elara is the nice human I told you about! She likes the candy I make, and her friends are going to help give me ideas for ones more humans will like! Plus, you haven’t even introduced yourself! Humans can’t sense a queen’s identity!” “Speaking of my colleagues,” I paused, pulling out several sheets of paper that had been folded together. “They may not be able to come to the sector for a while, so they asked me to deliver their notes to you.” She took them, and skimmed the first page, the glowing sections of her skin pulsing faster the more she read. “This is…this is great! I’m going to go work on the next batch!” And with that, the excitable candy girl darted out of the café, practically skipping as she went. “I’m Xilen, I run the mercantile Dvarl Clan,” the queen stated promptly, offering me her hand. When I shook it, she paused to study my face and search my eyes. “If you ever want off this planet, Rel knows how to contact me. It wouldn’t do for a pretty little thing like you to be wasted on the humans.” “…I’ll keep that in mind…” I gently reclaimed my hand while Aldiner snickered from somewhere. “Do you find women…?” Rel raised an eyebrow when I shook my head. “Then, you are being polite.” “I’m keeping my options open,” I countered. “If the military can’t recreate the Resonance phenomena—and maybe even if they can—their next step is going to be breeding our mutations down to offspring. I want no part of that, so having options is good.” “Ahhh, she’s so smart!” Xilen leaned over to squeeze me, rubbing her cheek against mine. To my surprise, the Syldrari in the cafe all looked ready to start a fight over it—with her. I got the distinct feeling it wasn’t jealousy, which made me all the more confused. “You just say the word and I’ll have you off this planet and into my arms! I’d love to see how such a cute human would look in Syldrari clothes—you don’t mind translucency, do you? I’d imagine not—” “Elara needs to have her meal before she returns to her duties.” Rel suddenly appeared behind us, his hand on the queen’s shoulder, and his voice cold as ice. “If you’re here to discuss trade, you can wait for me in the usual room.” “How dare—” One of the men I assumed to be the queen’s guards started to raise a weapon. I figured this was as good a time as any to make my point. I was out of my chair and twisting the weapon out of the man’s hand before he could finish his sentence. Using his body weight against him, I got him on the floor and twisted his arm behind his back, placing my booted foot against the back of his shoulders. “You— Ugh!” The other guard grunted when Casair’s fist met his stomach. “Please keep in mind that my job is to keep conflicts in the Syldrari Sector to a minimum, and I am authorized to use lethal force if you pull a weapon on anyone, regardless of race or species,” I spoke calmly, grinding my heel into the Syldrari’s back for emphasis. “You may keep your weapons and use them for defense if necessary. If you pull them again for any other reason…” “Cuuute!” Xilen promptly squeezed me in a hug. It took most of my willpower to beat down the feral, especially since I agreed with the idea of fucking ripping her arms off if she hugged me one more damn time. Xilen leaned down to speak quietly by my ear, “Be careful, dear. If you ever suspect you’re in trouble or in over your head, I’m sure you know how we can get them to come running to save you. And, stay far, far away from the R’selkti and their queen.” “Uh—?” I didn’t get to ask her what the hell she was on about. She fetched her guards and led them to some back room, leaving me confused and…a little unnerved. “I apologize for Queen Xilen’s…eccentricities,” Rel offered when I finally turned around to return to my seat. “Are all queens so goddamn pushy?” I snorted irritably, trying to shove Xilen’s insinuations out of my mind. “Ah…with Iri being the rarest of the six, they tend to act however they please…” Rel murmured awkwardly. “It is not uncommon for Syldrari women to turn their rarity into a form of power over others. Most Iri, even if they are not queens, have many…I believe the human word is ‘spouses?’” “Long story short: most recent queens have been groomed to see the other sexes as playthings to collect. Some of them even take other Iri, but it’s frowned upon,” Casair piped up flatly. “Xilen is of a different tide. She’s lasted so long because she can pretend. Whatever she whispered to you was probably as herself.” “Blah blah blah.” Aldiner rolled his eyes before leaning toward me. “You know, being a queen’s pet has its perks.” “Aldiner!” Rel barked, his markings flaring bright. “Go wash the dishes!” “Fiiine.” Aldiner sauntered off toward the back, though he turned and stuck his fingers up in a V and flicked his surprisingly long dual or split tongue between them before disappearing through the door. …I have a feeling it’s a good thing Rel didn’t catch that… I shook my head slightly. “So, are there any other developments I should know about before I start my patrols again?” “Just…be cautious. Someone has convinced the people here that you are Lethe…and that she may be a queen or related to one.” Rel sighed heavily and pushed his hair back. “Aside from that, things have been calming down after the little queen was found. With Xilen here…who knows. Her unannounced visits always cause trouble.” Next
One touch binary options are common types of extra ordinary (some people call it exotic) binary option. It offers you a payout the moment the price of the chosen by you underlying asset succeeds either to reach, or to pass the predetermined price. Some binary options trading methods are suited to One Touch trading, while others may work better for High/Low trades. Some systems are better for Boundary trades. If your system works well with One Touch trading, you are in luck; a lot of great brokers offer this type of trading! One-Touch Binary Options Explained. With the one-touch binary option trade, the binary options trader selects a strike price above or below the current market price as well as an expiration time. The broker will offer him a payout percentage corresponding to his selection. One touch binary options are special types of binary options. Like other binaries, one touch binary options offer fixed payout based on a certain outcome, as well as conditions being met within the allotted time period. It is the conditions that separate them from other binary options. Unlike most binary options, whose time period is actually a Touch is based on if the price action of the traded asset touches a price barrier before the expiration of the trade. A “One Touch” binary option is a trade type where the trader purchases an option that will deliver profit if the market price of the asset purchased touches the set target price at least once before the expiry of the date.
GTOptions -- How to Trade One Touch Binary Options
Forex & Binary Options expert Abe Cofnas looks at One Touch Binary Options - one of the faster growing trading instruments worldwide. He will also cover key fundamentals to give you the best ... Best Binary Bot 95% Win Rate ONETOUCH Forex Binary Options BD. The Biggest Reason Most Forex Strategies Fail (And What To Do About It) - Duration: 33:51. TRADE ATS Recommended for you. Binary Options - One Touch Intraday Trading Trend System Forexbooknat. Loading... Unsubscribe from Forexbooknat? Cancel Unsubscribe. Working... Subscribe Subscribed Unsubscribe 2.56K. A One Touch option is an exotic binary option that is becoming increasingly popular in the Forex and commodity markets. Learn more about One Touch Option in ... Hello. If you are interested in trading and trading strategies of binary options and forex, you can get a lot of paid tools and programs for free, all you have to do now is to subscribe to us in ...