Deadpool is now the 'Merc with a Meta Quest' as he makes his gaming return in his own VR exclusive.

After using Proxmox on my primary server, I decided the second system would be Ubuntu on bare metal.

Meta founder and CEO Mark Zuckerberg said recently on Theo Von’s “This Past Weekend” podcast that everything is shifting to holograms. A hologram is a three-dimensional image that represents an object in a way that allows it

Email authentication protocols like SPF, DKIM, and DMARC play a critical role in protecting domains from spoofing and phishing. However, when SEGs are introduced into the email path, the interaction with these protocols becomes more complex. Security gateways(SEGs) are a core part of many organizations’ email infrastructure. They act as intermediaries between the public internet and internal mail systems, inspecting, filtering, and routing messages. This blog examines how security gateways handle SPF, DKIM, and DMARC, with real-world examples from popular gateways such as Proofpoint, Mimecast, and Avanan. We’ll also cover best practices for maintaining authentication integrity and avoiding misconfigurations that can compromise email authentication or lead to false DMARC failures. Security gateways often sit at the boundary between your organization and the internet, managing both inbound and outbound email traffic. Their role affects how email authentication protocols behave. An inbound SEG examines emails coming into your organization. It checks SPF, DKIM, and DMARC to determine if the message is authentic and safe before passing it to your internal mail servers. An outbound SEG handles emails sent from your domain. It may modify headers, rewrite envelope addresses, or even apply DKIM signing. All of these can impact SPF,  DKIM, or DMARC validation on the recipient’s side. Understanding how SEGs influence these flows is crucial to maintaining proper authentication and avoiding unexpected DMARC failures. Inbound Handling of SPF, DKIM, and DMARC by Common Security Gateways When an email comes into your organization, your security gateway is the first to inspect it. It checks whether the message is real, trustworthy, and properly authenticated. Let’s look at how different SEGs handle these checks. Avanan (by Check Point) SPF: Avanan verifies whether the sending server is authorized to send emails for the domain by checking the SPF record. DKIM: It verifies if the message was signed by the sending domain and if that signature is valid. DMARC: It uses the results of the SPF and DKIM check to evaluate DMARC. However, final enforcement usually depends on how DMARC is handled by Microsoft 365 or Gmail, as Avanan integrates directly with them. Avanan offers two methods of integration:1. API integration: Avanan connects via APIs, no change in MX, usually Monitor or Detect modes.2. Inline integration: Avanan is placed inline in the mail flow (MX records changed), actively blocking or remediating threats. Proofpoint Email Protection SPF: Proofpoint checks SPF to confirm the sender’s IP is authorized to send on behalf of the domain. You can set custom rules (e.g. treat “softfail” as “fail”). DKIM: It verifies DKIM signatures and shows clear pass/fail results in logs. DMARC: It fully evaluates DMARC by combining SPF and DKIM results with alignment checks. Administrators can configure how to handle messages that fail DMARC, such as rejecting, quarantining, or delivering them. Additionally, Proofpoint allows whitelisting specific senders you trust, even if their emails fail authentication checks. Integration Methods Inline Mode: In this traditional deployment, Proofpoint is positioned directly in the email flow by modifying MX records. Emails are routed through Proofpoint’s infrastructure, allowing it to inspect and filter messages before they reach the recipient’s inbox. This mode provides pre-delivery protection and is commonly used in on-premises or hybrid environments. API-Based (Integrated Cloud Email Security – ICES) Mode: Proofpoint offers API-based integration, particularly with cloud email platforms like Microsoft 365 and Google Workspace. In this mode, Proofpoint connects to the email platform via APIs, enabling it to monitor and remediate threats post-delivery without altering the email flow. This approach allows for rapid deployment and seamless integration with existing cloud email services. Mimecast SPF: Mimecast performs SPF checks to verify whether the sending server is authorized by the domain’s SPF record. Administrators can configure actions for SPF failures, including block, quarantine, permit, or tag with a warning. This gives flexibility in balancing security with business needs. DKIM: It validates DKIM signatures by checking that the message was correctly signed by the sending domain and that the content hasn’t been tampered with. If the signature fails, Mimecast can take actions based on your configured policies. DMARC: It fully evaluates DMARC by combining the results of SPF and DKIM with domain alignment checks. You can choose to honor the sending domain’s DMARC policy (none, quarantine, reject) or apply custom rules, for example, quarantining or tagging messages that fail DMARC regardless of the published policy. This allows more granular control for businesses that want to override external domain policies based on specific contexts. Integration Methods Inline Deployment: Mimecast is typically deployed as a cloud-based secure email gateway. Organizations update their domain’s MX records to point to Mimecast, so all inbound (and optionally outbound) emails pass through it first. This allows Mimecast to inspect, filter, and process emails before delivery, providing robust protection. API Integrations: Mimecast also offers API-based services through its Mimecast API platform, primarily for management, archival, continuity, and threat intelligence purposes. However, API-only email protection is not Mimecast’s core model. Instead, the APIs are used to enhance the inline deployment, not replace it. Barracuda Email Security Gateway SPF: Barracuda checks the sender’s IP against the domain’s published SPF record. If the check fails, you can configure the system to block, quarantine, tag, or allow the message, depending on your policy preferences. DKIM: It validates whether the incoming message includes a valid DKIM signature. The outcome is logged and used to inform further policy decisions or DMARC evaluations. DMARC: It combines SPF and DKIM results, checks for domain alignment, and applies the DMARC policy defined by the sender. Administrators can also choose to override the DMARC policy, allowing messages to pass or be treated differently based on organizational needs (e.g., trusted senders or internal exceptions). Integration Methods Inline mode (more common and straightforward): Barracuda Email Security Gateway is commonly deployed inline by updating your domain’s MX records to point to Barracuda’s cloud or on-premises gateway. This ensures that all inbound emails pass through Barracuda first for filtering and SPF, DKIM, and DMARC validation before being delivered to your mail servers. Deployment Behind the Corporate Firewall: Alternatively, Barracuda can be deployed in transparent or bridge mode without modifying MX records. In this setup, the gateway is placed inline at the network level, such as behind a firewall, and intercepts mail traffic transparently. This method is typically used in complex on-premises environments where changing DNS records is not feasible. Cisco Secure Email (formerly IronPort) Cisco Secure Email acts as an inline gateway for inbound email, usually requiring your domain’s MX records to point to the Cisco Email Security Appliance or cloud service. SPF: Cisco Secure Email verifies whether the sending server is authorized in the sender domain’s SPF record. Administrators can set detailed policies on how to handle SPF failures. DKIM: It validates the DKIM signature on incoming emails and logs whether the signature is valid or has failed. DMARC: It evaluates DMARC by combining SPF and DKIM results along with domain alignment checks. Admins can configure specific actions, such as quarantine, reject, or tag, based on different failure scenarios or trusted sender exceptions. Integration methods On-premises Email Security Appliance (ESA): You deploy Cisco’s hardware or virtual appliance inline, updating MX records to route mail through it for filtering. Cisco Cloud Email Security: Cisco offers a cloud-based email security service where MX records are pointed to Cisco’s cloud infrastructure, which filters and processes inbound mail. Cisco Secure Email also offers advanced, rule-based filtering capabilities and integrates with Cisco’s broader threat protection ecosystem, enabling comprehensive inbound email security. Outbound Handling of SPF, DKIM, and DMARC by Common Security Gateways When your organization sends emails, security gateways can play an active role in processing and authenticating those messages. Depending on the configuration, a gateway might rewrite headers, re-sign messages, or route them through different IPs – all actions that can help or hurt the authentication process. Let’s look at how major SEGs handle outbound email flow. Avanan – Outbound Handling and Integration Methods Outbound Logic Avanan analyzes outbound emails primarily to detect data loss, malware, and policy violations. In API-based integration, emails are sent directly by the original mail server (e.g., Microsoft 365 or Google Workspace), so SPF and DKIM signatures remain intact. Avanan does not alter the message or reroute traffic, which helps maintain full DMARC alignment and domain reputation. Integration Methods 1. API Integration: Connects to Microsoft 365 or Google Workspace via API. No MX changes are needed. Emails are scanned after they are sent, with no modification to SPF, DKIM, or the delivery path.  How it works: Microsoft Graph API or Google Workspace APIs are used to monitor and intervene in outbound emails. Protection level: Despite no MX changes, it can offer inline-like protection, meaning it can block, quarantine, or encrypt emails before they are delivered externally. SPF/DKIM/DMARC impact: Preserves original headers and signatures since mail is sent directly from Microsoft/Google servers. 2. Inline Integration: Requires changing MX records to route email through Avanan. In this mode, Avanan can intercept and inspect outbound emails before delivery. Depending on the configuration, this may affect SPF or DKIM if not properly handled. How it works: Requires adding Avanan’s Protection level: Traditional inline security with full visibility and control, including encryption, DLP, policy enforcement, and advanced threat protection. SPF/DKIM/DMARC impact: SPF configuration is needed by adding Avanan’s include mechanism to the sending domain’s SPF record. The DKIM record of the original sending source is preserved. For configurations, you can refer to the steps in this blog. Proofpoint – Outbound Handling and Integration Methods Outbound Logic Proofpoint analyzes outbound emails to detect and prevent data loss (DLP), to identify advanced threats (malware, phishing, BEC) originating from compromised internal accounts, and to ensure compliance. Their API integration provides crucial visibility and powerful remediation capabilities, while their traditional gateway (MX record) deployment delivers true inline, pre-delivery blocking for outbound traffic. Integration methods 1. API Integration: No MX record changes are required for this deployment method. Integration is done with Microsoft 365 or Google Workspace. How it works: Through its API integration, Proofpoint gains deep visibility into outbound emails and provides layered security and response features, including: Detect and alert: Identifies sensitive content (Data Loss Prevention violations), malicious attachments, or suspicious links in outbound emails. Post-delivery remediation (TRAP): A key capability of the API model is Threat Response Auto-Pull (TRAP), which enables Proofpoint to automatically recall, quarantine, or delete emails after delivery. This is particularly useful for internally sent messages or those forwarded to other users. Enhanced visibility: Aggregates message metadata and logs into Proofpoint’s threat intelligence platform, giving security teams a centralized view of outbound risks and user behavior. Protection level: API-based integration provides strong post-delivery detection and response, as well as visibility into DLP incidents and suspicious behavior.  SPF/DKIM/DMARC impact: Proofpoint does not alter SPF, DKIM, or DMARC because emails are sent directly through Microsoft or Google servers. Since Proofpoint’s servers are not involved in the actual sending process, the original authentication headers remain intact. 2. Gateway Integration (MX Record/Smart Host): This method requires updating MX records or routing outbound mail through Proofpoint via a smart host. How it works: Proofpoint acts as an inline gateway, inspecting emails before delivery. Inbound mail is filtered via MX changes; outbound mail is relayed through Proofpoint’s servers. Threat and DLP filtering: Scans outbound messages for sensitive content, malware, and policy violations. Real-time enforcement: Blocks, encrypts, or quarantines emails before they’re delivered. Policy controls: Applies rules based on content, recipient, or behavior. Protection level: Provides strong, real-time protection for outbound traffic with pre-delivery enforcement, DLP, and encryption. SPF/DKIM/DMARC impact: Proofpoint becomes the sending server: SPF: You need to configure ProofPoint’s SPF. DKIM: Can sign messages; requires DKIM setup. DMARC: DMARC passes if SPF and DKIM are set up properly. Please refer to this article to configure SPF and DKIM for ProofPoint. Mimecast – Outbound Handling and Integration Methods Outbound Logic Mimecast inspects outbound emails to prevent data loss (DLP), detect internal threats such as malware and impersonation, and ensure regulatory compliance. It primarily functions as a Secure Email Gateway (SEG), meaning it sits directly in the outbound email flow. While Mimecast offers APIs, its core outbound protection is built around this inline gateway model. Integration Methods 1. Gateway Integration (MX Record change required) This is Mimecast’s primary method for outbound email protection. Organizations route their outbound traffic through Mimecast by configuring their email server (e.g., Microsoft 365, Google Workspace, etc.) to use Mimecast as a smart host. This enables Mimecast to inspect and enforce policies on all outgoing emails in real time. How it works: Updating outbound routing in your email system (smart host settings), or Using Mimecast SMTP relay to direct messages through their infrastructure. Mimecast then scans, filters, and applies policies before the email reaches the final recipient. Protection level: Advanced DLP: Identifies and prevents sensitive data leaks. Impersonation and Threat Protection: Blocks malware, phishing, and abuse from compromised internal accounts. Email Encryption and Secure Messaging: Applies encryption policies or routes messages via secure portals. Regulatory Compliance: Enforces outbound compliance rules based on content, recipient, or metadata. SPF/DKIM/DMARC impact: SPF: Your SPF record must include Mimecast’s SPF mechanism based on your region to avoid SPF failures. DKIM: A new DKIM record should be configured to make sure your emails are DKIM signed when routing through Mimecast. DMARC: With correct SPF and DKIM setup, Mimecast ensures DMARC alignment, maintaining your domain’s sending reputation. Please refer to the steps in this detailed article to set up SPF and DKIM for Mimecast. 2. API Integration (Complementary to Gateway) Mimecast’s APIs complement the main gateway by providing automation, reporting, and management tools rather than handling live outbound mail flow. They allow you to manage policies, export logs, search archived emails, and sync users. APIs enhance visibility and operational tasks but do not provide real-time filtering or blocking of outbound messages. Since APIs don’t process live mail, they have no direct effect on SPF, DKIM, or DMARC; those depend on your gateway (smart host) setup. Barracuda – Outbound Handling and Integration Methods Outbound Logic Barracuda analyzes outbound emails to prevent data loss (DLP), block malware, stop phishing/impersonation attempts from compromised internal accounts, and ensure compliance. Barracuda offers flexible deployment options, including both traditional gateway (MX record) and API-based integrations. While both contribute to outbound security, their roles are distinct. Integration Methods 1. Gateway Integration (MX Record / Smart Host) — Primary Inline Security How it works: All outbound emails pass through Barracuda’s security stack for real-time inspection, threat blocking, and policy enforcement before delivery. Protection level: Comprehensive DLP (blocking, encrypting, or quarantining sensitive content)  Outbound spam and virus filtering  Enforcement of compliance and content policies This approach offers a high level of control and immediate threat mitigation on outbound mail flow. SPF/DKIM/DMARC impact: SPF: Update SPF records to include Barracuda’s sending IPs or SPF include mechanism. DKIM: Currently, no explicit setup is needed; DKIM of the main sending source is preserved. Refer to this article for more comprehensive guidance on Barracuda SEG configuration. 2. API Integration (Complementary & Advanced Threat Focus) How it works: The API accesses cloud email environments to analyze historical and real-time data, learning normal communication patterns to detect anomalies in outbound emails. It also supports post-delivery remediation, enabling the removal of malicious emails from internal mailboxes after sending. Protection level: Advanced AI-driven detection and near real-time blocking of outbound threats, plus strong post-delivery cleanup capabilities. SPF/DKIM/DMARC impact: Since mail is sent directly by the original mail server (e.g., Microsoft 365), SPF and DKIM signatures remain intact, preserving DMARC alignment and domain reputation. Cisco Secure Email (formerly IronPort) – Outbound Handling and Integration Methods Outbound Logic Cisco Secure Email protects outbound email by preventing data loss (DLP), blocking spam and malware from internal accounts, stopping business email compromise (BEC) and impersonation attacks, and ensuring compliance. Cisco provides both traditional gateway appliances/cloud gateways and modern API-based solutions for layered outbound security. Integration Methods 1. Gateway Integration (MX Record / Smart Host) – Cisco Secure Email Gateway (ESA) How it works: Organizations update MX records to route mail through the Cisco Secure Email Gateway or configure their mail server (e.g., Microsoft 365, Exchange) to smart host outbound email via the gateway. All outbound mail is inspected and policies enforced before delivery. Protection level: Granular DLP (blocking, encrypting, quarantining sensitive content) Outbound spam and malware filtering to protect IP reputation Email encryption for sensitive outbound messages Comprehensive content and attachment policy enforcement SPF: Check this article for comprehensive guidance on Cisco SPF settings. DKIM: Refer to this article for detailed guidance on Cisco DKIM settings. 2. API Integration – Cisco Secure Email Threat Defense How it works: Integrates directly via API with Microsoft 365 (and potentially Google Workspace), continuously monitoring email metadata, content, and user behavior across inbound, outbound, and internal messages. Leverages Cisco’s threat intelligence and AI to detect anomalous outbound activity linked to BEC, account takeover, and phishing. Post-Delivery Remediation: Automates the removal or quarantine of malicious or policy-violating emails from mailboxes even after sending. Protection level: Advanced, AI-driven detection of sophisticated outbound threats with real-time monitoring and automated remediation. Complements gateway filtering by adding cloud-native visibility and swift post-send action. SPF/DKIM/DMARC impact: Since emails are sent directly by the original mail server, SPF and DKIM signatures remain intact, preserving DMARC alignment and domain reputation. If you have any questions or need assistance, feel free to reach out to EasyDMARC technical support.

Gun X Lock and Load Zombie Survival posted in GunX Lock and Load Published June 06, 2025 Advertisement Gun X: Lock. Load. Survive.Step into the boots of a true gunslinger in Gun X, the ultimate VR shooter that fuses tactical realism with explosive action. Master the art of gun assembly under pressure, engage in intense PvP duels, and hold your ground against relentless waves of zombies. Every match tests your reflexes, precision, and survival instincts.🔫 Key Features:Realistic gun assembly and reloading mechanicsFast-paced 1v1 PvP battlesHeart-pounding Zombie Survival ModeSkill-based gun progression — unlock and purchase new weapons as you level upDesigned exclusively for Meta Quest 2, Quest 3, and Quest ProWhether you're a competitive player or a survival enthusiast, Gun X throws you into a high-stakes battlefield where speed, accuracy, and gun knowledge are your only allies.Are you ready to lock and load?Get the App from Meta Store : GET IT NOW Comments Nobody has left a comment. You can be the first! You must log in to join the conversation. Don't have a GameDev.net account? Sign up!

With reclaimed land previously allocated to cars, the Grijalva River boardwalk offers generous public spaces and reconnects the Mexican city of Villahermosa to its river In Villahermosa, nature reigns supreme. Surrounded by rivers, lagoons, wild vegetation and the scorching heat of a humid tropical climate, the city’s identity is shaped by intense and unpredictable natural forces. The capital of the Mexican state of Tabasco was founded in 1564 on the banks of the Grijalva River, a vital trade route that has significantly shaped the city’s development. For locals, the river has long been both blessing and threat; major floods have been recorded since the 17th century. A devastating flood in 2007 submerged what officials estimated to be 80 per cent of the city, damaging or destroying more than 120,000 homes. In the aftermath of the inundation, high concrete retaining walls were built along both banks of the Grijalva River to prevent further flooding. While this was an understandable measure at first glance, it consequently caused residents to lose both their visual and physical connection with the river. As a result, people moved, particularly from the western bank where the historical centre is located, to new areas further away from the Grijalva River. The riverfront was left to deteriorate into a troubled zone. On the eastern bank, the neighbourhood of Gaviotas was already considered unsafe before the flood, yet it maintained more of its residential character. In 2022, 15 years after the dramatic flood, then‑president Andrés Manuel López Obrador, more commonly known as AMLO, announced the construction of a new 6km‑long riverfront promenade in Villahermosa, the capital of his home state. The idea was to enable the population to once again take pride in and live with their river, looking to Paris and Rome as examples. The monumental task, with its large urban scale and the population’s psychological trauma, was entrusted to the Ministry of Agricultural, Territorial and Urban Development (SEDATU) as part of their Programa de Mejoramiento Urbano (Urban Improvement Programme, or PMU). This programme aimed to use architecture as an ‘instrument of social transformation’. High expectations were placed on these projects; architects were asked to create ‘places of national pride’ while improving everyday living conditions. The architectural trio of Alejandro Castro Jiménez Labora, Mauricio Rocha Iturbide, and Óscar Rodríguez Castañeda, along with their teams, were commissioned to design a linear park along both banks of the Grijalva. Each architect contributed their strength: Castro brought his expertise in poetic urban furniture; Rocha his sensitive and atmospheric architectural approach; and Rodríguez his thoughtful urban and traffic planning skills. The SEDATU team provided technical and participatory expertise, enabling contextual sensitivity by sharing essential information about the site’s topography, soil conditions and water flows. From the city’s existing observatory, the Torre del Caballero landmark, visitors enjoy an excellent view over the redesigned riverbanks. The historical centre and the Gaviotas neighbourhood now form a single ensemble, while the intervention carefully responds to the different conditions found along the length of the river. The project’s main objective is to reclaim some of the land previously allocated to cars and create a promenade for pedestrians and slower vehicles, punctuated with public spaces and facilities. On both sides of the river, cars are now limited to just one or two grey asphalt lanes. Running alongside are generous cycle paths and pedestrian walkways made of earth‑coloured concrete. Speed bumps in the same material and colour connect the pavements on either side of the road while helping to limit traffic speed to 30km/h, further enhancing pedestrian safety. Several design elements are found along almost the entire promenade. A ribbon of light‑grey benches delineates the edge of the elevated riverfront; stone walls, steps and ramps are used to negotiate the slight changes in level; planters and lush vegetation soften the transition to the walkways, creating a welcome buffer from street traffic. The most visually striking components are the tall, red‑pigmented concrete light poles on the elevated path, adorned with elegant L‑shaped steel light fixtures, which establish a strong and cohesive visual rhythm. Only upon closer inspection you notice the 2007 retaining walls peeking through the dense tropical vegetation. Removing these unattractive concrete barriers was never an option; they stand as a symbol of successful flood protection for the local population. The architectural team ingeniously built the elevated promenade atop the existing wall – an effective concealment from the street side while simultaneously inviting residents to reconnect with the Grijalva.  At the foot of the observatory, directly below the retaining wall, the earth‑toned concrete platforms of the Carlos A Madrazo Becerra Park stretch towards the river. Visitors can access the park via a ramp from the promenade on the western bank or by ferry from the opposite side. In the park, concrete furnishings invite visitors to linger among tropical vegetation set against tall natural stone walls. Importantly, it is a space that is durable and requires minimal maintenance – a survival formula for public parks in the Mexican context. Small traces on the concrete benches reveal that the park weathered its baptism of fire last year: the design accommodates the river’s natural dynamics, adapting to fluctuating water levels without compromising public safety. Beyond providing much‑needed shade, the extensive planting of native, low‑maintenance plants on both riverbanks has improved soil stability. Above the park, on a broad extension of the elevated pathway, stand three long, elegant buildings with large cantilevered roofs supported by hefty beams resting on distinctive double columns. The tall glass walls that enclose the interiors are set back, creating a visual flow between interior and exterior spaces. While the beams evoke timber construction, they – like the columns – are made of the same pigmented concrete used for the promenade paving. Despite their refined composition, these structures have remained largely unused since their completion over a year ago, neither serving their intended function as restaurants nor hosting alternative uses. Even the beautifully designed park sees only limited public engagement. The ambitious goal of SEDATU with the PMU projects to ‘counteract violence and strengthen the social fabric’ appears, for now, to have fallen short in this area. According to national statistics, Villahermosa ranks first in perceived insecurity among Mexican cities. This sense of insecurity is tangible on the promenade by the city centre, where buildings that look abandoned contribute to an atmosphere of neglect. The situation is markedly different on the opposite riverbank, in the Gaviotas neighbourhood. Construction of the 3.5km promenade on this side began in 2021 with three open pavilions housing several small kiosks, which quickly evolved into popular taco stands. The Plaza Solidaridad, revitalised by the architectural trio, draws people from the surrounding vibrant neighbourhood. Further south, the final section that was built is a large sports area and children’s playground, which were embraced by the local community even before their official inauguration in February 2024. Especially after sunset, when the air cools, the well‑lit Gaviotas riverfront comes to life. During daylight hours, however, air‑conditioned shopping centres remain the preferred gathering places for the residents of Villahermosa. Rocha describes the city’s new promenade as a ‘jazz composition’, a striking metaphor that speaks of rhythmic complexity and the freedom to improvise. With just a few designed elements and carefully selected colours, the architects have harmoniously layered the river’s urban spaces. The project is earning international recognition but, in Mexico, it faced sharp criticism and was overshadowed by accusations of nepotism. Castro is a friend of AMLO’s son, and the fact that the intervention took place in the home state of the then‑president, coupled with its substantial budget by local standards, drew considerable attention. According to residents, this undermined public acceptance. When asked about the negative press, Rocha speaks of the need to develop a ‘crisis muscle’; he says architects working on public projects in Mexico must ‘let go of perfectionism’ as much lies beyond their control.  During AMLO’s six‑year term, which ended in 2024, SEDATU implemented 1,300 PMU projects in 193 highly marginalised municipalities across the country. While many of these interventions undoubtedly improved people’s quality of life, the Villahermosa riverside project also reveals architecture’s limitations, exposing some of the programme’s weaknesses: architectural interventions often act as sticking plasters on an extensively damaged urban fabric. They are handed over from a national ministry with comprehensive expertise and funding to local governments lacking the means to sustain them. Although SEDATU conducted participatory consultations during the project’s implementation, this engagement was absent once the project was completed. Public acceptance and appropriation can take time; what this project does is send an invitation out. 2025-06-05 Reuben J Brown Share AR June 2025RoadsBuy Now

In my last Fast Company column, I shared my reasons for manufacturing my electric trucks in the U.S. I’m not alone. While near-shoring to North America has been underway for several years, the current tariff shifts and shipping complexities make U.S. manufacturing a higher priority still. However, there were 292,825 factories in the U.S. as of 2021. Of those, 846 employ 1,000 people or more. Some of these are my engineering firm’s clients, giving us a front row seat to the complexity of retrofitting an existing factory to full U.S. manufacturing. While building a new factory is expensive and lengthy, these companies’ tasks are more difficult still. There are good reasons for making the shift as quickly as possible. Moving to most or fully U.S. manufacturing brings higher visibility, faster response time, and higher resilience to supply chain disruption, as well as greater protection from tariff shifts and geopolitical change. But if you’re early in the process, here’s my advice for your transition: Determine a priority ranking for the refining and raw materials you shift to in-country and North American sourcing. Give highest ranking to categories including defense, high value items (such as steel, aluminum, and rare minerals, etc.), and consumer safety items (such as pharmaceutical components, etc.). Be more strategic in the offshore suppliers you continue using for non-advanced manufacturing by prioritizing closer and more geographic-friendly locations for production and shipment such as Mexico and Argentina. Utilize government-backed capital, where possible, for extracting/mining minerals and metals such as lithium, red mud, magnesium, etc. Beyond the high-ranking product categories, move to domestic suppliers for primary materials such as steel, aluminum, cement, and plastics. Likewise, reduce offshoring of technical staff as well as raw materials, where possible. Use all means possible to become power independent through solar production, micro-grids, and nuclear power production. Consider creating a 4-year completion bonus for military vets. Hire vets wherever possible, as they make great workers and entrepreneurs. Likewise, we can press for future policy changes that best support Made in America manufacturing, as follows: Encourage ship building in the U.S., as well as creating new means of automated freight transit. Work towards transformation plans for government-funded R&D to include more attractive loans, rebates, and grants, as well as programs for tax-free status for intellectual property during commercialization, to incent and support organizations making the shift. Consider energy rebates to U.S. manufacturers and distributors to make American manufacturing more cost-effective and viable.   Create policies to include the cost of offshore staff in tariff calculations. Expand trade relationships with Caribbean nations for products such as sugar, avocados, bananas, etc. Avoid or even ban foreign ownership of the food supply chain. Create fair competition for government contracting. Make health supplements and homeopathic medicines tax deductible, to promote a healthy workforce. While it may not be readily evident, these policy changes are related to successful reshoring. In all, we need larger scale, lower costs, and more automated and simplified mechanisms for product manufacturing. These issues, in my experience, are as equally important as the raw materials we require. We need increased support for niche manufacturing. In my opinion, we also need deregulation, and increased access to land (particularly in the west; the federal government owns great quantities of the available land, which is choking available supply). I believe we need better education, self-reliance, health, and incentive structures to get the capital, entrepreneurs, and workers for Made in America manufacturing. Who’s with me? Matthew Chang is the founding partner of Chang Robotics.

The auto industries in both the US and Europe could come to a standstill within weeks thanks to China’s ongoing restrictions on exports of rare earth minerals and magnets. Several European car part manufacturers have already halted production lines a

While Mark Zuckerberg was hyping Meta’s latest Ray-Ban smartglasses and Apple was promoting its Vision Pro mixed reality headset in 2023, Finnish startup IXI was quietly crafting high-tech specs for more practical purposes.  Founded in 2021, the comp