#rw denial of normality

[altitudeofalcatraz]

Did a reference for the sluggies, now time for the iterators! Along with references for all my current rainworld ocs that I’ve made, hehe ☆ I care for them lots <3

[altitudeslocalgroup]

(Cutely tells in detail to DOH how to make a nuclear bomb)

[DON: . . . Well, it certainly seems that my overseers managed to locate one of the lizards! I don't. . . think it damaged the overseer at all. That's relieving.]

[divinefireangel]

cause you want supernatural stuff you can do a sf9 reaction to reader being a vampire or them turning into a vampire idk anything with vampires since i've been watching the vampire diaries this past week so vampires are on my mind lol

I LOVE TVD 😍 Although, my fav is The Originals 😋

Warnings: Blood. Vampire-y stuff. Killing. Mostly based on TVD vampires *flays hands vaguely*. Angst?

YB:

If you were a vamp- He's gonna be shocked

Moral conflict cause you need to drink blood to survive and shit

Wonders if you've killed people

Your relationship is a bit in danger 🥺

Once he accepts who you are, he's gonna break up with you and wishes you the best

Will be a whole ass mess for months tho

If he was a vamp- Honestly at first he'd try to avoid you and getting feelings for you

Because he thinks he is a danger to you

Of course if you do end up dating him, he will tell you the moment he know he can trust you

He won't force you to turn into a vampire if you aren't willing

If you want to turn into an immortal, he will be the happiest vamp in town

IS:

If you're a vamp- He'd be scared of you lmao

Kinda on edge with you around

See, he loves you, truly loves you but

You're kinda dead?

And he will not at all be willing to turn into a vampire

But will date you for a few more months then he will express his concern about him growing old and dying and you still being here without him

And he wants a family too, so inevitable heartbreak 😭

If he was a vamp- He's gonna be the Shakespearean type vamp

Smart and artsy

Elijah Mikaelson style you know?

He'd be super understanding with your decision to not date him or wanting to forget about him completely

Tbh he's gonna freak out if you say you also want to become one

Cause he sees you as pure, kind and not a killer

JY:

If you're a vamp- Thinks you're lying at first

Gosh how you also wish you were

In denial at first and then eventually he does accept it

Then he's conflicted cause he doesn't want to leave you, but he isn't ready to kill someone

When you tell him he doesn't actually have kill a person, he's more relaxed

Willingly ready to become a Vampire for you and spend forever with you

If he's a vamp- Promises to love you forever irrespective of your decision

If you wanna be with him, okay

If you don't, also okay

If you don't wanna turn into a vampire, okay

If you want to turn into one, super okay.

He loves you a lot, so he'll be happy with your every decision

DW:

If you're a vamp- He'll accept you, for who you are

But deep down he's scared

You know cause you hear his heartbeat

Puts on a pretense, cause he cares about you

But he can for only so long

Breaksdown suddenly and begs you to end it 😢

The only solution is to make him forget that he ever knew you

If he's a vamp- Like YB he'll avoid you

Just being happy for you from afar as you fall for a human and live your life normally, happily

Although if you do end up in a life threatening situation, he shows himself to save you

Displeased when you want to become one

Tells you all the bad things only so you don't ask further

As much of a gift it is, it's also a curse

RW:

If you're a vamp- Confused baby

No like genuinely confused cause you don't look dead

His morals are telling him no, leave them

His heart though, is wrapped up in the thought of being with you forever

And with his looks gee man

He'd be jumping when he finds out he can look like that forever and be with you while looking that godly

If he's a vamp- He's like Damon Salvatore

No doubts

But he is more caring and understanding

Truly loves you but tries to convince you to become a vampire a lot

Only so he can spend forever with you

ZH:

If you're a vamp- Terrified of you

Sorry, but he is

Can't look at you without feeling sorry for you

A lot of trust issues arise, he starts to overthink everything

The only solution is to make him forget 😔

If he's a vamp- First off, he refuses to let you become one too

Takes a lot of convincing, that is if you want to

If you don't want to become a vampire like him, he does what he thinks is best for you

Makes you forget, makes you move on from him

Feels empty forver :(

YT:

If you're a vamp- Scared baby

But he's practical

There should be a good enough reason for you to have become a vampire

Has so many questions

Curious

Won't actually want to become one but he won't leave you abruptly

If he's a vamp- The charming one, clearly

Perfectly okay with whatever decision you make

But secretly hopes you'd want to become a vampire for him

Spend all the time you'll have travelling the world together

HY:

If you're a vamp- *Blinks* What

Thinks it's hot 💀💀

Of course for practical reasons, he'd be upset

Upset because you've been alone for so long

Upset cause you're dead...

Won't agree to become a vamp but ready to spend as much time with you as you want

If he's a vamp- Wonder why you fell for him

Genuinely thinks you deserve better

Uses his skills for sex

His love for you blinds him enough to turn you, if you asked

CH:

If you're a vamp- This cutepie doesn't know how to process the information

On one hand, he's happy that a pretty person like you can grace this planet forever

On the other he's sad cause it means you're gonna be alone most of your life

Pesters you so much to turn him

Really takes a lot of convincing you, but he really wants to become your forever lover

If he's a vamp- A whole mess when you find out

Honestly, you're doing better

Scared that you'll leave him

But you wanna stay

Though secretly, he wants to leave you so he won't "rot" your life too

Sees you as too pure too good

Makes you forget about him and moves on

Takes a century to get over you 😭

[globalmediacampaign]

Comparing RonDB 21.04.0 on AWS, Azure and GCP using Sysbench

 Release of RonDB 21.04.0RonDB is based on MySQL NDB Cluster optimised for use in modern cloud settings. Today we launch RonDB 21.04.0. In RonDB 21.04.0 we have integrated benchmark scripts to execute various benchmarks towards RonDB.There are three ways of using RonDB. The first is using the managed version provided by Logical Clocks. This is currently available in AWS and is currently being developed to also support Azure. This is still in limited access mode. To access it contact Logical Clocks at the rondb.com website.The second way is to use a script provided by Logical Clocks that automates the creation of VMs and the installation of the software components required by RonDB. These scripts are available to create RonDB clusters on Azure and GCP (Google Cloud). This script can be downloaded from nexus.hops.works/rondb-cloud-installer.sh.The third manner to use RonDB is to simply download the RonDB binary tarball and install it on any computers of your own liking.All these methods start by visiting http://rondb.com. From here you will find the download scripts, the tarball to download and to send an email request access to the managed version of RonDB.RonDB 21.04.0 can be used in any of the above settings, but we focus our development, testing and optimisations towards executing RonDB in an efficient manner in AWS, Azure and GCP. We will likely add Oracle Cloud eventually to the mix as well.Benchmark SetupWhat we have discovered in our benchmarking is that even with very similar HW there are some differences in how RonDB performs on the different clouds. So this report presents the results using very similar setups in AWS, Azure and GCP.Above we have the benchmark setup used in all the experiments. There are always 2 RonDB data nodes and they are replicas of each other. Thus all write operations are written on both data nodes to ensure that we are always available even in the presence of node failures.The MySQL Servers are pure clients since data is located on the RonDB data nodes. Thus we can easily scale the benchmark using any number of MySQL Servers. The benchmark application runs on a single VM that sends SQL queries to the MySQL Servers and receives results using a MySQL client written in C. It is sufficient to have a single Sysbench server for these experiments.In this experiment we will scale RonDB data nodes by using different VM types. It is also possible to scale RonDB by adding more RonDB data nodes. Both of these changes can be performed without any downtime.It is possible to execute the Sysbench server local to the MySQL Server and let multiple Sysbench servers execute in parallel. This would however be a 2-tiered cluster and we wanted to test a 3-tiered cluster setup since we think this is the most common setup used. Obviously a 2-tiered cluster setup will have lower latency, but it will also be more complex to maintain.There is also a RonDB management server in the setup, however this is not involved in the benchmark execution and is either located in the Sysbench server or a separate dual CPU VM. Availability ZonesAWS, Azure and GCP all use a concept called Availability Zones. These are located in the same city, but can be distant from each other. The latency between Availability Zones can be more than 1 millisecond in latency for each jump. RonDB contains options to optimise for such a setup, but in this test we wanted to test a setup that is within an Availability Zone.Thus all setups we ensured that all VMs participating in cluster setup were in the same zone. Even within a zone the variance on the latency can be substantial. We see this in that the benchmark numbers can vary even within the same cloud and the same availability zone on different runs. From other reports it is reported that network latency is around 40-60 microseconds between VMs in the same availability zone. Our experience is that it is normal that this latency varies at least 10-20 microseconds up or down. In Azure it is even possible that the variance is higher since they can implement some availability zones in multiple buildings. In this case Azure provides a concept called Proximity Placement Groups that can be used to ensure that VMs are located in the same building and not spread between buildings in the same availability zone.RonDB VM TypesAll cloud vendors have VMs that come from different generations of SW and HW. For a latency sensitive application like RonDB this had serious implications. All the VMs we tested used very similar Intel x86 CPUs. There is some difference in performance between older Intel x86 and newer CPUs. However this difference is usually on the order of 30-40%, so not so drastic.However an area where innovation has happened at a much higher pace is networking. Cloud vendors have drastically improved the networking latency, bandwidth and efficiency from generation to generation.What we found is that it is essential to use the latest VM generation for MySQL Servers and RonDB data nodes. The difference between the latest generation and the previous generation was up to 3x in latency and performance. We found that the latest generation of VMs from all cloud vendors have similar performance, but using older versions had a high impact on the benchmark results. All the benchmarking results in this report uses the latest generation of VMs from all vendors.For AWS this means using their 5th generation VMs. AWS has three main categories of VMs, these c5, m5 and r5. c5 VMs are focused on lots of CPU and modest amounts of memory. m5 VMs twice as much memory with the same amount of CPU and r5 have 4x more memory than the c5 and the same amount of CPU. For RonDB this works perfectly fine. The RonDB data nodes store all the data and thus require as much memory as possible. Thus we use the r5 category here. MySQL Servers only act as clients in RonDB setup, thus require only a modest amount of memory, thus we use the c5 category here.The latest generation in Azure is the v4 generation. Azure VMs have two categories, the D and E VMs. The E category has twice as much memory as the D category. The E category is similar to AWS r5 and the D category is similar to the AWS m5 category.The latest generation in GCP is the n2 generation. They have n2-highcpu that matches AWS c5, n2-standard that matches AWS m5 and n2-highmem that matches AWS r5. GCP also has the ability to extend memory beyond 8 GB per CPU which is obviously interesting for RonDB.Benchmark Notes on Cloud VendorsSince we developed the RonDB managed version on AWS we have a bit more experience from benchmarking here. We quickly discovered that the standard Sysbench OLTP RW benchmark actually is not only a CPU benchmark. It is very much a networking benchmark as well. In some benchmarks using 32 VCPUs on the data nodes, we had to send around 20 Gb/sec from the data node VMs. Not all VM types could handle this. In AWS this meant that we had to use a category called r5n. This category uses servers that have 100G Ethernet instead of 25G Ethernet and thus a 32 VCPU VM was provided with bandwidth up to 25G. We didn’t investigate this thoroughly on Azure and GCP.Some quirks we noted was that the supply of Azure v4 VM instances was somewhat limited. In some regions it was difficult to succeed in allocating a set of large v4 VM instances. In GCP we had issues with our quotas and got a denial to increase the quota size for n2 VMs, which was a bit surprising. This meant that we executed not as many configurations on Azure and GCP. Thus some comparisons are between Azure and AWS only.Using the latest VM generation AWS, Azure and GCP all had reasonable performance. There were differences of course, but between 10-30% except in one benchmark. Our conclusion is that AWS, Azure and GCP have used different strategies in how to handle networking interrupts. AWS reports the lowest latency on networking in our tests and this is also seen in other benchmark reports. However GCP shows both in our benchmarks and other similar reports to have higher throughput but worse latency. Azure falls in between those.Our conclusion is that it is likely caused by how network interrupts are handled. If the network interrupts are acted upon immediately one gets the best possible latency. But at high loads the performance goes down since interrupt handling costs lots of CPU. If network interrupts are instead handled using polling the latency is worse, but at high loads the cost of interrupts stays low even at extreme loads.Thus best latency is achieved through handling interrupts directly and using polling one gets better performance the longer the delay in the network interrupt. Obviously the true answer is a lot more complex than this, but suffice it to say that the cloud vendors have selected different optimisation strategies that work well in different situations.Benchmark Notes on RonDBOne more thing that affects latency of RonDB to a great extent is the wakeup latency of threads. Based on benchmarks I did while at Oracle I concluded that wakeup latency is about 2x higher on VMs compared to on bare metal. On VMs it can be as high as 25 microseconds, but is likely nowadays to be more like on the order of 10-15 microseconds.RonDB implements adaptive CPU spinning. This ensures that latency is decreasing when the load increases. This means that we get a latency curve that starts a bit higher, then goes down until the queueing for CPU resources starts to impact latency and after that it follows a normal latency where latency increases as load increases.Latency variations are very small up to about 50% of the maximum load on RonDB.In our benchmarks we have measured the latency that 95% of the transactions were below. Thus we didn’t focus so much on single outliers. RonDB is implementing soft real-time, thus it isn’t intended for hard real-time applications where life depends on individual transactions completing in time.The benchmarks do however report a maximum latency. Most of the time these maximum latencies were as expected. But one outlier we saw, this was on GCP where we saw transaction latency at a bit above 200 ms when executing benchmarks with up to 8 threads. These outliers disappeared when going towards higher thread counts. Thus it seems that GCP VMs have some sort of deep sleep that keeps them down for 200 ms. This latency was always in the range 200-210 milliseconds. Thus it seemed that there was a sleep of 200ms somewhere in the VM. In some experiments on Azure we saw even higher maximum latency with similar behaviour as on GCP. So it is likely that most cloud vendors (probably all) can go into deep sleeps that highly affect latency when operations start up again.Benchmark ConfigurationOk, now on to numbers. We will show results from 4 different setups. All setups use 2 data nodes. The first setup uses 2 MySQL Servers and both RonDB data nodes and MySQL Servers use VMs with 16 VCPUs. This setup mainly tests latency and performance of MySQL Servers in an environment where data nodes are not overloaded. This test compares AWS, Azure and GCP.The second setup increases the number of MySQL Servers to 4 in the same setup. This makes the data node the bottleneck in the benchmark. This benchmark also compares AWS, Azure and GCP.The third setup uses 16 VPUs on data nodes and 2 MySQL Servers using 32 VCPUs. This test shows performance in a balanced setup where both data nodes and MySQL Servers are close to their limit. This test compares AWS and Azure.The final setup compares a setup with 32 VCPUs on data nodes and 3 MySQL Servers using 32 VCPUs. This setup mainly focuses on behaviour latency and throughput of MySQL Servers in an environment where the data nodes are not the bottleneck. The test compares AWS with Azure.We used 3 different benchmarks. Standard Sysbench OLTP RW, this benchmark is both a test of CPU performance as well as networking performance. Next benchmark is the same as OLTP RW using a filter where the scans only return 1 of the 100 scanned rows instead of all of them. This makes the benchmark more CPU focused.The final benchmark is a key lookup benchmark that only sends SQL queries using IN statements. This means that each SQL query performs 100 key lookups. This benchmark shows the performance of simple key lookups using RonDB through SQL queries.ConclusionsThe results show clearly that AWS has the best latency numbers at low to modest loads. At high loads GCP gives the best results. Azure has similar latency to GCP, but doesn’t provide the same benefits at higher loads. These results are in line with similar benchmark reports comparing AWS, Azure and GCP.The variations from one benchmark run to another run can be significant when it comes to latency. This is natural since there is a random latency added dependent on how far apart the VMs are within the availability zone. However throughput is usually not affected in the same manner.In some regions Azure uses several buildings to implement one availability zone, this will affect latency and throughput negatively. In those regions it is important to use Proximity Placement Groups in Azure to ensure that all VMs are located in the same building. The effect of this is seen in the last benchmark results in this report.The limitations on VM networking are a bit different. This played out as a major factor in the key lookup benchmark where one could see that AWS performance was limited due to network bandwidth limitation. Azure VMs had access to a higher networking bandwidth for similar VM types.AWS provided the r5n VM types, this provided 4x more networking bandwidth with the same CPU and memory setup. This provided very useful for benchmarking using RonDB data nodes with 32 VCPUs.Benchmark Results2 Data Nodes@16 VCPUs, 2 MySQL Server@16 VCPUsStandard OLTP RWIn this benchmark we see clearly the distinguishing features of AWS vs GCP. AWShas better latency at low load. 6,5 milliseconds compared to 9,66 milliseconds.However GCP reaches higher performance. At 128 threads it reaches 7% higherperformance at 7% lower latency. So GCP focuses on the performance at high loadwhereas AWS focuses more on performance at lower loads. Both approaches haveobvious benefits, which is best is obviously subjective and depends on the application.This benchmark is mainly testing the throughput of MySQL Servers. The RonDBdata nodes are only loaded to about 60-70% of their potential throughput with2 MySQL Servers.Moving to latency numbers one can see the same story, but even clearer. AWS hasa better latency up to 48 threads where the latency of GCP becomes better. In GCPwe see that the latency at 1 thread is higher than the latency at 12 threads and onlyat 24 threads the latency starts to increase beyond the latency at 1 thread. Thus inGCP the latency is very stable over different loads until the load goes beyond 50%of the possible throughput. We see the same behaviour on Azure whereas AWSlatency slowly starts to increase at lower thread counts.Standard OLTP RW using filterThe OLTP RW using a filter is more focused on CPU performance. The major differenceis seen at higher loads. The latency at low loads is very similar, but at higher loads weget higher throughput at lower latency. Thus standard OLTP RW has a steeper marchfrom acceptable latency to high latency. The difference in throughput is very smallbetween cloud vendors, it is within 10%.The comparison between AWS and GCP is similar though. The GCP benefit at higherload is slightly higher and similar to the latency. The AWS advantage at lower loads isslightly lower. Thus GCP has a slight advantage compared to standard OLTP RW,but it is a very small difference.Key LookupsIn the graph below we see the number of key lookups that 2 MySQL Servers can drive.The numbers are very equal for the different cloud vendors. AWS as usual has anadvantage at lower thread counts and GCP gains the higher numbers at higherthread counts and Azure is usually in the middle.The latency numbers are shown below. These numbers more clearly show theadvantage of AWS at lower thread counts. At higher thread counts the latencyis mostly the same for all cloud vendors. This benchmark is extremely regularin its use case and thus it is mostly the CPU performance that matters in thisbenchmark. Since this is more or the less same on all cloud vendors we seeno major difference.2 Data Nodes@16 VCPUs, 4 MySQL Server@16 VCPUsIn this benchmark the bottleneck moves to the RonDB data nodes. We now havesufficient amounts of MySQL Servers to make the RonDB data nodes a bottleneck.This means a bottleneck that can be both a CPU bottleneck as well as a networkingbottleneck.Standard OLTP RWThe latency is very stable until we reach 64 threads where we have around 15k TPS at20 milliseconds latency. At higher thread counts the data nodes becomes the bottleneckand in this case the latency has a much higher variation. We can even see that latencyat 128 threads in Azure goes down and throughput up. We expect that this is due tointerrupt handling being executed on the same CPUs as database processing happens.This is something that we will look more into.OLTP RW using filterThe throughput of OLTP with a filter means that the focus is more on CPU performance.This makes it clear that the high variation on throughput and latency in standard OLTP RWcomes from handling the gigabytes per second of data to send to the MySQL Servers.In this benchmark the throughput increases in a stable manner and similarly the latencygoes up in an expected manner.All cloud vendors are very close to each other except at low thread counts whereAWS have an advantage.Key LookupsThe key lookups with 4 MySQL Server and 2 data nodes and all nodes using16 VCPUs per node moves the bottleneck to the data node. As usual AWSwins out on the latency at lower thread counts. But at higher thread countsAWS hits a firm wall. Most likely it hits a firm bandwidth limitation on the VMs.This limitation is higher on Azure, thus these VM can go an extra mile and serve1 million more key lookups per second.2 Data Nodes@16 VCPUs, 2 MySQL Server@32 VCPUsThis benchmark uses the same amount of CPUs on the MySQL Server side,but instead of divided on 4 MySQL Servers, it is using 2 MySQL Servers.We didn’t test GCP in this configuration. We expect no surprises in throughputand latency if we do.Standard OLTP RWIn the Standard OLTP RW we see that the throughput is the same as with4 MySQL Servers. However the throughput increases in a more regular manner.What we mainly see is that we can achieve a higher throughput using a smalleramount of threads in total. This makes the throughput more stable. Thus weconclude that at least up to 32 VCPUs it pays off to use larger MySQL Serversif required.2 Data Nodes@32 VCPUs, 3 MySQL Server@32 VCPUsIn this benchmark we increased the number of CPUs on the RonDB datanodes to 32 VCPUs. Most of the testing in this setup has been performedon AWS. The main reason for including the Azure numbers is becausethese numbers show the impact of not using Proximity Placement Groupsin Azure on large regions. We saw clearly in these benchmarks that thelatency in the Azure setup was much higher than in previous benchmarksthat were using a smaller region.However in the smaller region it was difficult to allocate these larger VMsin any larger number. We constantly got failures due to lacking resourcesto fulfil our requests.Standard OLTP RWIn AWS we discovered that the network was a bottleneck when executingthis benchmark. Thus we used r5n.8xlarge instead of r5.8xlarge VMs inthis benchmark. These VMs reside in machines with 100G Ethernetconnections and each 32 VCPU VM have access to at least 25 Gb/secnetworking. The setup tested here with 3 MySQL Servers doesn’t load theRonDB data node fully. In other benchmarks we were able to increasethroughput to around 35k TPS. However these benchmarks used a differentsetup, so these numbers are not relevant for a comparison. What we see isthat the throughput in this case is roughly twice the throughput when using16 VCPUs in the data nodes.Latency numbers look very good and it is clear that we haven't reallyreached the bottleneck really in neither the MySQL Servers nor theRonDB data nodes.OLTP RW using filterSimilarly in this experiment we haven’t really reached the bottleneck on neither theRonDB data nodes nor the MySQL Servers. So no real news from this benchmark. http://mikaelronstrom.blogspot.com/2021/04/comparing-rondb-21040-on-aws-azure-and.html

[nifahnisa]

i think, i was positive (pt.1)

awalnya gue gamau nulis tentang ini samsek, tapi ternyata hal ini jauh lebih runyam dari yang gue kira, dan banyak hal yang bisa jadi pelajaran. gue akan nulis cerita ini serunut, sejelas (ga belibet), akan gue coba ringkas dan tanpa bumbu, tapi perlu diingat gue bukan penulis dan ini 100% hal yang terjadi melalui perspektif gue. 

buat yang baca postingan gue sebelumnya mungkin kalian udah tau Pakde gue (Pakde Bud) baru aja meninggal. jadi Pakde gue tanggal 24 november meninggal, qodarullah memang sudah ajalnya dan memang sudah sakit cukup lama, sampe terakhir terpapar covid. bahkan sampai akhir keluarga pun awalnya gasadar Pakde kena covid, karna memang udah cukup lama sakitnya.

nah pas tanggal 23, Ummi sama Bapak nengokin Pakde ke rumahnya, sampe pas malem karena keluarga dirumah gatau harus ngasih treatment apa ke pakde, akhirnya mutusin untuk dibawa ke rs. Ummi sama Bapak ikut nemenin dan nganterin juga, dan kata dokter disana Pakde sepertinya gejala covid, akhirnya di swab lah. tapi disitu keluarga pun gak ada yang sadar, dan Ummi udah nyiumin, meluk dan mijitin Pakde. besoknya innalillahi Pakde meninggal. setelah Pakde meninggal, seluruh keluarga di swab dan ternyata sebagian besar hasilnya positif.

Ummi sama Bapak yang kontak langsung sama keluarga Pakde langsung waswas ikut kena. akhirnya tanggal 25 Ummi, Bapak dan Gue swab antigen (H+2 kontak dengan yang covid) dan hasilnya negatif. 

ini hal yang gue tau: mungkin juga salah - rapid test = tes dari darah reaktif dan non-reaktif. tapi yang ini menurut gue ga akurat karna keluarga Pakde di rapid hasilnya non-reaktif semua tapi ternyata pas di swab positif. - swab antigen/rapid antigen: ini diambil lendir dari hidungnya. nah tapi kalo ini yang dicari antigen tubuh ada gak perlawanan sama virus covidnya. makanya bisa jadi kalo awal terpapar hasilnya negatif karna tubuhnya belum ngebentuk antigen. again yang ini juga ga akurat, kalo negatif di antigen bisa jadi positif. - swab pcr: nah ini sample dari lendir hidung dan mulut. ini yang paling akurat buat ngedeteksi virusnya ada atau enggak, karna emang dia yang dicari virusnya. kenapa orang-orang tetep rapid dan swab antigen? karena hasilnya keluar cepet, biasanya buat yang mau pergi2 prefer ini.

akhirnya kita udah tenang tuh tapi ya karna covid ini juga masih dipelajarin terus ada yang bilang masa inkubasi covid 1-5 hari baru dia menginveksi sedangkan keluarga gue terlalu cepet swabnya. besoknya tanggal 26 ummi tiba-tiba badannya anget meriang dan pusing tapi kita masih denial engga kok kemarin udah di swab hasilnya negatif. gue langsung nanya2 ke temen yang emang suster covid, dia bilang ditunggu dulu aja seminggu setelah kontak kalau gejalanya makin parah langsung bawa ke rumah sakit (re: gejala lain kaya sesek, batuk, mual).

gejala awal covid itu macem-macem ya, kalo ummi badannya anget tapi ga tinggi2 banget paling 37/38. dan pusing. abis itu angetnya ilang beralih ke mual (biasanya lambungnya juga kena), batuk atau flu. ohiya, penciuman Ummi normal, tapi lidahnya jadi pait atau asin kalo makan apa aja. nah yang harus diperhatiin, banyak yang gada gejala diatas tapi saturasi oksigen didarahnya turun. makanya banyak kasus yang ga ketolong karna saturasi oksigennya udah terlalu rendah. 

keluarga gue udah ‘jaga jarak’ alakadarnya dari pas awal gejala Ummi, biasanya sholat bareng ini sendiri-sendiri, gue jarang main ke kamar Ummi jadi emang yang banyak ngurusin dan kontak sama Ummi ya Bapak, yah gimana orang sekamar juga.. gue paling bisa masakin aja. bener aja seminggu kemudian, ummi tambah gejala udah gak anget tapi lemes, agak sesek, batuk dan mual. tandanya sama semua sama yang temen gue bilang. akhirnya hari Rabu (2 desember) ummi di swab pcr. 

gue swab pcr di UI ya, buat yang nanya tarifnya itu 900ribu hasil keluar H+3. 1.200.000 hasilnya keluar H+1. tinggal dateng aja tapi rame ya antri, pas Ummi swab aduh... karna rame dan antri itu, Ummi juga kondisinya udah lemes jadi kalo kondisinya udah kaya gini mending cari tempat swab yang bisa cepet/appointment dulu biar ga kecapean ngantri doang. 

hari Kamis (3 desember) siang hasilnya keluar dikirim lewat email dan bener positif. beneran hancur banget hati gue. gue juga bingung banget harus ngapain. gue udah nangis beneran bingung mau gapain. siangnya gue tanya Ummi mau ke RS gak? terus Ummi bilang gausah karna saturasi oksigennya masih bagus dan ga terlalu sesek, cuma lemes aja katanya. tapi pas magrib tiba-tiba Ummi seseknya tambah parah. gue langsung telfon RSUI nanya apa bisa dirawat, kata yang gue kontak di IGD nya ada 10orang masih antri kamar, mungkin bisa ditanganin tapi di IGD dulu. akhirnya gue nanya RS rujukan covid di depok mana aja, dia bilang RS BUNDA bisa, akhirnya gue mutusin buat coba ke RS BUNDA dulu. 

berangkat kita ke RS bunda, naik mobil sendiri bener2 disini udah ditahap yaudah pake masker dll tapi gamungkin kan jaga jarak? pake apd? no. yang penting Ummi ditanganin dulu. jujur gue gamikirin gue positif apa enggak. akhirnya pertama kita ke RS BUNDA. disana ditanya swabnya dimana dll, gue bilang di RSUI, susternya nanya balik ‘kenapa gak ke rsui aja?’ disini gue udah feeling ternyata ga semudah itu. pasti RS juga lempar-lemparan. hasilnya nihil Ummi ditolak karna katanya IGD RS BUNDA juga penuh. 

akhirnya kita ke RSUI. beneran yaAllah disini gue kesel dan sedih banget. kita sampe di RSUI dan dimeja depan IGD nya gak ada orang. gue nanya ke regis akhirnya, gak lama suster cowo keluar dengan muka yang dari awal udah gak enak. beneran gue masih kesel kalo nginget ini. kira-kira gini ya percakapannya

“iya kenapa mba?” ‘ini ibu saya tadi siang hasil swabnya keluar, dan hasilnya positif. sekarang udah  mulai sesek. dan ibu juga ada penyakit bawaan diabetes’ “tapi disini penuh, udah coba ke rs lain?” astagfirullah.. ‘tadi abis dari bunda dan penuh juga. tadi udah telfon dulu  katanya disini bisa di tanganin di igd dulu’ “gabisa mbak! penuh!” (well dia ga teriak tapi agak MELOTOT) (pengen gue colok matanya) ‘tapi tadi saya udah telfon katanya bisa’ “ya Tapi kan Saya yang ada di IGD, orang Administrasi tuh GAK TAU APA-APA’ (sambil nunjuk ke arah ruang admin) beneran disini gue udah gatau harus apa. coba bayangin aja jadi gue udah panik harus apa, ke rs tapi malah ketemu suster kaya gini. bukannya ngedoain tapi gue harap dia coba ngerasain ada diposisi gue terus digituin. lanjut dia ngomong lagi “terus sekarang mau gimana?!” WHAATTT????!!! kok lu nanya ke gue??? dia bahkan ga meriksa nyokap gue samsek. apake liat tensi, saturasi oksigen, demamnya gimana APAKEK. kalo gue suster atau punya peralatan rs juga gue gak akan bawa ibu gue yang udah lemes dan sesek kesini? pls gue tau lu capek tapi lu nyebelin. akhirnya karna gue nangis, bapak gue yang ngelanjutin ngomong ke susternya.  ‘yaudah sus ini sekarang ditanganin aja dulu baiknya gimana’

gue udah keluar dari tempat itu, jalan keluar sambil nangis ngambil hp dan ngechat kakak gue minta cariin RS yang nanganin covid karna di UI ditolak. gak lama tiba-tiba si suster cowo ini keluar manggil gue ‘mbak ini ibunya’ pas gue masuk lagi udah ada suster lain yang ini cewe, dan cara ngomongnya MUCH BETTER dari si suster cowo. suster yang cewe ini ngejelasin kondisi Ummi katanya masih gapapa dirumah dulu karna saturasinya masih bagus belum drop, paling hanya sesek. terus suster cewe ngejelasin baiknya gimana. dan suster cowo SOK2an nambah2in, sekarang dia udah lebih baik ngomongnya, mungkin karna liat gue nangis. tapi gue gamau banget ngeliat mukanya. akhirnya kita pulang lagi.

Ummi cuma ngomong dimobil ‘udah adek jangan nangis terus, ummi jadi ikutan sedih’. Bapak ngomong ‘udah dek Ummi nya gapapa kok gausah nangis’. kaya gue juga gamau nangis karna nangis ganyelesaiin masalah dan malu jujur nangis tuh. tapi karna faktor runyam banget dan hari ke-2 gue dapet deh kayanya jadi bener-bener nangis mulu. 

pas pulang itu kita akhirnya lapor ke RT/RW rumah, karna hasil gue tanya-tanya memang prosedurnya lapor ke RT/RW nanti mereka yang lapor ke puskesmas untuk rujukan RS, Swab keluarga yang lain dan disinfektan rumah. dan nanti harusnya yang bawa pasien kalau butuh dirawat di RS dari Puskesmas. udah akhirnya kita pulang lagi dan nunggu besok gimana.

lanjut pt.2 ya nanti.. 

[tekmodetech]

Everyone hates us, and it’s not because of our sex parties

It was, briefly, the zeitgeist’s good Silicon Valley story: a sex-and-drugs celebration hosted hosted by since-ousted top-tier VC Steve Jurvetson, at an official Draper Fisher Jurvetson occasion,attended by a number of billionaires together with Elon Musk. So mentioned Paul Biggar, founding father of CircleCI, in a widely read Medium post, increasing on Self-importance Truthful’s excerpt of Emily Chang’s new e-book.

(To be clear, it was Axios who subsequently named Jurvetson and DFJ.)

Is that really what occurred? Did a serious Valley VC agency host a decadent sex-and-MDMA celebration as a part of considered one of its official occasions smack within the midst of final yr’s widespread sexual-harassment revelations? Uhhhhhh. Nicely. Because it seems, not a lot. Biggar notes that he didn’t truly see something outrageous or salacious occurring by the point he left, and, it appears others have vouched that, afterwards … such issues continued to not occur:

I wish to share some longer remarks on the so-called Silicon Valley elite “intercourse celebration” that’s making the rounds. (Be warned: the reality is boring.) http://pic.twitter.com/T4BrLTeFof

— Mason Hartman (@webdevMason) January 12, 2018

In equity to Chang, she was writing about secret Valley intercourse events normally, talked about in passing that “whereas some events could also be devoted primarily to medicine and sexual exercise, others could boast simply pockets of it,” and cited this specific occasion — and a girl there being given medicine by one man, after which hit on by one other in an inappropriate and exploitative means — for instance.

So what occurred at that celebration? It seems like the reply is “at the least two cases of shitty habits that are principally, infuriatingly, fairly typical examples of how the tech business treats ladies.” However it additionally sounds prefer it was principally a reasonably tame, if themed and Burning-Man-ish, occasion which some culturally conservative individuals noticed and instantly misinterpreted as a intercourse celebration.

Which is strictly why I name it the right Silicon Valley story: everyone seems to be on the lookout for lightning-rod causes to hate the Valley proper now. The sex-party narrative is sort of a Rorschach excuse. Proper-wingers can condemn it for instance of tech’s corrupt, decadent liberalism. Leftists can excoriate it as an example of tech’s bone-deep sexism and exploitative hegemony of privileged white males.

This is only one particularly vivid instance. Slings and arrows from throughout the political spectrum are being aimed toward tech. Liberals level out that it has handled ladies abominably for many years, whereas Asians face a “bamboo ceiling” and different nonwhite persons are all however excluded; they blame Fb for the election, Twitter for permitting Donald Trump and neo-nazis to run rampant, Amazon and Google for avoiding taxes, and many others.

Conservatives, in the meantime, accuse tech of a scarcity of “viewpoint diversity” — which bespeaks a weird miscomprehension that their perception techniques are rejected purely as a result of they’re totally different, when the truth is they’re rejected as a result of climate-change denialism, and denying the systemic oppression of people that weren’t born white males, are as demonstrably & morally incorrect as e.g. flat-eartherism and eugenics, and handled accordingly. Barely extra plausibly, they accuse Fb of censoring conservative information, whereas targeting Twitter for shadow-banning right-wingers.

Whereas the “shithole” story continues to dominate on mainstream retailers, over within the RW media universe, Breitbart nonetheless giving all its consideration to allegations Twitter is biased in opposition to conservatives… http://pic.twitter.com/mpgJO0ceke

— Oliver Darcy (@oliverdarcy) January 12, 2018

However wait, there’s extra! Because the rent crisis wracks America, its victims, determined for reasonably priced housing in fascinating locations, hate the tech business for gentrifying the cities — San Francisco, Seattle, Los Angeles, NYC, Boston, and many others — the place individuals most wish to reside.

In the meantime, because the media hemorrhages cash, it turns into ever extra reliant on Fb and Google — whilst that duopoly devours a lot of the promoting that used to go to the media. And as each media and finance go tech, East Coasters (and Londoners) see that their center-of-the-universe affect, which they as soon as thought unassailable, has moved to California and past. Is it actually that stunning, while you observe the cash, that the American media’s love affair with the tech business is coming to a bitter and more and more livid finish?

The explanation why is clear. We have now the cash, now. Seven of the ten largest publicly traded firms on the earth are tech firms, and three of them are headquartered inside biking distance of each other in Silicon Valley, surrounded by a nimbus of dozens of unicorns. With that wealth comes big (at the least perceived) energy — not simply monetary, however the energy to form the longer term, to affect the lots, to form mass political actions.

Do you see a variety of standard narratives whose heroes are privileged, unelected engineers and buyers whose beforehand sizable wealth has grown into immense riches and massive energy? Uh, no. Actually you’ll have observed that, in just about each standard story, such persons are the bad guys. There’s a purpose for that: traditionally, energy corrupts.

Folks in all places are already anticipating lightning-rod trumped-up causes to hate the Valley and the tech business as a complete. And it’s not like we haven’t given them at the least just a few actual ones. So it may be time to start out considering much less about cash and energy, and extra about values, and the way we’d truly make sacrifices in service of these values — as a result of historical past signifies that blatant, widespread hypocrisy is considered one of a number of efficient methods to remodel a lightning rod into an indignant mob wielding pitchforks and torches.

http://platform.twitter.com/widgets.js !operate(f,b,e,v,n,t,s)if(f.fbq)return;n=f.fbq=operate()n.callMethod? n.callMethod.apply(n,arguments):n.queue.push(arguments);if(!f._fbq)f._fbq=n; n.push=n;n.loaded=!zero;n.model=’2.zero’;n.queue=[];t=b.createElement(e);t.async=!zero; t.src=v;s=b.getElementsByTagName(e)[0];s.parentNode.insertBefore(t,s)(window, doc,’script’,’//join.fb.web/en_US/fbevents.js’); fbq(‘init’, ‘1447508128842484’); fbq(‘observe’, ‘PageView’); fbq(‘observe’, ‘ViewContent’, content_section: ‘article’, content_subsection: “publish”, content_mns: [“93484976″,”2787122″,”93484977″,”93484973″,”93484975″,”773631″,”93484965″,”93484948″,”93484944″,”93484974”], content_prop19: [“opinion”,”tc”] );

window.fbAsyncInit = operate() FB.init( appId : ‘1678638095724206’, xfbml : true, model : ‘v2.6’ ); FB.Occasion.subscribe(‘xfbml.render’, operate() jQuery(‘.fb-messenger-loading’).detach() ); ;

(operate(d, s, id) var js, fjs = d.getElementsByTagName(s)[0]; if (d.getElementById(id)) return; js = d.createElement(s); js.id = id; js.src = “http://ift.tt/2j7LkPh;; fjs.parentNode.insertBefore(js, fjs); (doc, ‘script’, ‘facebook-jssdk’));

operate getCookie(title) ()[]/+^])/g, ‘$1’) + “=([^;]*)” )); return matches ? decodeURIComponent(matches[1]) : undefined;

window.onload = operate() var gravity_guid = getCookie(‘grvinsights’); var btn = doc.getElementById(‘fb-send-to-messenger’); if (btn != undefined && btn != null) btn.setAttribute(‘data-ref’, gravity_guid)

Source link

The post Everyone hates us, and it’s not because of our sex parties appeared first on Tekvision.

from WordPress http://ift.tt/2B466pO via IFTTT

[altitudeofalcatraz]

More simple doodles, this time around it’s mostly ocs with a bit of canon sprinkled in ☆

[altitudeofalcatraz]

I would love to hear about your iterator ocs!

Alright!! Once again, gonna try keeping it as simple as possible, nothing too detailed! (Copying RI and WOTM from the post before this, using this as some sort of master list i assume)

There is art in this as well!! Might have been too much but I like being extra about my ocs

Haphazardly Throwing Needles HTN is the third eldest iterator of the local group. Back when the ancients were still around, they always had a distaste for them, thinking they were making too much of a fuss over the cycles. If they were really good enough to transcend, then they should be able to do it themselves without the help of supercomputers. They always were bitter towards the ancients, refusing to help them as much as they could, which sparked a multitude of arguments. When the mass extinction happened, HTN felt immense relief, as the ancients only ever caused negative effects on them. 

Even before the extinction, HTN didn’t bother much with trying to solve ‘The Great Problem’, preferring to research the local flora and fauna instead. With the ancients gone, they could focus even more time into this. When they first found out about the rot, they grew curious about its creation and upbringing, and in a careless experiment, purposefully tried to grow the rot in their systems. It ended up working, and unlike many iterators, HTN was quite content with it. Over time, they modified the rot and helped it grow, creating an almost mutualism relationship with it. The rot would feast on the fauna around the superstructure, and in turn protect and surprisingly keep HTN in good conditions, causing them to be one of the most resilient structures of the local group. There is little life in the superstructure besides the rot, due to the constant feeding and absorption. The Machine does visit HTN, and is almost always met with rudeness and bitterness. This comes from a place of care, though, as HTN is concerned about Machine’s reckless travelling around something dangerous like the rot, as they still don’t have full control of it around the superstructure.

Sight Through Blindness STB is the eldest of the local group, and is treated with the most respect. During the time of ancients, she was rarely chatted with, left to focus by herself. STB was built by the ancients with no overseers nor sight, as they believed being able to see the outside world would only distract from work, and that being confined to herself would make her work diligently and quickly. She had been reinforced over the course of the cycles, making her more resilient to outside forces. STB did not mind the lack of outside stimulation, doing as she was ordered and working tirelessly to help with whatever was needed.

After the loss of the ancients, STB finally opened up, establishing connections with the local group more often, now helping them with problems instead of the ancients. She still works on trying to solve the great problem, even if she herself doubts it ever working, since that was what she was made to do. She is very thoughtful and patient, taking time to listen and help the iterators with whatever they are troubled with. This makes her a very popular go-to for the group when they are stressed or overworked. Surprise visits from The Machine are always exciting for her, as they are the only thing to have ever entered her chamber for more than just maintenance. She is very gentle with them, and makes sure to always prep Machine for their next journey.

Deafening Silence DS is the fourth eldest of the local group. The relationship with the ancients living on top of him was very straightforward : he provided them with their needs of living, and they provided him with the same. There was never any conversation between them, a very silent relationship. All he did was work, never communicating with anything, including other iterators. Some wonder why he was even given access to communications, with the lack of activity from him.

After the mass extinction, DS almost immediately stopped working on the great problem. He had no purpose to do it anymore. In his eyes, it was worthless, only doing it because the ancients were around to watch him. For many cycles now, DS has essentially been doing nothing. The only thing he worked on after the extinction was finding a way to hack into the chatlogs and gain access to private chats between iterators. All he does nowadays is sit at the bottom of his chamber, acting lifeless, watching chatlogs of the local group without ever responding. The group is aware of this behaviour, and have tried countless times to contact him, never getting any replies. Some have sent overseers to his chamber in the past, but he almost instantly deactivates them, causing most to give up on that route. The Machine has never directly interacted with DS, as he has found ways to block Machine out, such as clogging pipes and tunnels to deny access.

Denial Of Normality

DON is the second eldest iterator of the local group. When she was first built, she wasn’t instantly put to work, given a bit of time to study and get used to the world around her before fully indulging herself in various problems and tasks. Due to this, she grew very intrigued in the surrounding fauna early on, taking any free time she could to play around and research it. Ever since her creation, she’s always been the most prideful and egotistical out of the local group. Constantly she separates herself from her puppet when speaking, having to remind anyone that talks to her that she is in fact, more than any simple creature can understand, and her puppet is just there so they can comprehend her. Her pride does not mean she doesn’t have kindness, as she is very active within the local group, and is welcoming to help out when needed.

After the extinction, DON ditched any work the ancients wanted and focused on studying and creating genetically modified creatures from the fauna nearby. It was messy at first, but she got the hang of it, creating many experiments from whatever her heart desired. Most of the life around her superstructure is said modified beings, very little creatures from beforehand exist, as they have been killed by the newcomers or have fled to new land. Overtime, her experiments have gotten more drastic, creating some things that shouldn’t be possible by normal standards. At some point, she began to practice modifying already alive creatures, starting by experimenting on her puppet and overseers. She was the creator of The Machine, originally making it for VSH and WOTM since they had no experience in genetic modification. She gets visited by them sometimes, often engaging in training and playing with them to keep up on their skills. 

Violent Sky Hues

VSH is the fourth youngest of the local group, made shortly before WOTM. they were made unusually high up in the sky, far above the clouds and other superstructures. This caused the group of ancients living on top of them to be isolationist towards other groups of ancients, communicating only with those on the structure. VSH was frequently talked to and communicated with, the ancients treating them as simply another member of the civilization, making them very fond of the ancients. Despite them originally being built with the great problem in mind, when they were actually finished the ancients instead simply gave them the task to provide for them and keep them company.

When the mass extinction happened VSH was saddened, but their sadness turned into curiosity, beginning to start a hobby of collecting, reading, and archiving pearls left behind by the now gone civilization. They could not easily gain these pearls, so with the help of WOTM they convinced DON to make The Machine for them, as a way to transport pearls from structure to structure. VSH considers themselves Machine’s “dad”, getting visited by them the most due to the frequent pearl shipments. VSH gets very violent if something tries to remove the pearls from their chamber, resorting to instantly killing the thing that attempted it. Besides that, they are very lighthearted, and talkative, constantly in some sort of chat with WOTM.

Harmless Abandonment

HA is the youngest iterator of the local group. When the ancients were still around, they had begun building HA, only to abruptly stop due to reasons unbeknownst to the local group. They had most of the necessary equipment to run, minus communications, but suffered from constant malfunctions, buildup, and breakdowns. They were also never equipped with overseers, causing them to be unaware of the outside world. For a long time, they were not powered on, laying dormant in the background.

When the ancients disappeared, the local group took it upon themselves to try and power on HA. Using The Machine as their carrier and messenger, they slowly transferred materials from their own cans to HA, in an attempt to build as much as they could with the slugcat, and get him running again. The main contributors were VSH, WOTM, DON, and STB. RI wanted to help, but the group fought against it as he was unstable already and could pose liabilities if transferring stuff from him to HA. After countless cycles of work, they had finally gotten a response from the unfinished iterator, using Machine to retrieve messages from him. After his initial awakening, Machine has been sent a multitude of times to continue helping to repair and fix whatever they could. During these adventures, they would bring outside items they found to HA, who often used them to decorate his puppet. Since HA does not have access to communications, VSH and WOTM both have a couple overseers near him at all times to talk and check up on him, which he appreciates. Occasionally the other iterators also send over overseers to have a chat, but those overseers don’t usually stay for long. Since their main communication is through overseers, HA rarely interacts with STB, as they have to communicate either through another iterator or Machine.

Requisite Betrayal

RB is the second youngest of the local group. When built by their iterators, they were specifically designed around the kill code taboo, both subconsciously and consciously doing whatever they can to keep their superstructure in perfect conditions. They were meant to exist for eternity, the ultimate guide and solution to the great problem. The ancients did constant work and repairs on them, keeping them constantly up to date and working 100% functionally. They were built in such a way that they could survive even with minimal water, by running on something similar to a ‘battery saver’. They were rarely treated as a living thing, ancients too focused on making sure they were physically intact to care about their mentality.

Even after the extinction RB continues to run in excellent conditions, facility having modified creatures within to do minimal repairs wherever they can access, keeping them ahead of the other iterators. They are very blunt and logical, not understanding jokes or casual chatting and preferring to have discussions about work and other scientific things. A while after The Machine was created, RB had made his own purposed organism, The Rogue. It’s purpose was much like the creatures inside of their structure, keeping RB in as perfect condition as possible. They were occasionally sent on missions to other, older structures of decaying iterators to ‘borrow’ (steal) things such as neuron flies and rarefaction cells to use as replacements in case any of RB’s parts were damaged and unable to be repaired. The Machine occasionally visits RB, but when The Rogue is around they usually don’t stay for long.

Reckless Infatuation

RI is basically a middle child in terms of iterator ages, directly in the middle of eldest and youngest. During creation, he was very haphazardly put together, as the ancients building him weren't very fond of the work they were doing, and so "gave up" during the process. This caused a lot of mechanical failures to happen, most notably the seemingly random miniature explosions that happened around his superstructure, especially frequent inside the chamber where his puppet was. Due to these unpredictable and sometimes dangerous explosions, he was deemed unfit to live on, and so he never really had ancients near him during their existence. The only ancients that he ever came into contact with are those sent to try and fix his failures when they occurred, and even then that was sparse. This sparked some form of clinginess in him, as he was very social and constantly sought attention. Anytime the ancients would come into his chamber he would try and prevent them from leaving in any way he could, causing strain on him and his puppet. The last visit he ever had with an ancient ended up with him getting ripped off of the arm that connects him to the wall (cords/umbilical still intact.)

He currently still has access to communications, and constantly pesters any iterator in the local group when they care to listen to him. It's mostly STB, VSH, and WOTM that he talks to, as they are the most open to the constant chatter. RI loves The Machine, labelling it as one of his best friends, becoming ecstatic whenever he sees them. The Machine, on the other hand, isn't too keen on visiting him, as he has a habit of trying to cling onto and prevent them from leaving, which never feels good.

Whispering Of The Many

WOTM is the third youngest iterator of her local group, made shortly after Violent Sky Hues (VSH). The ancients that built and lived on her were lively, very. . . "Dramatic", in her words. They'd always have some drama, some argument, some issue going on, and WOTM was all ears to listen in and learn about the situation. Many would come to her for problem-solving, second opinions, or even just to rant and ramble. Over time she basically became the iterator equivalent of a gossip girl. It was a common occurrence for her to talk about the latest argument or problem to the local iterators, and sometimes other iterators entirely. Not only did she listen in on all of this, but anything interesting that she overheard was likely to be written into data pearls, for safekeeping (she thought it was fun to record all of this and look back at it, since there was never a dull moment in her civilization and she wanted to keep memories of it.)

After the mass extinction of the ancients, she entered an almost depressed-like state for some cycles, she was unused to the sudden silence of the world around her. With the help of the local iterators, she quickly left this state, and now spends most of her time chatting with the local group or helping VSH archive pearls. She treats herself as The Machine's "mom" of sorts, despite not creating them, and takes great pride in her relationship with them.

[altitudeslocalgroup]

DON, opinion on my favorite lizard the cyan goobers!!!

[DON : If they are still around, they should be roaming somewhere around here. Maybe my overseers can locate one for you! We'll have to see.]

[altitudeslocalgroup]

[CONNECTION ESTABLISHED] Asks are now open! I’m fine with a majority of asks, serious and non-serious, but if I don’t feel comfortable I will deny the ask. The available characters for asks are currently : [VSH] - Violent Sky Hues {they/he} [RI] - Reckless Infatuation {he/they} [HTN] - Haphazardly Throwing Needles {they/them} [STB] - Sight Through Blindness {she/her} [DON] - Denial Of Normality {she/they} [WOTM] - Whispering Of The Many {she/it} [HA] - Harmless Abandonment {he/him} [RB] - Requisite Betrayal {they/them} [DS] - Deafening Silence {he/it}

The Machine {they/them} The Rogue {they/them} The Companion {they/them} Information about the main cast is found here.

[altitudeofalcatraz]

Can denial of normality hit the griddy?

yes.

[altitudeslocalgroup]

HA, how did you get your name?

[HA: Thhhough.... Technically it cccould be consideredd... myy real name nnow... hmmm...]

[altitudeslocalgroup]

DON, what’s your favorite modified species?

DON: [Though I think that's pretty obvious, given my puppet's looks.]