Vocabulary workshop level c unit 9 answers]

Description:
Sunday driver to strengthen the signal, gives clarity. Noise gate at the beginning to reduce noise from single coils or humbuckers. BB preamp as a nice crunchy platform, often on. Sl drive, pantheon set differently to have broaden spectrum of drives. Big Muff to have some creamy solo sound. Rarely used but useful sometimes. Ep booster always on. Makes everything sound better. Halo is a fantastic delay, I modified programmed presets, fantastic option. Dl8 has great lofi and tape delays and reverse which halo does not. HOF with some spring reverb.
https://preview.redd.it/7bs49jnu692d1.jpg?width=4096&format=pjpg&auto=webp&s=35bb100f8491233fecab9b030eb42f5af814b06b
For rock or alternative rock songs, often with just a single guitar.

Hello to all,
I am a staff officer and I have been in the Guard for 9 years with no prior health problems. Unfortunately, my mom has been fighting cancer stage IV since 2020 and I we are loosing the fight.
This situation has naturally increased my anxiety levels and in a preventive measure I decided to go to a psychiatrist and a psychologist (I know for a fact that both of them work better together). I was prescribed with Lexapro and Klonopin in April and have been since then using them in conjunction with my psychotherapy. ( I haven’t used Klonopin in a while and I think that my doctor will not prescribe again due to my progress).
The treatment is working and I have reduced my anxiety levels to normal in the last couple of weeks. I am stable and have no limitations in my civil / military duties.
I went to PHA and disclosed my treatment to the social worker and she put me on a management program, requested a letter from my psychologist and gave 30 days. My psychologist is already working on it and she told me that she will put in it that I am stable and have no limitations in job duties. My Chain of Command is also aware of my situation and my BN Commander told me that he has my back and is supportive.
I am worried because the social worker told me that I could be Med Boarded if I do not finish my treatment within a year and that really bothers me because I really like my job at the Guard and as stated before, I am fully functional. I am not on any profile for the moment, they will evaluate my psychologist letter and decide if they close the case or put me in a temporary profile for 90 days.
Can anyone tell me how long do I have to complete my treatment before it can trigger an MEB? And if I have a timeline, how can I get of a temporary profile in case one is put in place.
Thank you for your time and answers.

Hello to all,
I am a staff officer and I have been in the Guard for 9 years with no prior health problems. Unfortunately, my mom has been fighting cancer stage IV since 2020 and I we are loosing the fight.
This situation has naturally increased my anxiety levels and in a preventive measure I decided to go to a psychiatrist and a psychologist (I know for a fact that both of them work better together). I was prescribed with Lexapro and Klonopin in April and have been since then using them in conjunction with my psychotherapy. ( I haven’t used Klonopin in a while and I think that my doctor will not prescribe again due to my progress).
The treatment is working and I have reduced my anxiety levels to normal in the last couple of weeks. I am stable and have no limitations in my civil / military duties.
I went to PHA and disclosed my treatment to the social worker and she put me on a management program, requested a letter from my psychologist and gave 30 days. My psychologist is already working on it and she told me that she will put in it that I am stable and have no limitations in job duties. My Chain of Command is also aware of my situation and my BN Commander told me that he has my back and is supportive.
I am worried because the social worker told me that I could be Med Boarded if I do not finish my treatment within a year and that really bothers me because I really like my job at the Guard and as stated before, I am fully functional. I am not on any profile for the moment, they will evaluate my psychologist letter and decide if they close the case or put me in a temporary profile for 90 days.
Can anyone tell me how long do I have to complete my treatment before it can trigger an MEB? And if I have a timeline, how can I get of a temporary profile in case one is put in place.
Thank you for your time and answers.

This video has been posted here before, but without a summary of the doc mentioned in it. https://www.youtube.com/watch?v=LGX8vYyOm70&t=1s
In the video, they mention this doc: LONG COVID: PREVENTION AND TREATMENT https://drgalland.com/wp-content/uploads/2023/03/LONG-COVID-PREVENTION-AND-TREATMENT-FINAL.pdf The site is https://drgalland.com
A rough summary of the doc is below. Please refer to the doc for specific details.
Philosophy is Long Covid starts as respiratory infection, but it is essentially a circulatory/blood vessels disease. Reversal may be possible by restoring ACE2 and rescuing mitochondrial function. Caution: treatment may cause adverse reactions in those with MCAS.
Virus attaches to ACE2 (enzyme) in cells, causes cell damage and ACE2 damage. That causes ACE2 deficiency. ACE2 deficiency causes issues with vessels and circulation to organs, increases inflammation. Inflammation impacts mitochondria, which generates 90% of energy to live.

• Lifestyle
  • Sleep - Sleep more than you think you need to.
  • Water - Make sure you stay well-hydrated.
  • Exercise - Exercise is essential for recovery, but for some people even small amounts of exercise makes them much worse for days or weeks.
• Nutrition
  • Diet - Eat more vegetables, eat anti-inflammatory foods
    • Include fermented foods (careful if you have histamine intolerance)
    • Intermittent fasting
    • If you have MCA, low histamine diet may help
  • Spices and Herbs - can enhance ACE2 activity
  • Supplements for ACE2 activity
    • Vitamin D - increases ACE2
    • Curcumin - anti-inflammatory, anti-cancer, antiviral
    • Omega 3 fatty acids - promotes ACE2, anti-inflammatory, neuroprotective, enhance cognitive function, prevent blood clotting
    • CBD - potential ACE2 booster
    • Resveratrol - enhance ACE2 activity, enhance immunity, antiviral, antibacterial
    • Alpha lipoic acid - prevent ACE2 destruction, repair nerve tissue, preserve ACE2 in brain
    • NAC (N-acetylcysteine) - protects ACE2, helps lung function, antioxidant
    • Estrogen - increase ACE2 activity. Ask doctor
    • Cortisol - enhances ACE2 activity. Ask doctor
  • Supplements for mitochondrial rescue
    • Coenzyme Q10 - reverse covid-related fatigue
    • B vitamins - especially B1, B2, B3 for mitochondrial rescue
    • L-Carnitine - mixed results. Ask doctor
  • Reestablishing a healthy gut microbiome - virus, virus remnants may persist in gut
    • Correct imbalance of gut microbes
  • Viral eradication - two step process
    • Tollovid, Bacillus Subtitlis, Vendicinals-9
    • High fiber, plant based diets
    • Vitamin D, Resveratrol
    • Probiotic Lactobacillus plantarum
    • Prebiotic arabinogalactan or galactooligosaccharides, or butyrate itself - butyrate levels
    • Reishi mushrooms
    • Zinc - T-cell function
  • Auto-antibody production - exploring treatment approaches
  • Monocyte/macrophage polarization - enhance ACE2 to restore monocyte and macrophage balnace. Improves T-Cell function
  • Mast cell activation - very complex area. Treatments may cause advers effects in those with MCAS. ​​Specific steps that can alleviate MCAS, described in APPENDIX C
  • Microthormbosis and endothelitis - microthrombosis (micro blood clots) prevention -
    • Gingko biloba and Dan Shen, herbs for microthrombosis
    • Quercetin - bioflavonoid inhibits blood clotting, may help with MCA
    • Nattokinase - anti-thrombotic, heal blood vessels lining, destroys virus spike protein
    • Pycnogenol - heal blood vessels, reduce MCA
    • Vinpocetin - enhance brain function
    • Rhaman sulfate - heal inner lining of blood vessels
• Repairing organ damage - See doctors/specialists
• Mental and emotional health - get help from friends and family if possible. Do not give up!

Appendix A: natural products and dosages

• Sleep aids
  • Melatonin
  • Magnesium glycenate
  • Theanine
  • CBD
• Supplements for ACE2 enhancement
  • Vitamin D
  • Omega 3 fats
  • Resveratrol
  • Curcumin
  • Rosmarinic acid
  • Alpha lipoic acid (ALA)
  • N-Acetylcysteine (NAC)
• Supplements for restoring mitochondrial function
  • Coenzyme Q10
  • Vitamin B1
  • Vitamin B2
  • Vitamin B3
  • Urolithin A
  • Vitamin C, with caution, can impair mitochondrial regeneration in response to exercise
  • Note: virtually no Rx show to enhance mitochondrial function. Hyperbaric oxygen being studied for reversal of fatigue and brain fog
• Supplements for enhancement of memory T-Cells
  • Lactobacilli, especially lactobacillus plantarum probiotic
  • Butyric acid (butyrate) post-biotic
  • Prebiotics, including galactooligosaccharides and arabinogalactan
  • Reishi mushrooms
  • Zinc, for T-Cell function, antiviral effects
• Supplements for reversing microthrombosis and endothelitis
  • Gingko Biloba
  • Dan Shen
  • Qercetin
  • Vinpocetin
  • Nattokinase
  • Arterosil
  • Pycnogenol
  • Note: almost no Rx studied for endothelitis. Exception is pravastatin
• Dosing for viral eradication
  • Tollovid
  • Bacillius subtitlis (Tundrex 1)
  • Vedicinals-9

Excerpt:
I USUALLY HAVE MY PATIENTS FOLLOW VIRAL ERADICATION WITH ACE-2 AND MICROBIOME SUPPORT AND THEN WITH TEMS ENHANCEMENT (DESCRIBED ABOVE) TO RESTORE NORMAL T-LYMPHOCYTE FUNCTION.
FOR PATIENTS WITH POST-COVID FATIGUE, I ADD MITOCHONDRIAL SUPPORT AND FOR PATIENTS WITH CIRCULATORY DISTURBANCES ORSHORTNESS OF BREATH, I ADD TREATMENT FOR ENDOTHELITIS AND MICROTHROMBOSIS. PEOPLE WITH BRAIN FOG MAY NEED SUPPORT IN ALL OF THESE AREAS. THAT PROBLEM IS ADDRESSED IN APPENDIX B.

Navigating The Privacy Tightrope: User Concerns on Social Media Engagement

Name
Department
University
Email

Abstract
This study analyses consumer concerns about privacy in social media engagement, the factors influencing these concerns, and provides strategies for handling them. To achieve this objective, this paper provides feedback on two vital questions (What are the primary concerns of social media users regarding privacy? And What factors contribute to these concerns?) that guide this research. The paper uses qualitative analysis to obtain analyze data. Lastly, the paper provides suggestions for future research and solution
I. INTRODUCTION
In the current digitized world, many people are increasingly sharing their information with the public through social media. However, this act of sharing their details through electronic gadgets such as smartphones has and still increases the risk of privacy violations as people engage through social media. One of the events that significantly deepened consumer privacy concerns in the United States was the Cambridge Analytica data breach on Facebook half a decade ago, which affected many user accounts in the land. This data breach initiated the #deletefacebook movement across social networking sites culminating in many users reconsidering their connections with social media platforms about their trustworthiness, and potential for confidential issues. For one section of users, this meant signing out of these sites while the other section considered it as a chance to reset their confidential settings. According to Bright et al, user privacy concerns differ across sites in the user journey, and only a few sites are developed equally when it comes to user concerns as well as disclosures specifically in connection to social networking sites (1). Throughout this duration of redefining their connections with social networking sites, users find themselves coping with the "privacy paradox" and despite having privacy concerns, online users persist in disclosing their private details for distinct reasons, rather than safeguarding their details online. Therefore, this paper investigates [consumer concerns about privacy in social media engagement, and factors influencing these concerns, and provides strategies for handling them]().
A. Research problem
Social media plays a significant role in promoting interaction and sharing of information among users from all over the world. However, sharing of information over social media sites has and still increases the risk of privacy violations as people engage through social media. It's from this, that this paper settled on evaluating the consumer concerns about privacy in social media engagement, factors influencing these concerns, and providing strategies for tackling them.
B. Aim and Objectives
This study is determined to analyze the user concerns about privacy in social media engagement, highlight the primary factors influencing these concerns, and provide recommendations on desired approaches for handling them.
C. Research question
[1. What are the primary concerns of social media users regarding privacy?]()
2. What factors contribute to these concerns?
II. EXTENDED BACKGROUND
Social media has grown to become the modern-day routine. Currently, many social networking sites are continuing to integrate to offer distinct digital affordances as well as chances to enlarge individual networks, interactions, and information sharing. The availability of these sites has significantly culminated in to rise in user engagement. For instance, TikTok is among the most used sites with a massive following of more than 750 million accounts. Currently, people are becoming more open to sharing individual data and with the aid of the modern digital culture, this has been made possible by utilizing the availability of internet service. Although social media is considered to be of great significance in facilitating communication and entertainment among users, it also stores noticeable repositories of individual details that culminate to privacy concerns. This threat of privacy breaches has continuously increased as social media are frequently accessed through applications on cell phones, where a substantial number of identifiable data is stored, aggregated, and linked across various social networking sites.
Even as the issue of privacy threat has attained massive attention and recognition, especially among people who use these platforms, many studies have reported the concept of privacy paradox, which implies discrepancies involving persons' habits of disclosing individual details and their concern concerning privacy threat. Even though social media users have an increasing concern concerning privacy on media platforms, they are willing to proceed to disclose their data for various gratifications. According to Chen et al, some social media users always show or rather demonstrate reduced effort to offer safety on their confidentiality despite showing significant concern associated with social media (2). On the contrary, there is also a section of social media consumers who are not naive in their revel actions (2). This brings us to an analysis of the historical evolution of social media platforms, the emergence of privacy concerns, and important theoretical frameworks particularly privacy calculus.
Typically, the rise of privacy is significantly connected to the fast growth of technologies and the growing nature of the modern digital space. History shows that privacy was mainly linked with physical and individual interactions. During this time, people were interacting at their homes and with immediate families. However, this was significantly changed by the massive evolution in the digital world. The development of social media sites, and the level of connectivity they provide initiated a new era of unprecedented access to individual information. The new developments have made it simple for people to share their stories and even sensitive information with just one click significantly subjecting one to underlying privacy perils. The world is experiencing significant growth or cases in several data breaches leading to massive breaches of private data to the public. Hackers always target unsuspecting firms or companies to access important details such as the profile of clients or company records which could result in various forms of exploitations. When such a breach happens, it severely affects both the company and the individuals because while the person's data is compromised so is the deterioration of trust in the organization by the public.
Privacy calculus (shown in Figure 1 in the appendix section) refers to the comprehension of privacy as well as safety trade-offs of a certain innovation or firm. It assumes that individuals will divulge individual details whenever the perceived rewards or advantages outweigh the potential cost. Kehr et al. ascertain that the choice of sharing information is associated with privacy calculus as the equilibrium between the rewards and the hazards of revealing individual details or data. A person's privacy calculus can be impacted by several factors including but not limited to the perceived value of the details being revealed and the repercussions of the disclosure. Additionally, the cultures and factors within the society might considerably influence privacy caliculus These factors include but are not limited to societal norms associated with privacy in specific locations. Research has indicated that the threshold of diversity which is always accompanied by the growing society has some considerable effect on the withdrawal from the globe making people even more sensitive to what they share with the public.
III. RESEARCH METHODOLOGY
This study used a qualitative approach in analyzing the user concerns on social networking site engagement. Primarily, this method was applied in this study because it offers a significant opportunity for the researcher to devolve deeply into but not limited to nuances of consumer experiences, viewpoints as well as emotions. Compared to a quantitative approach which only focuses on numerical as well as statistical evaluations, the selected approach here delves deeply into the underlying inspirations, feelings, and means that drive consumer connections online. Approaches such as but not limited to interviews and focus groups provided a substantial opportunity for the researcher to unveil the intricate web of norms and values that significantly impact how consumers interact and their perception of social media sites.
Additionally, the qualitative approach substantially enabled the researcher to attain different consumer concerns. According to Van der Vlist, and Helmond, social networking sites are characterized by a sophisticated structure that comprises different cultures and subcultures with distinct practices as well as concerns (3). By applying a qualitative approach, an investigator can therefore attain immediate information precisely on the experiences of consumers over different populations, and locations. This great understating is significant because it helps to design comprehensive as well as consumer-centric sites that cater to the different requirements as well as tests of the audiences across the world.
Moreover, the qualitative approach offered the researcher a flexible and adaptable experience especially when analyzing emerging issues within social media and user engagement. As indicated by, Reynolds, and Bennett, the qualitative approach allows the use of their analytical paradigms to suit the certain features of emerging issues encompassed in social media as well as consumer involvement (4).
When collecting data, the research applied the following types of qualitative methods:
A. Interviews
Interviews offered a significant platform for participants to articulate their concerns using their own words thus providing the researcher with the desired information on the experiences and viewpoints of people using the complex domain of social media. By applying the open-ended questions, the researcher was able to analyze the profound inspirations that significantly provided limelight to the intricacies of social media. Besides, interviews helped in contextualizing the user concerns in the wider brackets of social and cultural settings in which they take place. By involving the respondents in the study through discussion, the researcher was able to identify factors that significantly influence consumers'' viewpoints and habits including but not limited to peer pressure and cultural ideals. The contextual comprehension offered great support especially in deciphering the motive behind consumer concerns and coming up with solutions or rather strategies that perfectly resonate with the distinct array of consumers globally. Lastly, the interview helped to foster significant discourse that involved the researcher and respondents. This helped in cementing trust and the needed help that improved the credibility of the research.
B. Questionnaires
This study also used questionnaires to obtain relevant data that assisted in the completion of this research. Typically, questionnaires are valuable equipment issued when collecting data because they can gather a significant number of standardized information effectively. This study started by clarifying the objective of the questionnaires to participants. The researcher applied an open-ended type of questionnaire and crafted questions that aided in the collection of data from the respondents. The questionnaires were delivered to participants through email surveys that significantly aligned with the features of the sample group as well as the study aims. The clarity of the communication in the email and privacy substantially fostered participant involvement in the study. Besides, the researcher ensured that the information provided through this tool was secured and systematically organized to foster the analysis of information. In a nutshell, the study implemented effective usage of questionnaires in collecting vital data in the study. The researcher adhered to the best practices and embraced the spirit of iterative refinement thus harnessing the complete ability of the questionnaires and advanced knowledge concerning user concerns on social media engagement.
The sampling technique applied in this study was purposeful approach. This approach is broadly applied in qualitative studies to identify data-rich scenarios for the most efficient usage of scarce resources (5). The sampling techniques comprise of coming up and choosing people or groups that possess knowledge concerning or have experience with the topic under study (5). Through the use of emails, the researcher chose respondents who met certain qualifications and offered valuable information concerning consumer concerns on social media. Based on the participants’ selection criteria, a purposeful sample of (n=60) was selected to participate in the survey.
The research used thematic analysis (TA) in analyzing data. TA has enabled the research to unveil the profound concerns that prevail more across social media consumers. Through a systematic analysis specifically of the content that is common among consumers, the research was able to pinpoint reappearing subjects that show shared concerns, and frustrations. For example, factors including but not limited to privacy issues, and cyberbullying frequently arise in literature addressing the concept of consumer concerns within the context of social media. Nevertheless, TA offered a structured framework that greatly helped in organizing as well as interpreting qualitative information. Through conducting a thorough grouping of information or rather data into topics and sub-topics, the research was able to attain a fundamental insight into the diverse range of issues from the consumers. As argued by Thompson, TA promotes the rigor as well as reliability of the study outcomes, making sure that conclusions are based on empirical proof (6).
Additionally, TA offered significant support in facilitating comparisons as well as synthesis over distinct studies. Considering the idea that the use of social media keeps on growing, investigators always face various pieces of publications addressing the same subjects. TA gives these investigators to highlight the similarities and differences across datasets thus facilitating the enrichment of their comprehension concerning consumer concerns. Despite the above merits of TA in this study, this approach also significantly fails in various areas especially when applied to data analysis (7). For instance, the TA does not have strict directives for completing an analysis. This might easily culminate in variability, particularly in the manner in which this approach is used in different studies, thus rendering it difficult to draw a comparison in findings or replicate studies.
IV. ETHICAL CONSIDERATIONS
The consideration of ethics within studies is paramount since it ensures that the studies are completed by observing integrity, respect as well as fairness specifically on respondents involved. It's vital to uphold ethical consideration because morally right and also helps to maintain the credibility of the research. This research upheld the ethical standards before, during, and after the study in various ways. Firstly, the researcher ensured that the idea of informed consent was considered by significantly providing vivid information to respondents so that they could come up with independent choices about their involvement in the study. The researcher also ensured that there was room for withdrawal from the research by any respondent if they felt to do so. The research also ensured the concepts of confidentiality and privacy were considered during the interview process. Research has shown that it is vital to offer respect to the privacy of respondents to enhance or build confidence and trust (8). Enria et al. Emphasizes the need to maintain privacy during the study process from information gathering up to publication to lock out unauthorized personnel or disclosure of personal details (8). In this study, the researcher adopted the necessary measures to offer the needed protection or security for sensitive data or details gathered during the interview and the study at large.
Furthermore, the researcher also took the responsibility of reducing harm and at the same time raising the benefits for respondents. The researcher achieved this carefully by offering potential safety and eliminating threats associated with the research such as but not limited to physical harm. The researcher ensured that the relevant measures were executed to provide safety to vulnerable groups. In addition, the researcher ensured that there was respect for the respondent's independence as well as dignity. This was achieved by significantly treating respondents with respect and dignity. This entirely involved, honoring their choices concerning but not limited to their inclusion in the research.
Nonetheless, the researcher also ensured that fairness and equity were upheld during the study. The researcher observed the concept of diversity in recruiting participants and at the same time eliminating the prejudices grounded on aspects including but not limited to race or religion. Besides, the researcher took the necessary steps by considering the potential outcomes of the study for the most vulnerable respondents specifically people living with a disability. Lastly, the researcher guaranteed that ethical oversight, as well as responsibility, is observed throughout the research procedure. The researcher took the primary function of ensuring that the study adheres to the ethical standards designed by Institutional review boards.
V. RESULTS
The analysis focused on demographic examination by exploring aspects such as age, gender, education, job status, and social media platforms used. Based on gender, there 27 were female while 33 participants were men. The youngest participant was aged 21 years while the oldest was 57 years. The average age of the participants was 35.4 years, indicating that most were men. The minimum education level of the participant is a high school graduate and all participants were actively in employment or self-employed.
All the participants had registered an account with at least two social media platforms, although a majority (48), had multiple accounts. Facebook, X, Instagram, and TikTok were the most common social media platforms. However, most of the participants had registered an account with professional platforms like Linkedin, although most were not active participants on these platforms. Facebook emerged as the most popular for general networking while X was preferred for emerging news and trending online topics.
TA was adopted to explore the concerns of the users regarding privacy. Following the analytical approach proposed, there were five emerging themes on the most pressing privacy issues by users of social media networks; namely the scale and scope of data collection, potential misuse of user data, third-party app portability, behavioral tracking, and potential data breaches.
VI. ANALYSIS DISCUSSION
A. Discussion
To achieve the objective of the study, it was vital to provide substantial feedback on the two research questions that guided this study. The first question focused on understanding the primary concerns of social media about privacy. Social media networks have revolutionized and transformed communication, social networking, and bridging people's relationships. These mediums offer crucial benefits but also introduce noteworthy privacy concerns. The interviews revealed that the concerns delve around the process of data collection, use of information collected, security, control over private data, tracking behavioral patterns, and the association of third-party stakeholders. The interviews provided a comprehensive understanding by highlighting relevant concerns in detail, which will be explored further by applying the TA framework to ensure that each factor is understood well.
Scope and scale of Data Collection
The interviewees showed concerns about the scale and scope of data collection by social media networks. It emerged as one of the most pressing issues among social media users because of the intricacy of remaining private. Social media platforms obtain an enormous volume of information, including aspects like name, age, and residence and intimate details such as internet activities, hobbies, and text messages. The respondents indicated that the platforms can collect Personal Identifiable Information (PII) because account holders it is one of the requirements at the point of registration [10]. Crucial information like personal email addresses, contact numbers, and date of birth. The participants showed concerns because they suspected fraudulent actors could access the data and use it for malicious purposes.
The participants also showed concern for the ability of social media platforms to study behavioral patterns using the data collected. Participants argued that privacy is a crucial aspect of human dignity and should be guaranteed by social media platforms [11]. One participant noted that Facebook can track their interment activities, sites visited visit, content, preferences, and communication patterns. Therefore, it demonstrates that the use of collected data by social media is an issue that could pose privacy risks.
Misuse of Personal Data
The participants showed concerns about the use of information collected and stored in social media databases. Social media platforms can leverage the data collected to understand how to improve the experiences of users and other aspects that improve the quality. Based on the participants' responses, targeted advertising can be a vulnerability to users. Social media platforms can use the data to facilitate Ad Personalization [11]. The algorithms can be trained to analyze user data to enable personalized advertisements, which is an invasive antic. The platforms can be involved in the monetization of user data by selling the analyzed ta to third-party organizations.
The participants of the survey observed that social media platforms used the data beyond advertising purposes. The algorithms can be refined to understand social media consumption patterns to influence their purchase decisions. This is a form of manipulation by feeding users targeted information to influence their attitudes, behaviors, and choices [12]. Third-party organizations can leverage modern advances in AI and analytics to study the behavior of social media users and enable the system to make product recommendations and even product development.
Data Breaches
Data security emerged as a leading theme in during the interviews as recent news of frequent cyberattacks and monumental data breaches led to the exposure of personal information. Most participants noted that the high-profile incidents of data breaches by social media platforms like the Facebook-Cambridge Analytica scandal led to the manipulation of voters' decisions in the US election and the Brexit vote. Millions of personal information data were mined without the users' consent. The exposure of the data led to adverse consequences including identity theft, financial fraud, and online vulnerabilities.
Similarly, users noted that user accounts frequently face security vulnerabilities. The accounts have weak password protocols. Some participants indicated that they have been victims of social media account hacks due to the weak security protocols. However, the participants were encouraged to indicate the password, implying that they used a common password including date of birth, name, and city [10]. Some users understood the two-factor authentication, which is crucial in minimizing hacking. The two-factor authentication protocols lead to problems by adding layers. Making it unpopular among most social media users.
Poor account security reduces the ability of users to control their personal information. However, most social media platforms recognize that there is a need to enhance the security of users' accounts. The security setting is complex and confusing to many ordinary social media users. A significant proportion of participants did not understand the process of setting the advanced security protocols [13]. Most users rely on the default security setting, which encourages sharing of personal information and social media activities. The users are expected to maneuver the complex process to ensure the security of their data. Shifting such an obligation to users with limited knowledge about the technicality of social media account security raises ethical and moral concerns.
Behavioral Tracking
Most users noted that social media platforms can perform behavioral tracking by analyzing social media activities, patterns, and content. Cookies Technologies provide the platforms with a tool to perform continuous tracking across different websites, retaining in-depth profiles of user's behavior [13]. The platforms can conduct behavioral tracking with informed consent: The Cambridge-Analytica incident reveals the vulnerability of social media platforms on individuals and society. The profiles created were used not only for marketing and advertising purposes but also to influence political campaigns.
Participants of the study indicated that the ability of social media platforms to collect data limitlessly can expose users to surveillance vulnerabilities. Collecting private and intimate data, such as personal health information and PII can enable third-party actors to perform surveillance since each aspect of social media interaction is documented. The Power held by social media companies leads to the loss of anonymity over personal information to some extent. The structure of social media communication makes it impossible to maintain anonymity because the data is augmented into a singular platform.
Third-Party Apps Data Portability
Portability and the right to delete information is also a concern among users. This stems from the concept of the "right to be forgotten." Users may opt for some content from their social media platforms. Users have limited control over the spread and distribution of the content they post. Deleting the content does not limit other account owners to post similar information [14]. This is a significant concern highlighted by the participants of the survey. deleting their data or controlling its spread once shared.
The growth of social media has coincided with an era of integration of online systems and solutions. Most social media platforms allow third-party apps and integrations. Third-party applications operate based on their practices, policies, and unique terms and conditions for service. There are more privacy issues when social media networks integrate third-party apps and services. Integration of third-party Apps into the social media application can facilitate the collection of data and potential for misuse [12]. There is a lack of clarity over the party responsible for the security of data. Besides, the more the data is available to employees of both organizations, it can be at risk of breaches.
The second question focused on examining the mediating factors contributing to the social media user’s privacy concerns. Based on the TA, the merging factors included inadequate regulatory protection, ineffective social media platform privacy policies, and ignorance of users on appropriate security settings.
Accessibility and Permission
Accessing the data held may require permission from the user or the social media platform. Some apps may be granted broad permissions that allow them unlimited access to the information. Third-party apps often request access to a wide range of user data, which may not be necessary for their functionality. There is a lack of appropriate oversight over data and usage by third-party organizations and apps. The platforms do not provide sufficient oversight and guidelines on how the third parties use and protect the data they access.
Therefore, there is potential for misuse and manipulation of user data by social media platforms and third parties who access the data. Social media platforms may have strict privacy but third-party organizations may have inconsistent privacy concerns. The Cambridge Analytica scandal is an illustration of such an incident, where Facebook data was accessed with crucial privacy breaches. Social media platforms pose a significant threat because they can lead to trust issues among users. Some of the participants noted that they had deleted their accounts because of fear of privacy breaches [14]. The constant privacy issues influence the attitudes and behaviors on social media and their level of trust in these platforms. Hence, the participants have adopted self-censorship due to the awareness of potential online tracking and data collection. This involves avoiding sharing some details or expressing views freely.
The risk of privacy breaches can minimize the levels of social engagement to conceal one's true personality and character. Privacy concerns can lead to reduced engagement, with users less likely to participate in activities that require personal information sharing. Users have also shown concerns for better data and information security practices by social media platforms. The participants of the survey indicated that transparency over the use of the data collected is necessary to protect their confidentiality [12][13]. The growth in awareness and understanding of the right to privacy has been a significant factor that has influenced the demand for better information security protocols.
Inadequate Regulatory and Policy Concerns
Privacy is a right recognized by the laws of different countries including the United States. There are specific legislations such as the General Data Protection Regulation (GDPR) in the EU block or the California Consumer Privacy Act (CCPA), enacted to protect the privacy and confidentiality of users' data. However, it does not provide sufficient protection to users since there are several hurdles in its implementation. The lack of effectiveness and compliance with the law has contributed to the loopholes that are constantly utilized by the platforms to collect personal data [12]. The legislations impose legal and criminal liabilities on social media platforms, which can be a crucial method of deterring platforms from engaging in unauthorized sharing of users' data.
Ineffective Social Media Site Policies
Social media platforms have policies that guide the usage of data collected from account holders. Most of these terms are often complex and it is difficult for the users to comprehend. Users sometimes agree to conditions without fully understanding service and privacy rules since they are lengthy and complex [11]. The participants contented that they had never read through all the policies, terms, and conditions of using the site. These challenges lead to the acceptance of policies that allow the collection and usage of data.
Besides, social media platforms are constantly enhancing policy changes that could affect the security of users' data. Platforms regularly change their terms of service, sometimes making major adjustments to privacy provisions that users might not always see or comprehend [13]. The ignorance of users creates vulnerabilities in users and places social media platforms in a superior position. This enables the platforms to include policies that are pro-data collection.
B. Conclusion
Social media companies need to improve privacy controls, strengthen security, simplify privacy settings, and follow strict regulations to strike a balance between user interaction and privacy. Platforms can provide a safer and more reliable environment and encourage users to interact without jeopardizing their personal information by fully addressing these main concerns. This fine balance, where the advantages of connection and sharing are evaluated against the fundamental right to privacy, will determine the future of social media.
Dealing with a wide range of intricate issues is necessary when navigating the social media privacy tightrope. It makes sense that users are concerned about the scope of data gathering, the uses to which it is put, the security of their data, and their control over it. These issues become even more complicated when third-party apps are involved and behavioral tracking is used. These privacy concerns provide serious legal and policy hurdles in addition to affecting user behavior and confidence.
C. Future Research
Social media platforms need to reconsider the concept of user privacy to protect the confidentiality of user data. It is necessary to communicate clearly about the purpose for which the data collected is to be used. The current system is opaque and the users have limited knowledge about the terms and conditions of service. Organizations must protect the integrity of user data. Failure to comply with the regulatory requirement can lead to substantial financial and reputational damage to a social media platform. Facebook has been heavily fined for data breaches and scandals.
Policymakers and legislator should also understand the risk that social media platforms expose to their users and introduce stricter regulations and guidelines on how these platforms can use data collected. Currently, social media platforms are powerful and can influence users to accept terms that would allow the collection of personal information. The legislation should focus on introducing guidelines that compel the platforms to be transparent and use terms that are easily understandable to all users. The study focused on users that are educated but they were also not familiar with the terms on the use of personal data by the platforms. The government can provide better protection by introducing liabilities on platforms that mislead users to accept opaque terms and conditions with a loophole that will allow the collection of PII. Government involvement will be necessary as information and communication technologies continue to transform how organizations collect, analyze, and utilize online users and activities.






References

(1) Bright, Laura F., Hayoung Sally Lim, and Kelty Logan. "“Should I Post or Ghost?”: Examining how privacy concerns impact social media engagement in US consumers." Psychology & Marketing 38, no. 10 (2021): 1712-1722.
(2) Chen, Hsuan-Ting. "Revisiting the privacy paradox on social media with an extended privacy calculus model: The effect of privacy concerns, privacy self-efficacy, and social capital on privacy management." American behavioral scientist 62, no. 10 (2018): 1392-1412.
[(3) Kehr,]() Flavius, Tobias Kowatsch, Daniel Wentzel, and Elgar Fleisch. "Blissfully ignorant: the effects of general privacy concerns, general institutional trust, and affect in the privacy calculus." Information Systems Journal 25, no. 6 (2015): 607-635.
(4) Van der Vlist, Fernando N., and Anne Helmond. "How partners mediate platform power: Mapping business and data partnerships in the social media ecosystem." Big Data & Society 8, no. 1 (2021): 20539517211025061.
(5) Reynolds, Samantha, and Noah Bennett. "Dynamic Insights: Qualitative Explorations Across Diverse Sectors in the Evolving Socioeconomic Landscape." (2024).
(6) Palinkas, Lawrence A., Sarah M. Horwitz, Carla A. Green, Jennifer P. Wisdom, Naihua Duan, and Kimberly Hoagwood. "Purposeful sampling for qualitative data collection and analysis in mixed method implementation research." Administration and policy in mental health and mental health services research 42 (2015): 533-544.
(7) Thompson, Jamie. "A guide to abductive thematic analysis." (2022
(8) Peel, Karen L. "A beginner's guide to applied educational research using thematic analysis." Practical Assessment, Research, and Evaluation 25, no. 1 (2020): 2.
[(9) Enria, ]()Luisa, Naomi Waterlow, Nina Trivedy Rogers, Hannah Brindle, Sham Lal, Rosalind M. Eggo, Shelley Lees, and Chrissy H. Roberts. "Trust and transparency in times of crisis: Results from an online survey during the first wave (April 2020) of the COVID-19 epidemic in the UK." PloS one 16, no. 2 (2021): e0239247.
(10) L. Baker-Eveleth, R. Stone, and D. Eveleth, “Understanding social media users’ privacy-protection behaviors,” ICS, vol. 30, no. 3, pp. 324–345, May 2022, doi: 10.1108/ICS-07-2021-0099.
(11) Z. Rózsa, L. Ferenčáková, D. Zámek, and J. Firstová, “Generation Z’s perception of privacy on social media: Examining the impact of personalized advertising, interpersonal relationships, reference group dynamics, social isolation, and anxiety on self-disclosure willingness,” oc, vol. 15, no. 1, pp. 229–266, Mar. 2024, doi: 10.24136/oc.2956.
(12) N. Barrett-Maitland and J. Lynch, “Social Media, Ethics and the Privacy Paradox,” in Security and Privacy From a Legal, Ethical, and Technical Perspective, C. Kalloniatis and C. Travieso-Gonzalez, Eds., IntechOpen, 2020. doi: 10.5772/intechopen.90906.
(13) J. Suter, A. Irvine, and C. Howorth, “Juggling on a tightrope: Experiences of small and micro business managers responding to employees with mental health difficulties,” International Small Business Journal: Researching Entrepreneurship, vol. 41, no. 1, pp. 3–34, Feb. 2023, doi: 10.1177/02662426221084252.
(14) K. D. Martin and R. W. Palmatier, “Data Privacy in Retail: Navigating Tensions and Directing Future Research,” Journal of Retailing, vol. 96, no. 4, pp. 449–457, Dec. 2020, doi: 10.1016/j.jretai.2020.10.002.





































Appendix

Figure1: The conceptual model of extended privacy calculus

I'll put you in context:
we met in an event and I got her Instagram thanks to a friend. At the event she winked at me and we exchanged a few words, but nothing more. Then I opened up on her Instagram, teasing her. She ignored me and I realized she had a boyfriend from the featured stories. However at the same time, she always liked my stories and sometimes answered them until one day we started chatting about superficialities. The girl is 20 years old and I am 24. I have told her that I will pursue an academic career and I am waiting to enroll in a doctorate, something that she also wants to do later in the same field. Yesterday we exchanged phone numbers. I told her that maybe it was a little violent, but partly I don't like talking on Instagram (the platform is very uncomfortable). We have continued talking and she has confessed to me that she is bisexual. She also asked me about a woman at the event we were at and she jokingly told me that she questioned her relationship with her boyfriend because of a very pretty girl who was with us (I don't get it it's was a joke or not, sometimes it's hard for me to catch them). she has also told me that I am a cool and intelligent girl, we have talked about our areas of study and she is passionate that I am specialized in what she wants to do.
What makes me doubt is that I don't know if she is really just being nice to me because she admires my professional and academic career level (I am currently working on something very cool related to what I have studied) seeing me as a mentor or if she is really interested in me. I also told her that I can try to help her to get an internship to the same NGO I was this year… Yes, I'm aware that she has a boyfriend... it's complicated. I also flirted a bit with her, but I don’t know how she is interpreting it even thought I know she gets it but: a) she doesn’t want to make any move since she has a boyfriend b) she doesn’t like me at all and just wants me as a friend c) she just wants the internship so

This is a collection of responses from the competitiveoverwatch AMA from developers u/Blizz_Alec , u/Blizz_JNoh , u/Blizz_Hudson , and u/Blizz_Jodie . Thank you for your information!
Edit: Link to the original competitiveoverwatch thread
Alec answering question from North-Blueberry-7710 about testing in Mirrorwatch

No secret testing of anything upcoming in the immediate! We do look at how some changes play out though when they become more real and get lots of games, I think the Bastion Ultimate in particular was quite fun even if very loud and on the border technically. Reinhardt's Frenzy passive was also something we played around with internally but it was quite hard to communicate effectively. It's always good to see what players get excited about when there are more wacky ideas such as Mirrorwatch or April Fool's, some of those could become real down the line.

Alec answering question from swamp_god about Cassidy and Reaper changes

The two upcoming updates that were mentioned were for Cassidy and Reaper.
For Cassidy, we started some exploration pre-Season 9 for his update. Due to where he was at that time, this update was originally looking at multiple pieces of his kit but we saw the Season 9 changes largely benefit him so the update has gotten more focused on Magnetic Grenade and other Quality of Life updates (specifically to his Ultimate). In Season 11 we are updating Magnetic Grenade. It will behave closer to old Flashbang (no magnetic homing to the target, used in the short range) and will slow/hinder the target. We think that plays a lot better with his kit and removes some of the larger frustrations around Magnetic Grenade. More specifics on all that soon.
For Reaper, we went fairly wide as well in the beginning and then started to focus closely on updating Shadow Step. At the moment, we have something we quite like but it's actually a large technical challenge and we are in the process of planning out the work/seeing what's possible. In the meantime, we may buff Reaper in some non-Tank Buster ways as he lost a lot in the most recent update.

Jnoh answering question from Headedbigfoot8 about the hardest hero to balance in each role

Probably Sombra due to permanent invisibility restricting how deadly we can make her but also because she is a hero that excels with strong team coordination.
There are a handful of other heroes with performance stats that differ greatly from the broader community perception of them and that can create difficulty in how we approach balancing them as well.

Hudson answering question from walter_2010 about average playtester rank

A huge part of our team culture revolves around playtesting. From Designers, to QA and community management, everyone has the opportunity to play what we're working on and give open honest feedback. One of the advantages of this model is we get perspective from a wide range of player ranks from GM 1 to Bronze 5. It's been a while since we've taken an official poll on average rank, but having a wide sample helps prevent tunnel visioning on feedback from specific ranks.

Alec answering question from O2M about lack of patch consistency and Symmetra

1. ⁠We should do a better job about this, especially when it comes to getting the community's visibility on what we are seeing vs. what the playerbase may seem to think is the best hero at any given one time. These can differ regularly as certain heroes get power reputations (weaker or stronger than their reality at a given rank) that are hard to shake off. Thanks for the feedback there, will make sure we have something here even if it's a simple change.
2. Symmetra kept some of the buffs in that patch but yes we hear the feedback of where her current power level is. We may have been a bit overreactive to the Mauga compositions popping up during that timeframe (he was certainly overtuned), but we wanted to be sure of it. For right now, we are in discussions about Symmetra and especially her frontline presence. Believe that's a piece of the kit we'd like to promote further, whether through her survivability or beam damage.

Alec/Gavin answering question from Thee_Archivist about the removed smurf detection from MMR going from QP to comp

I tapped in our own Gavin Winter for this first part, he's what he had to say: "There haven't been any changes to these systems, but there are edge cases like the example of Guxue that was recently posted in this subreddit where our systems don't perform in the way we'd like. Most players will still be placed appropriately as they transition from Quick Play to Competitive Play, but unfortunately cases like this have always been possible. Explaining exactly how this happens would make it easier reproduce, so you'll have to excuse me from not going into intricate detail here."
For the second part of your question, we believe we made it slightly too difficult to climb at the highest ranks and are looking at making some adjustments soon.

Jnoh answering question from Owlcharts about making win and pick rates public (this one hurts).

There aren't any plans currently to shift resources toward supporting something like that. Sites like Overbuff don't have the complete picture, but the data there for win rates and such is generally fairly close.
There is some argument against being too transparent with those stats in that it can create a bit of a feedback loop where you might see player behavior driven by what appears to be the meta in the stats, but that kind of happens already with just the general discussion and sentiment around heroes without stats as well.
Our target range for hero viability by win rate is between 45-55% unmirrored win rate at Masters rank and above. Those individual win rates often can fluctuate 2-3% by day, mostly because heroes tend to have a wider range of win rates per map and we're looking at the global average of those, but also individual player performance isn't consistent.
Lower pick rate heroes fluctuate more and there is less confidence in their win rate being indicative of actual strength. Extremely high pick rate heroes have a similar problem when looking unmirrored stats.
In the end stats require interpretation to understand their context and that is why they are not the only basis for balance changes, but are a useful tool to measure impact of changes patch-over-patch.

Alec answering question from AccurateMeminnn about the reworks to Roadhog and WB

For the most part, we are relatively happy with the new bases both have been given but there is still some fine-tuning to be done.
I'll start with Wrecking Ball. Our goals were to give him more flexibility with his movement/engage options, heighten the benefits he gives to his team, and give him some quality of life updates. I think our changes all attempt to address those goals but one I think we can hit harder in the future is heightening the benefits he gives to his team. We were a little conservative with the Adaptive Shields change (overhealth is hyper scary in coordinated environments), so perhaps there's room for that to be more pronounced through tuning and actual feedback received in game (working on some updates there). Overall though, Wrecking Ball is doing much better after his recent updates and we believe we have a great base to work with going forward.
For Roadhog, aside from the conversations about his current survivability (we plan to hit that soon) there are some things for us to look at concerning the frequency of his combo. For example, his Pig Pen begins to go on cooldown when you throw it. So you can pre-place one, it gets destroyed, and then Roadhog already has it ready again (even though the enemy may think there's a window where Hook is less deadly). That's one discussion we've recently had. Still some work here for us to do in terms of the value Pig Pen brings outside of the combo as well and how we can make those windows of combo potential less frequent.

Jnoh answering question from Arrge about Hanzo post season 9, specifically about the one shot

Hanzo is still an effective mid-range burst damage hero even without the one-shot kills. Post season 9 with the projectile size changes actually saw an increase in Hanzo's performance on the stat side. I do hear you on the loss of how good the one shot kills felt, but an overarching goal of season 9 was to reduce a lot of those burst damage frustrations for players on the receiving end of it. Armor changes in season 10 have also been a benefit to his damage.
Still very early but we've been experimenting with adjusting health pools for some of the more evasive or high damage heroes which would also put them back into the range of lethal Hanzo headshots and some other hero combos at 225 HP, but while it would bring some interesting texture to hero interactions overall there are also a bunch of other problems to solve if we want to go through with it.

Alec answering question rom idrkbrotbh about Hog's survivability.

Yes, we plan on nerfing his survivability very soon. We are touching Take a Breather and Whole Hog in an upcoming patch. Hoping that can go live tomorrow.

Alec answering question from Heropon4Hyrule_010 about the difference in pick rates from before the midseason patch (major tank buffs) and after

Some of this is related to meta happenings or balance changes but also related to armor changes/headshot reduction for Tanks. From what we can see the biggest winners (in terms of their performance delta) of the patch are: Ana, Junkrat, Pharah, Roadhog, Sigma, Wrecking Ball, and Zarya.
Many heroes stayed relatively similar while a handful saw a decrease in performance (Bastion, D.Va, Mauga, Orisa, and Reaper).

Alec answering questions uestion from Mefionir-Omnic about Quick Play Hacked changes and Clash mode

These fall outside of hero design but can talk briefly about the first two questions

1. ⁠Think you are referencing the speed boosts that would potentially come to Flashpoint. Took us some time to get these in a good place but they have been promising in playtests and are on track for a later season. It's important to us that when we add elements like that to a mode that it not only brings quality gameplay but is also communicated well through Sound and VFX. Feel good here now.
2. ⁠We got a lot of great feedback but there are some things the team wished we did better with the Clash Preview. Firstly, it should have showed up more in Quick Play so y'all got more reps on it and can get a better feel for the flow of the game mode. Secondly, we don't think it was best suited for Open Queue in Arcade. If we do something like this again, we'll clean that up. With the feedback we received, we've been investigating how to make the final point more appealing to capture for the attacking team. Many games could result in the attacking team not actually wanting to push onto the last point because it wasn't worth the reward (harder to capture, give up a lot of positioning if you lose). Plenty of iteration happening here now to address that particular issue.

Alec answering question from Mabangyan about Roadhog and Lifeweaver

Answered the Roadhog question in a different place, but yes changes coming soon.
For Lifeweaver, one of the discussions we are having right now (actually this week) and have been having for a while is around the friction that comes with switching between his healing and damage. Giving him more flexibility here would be a great boon to his capability within team fights. Additionally, we've experimented a lot with his Petal Platform. Personally would love for that to be a more attractive area to stand on as a teammate (whether that be through a buff the platform gives you or something else) but there's a lot of learned behavior to work through as allies hop off the platform quite often.

JNoh answering question from Scared_Funny_1865 about tank counterswapping

At its core, Overwatch is a game designed around being able to swap heroes to gain a tactical advantage or help solve a challenge you might be encountering. This contributes to keeping the moment-to-moment gameplay experience dynamic, drives hero diversity and offers a wider range of both strategic gameplay and skill expression in learning when/where/how to play multiple heroes.
There is a question of how much of an advantage is too much compared to the cost of switching. Ideally we want counters to be clear and understandable, but soft enough that it's still possible to outplay a disadvantaged matchup. It is a team game though and 1v1 matchups are not the highest priority when assessing the heroes.
Tanks do feel this the most with only one of them per team in 5v5 role queue, but all roles do experience the pressure to counter and be countered to an extent.
We're striving to find a balance between swapping heroes every death, (which certainly feels too often), and rarely swapping heroes or getting trapped in mirror matches every game, which quickly leads to fatigue. We've seen a lot of improvements here compared to earlier seasons, but it could always be better.
"Unhealthy" and unpopular designs are not necessarily the same thing. When designing heroes, we aim to provide a wide range of playstyles, mechanics, and aesthetics for players to enjoy. It's okay if they don't all resonate with everyone broadly. We'll do our best to make the game as fun as it can be for a wide audience.

Alec answerinf question from Skiesti about Mercy's lack of changes since the 20% DPaSsive revert, as well as general performance since season 9 (this answer is super tone deaf being real).

1. ⁠I think we are more happy in the 20% DPS Passive world than the 15% (it cuts through a lot better, helps mitigate the healing more effectively) so Mercy is more worth a look when that world is permanent. There are some questions of how far we can push her movement and know that is one of the most requested changes.
2. ⁠Mercy is still a top-picked 3/4 Support and even higher on console until you hit GM/Top 500. Her performance follows a similar trend, where she's in the top grouping for most ranks and remains above average at the highest ranks. Doesn't mean that she wont receive changes but that is where she is at currently.

So I was recently using an ASUSTOR NAS with an 8TB HDD (The device in question) and I removed it while trying to install a larger 12TB HDD thinking if anything went wrong I could preserve my data. Well something went wrong when I tried to plug it back in as it became unreadable somehow. I quickly shut it off to prevent any further damage to my data and I'm now trying to read it in a linux system I have.
Output from a few commands I've executed:

lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS [redacted irrelevant drives] sdd 8:48 0 7.3T 0 disk ├─sdd1 8:49 0 255M 0 part ├─sdd2 8:50 0 2G 0 part │ └─md126 9:126 0 2G 0 raid1 ├─sdd3 8:51 0 2G 0 part │ └─md127 9:127 0 2G 0 raid1 └─sdd4 8:52 0 7.3T 0 part └─md125 9:125 0 0B 0 raid1 sr0 11:0 1 1024M 0 rom 

**********************************************************

sudo mount /dev/md125 temp mount: /home/xerxys/temp: can't read superblock on /dev/md125. 

**********************************************************

sudo mdadm --examine /dev/sdd4 /dev/sdd4: Magic : a92b4efc Version : 1.2 Feature Map : 0x2 Array UUID : eae8d157:f26bed0e:53401d56:a51f05ee Name : AS1102T-A234:1 Creation Time : Sat Jan 7 01:34:53 2023 Raid Level : raid1 Raid Devices : 2 Avail Dev Size : 15618875392 sectors (7.27 TiB 8.00 TB) Array Size : 7809437696 KiB (7.27 TiB 8.00 TB) Data Offset : 264192 sectors Super Offset : 8 sectors Recovery Offset : 0 sectors Unused Space : before=263912 sectors, after=0 sectors State : clean Device UUID : 70732a10:4b9639ce:b464abbc:1a4e673c Update Time : Thu May 23 20:11:31 2024 Bad Block Log : 512 entries available at offset 264 sectors Checksum : cdfa67f3 - correct Events : 1560 Device Role : Active device 0 Array State : A. ('A' == active, '.' == missing, 'R' == replacing) 

**********************************************************

lsblk -f NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS sda ext4 1.0 9e05ed66-14eb-41ab-aab0-7a72a9690650 820G 73% /home sdb ├─sdb1 vfat FAT32 89F0-4BB5 1G 1% /boot/efi ├─sdb2 ext4 1.0 132ea5ec-fc55-44d8-a8fa-b3aa739e31f4 1.5G 13% /boot └─sdb3 LVM2_member LVM2 001 kXvAK2-isKg-dHeQ-ELFO-K5hl-Tdfz-o5yPdS └─ubuntu--vg-ubuntu--lv ext4 1.0 8b5cf176-34a1-467c-85b1-68b14512c468 50.8G 43% / sdc └─sdc1 ext4 1.0 8d208379-8a90-4ff1-8e83-15ed55eb506d 3.4T 0% /$HOME/d1 sdd ├─sdd1 ├─sdd2 linux_raid_member 1.2 AS1102T-A234:0 e87b3b05-9c86-e5b6-cfa4-0a3eaf0b8c6b │ └─md126 ext4 1.0 e1698386-a948-47a3-a1bf-a93030828037 ├─sdd3 linux_raid_member 1.2 PrinceNAS:126 cb96333c-7c88-3cb1-6c2b-92de5075488f │ └─md127 swap 1 61ea6651-cf6e-4b34-98ec-a283ca6233d8 └─sdd4 linux_raid_member 1.2 AS1102T-A234:1 eae8d157-f26b-ed0e-5340-1d56a51f05ee └─md125 sr0 

**********************************************************

sudo fdisk -l /dev/sdd Disk /dev/sdd: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors Disk model: ST8000VN004-3CP1 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: A22F2D9C-CA68-4E0E-AF8F-F1CF06D0B93B Device Start End Sectors Size Type /dev/sdd1 2048 524287 522240 255M Linux filesystem /dev/sdd2 524288 4718591 4194304 2G Linux RAID /dev/sdd3 4718592 8912895 4194304 2G Linux RAID /dev/sdd4 8912896 15628052479 15619139584 7.3T Linux RAID 

**********************************************************

cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md125 : inactive sdd4[2] 7809437696 blocks super 1.2 md126 : active raid1 sdd2[3] 2094080 blocks super 1.2 [2/1] [U_] md127 : active (auto-read-only) raid1 sdd3[3] 2094080 blocks super 1.2 [2/1] [U_] unused devices:  

I am able to mount md126 although it only contains the 'etc' and 'usr' directories which isn't what I'm interested in recovering. This problem is exclusive to md125 which is inconvenient as it has all my data on it.
The drive says it's part of a RAID1 system but building my single drive into the raid array with the 12TB drive didn't accomplish what I wanted it to so there's no secondary drive to fall back on. If someone could help me either get around the superblock issue or help me rebuild the superblock without damaging my data I'd be eternally grateful.

Lords of Magic is a PC strategy game in the 4X tradition (eXplore,eXploit,eXpand,eXterminate) originally released in the ancient age of 1998. Despite LoMs antiquity I still find it to be a quite unique game, or rather a unique integration of staple mechanics from many genres. LoM drops the player into a generic High Fantasy adventure to destroy the Lord of Death, Balkoth, before he conquers the rather Tolkienesque world of Urak.
LoM consists of three distinct but entwined gameplay systems. The first one a player is introduced to is the basic roleplaying-game system. The player chooses his personal character, or "Lord", from one of three character classes: warrior, thief, or mage. The classes are typical of the fantasy RPG genre: warriors specialize in toughness and close combat, thieves are stealth and projectile experts, mages can cast unique magic spells but are exceedingly fragile. The game does a barely explains the differences between the various Faiths, or factions/races as other games would call them, and there's 7 of them the player can initially choose. The starting circumstances and personal stats of the player's Lord can vary wildly depending on Faith and new players won't have much to go on except the game's lengthy but vague manual. This can be annoying since the Lord is of crucial importance: not only will he be the player's premier unit for the early game but if he dies it is Game Over. After picking a Lord the player can select from the standard three difficulties (easy, normal, hard) and optionally elect for a 'Custom' start. Custom is more like setting up a party in a tactical RPG or Warhammer-style tabletop game, as it allows the player to spend 'Barter Points' on nearly any unit, item, and resource available in the game to optimize his starting party. The Lord can increase his Level up to 12, gaining increased stats with each Level, but the specific stats increased are set in stone based on Level and Lord-type and cannot be allocated or altered by the player. However the player can give 'artifacts' to his Lord that will influence his stats and abilities but a Lord can only use two at the same time (although he can carry an unlimited amount of artifacts) and most are heavily restricted in what class and/or Faith can use them, so this isn't a deep character customization system. Veteran players can create game-breaking starting parties with Custom but a new player is likely to be overwhelmed by its hundreds of options and you'll usually do fine with a default party at least on the difficulties lower than Hard.
When the player finalizes his starting unit selection he is introduced to the second major part of the game: the turn-based grand strategy that takes place on the world map. This is a slow introduction though and one of my biggest gripes about LoM is how repetitive and restricted the beginnings of each campaign are. The player's Lord and starting party begin slightly outside his chosen Faith's capital (and only) city. This starting area will be mostly empty of intruding Faiths for a few dozen turns and is littered with dungeons that feature easy combat encounters to conquer for unit Level-ups and bonus resources as loot. The goal in this starting area is to conquer your Faith's Great Temple, which is occupied by somewhat more difficult monsters. This stage of every campaign feels like an extended tutorial as you power up your starting party to take the Great Temple and then begin the campaign properly. While the player isn't technically required to take this course of action refusing to do so will make the game extremely difficult as you cannot truly utilize your Faith's buildings to produce resources or train units if you skip this step. With the Great Temple under his control the player will gain a Stronghold (essentially a cosmetic upgrade) in his Faith's city and gain full control over the city and the military buildings immediately next to it. Now this part of the game plays like an extremely pared down version of the Civilization games: you can upgrade your buildings and city with your resources, buy units at those buildings, assign Followers to work producing a resource income in your cities, and move military parties and scouts about the map to reveal hidden terrain or attempt negotiations and trades with other Faiths' parties. However you cannot add any new cities or buildings to the map (except at fixed-location and rather sparse villages) and, while magic spell-casting units can gain limited means to alter the terrain, your interactions with the world are very straightforward and there's little logistical consideration here. Any trades happen immediately if both sides agree to it, any party can attempt to trade with any other party, the vast majority of resource income is produced at cities, and the few mines or other map features that provide a resource income never move, never deplete, and cannot be upgraded, created, or destroyed. You can gain other Faiths buildings and the ability to produce their units by capturing their city. However fully knocking a rival Faith out-of-play requires you kill their Lord.
The final system is the real-time (with the option to pause) tactical combat that starts whenever one of the player's parties enters combat with another party. The player has the option to 'AutoCalc' (automatically calculate) to instantly get results for every battle except the final combat against Lord Balkoth, so this is system can mostly be ignored at the player's discretion. However you'll likely attain much more definitive victories with fewer unit losses by playing combat manually and utilizing basic tactics against the dull enemy AI. Each party, for both player and AI, is limited to containing at maximum 3 champions (warriors,thieves,mages) and 9 other units. Rank-and-file infantry, cavalry, and archer units come in stacks of three men per unit so the most units a party can field is 3 + (9*3) = 30. With a maximum of 60 units fighting each other on the fairly expansive combat maps LoM is not nearly as chaotic and click-intensive as many real-time strategy combat systems in other games. The player can pause combat at any time and issue orders to his units while paused, which they will immediately carry out upon unpause, so the fast-paced micromanagement of a game like Starcraft is practically absent. This is not to say there is no need to manage your units, as almost all have at least two essential special abilities that must be manually activated.

I'm trying to run a full node in my laptop (Asus Vivobook) here are the specs:
Processor 13th Gen Intel(R) Core(TM) i9-13900H 2.60 GHz
Installed RAM 16.0 GB (15.6 GB usable)
System type 64-bit operating system, x64-based processor
And when it reaches a certain point (18.28%) it stops connecting to peers. Exactly at the same block height (440741). I was downloading the blocks into an external hard drive, I thought that was the problem so I deleted everything from it and uninstalled the whole Bitcoin core. I then downloaded it again and started the blockchain synchronization this time directly on the laptop, it has sufficient storage (1tb). However, it has happened exactly the same thing. Here is the debug file:
2024-05-23T20:48:16Z UpdateTip: new best=0000000000000000030d8d81327ad254e445940d1c135aa809097e3119c67e4e height=440733 version=0x20000000 log2_work=85.596214 tx=174085329 date='2016-11-26T22:48:28Z' progress=0.182774 cache=260.0MiB(1755812txo)
2024-05-23T20:48:16Z UpdateTip: new best=000000000000000003cc05044dbf6c406af230241880940b7cb599bb9c587197 height=440734 version=0x20000000 log2_work=85.596244 tx=174087727 date='2016-11-26T23:11:09Z' progress=0.182777 cache=260.1MiB(1757093txo)
2024-05-23T20:48:16Z UpdateTip: new best=000000000000000002da5e992a8a862aead595ef580cb5b7d89c0fa53f9c5dac height=440735 version=0x20000000 log2_work=85.596274 tx=174088776 date='2016-11-26T23:22:48Z' progress=0.182778 cache=261.4MiB(1767716txo)
2024-05-23T20:48:16Z UpdateTip: new best=000000000000000000fe269cad821c434aa493f41caf1fc02632cd48ec2999da height=440736 version=0x20000000 log2_work=85.596304 tx=174091029 date='2016-11-26T23:24:25Z' progress=0.182780 cache=262.1MiB(1773056txo)
2024-05-23T20:48:16Z UpdateTip: new best=0000000000000000029f9e2b2bbcb73abeef3c6dd2f49579819d6d9d945d7e59 height=440737 version=0x20000002 log2_work=85.596334 tx=174093770 date='2016-11-26T23:38:03Z' progress=0.182783 cache=262.4MiB(1775634txo)
2024-05-23T20:48:16Z UpdateTip: new best=00000000000000000284a88167e8ed2a367de6527519d184c4d09dd9d2efef77 height=440738 version=0x20000000 log2_work=85.596363 tx=174095720 date='2016-11-26T23:39:33Z' progress=0.182785 cache=262.8MiB(1778832txo)
2024-05-23T20:48:16Z UpdateTip: new best=000000000000000000c8f8a4417a66eddcf61835e1f727391f2b4b87159ae234 height=440739 version=0x20000000 log2_work=85.596393 tx=174096971 date='2016-11-26T23:48:08Z' progress=0.182786 cache=262.9MiB(1779702txo)
2024-05-23T20:48:16Z UpdateTip: new best=000000000000000000729b5f66433e8013fca8bfc98f2eb99dab2ff356367940 height=440740 version=0x20000002 log2_work=85.596423 tx=174098992 date='2016-11-26T23:56:11Z' progress=0.182788 cache=263.2MiB(1782037txo)
2024-05-23T20:48:16Z UpdateTip: new best=0000000000000000037d893b1028690874b72e4e6e8b0781540779d2c2f2ad0d height=440741 version=0x20000000 log2_work=85.596453 tx=174099832 date='2016-11-26T23:59:19Z' progress=0.182789 cache=263.6MiB(1785795txo)
2024-05-23T20:48:55Z New outbound peer connected: version: 70016, blocks=844802, peer=40 (outbound-full-relay)
2024-05-23T20:52:25Z New outbound peer connected: version: 70016, blocks=844802, peer=41 (outbound-full-relay)
2024-05-23T20:52:32Z New outbound peer connected: version: 70016, blocks=844802, peer=42 (outbound-full-relay)
2024-05-23T20:52:43Z New outbound peer connected: version: 70016, blocks=844802, peer=44 (outbound-full-relay)
2024-05-23T20:52:44Z New outbound peer connected: version: 70015, blocks=844802, peer=45 (outbound-full-relay)
2024-05-23T20:53:13Z Synchronizing blockheaders, height: 844803 (~100.00%)
2024-05-23T20:54:58Z New outbound peer connected: version: 70016, blocks=844803, peer=46 (outbound-full-relay)
2024-05-23T20:55:10Z New outbound peer connected: version: 70016, blocks=844803, peer=47 (outbound-full-relay)
2024-05-23T20:55:13Z New outbound peer connected: version: 70016, blocks=844803, peer=48 (outbound-full-relay)
2024-05-23T20:55:47Z New outbound peer connected: version: 70016, blocks=844803, peer=49 (outbound-full-relay)
2024-05-23T20:55:50Z Peer=16 is stalling block download, disconnecting
2024-05-23T20:55:54Z New outbound peer connected: version: 70015, blocks=844803, peer=50 (outbound-full-relay)
2024-05-23T20:56:00Z New outbound peer connected: version: 70016, blocks=844803, peer=51 (block-relay-only)
2024-05-23T20:56:01Z New outbound peer connected: version: 70016, blocks=844803, peer=52 (block-relay-only)
2024-05-23T20:56:02Z Peer=45 is stalling block download, disconnecting
2024-05-23T20:56:02Z New outbound peer connected: version: 70016, blocks=844803, peer=53 (outbound-full-relay)
2024-05-23T20:56:20Z Peer=1 is stalling block download, disconnecting
2024-05-23T20:56:20Z New outbound peer connected: version: 70016, blocks=844803, peer=54 (outbound-full-relay)
2024-05-23T20:56:32Z New outbound peer connected: version: 70016, blocks=844803, peer=55 (outbound-full-relay)
2024-05-23T20:56:39Z New outbound peer connected: version: 70016, blocks=844803, peer=56 (outbound-full-relay)
2024-05-23T20:56:39Z New outbound peer connected: version: 70016, blocks=844803, peer=57 (block-relay-only)
2024-05-23T20:57:03Z New outbound peer connected: version: 70016, blocks=844803, peer=58 (outbound-full-relay)
2024-05-23T20:57:15Z New outbound peer connected: version: 70016, blocks=844803, peer=59 (outbound-full-relay)
2024-05-23T20:57:24Z New outbound peer connected: version: 70015, blocks=844802, peer=60 (outbound-full-relay)
2024-05-23T20:57:24Z New outbound peer connected: version: 70016, blocks=844803, peer=61 (outbound-full-relay)
2024-05-23T20:57:25Z New outbound peer connected: version: 70016, blocks=844803, peer=62 (outbound-full-relay)
2024-05-23T20:57:53Z New outbound peer connected: version: 70016, blocks=844803, peer=63 (outbound-full-relay)
2024-05-23T20:58:10Z New outbound peer connected: version: 70015, blocks=844803, peer=64 (outbound-full-relay)
2024-05-23T20:58:11Z New outbound peer connected: version: 70016, blocks=844803, peer=65 (outbound-full-relay)
2024-05-23T20:58:12Z New outbound peer connected: version: 70016, blocks=844803, peer=66 (outbound-full-relay)
2024-05-23T20:58:12Z New outbound peer connected: version: 70016, blocks=844803, peer=67 (outbound-full-relay)
2024-05-23T20:58:13Z New outbound peer connected: version: 70016, blocks=844803, peer=68 (outbound-full-relay)
2024-05-23T20:58:18Z New outbound peer connected: version: 70016, blocks=844803, peer=69 (outbound-full-relay)
2024-05-23T20:58:18Z New outbound peer connected: version: 70016, blocks=844803, peer=70 (outbound-full-relay)
2024-05-23T20:58:34Z New outbound peer connected: version: 70016, blocks=844803, peer=71 (outbound-full-relay)
2024-05-23T20:58:40Z New outbound peer connected: version: 70016, blocks=844803, peer=72 (outbound-full-relay)
2024-05-23T20:58:46Z New outbound peer connected: version: 70016, blocks=844803, peer=73 (outbound-full-relay)
2024-05-23T20:58:47Z New outbound peer connected: version: 70016, blocks=844803, peer=74 (outbound-full-relay)
2024-05-23T20:58:53Z New outbound peer connected: version: 70016, blocks=844803, peer=75 (outbound-full-relay)
2024-05-23T20:58:53Z New outbound peer connected: version: 70016, blocks=844803, peer=76 (outbound-full-relay)
2024-05-23T20:59:05Z New outbound peer connected: version: 70016, blocks=844803, peer=77 (outbound-full-relay)
2024-05-23T20:59:17Z New outbound peer connected: version: 70016, blocks=844803, peer=78 (outbound-full-relay)
2024-05-23T20:59:17Z New outbound peer connected: version: 70016, blocks=844803, peer=79 (outbound-full-relay)
2024-05-23T20:59:23Z New outbound peer connected: version: 70016, blocks=844803, peer=80 (outbound-full-relay)
2024-05-23T20:59:24Z New outbound peer connected: version: 70016, blocks=844803, peer=81 (outbound-full-relay)
2024-05-23T20:59:25Z New outbound peer connected: version: 70016, blocks=844803, peer=82 (outbound-full-relay)
2024-05-23T20:59:25Z New outbound peer connected: version: 70016, blocks=844803, peer=83 (outbound-full-relay)
2024-05-23T20:59:31Z New outbound peer connected: version: 70015, blocks=844803, peer=84 (outbound-full-relay)
2024-05-23T20:59:32Z New outbound peer connected: version: 70016, blocks=844803, peer=85 (outbound-full-relay)
2024-05-23T20:59:47Z New outbound peer connected: version: 70016, blocks=844803, peer=86 (outbound-full-relay)
2024-05-23T20:59:47Z New outbound peer connected: version: 70016, blocks=761248, peer=87 (outbound-full-relay)
2024-05-23T21:00:05Z New outbound peer connected: version: 70016, blocks=844803, peer=88 (outbound-full-relay)
2024-05-23T21:00:06Z New outbound peer connected: version: 70016, blocks=844803, peer=90 (outbound-full-relay)
2024-05-23T21:00:07Z New outbound peer connected: version: 70015, blocks=844802, peer=89 (outbound-full-relay)
2024-05-23T21:00:16Z New outbound peer connected: version: 70016, blocks=844803, peer=91 (outbound-full-relay)
2024-05-23T21:00:29Z New outbound peer connected: version: 70016, blocks=844803, peer=93 (outbound-full-relay)
2024-05-23T21:00:29Z New outbound peer connected: version: 70016, blocks=844803, peer=94 (outbound-full-relay)
2024-05-23T21:00:33Z New outbound peer connected: version: 70016, blocks=844803, peer=95 (outbound-full-relay)
2024-05-23T21:00:40Z New outbound peer connected: version: 70016, blocks=844803, peer=96 (outbound-full-relay)
2024-05-23T21:00:41Z New outbound peer connected: version: 70016, blocks=844803, peer=92 (outbound-full-relay)
2024-05-23T21:00:51Z New outbound peer connected: version: 70016, blocks=844803, peer=97 (outbound-full-relay)
2024-05-23T21:00:52Z New outbound peer connected: version: 70016, blocks=844803, peer=98 (outbound-full-relay)
2024-05-23T21:00:53Z New outbound peer connected: version: 70016, blocks=844803, peer=99 (outbound-full-relay)
2024-05-23T21:01:05Z New outbound peer connected: version: 70016, blocks=844803, peer=100 (outbound-full-relay)
2024-05-23T21:01:20Z New outbound peer connected: version: 70016, blocks=844803, peer=101 (outbound-full-relay)
2024-05-23T21:01:26Z New outbound peer connected: version: 70016, blocks=844803, peer=102 (outbound-full-relay)
2024-05-23T21:01:32Z New outbound peer connected: version: 70016, blocks=844803, peer=103 (outbound-full-relay)
2024-05-23T21:01:39Z New outbound peer connected: version: 70016, blocks=844803, peer=105 (outbound-full-relay)
2024-05-23T21:01:50Z New outbound peer connected: version: 70016, blocks=844803, peer=107 (outbound-full-relay)
2024-05-23T21:01:53Z New outbound peer connected: version: 70016, blocks=844803, peer=109 (outbound-full-relay)
2024-05-23T21:01:57Z New outbound peer connected: version: 70015, blocks=844803, peer=110 (outbound-full-relay)
2024-05-23T21:01:58Z New outbound peer connected: version: 70015, blocks=844803, peer=111 (outbound-full-relay)
2024-05-23T21:02:09Z New outbound peer connected: version: 70016, blocks=844803, peer=112 (outbound-full-relay)
2024-05-23T21:02:15Z New outbound peer connected: version: 70016, blocks=844804, peer=113 (outbound-full-relay)
2024-05-23T21:02:16Z New outbound peer connected: version: 70016, blocks=844804, peer=114 (outbound-full-relay)
2024-05-23T21:02:16Z Synchronizing blockheaders, height: 844804 (~100.00%)
2024-05-23T21:02:17Z New outbound peer connected: version: 70016, blocks=844804, peer=115 (outbound-full-relay)
2024-05-23T21:02:23Z New outbound peer connected: version: 70016, blocks=844804, peer=116 (outbound-full-relay)
2024-05-23T21:02:23Z New outbound peer connected: version: 70016, blocks=844804, peer=117 (outbound-full-relay)
2024-05-23T21:02:24Z New outbound peer connected: version: 70016, blocks=844804, peer=118 (outbound-full-relay)
2024-05-23T21:02:24Z New outbound peer connected: version: 70016, blocks=844804, peer=119 (block-relay-only)
2024-05-23T21:02:25Z New outbound peer connected: version: 70016, blocks=844804, peer=120 (block-relay-only)
2024-05-23T21:02:26Z New outbound peer connected: version: 70015, blocks=844804, peer=121 (block-relay-only)
2024-05-23T21:02:32Z Peer=92 is stalling block download, disconnecting
2024-05-23T21:02:44Z New outbound peer connected: version: 70016, blocks=844804, peer=122 (outbound-full-relay)
2024-05-23T21:02:45Z New outbound peer connected: version: 70016, blocks=844804, peer=123 (outbound-full-relay)
2024-05-23T21:02:46Z New outbound peer connected: version: 70016, blocks=844804, peer=124 (outbound-full-relay)
2024-05-23T21:02:52Z New outbound peer connected: version: 70016, blocks=844804, peer=125 (outbound-full-relay)
2024-05-23T21:03:04Z New outbound peer connected: version: 70016, blocks=844804, peer=126 (outbound-full-relay)
2024-05-23T21:03:05Z New outbound peer connected: version: 70016, blocks=844804, peer=127 (outbound-full-relay)
2024-05-23T21:03:09Z New outbound peer connected: version: 70016, blocks=844804, peer=128 (outbound-full-relay)
2024-05-23T21:03:10Z New outbound peer connected: version: 70016, blocks=844804, peer=129 (outbound-full-relay)
2024-05-23T21:03:21Z New outbound peer connected: version: 70016, blocks=844804, peer=130 (outbound-full-relay)
2024-05-23T21:03:23Z New outbound peer connected: version: 70016, blocks=844804, peer=133 (outbound-full-relay)
2024-05-23T21:03:23Z New outbound peer connected: version: 70015, blocks=844804, peer=134 (outbound-full-relay)
2024-05-23T21:03:29Z New outbound peer connected: version: 70016, blocks=844804, peer=131 (outbound-full-relay)
2024-05-23T21:03:30Z New outbound peer connected: version: 70016, blocks=844804, peer=135 (outbound-full-relay)
2024-05-23T21:03:31Z New outbound peer connected: version: 70016, blocks=844804, peer=132 (outbound-full-relay)
2024-05-23T21:03:31Z New outbound peer connected: version: 70016, blocks=844804, peer=137 (outbound-full-relay)
2024-05-23T21:03:53Z Peer=107 is stalling block download, disconnecting
2024-05-23T21:04:01Z New outbound peer connected: version: 70016, blocks=844804, peer=139 (outbound-full-relay)
2024-05-23T21:04:29Z New outbound peer connected: version: 70016, blocks=844804, peer=140 (outbound-full-relay)
2024-05-23T21:04:29Z New outbound peer connected: version: 70016, blocks=844804, peer=141 (outbound-full-relay)
2024-05-23T21:05:02Z New outbound peer connected: version: 70016, blocks=844804, peer=142 (outbound-full-relay)
2024-05-23T21:05:03Z New outbound peer connected: version: 70016, blocks=844804, peer=143 (outbound-full-relay)
2024-05-23T21:05:29Z New outbound peer connected: version: 70016, blocks=844805, peer=144 (outbound-full-relay)
2024-05-23T21:05:29Z Synchronizing blockheaders, height: 844805 (~100.00%)
2024-05-23T21:05:30Z New outbound peer connected: version: 70016, blocks=844805, peer=145 (outbound-full-relay)
2024-05-23T21:05:46Z New outbound peer connected: version: 70016, blocks=844805, peer=147 (outbound-full-relay)
2024-05-23T21:05:59Z New outbound peer connected: version: 70016, blocks=844805, peer=148 (outbound-full-relay)
2024-05-23T21:06:05Z New outbound peer connected: version: 70016, blocks=844805, peer=149 (outbound-full-relay)
2024-05-23T21:06:27Z New outbound peer connected: version: 70016, blocks=844805, peer=150 (outbound-full-relay)
2024-05-23T21:06:28Z New outbound peer connected: version: 70016, blocks=844805, peer=151 (outbound-full-relay)
2024-05-23T21:06:29Z New outbound peer connected: version: 70016, blocks=844805, peer=152 (outbound-full-relay)
2024-05-23T21:06:35Z New outbound peer connected: version: 70016, blocks=844805, peer=153 (outbound-full-relay)
2024-05-23T21:06:36Z New outbound peer connected: version: 70016, blocks=844805, peer=155 (outbound-full-relay)
2024-05-23T21:06:37Z New outbound peer connected: version: 70016, blocks=844805, peer=154 (outbound-full-relay)
2024-05-23T21:06:37Z New outbound peer connected: version: 70016, blocks=844805, peer=156 (outbound-full-relay)
2024-05-23T21:06:38Z New outbound peer connected: version: 70016, blocks=844805, peer=157 (outbound-full-relay)
2024-05-23T21:06:38Z New outbound peer connected: version: 70016, blocks=844805, peer=158 (outbound-full-relay)
2024-05-23T21:06:59Z New outbound peer connected: version: 70016, blocks=844805, peer=159 (outbound-full-relay)
2024-05-23T21:07:28Z New outbound peer connected: version: 70016, blocks=844805, peer=160 (outbound-full-relay)
2024-05-23T21:07:28Z New outbound peer connected: version: 70016, blocks=844805, peer=161 (outbound-full-relay)
2024-05-23T21:08:19Z New outbound peer connected: version: 70016, blocks=844805, peer=162 (outbound-full-relay)
2024-05-23T21:08:20Z New outbound peer connected: version: 70016, blocks=844805, peer=163 (outbound-full-relay)
2024-05-23T21:08:24Z New outbound peer connected: version: 70016, blocks=844805, peer=164 (outbound-full-relay)
2024-05-23T21:08:35Z New outbound peer connected: version: 70016, blocks=844805, peer=165 (outbound-full-relay)
2024-05-23T21:08:37Z New outbound peer connected: version: 70016, blocks=844805, peer=166 (outbound-full-relay)
2024-05-23T21:08:43Z New outbound peer connected: version: 70016, blocks=844805, peer=167 (outbound-full-relay)
2024-05-23T21:08:44Z New outbound peer connected: version: 70016, blocks=844805, peer=169 (outbound-full-relay)
2024-05-23T21:08:44Z New outbound peer connected: version: 70016, blocks=844805, peer=170 (outbound-full-relay)
2024-05-23T21:08:45Z New outbound peer connected: version: 70015, blocks=844805, peer=168 (outbound-full-relay)
2024-05-23T21:08:46Z New outbound peer connected: version: 70016, blocks=844805, peer=171 (outbound-full-relay)
2024-05-23T21:08:57Z New outbound peer connected: version: 70016, blocks=844805, peer=172 (outbound-full-relay)
2024-05-23T21:09:03Z New outbound peer connected: version: 70015, blocks=844805, peer=173 (outbound-full-relay)
2024-05-23T21:09:04Z New outbound peer connected: version: 70016, blocks=844805, peer=174 (outbound-full-relay)
2024-05-23T21:09:04Z New outbound peer connected: version: 70016, blocks=844805, peer=175 (outbound-full-relay)
2024-05-23T21:09:22Z New outbound peer connected: version: 70016, blocks=844805, peer=176 (outbound-full-relay)
2024-05-23T21:09:24Z New outbound peer connected: version: 70016, blocks=844805, peer=177 (outbound-full-relay)
2024-05-23T21:09:25Z New outbound peer connected: version: 70016, blocks=844805, peer=178 (outbound-full-relay)
2024-05-23T21:09:26Z New outbound peer connected: version: 70016, blocks=844805, peer=180 (outbound-full-relay)
2024-05-23T21:09:27Z New outbound peer connected: version: 70016, blocks=844805, peer=181 (outbound-full-relay)
2024-05-23T21:09:28Z New outbound peer connected: version: 70016, blocks=844805, peer=182 (outbound-full-relay)
2024-05-23T21:09:33Z New outbound peer connected: version: 70016, blocks=844805, peer=183 (outbound-full-relay)
2024-05-23T21:09:58Z New outbound peer connected: version: 70015, blocks=844805, peer=184 (outbound-full-relay)
2024-05-23T21:09:59Z New outbound peer connected: version: 70016, blocks=844805, peer=185 (outbound-full-relay)
2024-05-23T21:09:59Z New outbound peer connected: version: 70016, blocks=844805, peer=186 (outbound-full-relay)
2024-05-23T21:10:00Z New outbound peer connected: version: 70016, blocks=844805, peer=187 (outbound-full-relay)
2024-05-23T21:10:01Z New outbound peer connected: version: 70016, blocks=844805, peer=188 (outbound-full-relay)
2024-05-23T21:10:12Z New outbound peer connected: version: 70016, blocks=844805, peer=190 (outbound-full-relay)
2024-05-23T21:10:19Z New outbound peer connected: version: 70015, blocks=844804, peer=191 (outbound-full-relay)
2024-05-23T21:10:20Z New outbound peer connected: version: 70016, blocks=844805, peer=192 (outbound-full-relay)
2024-05-23T21:10:27Z New outbound peer connected: version: 70016, blocks=844805, peer=193 (outbound-full-relay)
2024-05-23T21:10:34Z New outbound peer connected: version: 70016, blocks=844805, peer=195 (outbound-full-relay)
2024-05-23T21:10:35Z New outbound peer connected: version: 70016, blocks=844805, peer=197 (outbound-full-relay)
2024-05-23T21:10:47Z New outbound peer connected: version: 70016, blocks=844806, peer=199 (outbound-full-relay)
2024-05-23T21:10:47Z Synchronizing blockheaders, height: 844806 (~100.00%)
2024-05-23T21:10:48Z New outbound peer connected: version: 70016, blocks=844806, peer=200 (outbound-full-relay)
2024-05-23T21:10:49Z New outbound peer connected: version: 70016, blocks=844806, peer=201 (outbound-full-relay)
2024-05-23T21:10:56Z New outbound peer connected: version: 70016, blocks=844806, peer=198 (outbound-full-relay)
2024-05-23T21:11:06Z New outbound peer connected: version: 70016, blocks=844806, peer=202 (outbound-full-relay)
2024-05-23T21:11:06Z New outbound peer connected: version: 70016, blocks=844806, peer=203 (outbound-full-relay)
2024-05-23T21:11:07Z New outbound peer connected: version: 70016, blocks=844806, peer=204 (outbound-full-relay)
2024-05-23T21:11:13Z New outbound peer connected: version: 70016, blocks=844806, peer=205 (outbound-full-relay)
2024-05-23T21:11:14Z New outbound peer connected: version: 70016, blocks=844803, peer=206 (outbound-full-relay)
2024-05-23T21:11:18Z New outbound peer connected: version: 70016, blocks=844806, peer=207 (outbound-full-relay)
2024-05-23T21:11:46Z tor: Thread interrupt
2024-05-23T21:11:46Z opencon thread exit
2024-05-23T21:11:46Z addcon thread exit
2024-05-23T21:11:46Z Shutdown: In progress...
2024-05-23T21:11:46Z torcontrol thread exit
2024-05-23T21:11:46Z msghand thread exit
2024-05-23T21:11:46Z net thread exit
2024-05-23T21:11:46Z DumpAnchors: Flush 0 outbound block-relay-only peer addresses to anchors.dat started
2024-05-23T21:11:46Z DumpAnchors: Flush 0 outbound block-relay-only peer addresses to anchors.dat completed (0.00s)
2024-05-23T21:11:46Z scheduler thread exit
2024-05-23T21:11:46Z Writing 0 unbroadcast transactions to disk.
2024-05-23T21:11:46Z Dumped mempool: 0s to copy, 0.006783s to dump
2024-05-23T21:11:48Z Shutdown: done
2024-05-23T21:11:51Z Bitcoin Core version v25.0.0 (release build)
2024-05-23T21:11:51Z Qt 5.15.5 (static), plugin=windows (static)
2024-05-23T21:11:51Z Static plugins:
2024-05-23T21:11:51Z QWindowsIntegrationPlugin, version 331520
2024-05-23T21:11:51Z QWindowsVistaStylePlugin, version 331520
2024-05-23T21:11:51Z Style: windowsvista / QWindowsVistaStyle
2024-05-23T21:11:51Z System: Windows 10 Version 2009, x86_64-little_endian-llp64
2024-05-23T21:11:51Z Screen: \\.\DISPLAY1 1440x810, pixel ratio=2.0
2024-05-23T21:11:51Z Using the 'x86_shani(1way,2way)' SHA256 implementation
2024-05-23T21:11:51Z Using RdSeed as an additional entropy source
2024-05-23T21:11:51Z Using RdRand as an additional entropy source
2024-05-23T21:11:51Z GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely…"
2024-05-23T21:11:51Z Default data directory C:\Users\aixar\AppData\Roaming\Bitcoin
2024-05-23T21:11:51Z Using data directory C:\Users\aixar\Node\Bitcoin
2024-05-23T21:11:51Z Config file: C:\Users\aixar\Node\Bitcoin\bitcoin.conf
2024-05-23T21:11:51Z Using at most 125 automatic connections (2048 file descriptors available)
2024-05-23T21:11:51Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements
2024-05-23T21:11:51Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements
2024-05-23T21:11:51Z Script verification uses 15 additional threads
2024-05-23T21:11:51Z scheduler thread start
2024-05-23T21:11:51Z Using wallet directory C:\Users\aixar\Node\Bitcoin
2024-05-23T21:11:51Z init message: Verifying wallet(s)…
2024-05-23T21:11:51Z Using /16 prefix for IP bucketing
2024-05-23T21:11:51Z init message: Loading P2P addresses…
2024-05-23T21:11:51Z Loaded 46092 addresses from peers.dat 82ms
2024-05-23T21:11:51Z init message: Loading banlist…
2024-05-23T21:11:51Z SetNetworkActive: true
2024-05-23T21:11:51Z Cache configuration:
2024-05-23T21:11:51Z * Using 2.0 MiB for block index database
2024-05-23T21:11:51Z * Using 8.0 MiB for chain state database
2024-05-23T21:11:51Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2024-05-23T21:11:51Z init message: Loading block index…
2024-05-23T21:11:51Z Assuming ancestors of block 000000000000000000035c3f0d31e71a5ee24c5aaf3354689f65bd7b07dee632 have valid signatures.
2024-05-23T21:11:51Z Setting nMinimumChainWork=000000000000000000000000000000000000000044a50fe819c39ad624021859
2024-05-23T21:11:51Z Opening LevelDB in C:\Users\aixar\Node\Bitcoin\blocks\index
2024-05-23T21:11:51Z Opened LevelDB successfully
2024-05-23T21:11:51Z Using obfuscation key for C:\Users\aixar\Node\Bitcoin\blocks\index: 0000000000000000
2024-05-23T21:11:54Z LoadBlockIndexDB: last block file = 698
2024-05-23T21:11:54Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=19, size=16459133, heights=441510...441762, time=2016-12-02...2016-12-03)
2024-05-23T21:11:54Z Checking all blk files are present...
2024-05-23T21:11:54Z Initializing chainstate Chainstate [ibd] @ height -1 (null)
2024-05-23T21:11:54Z Opening LevelDB in C:\Users\aixar\Node\Bitcoin\chainstate
2024-05-23T21:11:54Z Opened LevelDB successfully
2024-05-23T21:11:54Z Using obfuscation key for C:\Users\aixar\Node\Bitcoin\chainstate: 2423fc3713ba2d80
2024-05-23T21:11:54Z Loaded best chain: hashBestChain=0000000000000000037d893b1028690874b72e4e6e8b0781540779d2c2f2ad0d height=440741 date=2016-11-26T23:59:19Z progress=0.182788
2024-05-23T21:11:54Z [snapshot] allocating all cache to the IBD chainstate
2024-05-23T21:11:54Z Opening LevelDB in C:\Users\aixar\Node\Bitcoin\chainstate
2024-05-23T21:11:54Z Opened LevelDB successfully
2024-05-23T21:11:54Z Using obfuscation key for C:\Users\aixar\Node\Bitcoin\chainstate: 2423fc3713ba2d80
2024-05-23T21:11:54Z [Chainstate [ibd] @ height 440741 (0000000000000000037d893b1028690874b72e4e6e8b0781540779d2c2f2ad0d)] resized coinsdb cache to 8.0 MiB
2024-05-23T21:11:54Z [Chainstate [ibd] @ height 440741 (0000000000000000037d893b1028690874b72e4e6e8b0781540779d2c2f2ad0d)] resized coinstip cache to 440.0 MiB
2024-05-23T21:11:54Z init message: Verifying blocks…
2024-05-23T21:11:54Z Verifying last 6 blocks at level 3
2024-05-23T21:11:54Z Verification progress: 0%
2024-05-23T21:11:54Z Verification progress: 16%
2024-05-23T21:11:55Z Verification progress: 33%
2024-05-23T21:11:55Z Verification progress: 50%
2024-05-23T21:11:55Z Verification progress: 66%
2024-05-23T21:11:55Z Verification progress: 83%
2024-05-23T21:11:55Z Verification progress: 99%
2024-05-23T21:11:55Z Verification: No coin database inconsistencies in last 6 blocks (11056 transactions)
2024-05-23T21:11:55Z block index 3641ms
2024-05-23T21:11:55Z Setting NODE_NETWORK on non-prune mode
2024-05-23T21:11:55Z block tree size = 844807
2024-05-23T21:11:55Z nBestHeight = 440741
2024-05-23T21:11:55Z loadblk thread start
2024-05-23T21:11:55Z Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there, 0 waiting for initial broadcast
2024-05-23T21:11:55Z loadblk thread exit
2024-05-23T21:11:55Z torcontrol thread start
2024-05-23T21:11:55Z Bound to 127.0.0.1:8334
2024-05-23T21:11:55Z Bound to [::]:8333
2024-05-23T21:11:55Z Bound to 0.0.0.0:8333
2024-05-23T21:11:55Z Loaded 0 addresses from "anchors.dat"
2024-05-23T21:11:55Z 0 block-relay-only anchors will be tried for connections.
2024-05-23T21:11:55Z init message: Starting network threads…
2024-05-23T21:11:55Z net thread start
2024-05-23T21:11:55Z init message: Done loading
2024-05-23T21:11:55Z addcon thread start
2024-05-23T21:11:55Z dnsseed thread start
2024-05-23T21:11:55Z Waiting 300 seconds before querying DNS seeds.
2024-05-23T21:11:55Z msghand thread start
2024-05-23T21:11:55Z opencon thread start
2024-05-23T21:11:55Z GUI: Platform customization: "windows"
2024-05-23T21:11:55Z New outbound peer connected: version: 70016, blocks=844807, peer=0 (outbound-full-relay)
2024-05-23T21:11:56Z Synchronizing blockheaders, height: 844807 (~100.00%)
2024-05-23T21:11:58Z New outbound peer connected: version: 70016, blocks=844807, peer=4 (outbound-full-relay)
2024-05-23T21:11:58Z New outbound peer connected: version: 70016, blocks=844806, peer=1 (outbound-full-relay)
2024-05-23T21:11:59Z New outbound peer connected: version: 70016, blocks=844807, peer=5 (outbound-full-relay)
2024-05-23T21:12:00Z New outbound peer connected: version: 70016, blocks=844806, peer=2 (outbound-full-relay)
2024-05-23T21:12:07Z New outbound peer connected: version: 70016, blocks=844806, peer=3 (outbound-full-relay)
2024-05-23T21:12:17Z New outbound peer connected: version: 70016, blocks=844807, peer=7 (outbound-full-relay)
2024-05-23T21:12:24Z New outbound peer connected: version: 70016, blocks=844807, peer=9 (outbound-full-relay)
2024-05-23T21:12:26Z New outbound peer connected: version: 70016, blocks=844807, peer=8 (outbound-full-relay)
2024-05-23T21:12:33Z New outbound peer connected: version: 70016, blocks=844807, peer=11 (outbound-full-relay)
2024-05-23T21:12:34Z New outbound peer connected: version: 70016, blocks=844807, peer=12 (outbound-full-relay)
2024-05-23T21:12:40Z New outbound peer connected: version: 70016, blocks=844807, peer=13 (outbound-full-relay)
2024-05-23T21:12:47Z New outbound peer connected: version: 70016, blocks=844807, peer=10 (outbound-full-relay)
2024-05-23T21:12:57Z New outbound peer connected: version: 70016, blocks=844807, peer=14 (outbound-full-relay)
2024-05-23T21:12:58Z New outbound peer connected: version: 70016, blocks=844807, peer=15 (outbound-full-relay)
2024-05-23T21:13:08Z New outbound peer connected: version: 70016, blocks=844807, peer=16 (outbound-full-relay)
2024-05-23T21:13:09Z New outbound peer connected: version: 70016, blocks=844807, peer=17 (outbound-full-relay)
2024-05-23T21:13:09Z New outbound peer connected: version: 70016, blocks=844807, peer=18 (outbound-full-relay)
2024-05-23T21:13:21Z New outbound peer connected: version: 70016, blocks=844807, peer=19 (outbound-full-relay)
2024-05-23T21:13:22Z New outbound peer connected: version: 70016, blocks=844807, peer=20 (outbound-full-relay)
2024-05-23T21:13:22Z New outbound peer connected: version: 70016, blocks=844807, peer=21 (outbound-full-relay)
2024-05-23T21:13:22Z New outbound peer connected: version: 70016, blocks=844807, peer=22 (outbound-full-relay)
2024-05-23T21:13:23Z P2P peers available. Skipped DNS seeding.
2024-05-23T21:13:23Z dnsseed thread exit
2024-05-23T21:13:23Z Peer=16 is stalling block download, disconnecting
2024-05-23T21:13:23Z New outbound peer connected: version: 70016, blocks=844807, peer=23 (outbound-full-relay)
2024-05-23T21:13:24Z New outbound peer connected: version: 70016, blocks=844807, peer=25 (outbound-full-relay)
2024-05-23T21:13:25Z New outbound peer connected: version: 70016, blocks=844807, peer=24 (outbound-full-relay)
2024-05-23T21:13:25Z New outbound peer connected: version: 70016, blocks=844807, peer=26 (outbound-full-relay)
2024-05-23T21:13:26Z New outbound peer connected: version: 70016, blocks=844807, peer=27 (outbound-full-relay)
2024-05-23T21:13:32Z New outbound peer connected: version: 70015, blocks=844805, peer=28 (outbound-full-relay)
2024-05-23T21:13:42Z New outbound peer connected: version: 70016, blocks=844807, peer=30 (outbound-full-relay)
2024-05-23T21:13:50Z New outbound peer connected: version: 70015, blocks=844805, peer=31 (outbound-full-relay)
2024-05-23T21:13:51Z New outbound peer connected: version: 70016, blocks=844807, peer=33 (outbound-full-relay)
2024-05-23T21:13:52Z New outbound peer connected: version: 70016, blocks=844807, peer=34 (outbound-full-relay)
2024-05-23T21:13:52Z New outbound peer connected: version: 70016, blocks=844807, peer=35 (outbound-full-relay)
2024-05-23T21:13:53Z New outbound peer connected: version: 70016, blocks=844807, peer=36 (outbound-full-relay)
2024-05-23T21:13:59Z New outbound peer connected: version: 70015, blocks=844807, peer=37 (outbound-full-relay)
2024-05-23T21:14:00Z New outbound peer connected: version: 70016, blocks=844807, peer=38 (outbound-full-relay)
2024-05-23T21:14:02Z New outbound peer connected: version: 70016, blocks=844806, peer=29 (outbound-full-relay)
2024-05-23T21:14:28Z New outbound peer connected: version: 70016, blocks=844807, peer=39 (outbound-full-relay)
2024-05-23T21:14:29Z New outbound peer connected: version: 70016, blocks=844807, peer=40 (outbound-full-relay)
2024-05-23T21:14:30Z New outbound peer connected: version: 70015, blocks=844807, peer=41 (outbound-full-relay)
2024-05-23T21:14:31Z New outbound peer connected: version: 70016, blocks=844807, peer=43 (outbound-full-relay)
2024-05-23T21:14:31Z New outbound peer connected: version: 70016, blocks=844807, peer=44 (outbound-full-relay)
2024-05-23T21:14:32Z New outbound peer connected: version: 70016, blocks=844807, peer=45 (outbound-full-relay)
2024-05-23T21:14:32Z New outbound peer connected: version: 70016, blocks=844807, peer=46 (outbound-full-relay)
2024-05-23T21:14:41Z New outbound peer connected: version: 70016, blocks=844807, peer=42 (outbound-full-relay)
2024-05-23T21:14:44Z New outbound peer connected: version: 70016, blocks=844807, peer=47 (outbound-full-relay)
2024-05-23T21:14:45Z New outbound peer connected: version: 70016, blocks=844807, peer=48 (outbound-full-relay)
2024-05-23T21:14:57Z New outbound peer connected: version: 70016, blocks=844807, peer=50 (outbound-full-relay)
2024-05-23T21:15:03Z New outbound peer connected: version: 70016, blocks=844807, peer=51 (outbound-full-relay)
2024-05-23T21:15:04Z New outbound peer connected: version: 70016, blocks=844807, peer=52 (outbound-full-relay)
2024-05-23T21:15:04Z New outbound peer connected: version: 70016, blocks=844807, peer=53 (outbound-full-relay)
2024-05-23T21:15:05Z New outbound peer connected: version: 70015, blocks=844807, peer=54 (outbound-full-relay)
2024-05-23T21:15:06Z New outbound peer connected: version: 70016, blocks=844807, peer=55 (outbound-full-relay)
2024-05-23T21:15:24Z New outbound peer connected: version: 70016, blocks=844807, peer=57 (outbound-full-relay)
2024-05-23T21:15:30Z New outbound peer connected: version: 70016, blocks=844808, peer=58 (outbound-full-relay)
2024-05-23T21:15:30Z Synchronizing blockheaders, height: 844808 (~100.00%)
2024-05-23T21:15:34Z New outbound peer connected: version: 70016, blocks=844808, peer=59 (outbound-full-relay)
2024-05-23T21:15:37Z New outbound peer connected: version: 70016, blocks=844808, peer=60 (outbound-full-relay)
2024-05-23T21:15:38Z New outbound peer connected: version: 70016, blocks=844808, peer=61 (outbound-full-relay)
2024-05-23T21:15:38Z New outbound peer connected: version: 70016, blocks=844808, peer=62 (outbound-full-relay)
2024-05-23T21:15:39Z New outbound peer connected: version: 70016, blocks=844808, peer=63 (outbound-full-relay)
2024-05-23T21:15:39Z New outbound peer connected: version: 70016, blocks=844808, peer=64 (outbound-full-relay)
2024-05-23T21:15:58Z New outbound peer connected: version: 70016, blocks=844808, peer=66 (outbound-full-relay)
2024-05-23T21:15:59Z New outbound peer connected: version: 70016, blocks=844808, peer=67 (outbound-full-relay)
2024-05-23T21:16:00Z New outbound peer connected: version: 70016, blocks=844808, peer=68 (outbound-full-relay)
2024-05-23T21:16:00Z New outbound peer connected: version: 70016, blocks=844808, peer=69 (outbound-full-relay)
2024-05-23T21:16:01Z New outbound peer connected: version: 70016, blocks=844808, peer=70 (outbound-full-relay)
2024-05-23T21:16:07Z New outbound peer connected: version: 70015, blocks=844808, peer=71 (outbound-full-relay)
2024-05-23T21:16:07Z New outbound peer connected: version: 70016, blocks=844808, peer=72 (outbound-full-relay)
2024-05-23T21:16:19Z New outbound peer connected: version: 70016, blocks=844808, peer=73 (outbound-full-relay)
2024-05-23T21:16:25Z New outbound peer connected: version: 70016, blocks=844808, peer=74 (outbound-full-relay)
2024-05-23T21:16:26Z New outbound peer connected: version: 70016, blocks=844808, peer=75 (outbound-full-relay)
2024-05-23T21:16:27Z New outbound peer connected: version: 70016, blocks=844808, peer=76 (outbound-full-relay)
2024-05-23T21:16:45Z New outbound peer connected: version: 70016, blocks=844808, peer=78 (outbound-full-relay)
2024-05-23T21:17:01Z New outbound peer connected: version: 70016, blocks=844808, peer=80 (outbound-full-relay)
What can I do to solve this problem?

Q: It’s not related to S10 balance changes but I’m gonna ask anyway. Were we secretly testing any new upcoming heroes with the Mirrorwatch event?
Blizz_Alec: No secret testing of anything upcoming in the immediate! We do look at how some changes play out though when they become more real and get lots of games, I think the Bastion Ultimate in particular was quite fun even if very loud and on the border technically. Reinhardt's Frenzy passive was also something we played around with internally but it was quite hard to communicate effectively. It's always good to see what players get excited about when there are more wacky ideas such as Mirrorwatch or April Fool's, some of those could become real down the line.
Q: Who is the hardest character to balance and tweak out of the three roles?
Blizz_JNoh: Probably Sombra due to permanent invisibility restricting how deadly we can make her but also because she is a hero that excels with strong team coordination. There are a handful of other heroes with performance stats that differ greatly from the broader community perception of them and that can create difficulty in how we approach balancing them as well.
Q: I know you guys mentioned two upcoming DPS hero reworks. Is there any news about how those reworks are progressing, who they'll be for (I think people have a pretty decent idea, but official confirmation would be nice), and/or when they might be arriving? Also, are there any other heroes under consideration for potential reworks?
Blizz_Alec: The two upcoming updates that were mentioned were for Cassidy and Reaper.
For Cassidy, we started some exploration pre-Season 9 for his update. Due to where he was at that time, this update was originally looking at multiple pieces of his kit but we saw the Season 9 changes largely benefit him so the update has gotten more focused on Magnetic Grenade and other Quality of Life updates (specifically to his Ultimate). In Season 11 we are updating Magnetic Grenade. It will behave closer to old Flashbang (no magnetic homing to the target, used in the short range) and will slow/hinder the target. We think that plays a lot better with his kit and removes some of the larger frustrations around Magnetic Grenade. More specifics on all that soon.
For Reaper, we went fairly wide as well in the beginning and then started to focus closely on updating Shadow Step. At the moment, we have something we quite like but it's actually a large technical challenge and we are in the process of planning out the work/seeing what's possible. In the meantime, we may buff Reaper in some non-Tank Buster ways as he lost a lot in the most recent update.
Q: What is the average rank of your play testers and what level of input do they have in deciding what changes are made in each balance patch?
Blizz_Hudson: A huge part of our team culture revolves around playtesting. From Designers, to QA and community management, everyone has the opportunity to play what we're working on and give open honest feedback. One of the advantages of this model is we get perspective from a wide range of player ranks from GM 1 to Bronze 5. It's been a while since we've taken an official poll on average rank, but having a wide sample helps prevent tunnel visioning on feedback from specific ranks.
Q: 2 part question here: Why the inconsistency with dev comments/explanations for balance changes? There have been many changes that have been questionable (biggest offender was buffing Sojourn in January when she was widely considered the best DPS) that were shipped with 0 explanation. Justifying these changes would help a lot with player perception so we could understand these discrepancies. I have to ask - what is going on with Symmetra? She was weak, then buffed, then immediately reverted, now silence. Is she getting reworked? What data shows she needed a nerf? She is super weak and hard to use on ladder (uncoordinated environment by nature) and was only played in OWCS for Mauga - shouldn't nerfing Mauga have been enough?
Blizz_Alec: We should do a better job about this, especially when it comes to getting the community's visibility on what we are seeing vs. what the playerbase may seem to think is the best hero at any given one time. These can differ regularly as certain heroes get power reputations (weaker or stronger than their reality at a given rank) that are hard to shake off. Thanks for the feedback there, will make sure we have something here even if it's a simple change.
Symmetra kept some of the buffs in that patch but yes we hear the feedback of where her current power level is. We may have been a bit overreactive to the Mauga compositions popping up during that timeframe (he was certainly overtuned), but we wanted to be sure of it. For right now, we are in discussions about Symmetra and especially her frontline presence. Believe that's a piece of the kit we'd like to promote further, whether through her survivability or beam damage.
Q: Why was smurf detection essentially removed from MMR adjustment, especially for new accounts? GM-level players taking 60+ games to reach their proper rank ruins so many more games. It feels like climbing in general is artificially slowed down so people will play more even if they should have reached a higher rank many games ago.
Blizz_Alec: I tapped in our own Gavin Winter for this first part, he's what he had to say: "There haven't been any changes to these systems, but there are edge cases like the example of Guxue that was recently posted in this subreddit where our systems don't perform in the way we'd like. Most players will still be placed appropriately as they transition from Quick Play to Competitive Play, but unfortunately cases like this have always been possible. Explaining exactly how this happens would make it easier to reproduce, so you'll have to excuse me from not going into intricate detail here."
For the second part of your question, we believe we made it slightly too difficult to climb at the highest ranks and are looking at making some adjustments soon.
Q: Will you ever make pick rates and win rates public, even a couple of weeks after the fact? I feel like it would do a lot to help people understand why changes are made. Is there a win rate range you want to keep all heroes to stay within?
Blizz_JNoh: There aren't any plans currently to shift resources toward supporting something like that. Sites like Overbuff don't have the complete picture, but the data there for win rates and such is generally fairly close.
There is some argument against being too transparent with those stats in that it can create a bit of a feedback loop where you might see player behavior driven by what appears to be the meta in the stats, but that kind of happens already with just the general discussion and sentiment around heroes without stats as well.
Our target range for hero viability by win rate is between 45-55% unmirrored win rate at Masters rank and above. Those individual win rates often can fluctuate 2-3% by day, mostly because heroes tend to have a wider range of win rates per map and we're looking at the global average of those, but also individual player performance isn't consistent.
Lower pick rate heroes fluctuate more and there is less confidence in their win rate being indicative of actual strength. Extremely high pick rate heroes have a similar problem when looking at unmirrored stats.
In the end, stats require interpretation to understand their context and that is why they are not the only basis for balance changes but are a useful tool to measure the impact of changes patch-over-patch.
Q: What is Hanzo's new job? Is he supposed to take over Pharah's place as the new go-to permanently pocketed hero? To explain more in depth: Hanzo used to be a sniper, but the recent changes caused most heroes to require 1 extra shot to eliminate a target. Considering Hanzo is the slowest shooting primary fire focused DPS, he was impacted the most. Making him the only primary fire focused DPS who relies on cooldowns to finish off targets due to the very long time to kill: Assuming full charging the arrows (to be able to hit targets past melee range): 3 bodyshots = ~2.5 seconds TTK (~3.25 seconds if bow not preloaded) Or best case scenario: 1 headshot + 1 bodyshot = ~1.25 seconds TTK (~2 seconds if bow was not preloaded) Compared to for example Cassidy: 4 bodyshots = 1.5 seconds TTK Or best case scenario: 2 headshots = ~0.5 seconds TTK Hanzo's only advantage here is that he deals full damage past 35 meters, but trying to hit someone 2-3 times in a row even at 35 meters is next to impossible (considering physical cover + the long time to kill + projectile travel time) At the same time Mercy pocketed Hanzo can still one shot, with the added benefit of now having a 2x bigger arrow hitbox (and buffed storm arrows).
Blizz_JNoh: Hanzo is still an effective mid-range burst damage hero even without the one-shot kills. Post season 9 with the projectile size changes actually saw an increase in Hanzo's performance on the stat side. I do hear you on the loss of how good the one shot kills felt, but an overarching goal of season 9 was to reduce a lot of those burst damage frustrations for players on the receiving end of it. Armor changes in season 10 have also been a benefit to his damage. Still very early but we've been experimenting with adjusting health pools for some of the more evasive or high damage heroes which would also put them back into the range of lethal Hanzo headshots and some other hero combos at 225 HP, but while it would bring some interesting texture to hero interactions overall there are also a bunch of other problems to solve if we want to go through with it.
Q: A month later, and considering he's displayed proudly on the Twitter post for the AMA, I got my question: How have you guys felt about the past reworks on Roadhog and the new one, Wrecking Ball? Like what the goals were exactly, your personal thoughts, the community response, and what you want to fine-tune with them post rework. Those things. I think most people would be interested on how you guys have felt now that it's been a bit.
Blizz_Alec: For the most part, we are relatively happy with the new bases both have been given but there is still some fine-tuning to be done.
I'll start with Wrecking Ball. Our goals were to give him more flexibility with his movement/engage options, heighten the benefits he gives to his team, and give him some quality of life updates. I think our changes all attempt to address those goals but one I think we can hit harder in the future is heightening the benefits he gives to his team. We were a little conservative with the Adaptive Shields change (overhealth is hyper scary in coordinated environments), so perhaps there's room for that to be more pronounced through tuning and actual feedback received in game (working on some updates there). Overall though, Wrecking Ball is doing much better after his recent updates and we believe we have a great base to work with going forward.
For Roadhog, aside from the conversations about his current survivability (we plan to hit that soon) there are some things for us to look at concerning the frequency of his combo. For example, his Pig Pen begins to go on cooldown when you throw it. So you can pre-place one, it gets destroyed, and then Roadhog already has it ready again (even though the enemy may think there's a window where Hook is less deadly). That's one discussion we've recently had. Still some work here for us to do in terms of the value Pig Pen brings outside of the combo as well and how we can make those windows of combo potential less frequent.
Q: Are there any nerfs being discussed for Hog, specifically his survivability? Times where multiple people are shooting a Hog and he just walks away while using his breather seemingly gaining more health than losing health makes the damage you’re doing to him feel pointless and is very unfun to play against, especially now that headshots do less damage to him.
Blizz_Alec: Yes, we plan on nerfing his survivability very soon. We are touching Take a Breather and Whole Hog in an upcoming patch. Hoping that can go live tomorrow.
Q: Hello, with the major tank changes (e.g. armor changes, knockback changes, headshot change, and individual balance changes) that released last week, I am very curious: have there been any noticeable, immediate shifts in the win rates and pick rates amongst tanks? Has there been any collateral shifts within the DPS and support role because of the recent tank changes? I know that, for instance, after the recent armor changes, some heroes have become weaker against armored tanks (i.e. Tracer and Reaper) while others have become significantly stronger (i.e. Cass and Hanzo). I'm interested in knowing how the team's behind-the-scenes statistics have measured lately as a result of the recent tank changes—that is, if it is possible for you guys to share it. If not, understandable.
Blizz_Alec: Some of this is related to meta happenings or balance changes but also related to armor changes/headshot reduction for Tanks. From what we can see the biggest winners (in terms of their performance delta) of the patch are: Ana, Junkrat, Pharah, Roadhog, Sigma, Wrecking Ball, and Zarya.
Many heroes stayed relatively similar while a handful saw a decrease in performance (Bastion, D.Va, Mauga, Orisa, and Reaper).
Q: Ok, I'll try to ask some general questions. Free to choose which one to answer: ^_" In February I noticed that you had received great feedback on the maps after the first hacked mode. But I was wondering when those ideas would be implemented (especially for flashpoints). Personally, I liked Clash Mode. But I also wanted to know what kind of results you received that require modification in your opinion, or if you have noticed any optimal results to maintain, or imitate for other game modes.
Blizz_Alec: These fall outside of hero design but can talk briefly about the first two questions.
Think you are referencing the speed boosts that would potentially come to Flashpoint. Took us some time to get these in a good place but they have been promising in playtests and are on track for a later season. It's important to us that when we add elements like that to a mode that it not only brings quality gameplay but is also communicated well through Sound and VFX. Feel good here now.
We got a lot of great feedback but there are some things the team wished we did better with the Clash Preview. Firstly, it should have showed up more in Quick Play so y'all got more reps on it and can get a better feel for the flow of the game mode. Secondly, we don't think it was best suited for Open Queue in Arcade. If we do something like this again, we'll clean that up. With the feedback we received, we've been investigating how to make the final point more appealing to capture for the attacking team. Many games could result in the attacking team not actually wanting to push onto the last point because it wasn't worth the reward (harder to capture, give up a lot of positioning if you lose). Plenty of iteration happening here now to address that particular issue.
Q: Hi there, I think one of the most obvious questions people here will have is what are the plans to balance out Roadhog. With the midseason tank adjustments I’m sure the general sentiment is that Hog is an outlier for survivability and damage amongst the tanks, especially since Orisa isn’t there to keep him in check now. The headshot damage reduction and his soft rework from before means his survivability is through the roof, and his damage is as high as ever. What are the plans to reign him back in? I will also personally say I don’t think the solution is to buff Orisa, rather nerf Hog to keep him in line. Aside from Hog I think the tank balance is pretty great right now otherwise. Also is there going to be something done about the overbearing passiveness of heroes like LW, that will simultaneously not interact with the enemy team at all whilst also not providing any offensive utility for his own team? I think for all other 9 players in the lobby it’s a pretty miserable experience to have a LW. Thanks for your time.
Blizz_Alec: Answered the Roadhog question in a different place, but yes changes coming soon.
For Lifeweaver, one of the discussions we are having right now (actually this week) and have been having for a while is around the friction that comes with switching between his healing and damage. Giving him more flexibility here would be a great boon to his capability within team fights. Additionally, we've experimented a lot with his Petal Platform. Personally would love for that to be a more attractive area to stand on as a teammate (whether that be through a buff the platform gives you or something else) but there's a lot of learned behavior to work through as allies hop off the platform quite often.
Q: Hey! I have 2 Mercy questions:
1. Is the team looking at Mercy at all for any changes/small buffs? 2. What is Mercy's pick and win rate now compared to Season 3?
Back in Mid Season 9, the DPS passive was reduced and a dev blog stated Mercy wouldn't see changes as she should 'be more reliable moving forward' with the reduction. That nerf was reverted and Mercy stayed the same.
The community has been ranking Mercy as a D Tier support for a few Seasons now and she's in this weird spot where people don't like playing against her, with her, or as her anymore. I and many others still enjoy her most out of all the other heroes but she doesn't play nearly as fun as she used to after the changes that've been made to her (mainly nerfs) and the game over the last year. Thanks!
Blizz_Alec: 1. I think we are more happy in the 20% DPS Passive world than the 15% (it cuts through a lot better, helps mitigate the healing more effectively) so Mercy is more worth a look when that world is permanent. There are some questions of how far we can push her movement and know that is one of the most requested changes.

1. Mercy is still a top-picked 3/4 Support and even higher on console until you hit GM/Top 500. Her performance follows a similar trend, where she's in the top grouping for most ranks and remains above average at the highest ranks. Doesn't mean that she wont receive changes but that is where she is at currently.

Q:I'm not really sure how I am supposed to ask this, but?,
Is the current Balance Team confident about being able to dix the biggest problems the Tank role has been suffering since the OW2 release?
I'm specifically talking about the Counterswap Meta and unhealthy Tank designs being "allowed" to exist, like Tank busters and unkillable tanks (Roadhog, Mauga, and Orisa).
Are we confident that making Tanks able to do almost everything is the right thing to do? Are we confident that we can make Tank fun again for the majority of the player base without straight buffs?
The headshot reduction and knockback reduction changes are especially interesting to me because I really don't think that simple number changes will fix how Tanks feel to play.
I don't want to counterswap. I don't want to face unkillable and easy-to-play Tanks.I don't want Tank Busters.
I really LOVE this game but it currently feels like as if we were going into the wrong direction while ignoring the BIGGEST Problems :c
Blizz_jNoh: At its core, Overwatch is a game designed around being able to swap heroes to gain a tactical advantage or help solve a challenge you might be encountering. This contributes to keeping the moment-to-moment gameplay experience dynamic, drives hero diversity and offers a wider range of both strategic gameplay and skill expression in learning when/where/how to play multiple heroes.
There is a question of how much of an advantage is too much compared to the cost of switching. Ideally we want counters to be clear and understandable, but soft enough that it's still possible to outplay a disadvantaged matchup. It is a team game though and 1v1 matchups are not the highest priority when assessing the heroes.
Tanks do feel this the most with only one of them per team in 5v5 role queue, but all roles do experience the pressure to counter and be countered to an extent.
We're striving to find a balance between swapping heroes every death, (which certainly feels too often), and rarely swapping heroes or getting trapped in mirror matches every game, which quickly leads to fatigue. We've seen a lot of improvements here compared to earlier seasons, but it could always be better.
"Unhealthy" and unpopular designs are not necessarily the same thing. When designing heroes, we aim to provide a wide range of playstyles, mechanics, and aesthetics for players to enjoy. It's okay if they don't all resonate with everyone broadly. We'll do our best to make the game as fun as it can be for a wide audience.

Intro

This is just going to be a general post on Pallywood, highlighting some instances of Palestinians being falsely accused of faking their own injuries that y’all might not have seen. I also wanted to create something of a “list” of some notable cases of false accusations of Pallywood, as many of these cases have continuously cropped up despite being debunked many months ago.

What is Pallywood?

The following three points is what people are generally referring to when they label something as Pallywood:
1) The notion that Palestinians are staging scenes by faking destruction, injuries or death, and trauma/grief.
2) Opportunistic filming and photographing where Palestinians may “bait” a particular response by the IDF that they know is likely to occur. It varies in terms of the level of co-ordination, how much context is provided in the lead-up to the response and in the aftermath, and also how the footage may be deceptively edited.
3) People taking images and footage from other conflicts and misleadingly disseminating them as if they’re depicting some atrocity committed against Palestinians. This also includes the use of AI-generated images, or real images from Gaza but omitting other vital information.
In my personal view, if the term Pallywood absolutely must be used and we simply can't settle for terms like disinformation, misinformation, propaganda, manipulated footage, deceitful editing, "Deceptive Imagery Persuasion", etc., then I believe the term should only cover point 1, and point 2 when enough vital context is maliciously and disingenuously omitted. I consider intent to be a vital component here.
The reason I don’t think point 3 should be encompassed by the term (again, if it absolutely must be used) is because I believe that Palestinians should bear some responsibility here if we're going to use “Palestine” in the portmanteau. If Putin and Assad apologists like Jackson Hinkle want to take imagery and footage showing war crimes by the Syrian regime, and tweet them out as if they’re from Gaza, why is that the fault of the Palestinian people? Hinkle isn’t the only one that does this, and I would simply just call all these instances misinformation or disinformation. [1] [2] [3] [4]

The Worst Offenders

I will be focused on point 1, showing the many cases since the outbreak of the war where Palestinians have been falsely accused of staging scenes. When going through the examples, you’ll notice some familiar figures keep appearing as the most prolific spreaders of this conspiracy theory: Open Source Intel; The Mossad: Satirical, Yet Awesome; Israel War Room; Aviva Klompas; Nioh Berg; Oli London; Hamas Atrocities; Ofir Gendelman; and GAZAWOOD (GW).
GW is the absolute worst offender for this sort of nonsense. Elliot Higgins, founder of Bellingcat, has previously called them out:

This account is posting videos from TV and film productions and claiming their attempts to fake real scenes for propaganda purposes. Russia and Syria used the same tactics to smear the White Helmets and Syrian opposition as part of their attempts to deny war crimes.
One example is Russian TV using stills from a Syrian film production about a Western reporter working with the White Helmets to fake war crime footage to claim it was real footage of the White Helmets faking war crime footage [Link]
Needless to say, the sort of people who do this are shameless propagandists and should be called out as such.

Examples

For people giving the misinformation, just click the "Imgur" citation to see an imgur compilation of the relevant tweets. The fact-checks will nearly always be multiple different accounts or outlets doing the same fact-check.

Rafah crisis actors are preparing to stage scenes when Israel begins their main operation into Rafah. [Imgur] [5] [6] [7]

Fact-check: This is behind-the-scenes footage from a Palestinian TV series called "Bleeding Dirt". [8] [9] [10] [11]
Elliot Higgins tweets:

Purestrain OSHIT here, here's the community note that's not yet published [...]
For the record, because I think it's fair to say my opinion actually matters on this particular topic, @Osint613 [Open Source Intel] is an awful account that has nothing to do with OSINT, or any sort of investigation. A trash account shitting up this website.

That first tweet is crucial here: the misinformation has already spread like wildfire before the Community Note appears — and in some cases, the misinformation goes unaddressed.

GW implying that Palestinians are staging a scene in a hospital. Just asking questions, of course. [Imgur] [12]

Fact-check: Like with the previous example, this is behind-the-scenes footage from a Palestinian TV series called "Bleeding Dirt". [13] [14]

Behind-the-scenes footage of Gazans filming a staged video of a boy falling victim to an air-strike. [Imgur] [15] [16] [17] [18] [19] [20] [21] [22]

Fact-check: It’s a 2022 TikTok clip showing behind-the-scenes footage of a short film made for the Palestinian Civil Defence. [23] [24] [25] [26]

A shrouded corpse that moved its head. Supposedly, this shows that both the woman in grief and the “corpse” are actors. [Imgur] [27] [28] [29]

Fact-check: [30] [31]
Remember how I said the same cases will often reappear? This is one of them. The examples I gave here are all from April this year. The last time this went viral was in late October of last year, where the official Twitter account of the State of Israel even tweeted out this nonsense.

An image of a three-legged man in a wheelchair, showing a failed attempt by Hamas propagandists to generate AI imagery of an injury. [Imgur] [32] [33] [34] [35]

Fact-check: The original photo was doctored, and the man’s injuries are real. [36] [37] [38]

Dolls:

There have been so many incidents where Palestinians have been accused of using hyper-realistic dolls to fake child casualties. These accusations are false, but it continues to persist since the outbreak of the war:

• Incident #1: [Imgur] [39] [40]
  
  • Fact-check: [41] [42] [43]
• Incident #2: [44] [45]
  
  • Fact-check: [46] [47] [48]
• Incident #3: [Imgur] [49] [50]
  
  • Fact-check: [51]
• Incident #4 and Fact-check: [52] [53]
  
• Some other tweets that continue to push this narrative: [54] [55] [56] [57] [58]
  

Behind the scenes footage of make-up being applied to a little girl to fake an injury: [59]

Fact-check: It’s behind-the-scenes footage from a Lebanese short film. [60] [61] [62]

A Gazan in a shroud pretending to be dead. [Imgur] [63]

Fact-check: [64] [65]
This was being shared again recently. The last time it went viral was in November of last year.

A Palestinian girl pretending to be injured in two different incidents. [Imgur] [66] [67] [68] [69] [70]

Fact-check: She's not an actor, and it's the same injury in both of the videos. [71]

Quickfire examples:

• Fact Check: No ‘Pallywood’, this 2018 video shows a medical drill in Gaza. [72]
  
• Video showing Palestinians with fake blood taken from 2017 medical training exercise.
  
• Video doesn't show Palestinians learning to fake injuries amid Israel-Hamas war. [72] [73] Even MEMRI felt the need to tweet that "Gaza Strip Makeup Artist Paints Wounds On Actors In A Médecins du Monde Infomercial."
  
• Iraqi photoshoot misrepresented as Pallywood ‘crisis actor’ video. [74] [75]
  
• BTS footage of ad highlighting condition of Gaza shared with ‘Pallywood’ narrative [76] [Imgur]
  
• Video of Palestinian movie crew misrepresented as 'staged' war footage [77] [78] This was a case where “social media users on both sides of the latest Israel-Hamas war are sharing the video, each falsely alleging that it’s proof the other group is creating propaganda about their own.” [79]
  
• Old video showing staged funeral unrelated to 2023 Hamas-Israel war. [80] [81]
  
• Video from 2013 protest in Cairo misrepresented to falsely claim Palestinians are staging deaths
  
• Debunk of the claim that a man smoking in a bodybag is an instance of Pallywood.
  
• A video recorded by “Mr. Fafo” (Saleh al-Jafarawi) and another obnoxious vlogger that supposedly shows a Pallywood production of multiple bodies and a screaming young girl. [Imgur] [82] Neither Eliot Higgins nor Malachy Browne, an NYT investigative journalist, believe that this is a fabricated scene. The focus is always on Mr. Fafo because he “overreacts” when recording — which is what you expect from an obnoxious vlogger; that is the part of the video which is “inauthentic.” There’s no evidence that all these individuals concocted a plan to punch a hole in the roof, pour fake blood over everyone, and start recording having “set the scene.” There is insufficient evidence that Saleh is a crisis actor, but misinformation involving him continues to persist despite being debunked months ago.
  
• Debunk of the claim that an image shows the same Palestinian child being rescued three times. [83] [84] [85]
  
• Visuals of different individuals shared to claim Palestinian boy 'faked' his injuries
  
• Debunk of the claim that two female Hamas terrorists are pretending to be victims in another video. Another incident that recently made an appearance via Tommy Robinson.
  
• Debunk [86] [87] [88] of the claim that a clip shows a Pallywood hospital production.
  
• Photo of man in hospital bed does not show Gaza 'crisis actor'. [89] [90]
  
• Video Of Injured Man Reassuring His Mother Peddled As Gazan Faking Injuries. [91] [92] [93] [94]
  
• A vloggesocial media influencer records a video claiming his house was bombed. Because he doesn't record the destruction and instead just films his own face (y'know, the typical obnoxious behavior that influencers tend to do across the world), it must be fake and yet another instance of Pallywood. While it could be disputed on who was responsible, there are videos available on his Instagram showing the destruction.
  
• Another false accusation of Pallywood merely because people are recording the injured civilians that are brought into a medical tent.
  
• A Dylan Burns video if you want some general commentary on Pallywood theories.
  
• Bizarrely, I’ve even seen people use the Pallywood label to describe incidents in the West. [Imgur] [95] So a clip that leaves out vital context is now a “Pallywood production.”
  

GW specific:

GW is one of the most prolific propagators of this conspiracy theory. Oftentimes a Pallywood conspiracy theory that goes viral originates from a tweet they made. Generally, the viral tweets grab the attention of various credible fact-checkers, but there's a plethora of tweets where we simply have to come to our independent conclusions; not that this is a difficult task. GW makes an appearance in nearly all of the examples given so far, and I though I would address a couple more tweets that caught my attention. A compilation of all the tweets mentioned can be found here.

• This clip shows a zombie-themed ad in Algeria, not Pallywood.
  
• This clip just shows Palestinians breaking their fast on top of the rubble of their houses. How is this Pallywood? Where is the deception?
  
• This clip presumably shows Palestinians helping others who have been injured after what seems to be a recent attack. If you're conspiracy-brained, then normal facial expressions and movements are suddenly interpreted as actors failing to "maintain character."
  
• There are endless examples like the previous one where normal hand gestures or behavior is evidence of Pallywood. In this clip we have a Palestinian mother grieving over the loss of her daughter. GW is generous enough to say that there "may" be a dead person wrapped in the blanket. But just before recording, apparently, someone had the idea to spill blood on the sheet to make the video more impactful. And GW agrees with another user that "she gestures her arm to keep the person away so as to not let them get in the way of the camera shot." As always, GW will never provide a source for the video -- something they have in common with trash OSINT accounts.
  
• This clip is from a TV show filmed in the West Bank, not Gaza.
  
• Watch this clip and think of the sheer volume of people that would need to be involved in this conspiracy.
  
• This is a video of two different children.
  

You get the idea. Every now and then someone with a large presence on Twitter will tweet out a GW video, and the likelihood the misinformation will go viral increases.

Final Thoughts

The usage of the term Pallywood ramped up on social media in the weeks after Oct. 7th. [96] [97] I will comfortably say that most of these are misapplications of the term. While the term might have had some merit years or even decades ago when it was first coined, I believe the current, colloquial usage of the term is abhorrent, and it shouldn't be used even if there are cases out there of Palestinians definitively faking their injuries. The number of false accusations since Oct. 7th far outweigh any genuine cases one might point to.

Intro

A while ago Destiny debated Alex (PWF) on various matters related to the Gaza War. One of the subject matters discussed was whether or not a particular incident in Gaza constituted a war crime. Amongst various other assessments, Destiny eventually came to the conclusion that these events could be classified as an act of Pallywood. In a subsequent discussion with Lonerbox after LB watched the debate, Destiny would again reiterate this belief.
The original goal for this post was to make the case that Destiny, or anyone else, should eschew from using this label to describe a particular set of behaviors and actions conducted by Palestinians. However, that post is probably not warranted seeing as I haven’t heard Destiny use the term recently, and he also seems to acknowledge how problematic the label is:

“You could call it opportunistic filming instead?” I guess, Pallywood in my mind feels like that, but maybe Pallywood just means completely and totally, like nobody's actually dying. It might be an inappropriate word, I admit that. I think if you listen to what I'm saying it's pretty obvious what I'm saying. So whatever you call the lower level of that.

So instead, this is just going to be a general post on Pallywood, highlighting some instances of Palestinians being falsely accused of faking their own injuries that y’all might not have seen. I also wanted to create something of a “list” of some notable cases of false accusations of Pallywood, as many of these cases have continuously cropped up despite being debunked many months ago.

What is Pallywood?

The following three points is what people are generally referring to when they label something as Pallywood:
1) The notion that Palestinians are staging scenes by faking destruction, injuries or death, and trauma/grief.
2) Opportunistic filming and photographing where Palestinians may “bait” a particular response by the IDF that they know is likely to occur. It varies in terms of the level of co-ordination, how much context is provided in the lead-up to the response and in the aftermath, and also how the footage may be deceptively edited.
3) People taking images and footage from other conflicts and misleadingly disseminating them as if they’re depicting some atrocity committed against Palestinians. This also includes the use of AI-generated images, or real images from Gaza but omitting other vital information.
In my personal view, if the term Pallywood absolutely must be used and we simply can't settle for terms like disinformation, misinformation, propaganda, manipulated footage, deceitful editing, "Deceptive Imagery Persuasion", etc., then I believe the term should only cover point 1, and point 2 when enough vital context is maliciously and disingenuously omitted. I consider intent to be a vital component here.
The reason I don’t think point 3 should be encompassed by the term (again, if it absolutely must be used) is because I believe that Palestinians should bear some responsibility here if we're going to use “Palestine” in the portmanteau. If Putin and Assad apologists like Jackson Hinkle want to take imagery and footage showing war crimes by the Syrian regime, and tweet them out as if they’re from Gaza, why is that the fault of the Palestinian people? Hinkle isn’t the only one that does this, and I would simply just call all these instances misinformation or disinformation. [1] [2] [3] [4]

The Worst Offenders

I will be focused on point 1, showing the many cases since the outbreak of the war where Palestinians have been falsely accused of staging scenes. When going through the examples, you’ll notice some familiar figures keep appearing as the most prolific spreaders of this conspiracy theory: Open Source Intel; The Mossad: Satirical, Yet Awesome; Israel War Room; Aviva Klompas; Nioh Berg; Oli London; Hamas Atrocities; Ofir Gendelman; and GAZAWOOD (GW).
GW is the absolute worst offender for this sort of nonsense. Elliot Higgins, founder of Bellingcat, has previously called them out:

This account is posting videos from TV and film productions and claiming their attempts to fake real scenes for propaganda purposes. Russia and Syria used the same tactics to smear the White Helmets and Syrian opposition as part of their attempts to deny war crimes.
One example is Russian TV using stills from a Syrian film production about a Western reporter working with the White Helmets to fake war crime footage to claim it was real footage of the White Helmets faking war crime footage [Link]
Needless to say, the sort of people who do this are shameless propagandists and should be called out as such.

Examples

For people giving the misinformation, just click the "Imgur" citation to see an imgur compilation of the relevant tweets. The fact-checks will nearly always be multiple different accounts or outlets doing the same fact-check.

Rafah crisis actors are preparing to stage scenes when Israel begins their main operation into Rafah. [Imgur] [5] [6] [7]

Fact-check: This is behind-the-scenes footage from a Palestinian TV series called "Bleeding Dirt". [8] [9] [10] [11]
Elliot Higgins tweets:

Purestrain OSHIT here, here's the community note that's not yet published [...]
For the record, because I think it's fair to say my opinion actually matters on this particular topic, @Osint613 [Open Source Intel] is an awful account that has nothing to do with OSINT, or any sort of investigation. A trash account shitting up this website.

That first tweet is crucial here: the misinformation has already spread like wildfire before the Community Note appears — and in some cases, the misinformation goes unaddressed.

GW implying that Palestinians are staging a scene in a hospital. Just asking questions, of course. [Imgur] [12]

Fact-check: Like with the previous example, this is behind-the-scenes footage from a Palestinian TV series called "Bleeding Dirt". [13] [14]

Behind-the-scenes footage of Gazans filming a staged video of a boy falling victim to an air-strike. [Imgur] [15] [16] [17] [18] [19] [20] [21] [22]

Fact-check: It’s a 2022 TikTok clip showing behind-the-scenes footage of a short film made for the Palestinian Civil Defence. [23] [24] [25] [26]

A shrouded corpse that moved its head. Supposedly, this shows that both the woman in grief and the “corpse” are actors. [Imgur] [27] [28] [29]

Fact-check: [30] [31]
Remember how I said the same cases will often reappear? This is one of them. The examples I gave here are all from April this year. The last time this went viral was in late October of last year, where the official Twitter account of the State of Israel even tweeted out this nonsense.

An image of a three-legged man in a wheelchair, showing a failed attempt by Hamas propagandists to generate AI imagery of an injury. [Imgur] [32] [33] [34] [35]

Fact-check: The original photo was doctored, and the man’s injuries are real. [36] [37] [38]

Dolls:

There have been so many incidents where Palestinians have been accused of using hyper-realistic dolls to fake child casualties. These accusations are false, but it continues to persist since the outbreak of the war:

• Incident #1: [Imgur] [39] [40]
  
  • Fact-check: [41] [42] [43]
• Incident #2: [44] [45]
  
  • Fact-check: [46] [47] [48]
• Incident #3: [Imgur] [49] [50]
  
  • Fact-check: [51]
• Incident #4 and Fact-check: [52] [53]
  
• Some other tweets that continue to push this narrative: [54] [55] [56] [57] [58]
  

Behind the scenes footage of make-up being applied to a little girl to fake an injury: [59]

Fact-check: It’s behind-the-scenes footage from a Lebanese short film. [60] [61] [62]

A Gazan in a shroud pretending to be dead. [Imgur] [63]

Fact-check: [64] [65]
This was being shared again recently. The last time it went viral was in November of last year.

A Palestinian girl pretending to be injured in two different incidents. [Imgur] [66] [67] [68] [69] [70]

Fact-check: She's not an actor, and it's the same injury in both of the videos. [71]

Quickfire examples:

• Fact Check: No ‘Pallywood’, this 2018 video shows a medical drill in Gaza. [72]
  
• Video showing Palestinians with fake blood taken from 2017 medical training exercise.
  
• Video doesn't show Palestinians learning to fake injuries amid Israel-Hamas war. [72] [73] Even MEMRI felt the need to tweet that "Gaza Strip Makeup Artist Paints Wounds On Actors In A Médecins du Monde Infomercial."
  
• Iraqi photoshoot misrepresented as Pallywood ‘crisis actor’ video. [74] [75]
  
• BTS footage of ad highlighting condition of Gaza shared with ‘Pallywood’ narrative [76] [Imgur]
  
• Video of Palestinian movie crew misrepresented as 'staged' war footage [77] [78] This was a case where “social media users on both sides of the latest Israel-Hamas war are sharing the video, each falsely alleging that it’s proof the other group is creating propaganda about their own.” [79]
  
• Old video showing staged funeral unrelated to 2023 Hamas-Israel war. [80] [81]
  
• Video from 2013 protest in Cairo misrepresented to falsely claim Palestinians are staging deaths
  
• Debunk of the claim that a man smoking in a bodybag is an instance of Pallywood.
  
• A video recorded by “Mr. Fafo” (Saleh al-Jafarawi) and another obnoxious vlogger that supposedly shows a Pallywood production of multiple bodies and a screaming young girl. [Imgur] [82] Neither Eliot Higgins nor Malachy Browne, an NYT investigative journalist, believe that this is a fabricated scene. The focus is always on Mr. Fafo because he “overreacts” when recording — which is what you expect from an obnoxious vlogger; that is the part of the video which is “inauthentic.” There’s no evidence that all these individuals concocted a plan to punch a hole in the roof, pour fake blood over everyone, and start recording having “set the scene.” There is insufficient evidence that Saleh is a crisis actor, but misinformation involving him continues to persist despite being debunked months ago.
  
• Debunk of the claim that an image shows the same Palestinian child being rescued three times. [83] [84] [85]
  
• Visuals of different individuals shared to claim Palestinian boy 'faked' his injuries
  
• Debunk of the claim that two female Hamas terrorists are pretending to be victims in another video. Another incident that recently made an appearance via Tommy Robinson.
  
• Debunk [86] [87] [88] of the claim that a clip shows a Pallywood hospital production.
  
• Photo of man in hospital bed does not show Gaza 'crisis actor'. [89] [90]
  
• Video Of Injured Man Reassuring His Mother Peddled As Gazan Faking Injuries. [91] [92] [93] [94]
  
• A vloggesocial media influencer records a video claiming his house was bombed. Because he doesn't record the destruction and instead just films his own face (y'know, the typical obnoxious behavior that influencers tend to do across the world), it must be fake and yet another instance of Pallywood. While it could be disputed on who was responsible, there are videos available on his Instagram showing the destruction.
  
• Another false accusation of Pallywood merely because people are recording the injured civilians that are brought into a medical tent.
  
• A Dylan Burns video if you want some general commentary on Pallywood theories.
  
• Bizarrely, I’ve even seen people use the Pallywood label to describe incidents in the West. [Imgur] [95] So a clip that leaves out vital context is now a “Pallywood production.”
  

GW specific:

GW is one of the most prolific propagators of this conspiracy theory. Oftentimes a Pallywood conspiracy theory that goes viral originates from a tweet they made. Generally, the viral tweets grab the attention of various credible fact-checkers, but there's a plethora of tweets where we simply have to come to our independent conclusions; not that this is a difficult task. GW makes an appearance in nearly all of the examples given so far, and I though I would address a couple more tweets that caught my attention. A compilation of all the tweets mentioned can be found here.

• This clip shows a zombie-themed ad in Algeria, not Pallywood.
  
• This clip just shows Palestinians breaking their fast on top of the rubble of their houses. How is this Pallywood? Where is the deception?
  
• This clip presumably shows Palestinians helping others who have been injured after what seems to be a recent attack. If you're conspiracy-brained, then normal facial expressions and movements are suddenly interpreted as actors failing to "maintain character."
  
• There are endless examples like the previous one where normal hand gestures or behavior is evidence of Pallywood. In this clip we have a Palestinian mother grieving over the loss of her daughter. GW is generous enough to say that there "may" be a dead person wrapped in the blanket. But just before recording, apparently, someone had the idea to spill blood on the sheet to make the video more impactful. And GW agrees with another user that "she gestures her arm to keep the person away so as to not let them get in the way of the camera shot." As always, GW will never provide a source for the video -- something they have in common with trash OSINT accounts.
  
• This clip is from a TV show filmed in the West Bank, not Gaza.
  
• Watch this clip and think of the sheer volume of people that would need to be involved in this conspiracy.
  
• This is a video of two different children.
  

You get the idea. Every now and then someone with a large presence on Twitter will tweet out a GW video, and the likelihood the misinformation will go viral increases.

Final Thoughts

The usage of the term Pallywood ramped up on social media in the weeks after Oct. 7th. [96] [97] I will comfortably say that most of these are misapplications of the term. While the term might have had some merit years or even decades ago when it was first coined, I believe the current, colloquial usage of the term is abhorrent, and it shouldn't be used even if there are cases out there of Palestinians definitively faking their injuries. The number of false accusations since Oct. 7th far outweigh any genuine cases one might point to.