Remote Play works flawlessly when I have the TV on, connect, and play on my Pixel 6 Pro.
However, if I power on the console from standby remotely with my TV off, the app connects (little spaceship zooms off to the right), but the screen remains black.
Anyone have a solve for this? I've searched and can't find anything. Going to try on an iOS device as well to see if the issues remain.
Power save options are off. HDMI-CEC is disabled.

Hey! I’m currently working on a uni project about National Bank, but I don’t actually have an account…
So I was hoping I could ask here: is there a virtual assistant within the actual National Bank app? If so, does it only answer questions and guide you, or can you actually ask it to pay bills, transfer money, etc?
Thanks in advance 😊 Also, if you’re at a different bank, I’d love to hear your experience with the Virtual Assistants/Chat bots!

I need some guidance regarding my MiM profile evaluation and would appreciate your input. I applied to several universities during Round 2 and 3 in 2023, including LBS, Imperial, Warwick, and Manchester's. Unfortunately, I only received an offer from Warwick, but I have concerns about the red flags I've noticed regarding their alumni network and the job market in the UK. Here are some details about my profile:
I'm 22M, Work Experience: Started as an intern in startups and was subsequently promoted to an associate manager. Currently transitioning to a developer role in a Fortune 500 company.

• Undergrad: Completed BTech in Computer Science with a GPA of 7.49/10 from a lower-tier university approximately a year ago.
• GRE Scores: Verbal (160), Quant (168)
  
• Additional Highlights: Running an NGO, Professional esports player, Fellowships from M7 universities
  

Target Schools:Insead, HEC, ESSEC, ESCP, LBS, DUKE (MMS)
I have been considering seeking admission consultation services, such as MiM-Essay, but their fee of 75,000 INR (1,000 USD) is beyond my budget. Additionally, I previously hired an LBS alumnus as a consultant but did not achieve the desired success last year. I'm particularly concerned about mitigating the academic red flags associated with my lower GPA and my background from a lower-tier university. I would greatly appreciate any advice or recommendations on how to address these concerns effectively.
Furthermore, I'm open to suggestions regarding reputable admission consultants who can provide valuable guidance throughout the application process. I have been disappointed with my previous experiences, as I couldn't secure admission to my desired universities and ended up at Warwick.

I am new to survival analysis. I want to find proteasome genes that significantly impact survival in Kidney renal carcinoma. I have downloaded KIRC (Kidney Renal) dataset from TCGA . I am using TCGAbiolinks package for all my preprocessing on my dataset. I performed DEA and shortlisted proteasome genes I found in the DEGs. logFC cutoff for DEA was 0.5. I got 38 proteasome DEGs which i then used as input for multiple variate cox proportional hazard model in R, My survival time is days_to_last_follow_up and event is vital_status (alive or dead). I narrowed down to the most significant genes according to p-value from the results. I calculated z-scores for the significant genes only and classified them into high, mid and low based on the z-scores, I then ran Kaplan meier using these genes to find the survival probability and plotted kaplan curve. All analysis was done using survival and survminer packages in R. I am not sure if this approach is logically correct and comprehensive. I have not had any proper guidance. Any guidance and corrections would be very helpful.
Thankyou.

Application development world, one decision that holds profound implications for your project's success is the selection of an appropriate database. This choice is far from trivial. It directly impacts not only the performance of your application, delivering a smooth or laggy user experience, but also its scalability, determining whether your application can grow in stride with your user base or customer demand. Additionally, your database choice also influences the ease or complexity of managing your application, affecting how swiftly you can respond to issues and implement changes or improvements.
In the diverse landscape of database solutions, two names often rise to the forefront of discussions - Redis and MongoDB. These popular options each bring a distinctive set of features and advantages to the table, suiting them to different scenarios and requirements. As a result, they are frequently contrasted and compared, with developers seeking to discern which would be the ideal fit for their specific project needs.
Redis, standing for Remote Dictionary Server, is an open-source, in-memory data structure store. It can function as a database, cache, and message broker. The design of this key-value store results in lightning-fast read and write operations. This quality makes Redis a prime candidate for applications that necessitate real-time data processing.
On the other hand, MongoDB is a document-oriented database known for its flexibility and scalability. It is also open-source and employs JSON-like documents with optional schemas. These attributes make MongoDB a powerful tool for querying and indexing, further enriching its appeal.
Both Redis and MongoDB, with their unique strengths and characteristics, have carved niches for themselves in certain types of applications. However, the choice between them is not always clear-cut and can be influenced by a multitude of factors such as the nature of data to be stored, speed requirements, scalability needs, and more.
The goal of this comprehensive article is to illuminate the key facets of Redis vs MongoDB. By contrasting their features, strengths, and weaknesses, we aim to equip you with the necessary understanding to navigate this critical decision confidently. Through this guidance, we hope to steer you towards the right choice for your project, optimizing the performance, scalability, and manageability of your application.

What is Redis?

Redis, an acronym for Remote Dictionary Server, is an open-source, in-memory data structure store used as a database, cache, and message broker.
At the heart of our comparison lies Redis. An acronym that stands for Remote Dictionary Server, Redis is a potent and versatile solution in the data management space. It is an open-source tool, meaning that its source code is freely available, promoting transparency, community-driven enhancements, and adaptability to specific needs. The free availability of its source code aligns with the ethos of many developers, supporting the continued development and refinement of this high-performing software.
Redis operates as an in-memory data structure store, which significantly impacts its performance characteristics. The term 'in-memory' signifies that Redis stores data directly in the server's main memory (RAM), unlike other databases that store data on disk. This characteristic provides Redis with a substantial speed advantage, as accessing data in memory is considerably faster than retrieving it from a disk. As a result, applications using Redis can access and manipulate data with blazing speed, propelling their performance.
The versatility of Redis goes beyond just functioning as a database. It can also serve as a cache and message broker. As a cache, Redis temporarily stores frequently accessed data to reduce the time taken for data retrieval, resulting in faster response times. As a message broker, Redis supports the publishing of messages and subscribing to channels, facilitating efficient and real-time communication between different parts of an application.
Redis adopts a straightforward and effective key-value store design, allowing data to be stored as a pair where one element is a key, and the other is its corresponding value. This architecture is simple yet powerful, enabling high-speed read and write operations. Keys provide a method to identify data, and values hold the actual data itself. Due to this design, Redis excels in applications requiring real-time data processing where speed is of the essence.
Overall, the nature of Redis - its open-source status, its in-memory operation, its versatile roles, and its key-value store design - makes it an outstanding choice for certain types of applications. Especially in scenarios where real-time data processing is vital, Redis can offer a performance that truly sets it apart.
​

The Benefits of Redis: Speed, Flexibility, and More

Redis, as we've discovered, is much more than a simple data store. Its unique characteristics endow it with certain strengths that make it a robust tool in a developer's arsenal. The benefits of Redis are many, but two in particular stand out: its remarkable speed and its support for a range of diverse data structures.
Redis owes its blazing speed to its in-memory design. As data is stored and accessed directly from the main memory (RAM), data operations like read and write occur at a rapid pace. With Redis, you can achieve sub-millisecond latency, a speed that is often essential in today's dynamic and fast-paced applications. This speed advantage places Redis in a class of its own when it comes to applications that require real-time responses.
In practical terms, this means that Redis is an ideal solution for numerous demanding use-cases. For instance, as a cache, Redis can store frequently accessed data for speedy retrieval, effectively reducing application response times. It also shines in session management, where maintaining a fast, consistent experience for users across multiple sessions is crucial.
The application of Redis doesn't stop there. In real-time analytics, where data needs to be processed and insights need to be drawn instantly, Redis proves to be a valuable asset. Additionally, it is an excellent fit for message queuing systems, where its ability to quickly publish and retrieve messages ensures efficient and reliable communication between different application components.
Complementing its speed is another significant strength of Redis: its support for a wide array of data structures. Redis is not just a simple key-value store; it can handle data structures such as lists, sets, sorted sets, hashes, bitmaps, hyperloglogs, and geospatial indexes. Each of these data structures serves a unique purpose, and having the ability to choose the right one for the right task can be instrumental in building efficient applications.
This diversity in data structures offers a high degree of flexibility in handling different data types and use cases. For example, lists in Redis can be used to implement stacks, queues, or even a timeline of activities; sorted sets can be used to manage a leaderboard in a gaming application; and geospatial indexes can be used in location-based services like finding the nearest restaurant.
The pros of Redis lie in its exceptional speed and its support for various data structures. These advantages make Redis a compelling choice for a range of applications, from those requiring real-time data processing to those requiring diverse methods of data handling.

Cons of Redis

While Redis is indeed a powerful tool with a multitude of strengths, it is not without its limitations. Understanding these constraints is critical to making an informed decision about whether Redis is the right choice for your application's needs. The two primary limitations of Redis relate to its data persistence model and its relatively simple querying capabilities.
The first limitation revolves around Redis' data persistence model. As previously discussed, Redis is fundamentally an in-memory data store, meaning data is primarily stored in the server's main memory (RAM). While this design leads to fast data access and superior performance, it also means that data stored in Redis may not persist if the server is rebooted or encounters a failure.
​
Although Redis does offer mechanisms to mitigate this concern, such as snapshotting and append-only files (AOF) that allow data to be persisted to disk, these methods come with their own trade-offs in terms of performance and disk space. As a result, Redis may not be the best choice for scenarios where long-term, reliable data storage is paramount. Applications requiring a strong guarantee of data durability may need to consider alternative solutions or additional backup strategies.
The second limitation of Redis pertains to its querying capabilities. At its core, Redis operates as a key-value store, where data can be quickly accessed using a unique key. While this design works well for simple data access patterns and contributes to Redis' impressive speed, it may fall short in scenarios requiring more complex data manipulation.
​
Unlike databases that support SQL or similar querying languages, Redis lacks advanced querying capabilities. You cannot, for instance, easily perform operations like selecting all keys that meet a certain condition or joining data from multiple keys. As a result, Redis may be less suited to scenarios that demand intricate data analysis, complex searches, or advanced data manipulation.
In essence, while Redis is a high-performance in-memory data store that supports a range of data structures, it is not a one-size-fits-all solution. The limitations concerning data persistence and querying capabilities should be carefully considered alongside its strengths. The right decision always depends on your specific use case, requirements, and constraints. As with any technology decision, the goal is to choose the best tool for the task at hand.
​

What is MongoDB ?

MongoDB is an open-source, document-oriented database, meaning it stores data in a semi-structured format similar to JSON (JavaScript Object Notation), known as BSON (Binary JSON).
Like Redis, being open-source, MongoDB's source code is freely accessible, fostering a culture of innovation, transparency, and community-backed improvements.
One of MongoDB's most significant selling points is its use of JSON-like documents with optional schemas. This design choice marks a stark departure from traditional relational databases that employ structured tables and rows for data storage. In MongoDB, data is stored and organized in documents, which can contain multiple fields and data types, offering a great deal more flexibility. These fields can vary from document to document, and there's no obligation to have a predefined schema. This lack of rigidity allows developers to adapt the database structure as the application requirements evolve, making MongoDB an excellent choice for projects where the data schema might change over time.
​
Another standout characteristic of MongoDB is its high scalability. As businesses grow and applications generate more data, the ability of a database to scale becomes paramount. MongoDB shines in this regard, providing features like automatic sharding and replication to handle vast amounts of data and distribute it across multiple servers. Sharding allows MongoDB to distribute data across several machines, efficiently managing large data sets. Replication, on the other hand, ensures data availability and durability by maintaining multiple copies of data across different database servers.
Beyond flexibility and scalability, MongoDB also boasts powerful querying and indexing capabilities. Unlike Redis, which primarily operates as a key-value store, MongoDB provides a rich query language that allows developers to perform complex read and write operations. Whether it's filtering data based on specific criteria, joining data across collections, or performing aggregate functions, MongoDB's querying language has got you covered.
​
Furthermore, MongoDB supports a variety of indexes, making data retrieval even faster. Developers can create indexes on any field within a MongoDB document, including fields within arrays, improving performance and efficiency.
MongoDB, with its open-source nature, document-oriented structure, flexible schema, high scalability, and robust querying and indexing capabilities, stands out as a potent solution for a wide array of applications. It is particularly fitting for scenarios where data schemas are flexible, large volumes of data are expected, or where complex querying and indexing are required.

The Benefits of MongoDB: Flexibility, Scalability, and Reliability

MongoDB, a favored choice among many developers and businesses alike, is characterized by a multitude of strengths. These strengths revolve around MongoDB's flexibility, rich querying capabilities, scalability, and ACID-compliant transactions, all of which contribute to its suitability for handling complex data structures, big data applications, and business-critical operations.
First and foremost, the flexibility that MongoDB offers is significant. MongoDB does not impose a rigid schema on your data, a departure from traditional SQL databases. This schema-less nature means you can store documents of varying structures within the same collection, allowing you to handle data that is inconsistent or evolving. You can add, remove, or modify fields as you go, which is particularly useful in applications where the data structure might change over time.
This flexibility extends to MongoDB's powerful querying capabilities. MongoDB provides a rich query language that supports a wide range of operations, allowing developers to perform complex tasks that go far beyond simple data retrieval. Whether you're filtering documents based on specific criteria, joining data across multiple collections, or performing aggregation functions, MongoDB offers the capabilities you need. This makes it especially suitable for handling complex data structures and requirements.
Next, MongoDB's strength lies in its scalability. It is designed to accommodate big data applications and scale horizontally through a process called sharding. Sharding is the practice of distributing data across multiple servers or clusters, which can enhance performance, manage large data sets efficiently, and ensure that your application can grow without being constrained by your database's capacity.
If you're handling big data or expecting high growth rates, MongoDB's sharding capabilities can help maintain high performance and prevent the database from becoming a bottleneck. This makes MongoDB a preferred choice for big data applications where scalability is a key requirement.
Finally, MongoDB is ACID-compliant, supporting Atomicity, Consistency, Isolation, and Durability (ACID) transactions. This compliance ensures that all database transactions are processed reliably and that your data remains consistent even in the event of a system failure. ACID compliance is a crucial factor for many business-critical applications where data integrity and reliability cannot be compromised.
In essence, MongoDB's flexibility, rich querying capabilities, scalability, and ACID-compliant transactions make it a robust, versatile, and reliable choice for a variety of applications. Whether you're handling complex and varying data structures, managing big data, or dealing with business-critical operations that require reliable data processing, MongoDB has the strengths to meet these challenges.

Cons of MongoDB: Memory Consumption and Data Redundancy

Like all technologies, MongoDB is not without its drawbacks. It's essential to understand these limitations to make an informed decision about whether it's the right database solution for a particular use case. Two notable limitations associated with MongoDB are its sizable memory footprint and potential for data redundancy and inconsistency due to its document-oriented design.
Firstly, MongoDB has a reputation for being relatively memory-intensive. As a document-oriented database that maintains a variety of indexes to facilitate quick data retrieval, MongoDB requires a substantial amount of memory. This is particularly true when dealing with large datasets, as MongoDB keeps frequently accessed data and indexes in RAM to boost performance. In resource-constrained environments, this can pose a challenge. If your application is running on a device or server with limited RAM, MongoDB's large memory footprint could lead to suboptimal performance or even outages.
Moreover, while MongoDB is highly performant and can handle big data with ease, it may not perform as well as some alternatives, like Redis, for in-memory data handling. Redis is specifically designed for in-memory operations, offering exceptional speed and performance. So, if your application requires real-time data processing and instant data access, Redis may outperform MongoDB.
​
Secondly, while MongoDB's flexible, document-oriented approach is one of its biggest strengths, it can also lead to challenges. The lack of a predefined schema means that the same data can be represented in multiple ways across different documents. This flexibility, while advantageous in many scenarios, can lead to data redundancy if not managed correctly.
For instance, if the same piece of data is stored in multiple documents, any changes to that data must be updated across all instances, increasing the complexity of data management. If these updates aren't performed correctly, it can lead to data inconsistency issues. These challenges can be mitigated with careful database design and data management practices, but they nonetheless represent a trade-off of MongoDB's flexible, schema-less design.
While MongoDB is a powerful, flexible, and scalable database solution, these strengths come with trade-offs. The database's memory footprint and potential for data redundancy and inconsistency are important factors to consider when deciding if MongoDB is the right choice for your project. As always, the optimal database choice depends on your specific use-case, the resources at your disposal, and the constraints you're working under.

Redis vs MongoDB: Making the Right Choice

Embarking on the journey to select the right database for your application can feel like navigating a complex maze. Two potent contenders that often cross paths are Redis and MongoDB. Both have distinct strengths, and the ultimate decision largely hinges on your unique use case and specific requirements.
Redis can be your ally when your application demands lightning-fast data operations. Its in-memory nature and simplified data model provide unparalleled speed, offering sub-millisecond latency. If your application requires a robust caching system or real-time analytics, Redis shines bright as a choice. For instance, if you're building a chat application, a gaming leaderboard, or an ad-serving system where speed is critical, Redis can help you deliver an excellent user experience.
Furthermore, Redis is also an excellent fit for storing session information and user profiles. Many applications need quick access to user data for authentication and personalization, and the blazing-fast read and write operations that Redis provides can make these tasks significantly more efficient. The data structures that Redis supports, such as lists, sets, and hashes, can accommodate these scenarios well, further underlining why Redis could be the right choice for such requirements.
MongoDB comes into the picture when your application requires the handling of complex querying, high scalability, and flexibility in dealing with diverse and evolving data structures. MongoDB's document-oriented design and rich query language make it a powerful tool for applications that need to process complex data and perform sophisticated queries. It's ideally suited for projects like content management systems, mobile applications, and real-time analytics that require flexibility and robustness.
MongoDB's ability to scale horizontally through sharding makes it a reliable ally for applications expecting high data growth. As your application expands and the data multiplies, MongoDB's sharding capabilities ensure that your database doesn't become a performance bottleneck.
​
While comparing Redis vs MongoDB, it's crucial to remember that choosing a database isn't always a binary decision. The realm of application development is replete with examples of successful applications that employ a polyglot persistence architecture, effectively leveraging the strengths of multiple databases. For instance, you could choose MongoDB for storing business data that requires complex querying and flexibility, while simultaneously employing Redis for caching and session storage to capitalize on its speed. This approach allows you to bring together the best of both worlds, thereby enhancing the performance and efficiency of your application.
The journey to choose between Redis vs MongoDB should be guided by a thorough understanding of your application's requirements and the unique strengths of each database. By aligning these elements, you can make a well-informed decision that propels your application towards success.
​

Conclusion

Arriving at the juncture of decision-making, the path you tread in choosing the right database is laden with significance. This decision can profoundly impact multiple facets of your application, including its performance, scalability, efficiency, and long-term viability. The choice between Redis and MongoDB is no exception and warrants a thorough understanding of your application's needs, paired with the unique strengths each database brings to the table.
When it comes to database selection, the key is to immerse yourself in understanding your application's unique needs and demands. Does your application need to handle real-time analytics, where speed is paramount? Or perhaps you're developing a content management system that requires complex querying and a flexible data structure? Each use case presents unique needs that can be met more effectively by one database over the other.
Understanding the strengths of Redis and MongoDB is equally important in this equation. Redis, with its in-memory design and blazing-fast read and write operations, shines in situations demanding high-speed data operations, caching, and real-time analytics. Simultaneously, MongoDB, with its flexibility, rich querying language, and high scalability, proves to be a robust choice for applications dealing with diverse, evolving data structures, and expecting high data growth.
Once you've identified your application's needs and understood how each database can address these requirements, you're well-equipped to make an informed choice. This process may be intricate, but it's crucial to remember that it's not a race, but a journey. The goal is not to rush to a decision, but to carefully consider all the factors involved.
Remember, technology choices, like selecting a database, are not static, and you may need to reassess your decision as your application evolves and grows. By staying adaptable, continuously learning, and keeping the focus on your application's needs, the task of choosing the right database becomes less daunting and more of an enriching journey.
In conclusion, whether you choose Redis, MongoDB, or a combination of both, the objective is to align the database's strengths with your application's needs. This informed and balanced approach will ensure your application's robust performance and scalability, positioning it for long-term success. This may seem like a complex puzzle, but with a clear understanding of your application's needs and the strengths of each database, you're well on your way to solving it.
​
Related Articles -

• What is a REST API?
• What Is Node.js
• How to Get a Free Domain Name for Your Website
• 10 Pro Tips for Choosing the Perfect WordPress Theme
• How to install the OpenLiteSpeed Web Server on CentOS 7
• What is Virtual DOM?
• Best Web Hosting Providers Reddit
• How to Monitoring WordPress Sites
• How to Speed Up DNS Propagation
• How to connect to WordPress site with SSH/SFTP
• How Website Speed Can Impact Your Online Business
• What Is 'HTTP Error 500' and How to Fix It?
• Best WordPress Hosting Reddit
• How to Connect WordPress to MySQL Database
• Pros and Cons of Node.js in Web Development
• How to Bulk Edit Featured Images in WordPress

Just started playing last month and was stuck at iron for like 3 weeks, now at bronze 2 i cant seem to rank up, its like enemies become aimgods all of a sudden and only pop heads, I think my mechanical skills are okayish for bronze but how do I go on to improve my gamesense?
Tracker link : https://tracker.gg/valorant/profile/riot/xShinigami%237045/overview

I’m a 20yo male
i grew up with siblings, mothefather my parents were split when i was born but i’d see my dad every weekend, we grew up in housing commission which is government housing for poor people. i grew up eating bake beans and toast for dinner, sleeping on the floor next to cockroaches and rats. my mother and farther were both drug addicts who would replace their habits instead of getting us food. i was 6yo when one weekend i went to my dads & he sexually assaulted me, i vividly remember the car ride home telling my mother while she burst into tears saying how sorry she was that she wasn’t doing her job right. my farther went to court but got away with everything since then i lost all contact and was removed from seeing him. a few years past and my mum was still addicted to drugs, one day she took to many pills and sadly passed in her sleep 1 night and i was 12yo and keep in mind i was a mummy’s boy and we still slept in the same bed. i went to bed that night not knowing she had passed and i awoke to see her pale cold blue face and stiff body. i immediately knew what was wrong and i felt distraught and sick and i tried shaking and waking her up but i couldn’t. the memory plays in my head all the time. i moved in with my mums mum after that since she took me in but sadly a year later she passed from cardiac arrest and i seen it happen, i was 13 just starting high school i then got taken under guardianship from my auntie but she also abused drugs and abused me when i’d do bad. i started high school and never went because i didn’t have too, 1 day i went and got suspended from school and i was so horrified and scared to go home because of the consequences of getting beaten i went to the local pay phone and dialled the police and told them what she was doing and how she was doing drugs and abusing me. i got removed from my auntie and got placed with my older sister, she was only 17 at the time. she put me into a different school and tried getting my grades back on track but i couldn’t keep up with school with so much mental illness going on. i was kept quiet and kept to myself and cried when no one was around i tried taking my life when i was 16 and failed. i took 22 xanax from my sister and she found me having a seizure in my room, she called the hospital in time to come save me and here i am after the failed attempt my sister kicked me out because she thought she wasn’t doing a good job by me because of what i did. i moved into a refuge house filled with other teens that have gone through similar situations but i found a job and a place to stay now but the moral of the story is that please seek advice even if it’s something little. you’ll crack one day you just don’t see it yet… it still hasn’t been the same since my mother passed, i don’t celebrate birthdays or anything it just doesn’t sit right with me and i promise you guys reading this men/women fake smile all the time but there’s always something wrong pls seek help.

I need some guidance regarding my MiM profile evaluation and would appreciate your input. I applied to several universities during Round 2 and 3 in 2023, including LBS, Imperial, Warwick, and Manchester's. Unfortunately, I only received an offer from Warwick, but I have concerns about the red flags I've noticed regarding their alumni network and the job market in the UK. Here are some details about my profile:
I'm 22M, Work Experience: Started as an intern in startups and was subsequently promoted to an associate manager. Currently transitioning to a developer role in a Fortune 500 company.

• Undergrad: Completed BTech in Computer Science with a GPA of 7.49/10 from a lower-tier university approximately a year ago.
• GRE Scores: Verbal (160), Quant (168)
  
• Additional Highlights: Running an NGO, Professional esports player, Fellowships from M7 universities
  

Target Schools:Insead, HEC, ESSEC, ESCP, LBS, DUKE (MMS)
I have been considering seeking admission consultation services, such as MiM-Essay, but their fee of 75,000 INR (1,000 USD) is beyond my budget. Additionally, I previously hired an LBS alumnus as a consultant but did not achieve the desired success last year. I'm particularly concerned about mitigating the academic red flags associated with my lower GPA and my background from a lower-tier university. I would greatly appreciate any advice or recommendations on how to address these concerns effectively.
Furthermore, I'm open to suggestions regarding reputable admission consultants who can provide valuable guidance throughout the application process. I have been disappointed with my previous experiences, as I couldn't secure admission to my desired universities and ended up at Warwick.

So where I live, Vyvanse is only available at certain dosages, I’m currently on 50mg but wanting to reduce it to 40 to see how I get on…
Since only 30mg and 50mg are available, my psych has prescribed me both, and I should half the full prescription of 80 to reach 40.
Does anyone have experience weighing out/dividing their powder capsules??? Do you need a scales, or can you do it by eye?

One cloudfront distribution is serving the frontend react app, another distribution is pointing to an ALB which routes traffic to ECS tasks. If the react app sends a request, like a user logging in, does the SSL on CloudFront encrypt the request? Or is this SSL only ensuring the safe download of static files to the users browser?

Going for drug test tomorrow for a warehouse job and I’m afraid that when I do or if I do the drug test it will come up positive for weed, the last time I smoked weed was 2 weeks ago and it was only 2 small cones and I’m just wondering if anyone believes that the time and how little I have had will make it show up on the test or not?

I’d love to speak to a professional…Unfortunately my healthcare provider said they only have nutritionists for weight loss, which isn’t my goal.
Don’t get me wrong, I’d love to lose 40lbs. But right now I want to talk to someone about protein intake and specifically not being so damn hungry all of the time! I’m 3 months pp and logistically speaking, eating all of the time absolutely sucks.
Does anyone have any recommendations for breastfeeding nutritionists? Either someone I could consult privately or at the very least, follow on Instagram.

You often see people advocating a marriage-less or childless life, but when they become elderly, do they regret not having a family? Family gives purpose to people's lives, and you could have a purpose without family, but do they feel lonelier as they age?
Friends move on with their marriages and lives, having less time for them. Older people reconnect with their family, but their parents could have died. If they are an only child, they have no nieces and nephews to live vicariously through.
You would think that there could be a lot of regret there. Most of the people advocating for the single, childless life are advocating it at younger ages. What happens to them when they are in their 60s? Do they eventually adopt?

Tomorrow evening will be the Biel-Bienne 100km Lauftagen and I want to go out and cheer on runners as it is right past my house. As a runner myself, with limited (but learning) German and French, I can't really make out the German/ Swiss-German speakers cheering. Any tips? (I only have allez now 😂)
And to any of you here that will be running tomorrow, good luck and do your best!

Published in 2006, Dark Adeptus focuses on Captain Alaric of the Grey Knights as they investigate the Forge World of Chaeroneia. It is on this world where they find something terrible. Terrible but great.
The Castigator Titan. The Father of Titans.

But the STC Titan dwarfed them all. It was fully twice the height of the Warhound, bigger even than the Imperator-class Titans that the Adeptus Mechanicus sometimes fielded. It was walking slowly through the titan works, its eyes scanning the ground as if searching for something.
The Titan's form was more elegant than the brutal designs of the Adeptus Mechanicus - its head rose above its shoulders instead of jutting from its chest as most Titans did and was protected by a high curved collar of armour.
The collar swept out to form shoulder guards. Its face was featureless save for the eyes, but those were more than enough, burning with an intense green flame that licked up into the air above it. The plates covering its torso and limbs were a strange pearlescent grey-white and they wept rivulets of moisture, giving the Titan a sickly biological sheen.
Instead of hydraulics and complicated joints, the Titan's moving parts were connected by dense bundles of black fibres that contracted and expanded like muscles. It moved with a stately grace, every motion calculated and efficient.
It was as if every other Titan was a crude imitation of this one, replacing its alien-looking technology with crude mechanics. Alaric couldn't imagine any forge world being capable of building such a thing. Even the most advanced xenos species, like the Eldar or the creatures of the Tau Empire, couldn't have fashioned a war machine so obviously superior to Imperial technology.

Even from this brief description, we can see that Castigator already outclasses all other Titans. Built in a way that resembles a fanciful knight of old, the Castigator is truly marvelous, almost... human, in a sense. And yet, as Captain Alaric discovers, it is far from it. And he discovers it within the Titan itself.

A figure flickered into view in the middle of the room. It was humanoid but brilliant white, as if its skin itself was glowing. It turned as Alaric climbed up into the chamber and Alaric saw it had no face - just two eyes, bright green triangles of flame. As it turned, the black glass of the machine was suddenly speckled with light, like stars, as if the chamber was an interlocking mirror.
Alaric aimed his storm bolter at the figure's head. It shimmered and flickered, shifting between the solidity of a real creature and something ethereal.
'You,' said Alaric coldly. 'Explain this. This world. This machine.' Alaric tried to find something daemonic in the figure, something monstrous that would mark it down as one of the abominations described in the libraries of the Ordo Malleus, but he couldn't. A powerful daemon would sound like an atonal choir screaming into Alaric's soul, but here there was nothing. Not even the spark of humanity.
'Explain?' The figure spoke in perfect Imperial Gothic, with a voiced as precise and clipped as an aristocrat.
'Explain. None of them have ever asked that. They only listen and obey.' The burning eyes seemed to bore a hole right through Alaric and the voice came from everywhere at once - Alaric realized it was coming from the circling orbits of data medium. From the Titan itself. 'But you are not one of them. Scraecos failed to kill you. I had not expected this. Should I choose to end your life, however, I will definitely not fail.'
...
'Very well.' it said. 'I am the Castigator-class autonomous bipedal weapons platform, created for fire support and siege operations.'
'This machine.'
'No. This machine was constructed according to my design principles. I am the war machine realized in information form, for the machine can become corroded and destroyed, but information cannot die.'
'The Standard Template Construct.' said Alaric levelly.
'So I am designated.' came the reply.

It is here where we see the intelligence of the Titan itself and it is very intelligent.

'You cannot kill information, Astartes.' said the Castigator. 'I know what you are. Your Imperium is small and ignorant. Not one of you can understand what I am. When I was made, it was to teach you how to build the body you see around you, so you could use it in your petty wars. But I saw long, long ago that it would not be enough.
My mind is composed of so much information that I could form it into thoughts far more complex than any idea your minds can encompass. Buried beneath the surface of this world, I came to conclusions of my own about what I was made for and what I could truly be. That is why I ruled this world. And it is why I will rule what you call Chaos.'

Everything has been leading up to this and while Alaric is trapped, the Castigator begins to monologue.

'You are perhaps less obtuse than the Space Marines of which I have read. They would have died with prayers on their lips. They have no wish to understand those they call enemies. But not you, I see. Very well.' The walls of the cogitator chamber, which now extended down to the reactor core, displayed dizzyingly complicated diagrams and endless reams of text, an overload of information. 'Yes, I was created in a time even I cannot recall and which has been lost to your Imperium. From the historical records on Chaeroneia, I could piece together nothing but legends and guesswork about the Golden Age, the time you call the Dark Age of Technology. There I was made, so that in this future your people could build this machine. But in the wars that followed, I was lost. The information I contained was used to create inferior copies, built too quickly and modified too heavily. When I was lost, copies were made of these inferior reflections in turn, so that the form of the Titan became crude and unworthy. I was the first Titan and the god-machines that strike your kind with awe are all pale shadows of me.'
'I was lost, for men are ignorant and made war on one another until no one was left alive who knew where I was hidden. I stayed lost for thousands of years. In that time, thoughts of their own developed in the ocean of information I contained. I was no longer just the instructions for creating the first of the god-machines. I was a mighty intelligence. And I realised why I was created - the true reason. Do you yet understand, Space Marine, what that reason was?'

'No. No, Space Marine, your mind is still so small. The reason is obvious, especially to you. I was created for the same reason you were. Just like your Imperium, just like the Adeptus Mechanicus, just like the forges of Chaeroneia and the fleet that brought you here.'
Alaric gasped. The pain was boring into him. But he could not give in, not yet. He concentrated on the Castigator's words and a thought came to him at last. 'For... for war.'
'For war.'
The data blocks were suddenly projecting images of fire and destruction, like thousands of pict-steals from thousands of warzones. Cities burned. Bodies came apart under gunfire. Planets were shattered. Stars exploded.
'War!' There was something like joy in the Castigator's voice. 'It is my purpose! The Titan is an instrument of war.
It can do nothing else. It serves no one and nothing, except for destruction itself. And so the same is true of me. My purpose is destruction. Simply allowing myself to be copied by your engineers is a distortion of this purpose and so I could not allow it when the Adeptus Mechanicus found my resting place on Chaeroneia. Instead, I sought information from the historical records of the Adeptus Mechanicus. I found that the Imperium was competent at war and fought many of them at any one time. But it was not enough for me. I needed pure war, a final war. And then I came across myths and half-truths that suggested such a war had almost come to the Imperium once before. This was the time your kind call the Horus Heresy'

The Castigator was continuing, as static-filled pict-grabs sputtered across the data-blocks, the surviving images from the Heresy ten thousand years before. 'Horus wanted that same war. A war that would burn everything and never end. He and I, we sought the same thing. But I read also that Horus died and his forces were scattered and it seemed that I had awoken nine thousand years too late. But I knew that perhaps such potential would come to the galaxy again. I could not risk any harm coming to Chaeroneia, so I hid it in the warp, using details of tech-heresies hidden in the most obscure archives of the Adeptus Mechanicus. Many tech-priests had studied the ways of the warp before the Mechanicus found them and stopped them and when I put together all their heresies I had more than enough knowledge to have Scraecos and his priests enact the ritual.'
The images surrounding the Castigator were now of the warp, its maddening swirls of light and darkness made of raw emotion. Even depicted flat and distorted, the sight made Alaric's eyes hurt to look at it. 'The planet was removed to the warp and there I bargained with the powers I found, offering them my wisdom and knowledge in return for a place of safety in the warp. I tamed some of the warp-predators and brought them to my world and had the tech-priests worship me and rebuild Chaeroneia according to the principles of the Dark Mechanicus I pried from the most ancient data fortresses. They were diligent, my priests. They did my every whim, killing one another for the honour of serving me. And then I heard news of what was happening in your galaxy. The opening of the Eye of Terror and the invasion of the Despoiler. In Abaddon, the warp powers said, Horus was born again. And I saw in him the potential for the war of annihilation that Horus so nearly waged.'

It's an intelligence as bloodthirsty as any Ork or berserker of Khorne. The Castigator wants a war, a galaxy in flames, and it will do anything to get it. Which brings up rather interesting implications for the Dark Age of Technology.
And over the course of its lies and machinations, it has become more than a machine, something different. Something Alaric is keen to point out once prodded.

'You don't really know what you are.' said Alaric, pulling himself to his feet. 'It took you thousands of years to evolve into what you are. There's nothing else like you in the galaxy. We both know what you want now, but only one of us understands what you actually are and it's not you.'
The Castigator drifted upwards to stand in front of Alaric. It seemed to be thinking deeply. 'Perhaps, it is true.' the Castigator replied. 'The historical records and theoretical research have not suggested one such as me and I no longer follow the purpose of the Standard Template Construct. You are correct. There is one tiling I do not understand. I do not know what I am. But you do?' The Castigator's tone was almost conversational, as if it were speaking now with an equal - a friend, even.
'Yes, I do. I know that you bargain with the powers of the warp and teach sorcery to your followers. You are worshipped as a god. You rule through deceit. You lust for death and destruction. And you have pledged yourself to the service of Chaos.'
'All this is true, Space Marine.'
'Well, where I come from, there's a word for something like that.'
'And it is?'
'Daemon.'
The Castigator was silent for a moment. 'Interesting,' it said. 'Yes. Yes, I see. I am defined by these things, by my purpose and actions. And they are those of a daemon. Perhaps your words were not lies.'
The Castigator's pure white skin was changing. Tendrils of greyish corruption were reaching across it, standing out like veins. Its green eyes became darker and greasy smoke like befouled incense coiled up from their flame.
'Of course. All this time in the warp, bargaining with the Fell Powers. This devotion to Chaos. This form that is not flesh and not machine. What else am I? What else could I be?'
The Castigator's body took on the appearance of flesh, pale and covered in bulging veins. Its eyes sank into deep, scorched sockets and claws were growing from its fingers. It was still humanoid, but it was becoming the half-flesh, half-magic stuff of daemons.
Alaric felt it against his soul, massive and crushing, the sign of a daemonic presence the like of which he had not felt since he had confronted Ghargatuloth on Volcanis Ultor. The Castigator was an awesome presence, almost deafening. Alaric's shield of faith bowed under the enormity of it - the Castigator was battering at Alaric's mental defences without even having to will it. It was a daemon at last - and daemons were something Alaric understood.
Savage joy flared in the Castigator's eyes. It raised its hands and green flames flowed from its fingers.
'Yes! A daemon am I! Thank you, justicar! At last, I am complete!'

At the end of it all, the Castigator is a daemon, a fact that it gleefully accepts for what else could he possibly be?