Users in the stable branch are getting the new gallery UI with HD+ quality uploads and captions.

This feature lets you can launch your favorite apps from your lock screen or Control Center.

FORM Brands Studio has given London’s Air Ambulance Charity a new look. Rather than transporting patients to hospital, the charity’s doctors and paramedics treat seriously injured people at the scene from its two helicopters and eight cars. It is the only organisation performing this role in London. Established in 1989, it is called to a rising number of patients across the capital every year, helping more than 2,000 people in 2024. London’s Air Ambulance Charity (LAAC) needs £17m a year to operate, 96% which comes from donations. “But 60% of Londoners don’t know we’re a charity,” says LAAC’s director of fundraising and marketing, Jayne Clarke. FORM Brands Studio identity for London’s Air Ambulance Charity in OOH posters Its new organisational strategy is about raising awareness, enhancing fundraising efforts and strengthening its connection with London’s communities. “We’re trying to make sure the strategy is about hope and looking forward to the future,” Clarke says. To accompany this new strategy, the charity also decided to change up its visual identity. “Our previous branding was very corporate,” Clarke admits.FORM Brands Studio won the job after a pitch. Strategy director Beth Andlaw set up the east London agency in 2022 with creative director Alex Andlaw. Before that she had been in comms and PR, and had worked with LAAC on and off for about 20 years. FORM Brands Studio identity for London’s Air Ambulance Charity on stage FORM introduced a new wordmark, colour palette, typeface, icons, motion, creative copy, messaging, fundraising memorabilia and photography. However, the existing helicopter icon was retained. “It has a lot of love and legacy,” says Clarke. The agency’s brand idea, Propelling Promise, was inspired by the urgent, intense nature of the work carried out by LAAC’s clinical and operational crews. That was used to give structure to creative copy lines and the new tone of voice. Each lead line includes an element of “propelling” to imply urgency and momentum, and “promise” to imply warmth and hope. That resulted in lines including “Trauma doesn’t stop. Neither do we” and “Here for London. Today, tomorrow, always.” FORM brought in Peggy Nyamekye to work on the copywriting. Meanwhile, the visual identity, developed with designer Mayan Mistry, comprises a gradient design system, drawing on the rotational motion of helicopter blades. Borough names are repeated in radiating patterns and overlaid with the gradient. Red is still central to the charity’s identity, but FORM introduced the vivid orange worn by medics on-scene. “These colours blend in the gradient, creating a visual signature that speaks to urgency, action, optimism and hope,” says Alex Andlaw. https://d3faj0w6aqatyx.cloudfront.net/uploads/2025/06/LAA_OOH_TUBE_1920x1080.mp4 With the help of motion graphics designer Matt Fowler, the agency introduced movement to the branding, to reflect the aircraft’s blades in flight. The logo’s new wordmark is in Barlow, inspired by the existing big white lettering on the helicopter tail booms. Before, the charity’s name was written lower case in a thinner font. “Now it’s bigger, bolder and more impactful,” says Alex Andlaw. FORM also redesigned the icons to have more personality but still be functional. “The icons help the team talk about quite hard subjects,” he says, such as casualties, and the designs had to balance warmth and realism. “We did quite a few hearts, some look too detailed and some too basic,” he explains. The agency also created a series of collectible badges, inspired by the embroidered badges worn by the charity’s doctors and pilots.FORM Brands Studio identity for London’s Air Ambulance Charity in Instagram posts Meanwhile, photographer James Pearson-Howes was briefed to capture real people, places and moments from across London. The new branding had to resonate with very different types of donors, from the charity’s collection buckets to seven-figure corporate donations, says Clarke. “And the doctors wearing the brand have very strong opinions, as do the pilots. FORM took in all these views and managed to make all those people happy.” https://d3faj0w6aqatyx.cloudfront.net/uploads/2025/06/LAA_OOH_BILLBOARD_1920x1080.mp4 FORM Brands Studio identity for London’s Air Ambulance Charity FORM Brands Studio identity for London’s Air Ambulance Charity in OOH posters

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.

Elon Musk is contemplating decommissioning SpaceX's Dragon spacecraft, responding to President Donald Trump's apparent intent to terminate government subsidies and contracts with the billionaire's companies. It looks like the feud between the former allies has quickly turned vicious.SpaceX's CEO initially announced that the company would retire its Dragon spacecraft in an X post on Thursday, with Musk sharing a screenshot of a post published on Trump's Truth Social account earlier in the day."The easiest way to save money in our Budget, Billions and Billions of Dollars, is to terminate Elon’s Governmental Subsidies and Contracts," said Trump in the screenshotted post. "I was always surprised that Biden didn’t do it!" You May Also Like "In light of the President’s statement about cancellation of my government contracts, @SpaceX will begin decommissioning its Dragon spacecraft immediately," Musk wrote on X.SpaceX's Dragon spacecraft are a family of vehicles designed to carry passengers and cargo. The National Aeronautics and Space Administration (NASA) has previously relied upon them to transport astronauts to and from the International Space Station (ISS). Mere hours prior to Musk's announcement, SpaceX posted on X that it was preparing to launch a Dragon next Tuesday.For a few hours, it seemed reasonable to assume that this launch would now not go ahead. However, Musk then appeared to quickly walk back his decision. Responding to an X user advising him to "cool off and take a step back for a couple days," the billionaire subsequently stated that Dragon will not be decommissioned after all.It's unclear whether Musk's initial announcement was sincere, or whether his apparent about-face might be sarcastic. Musk has a history of making flippant comments online with no apparent regard to their consequences. What is clear is that Musk and Trump's relationship is well past the honeymoon phase, and now looks much more like an ugly divorce.If Trump does terminate government contracts with Musk's companies, it would deal a significant blow to the billionaire. According to a Washington Post investigation, NASA has invested over $15 billion in SpaceX alone. When put together with Musk's other companies such as EV automaker Tesla, his various businesses have received at least $38 billion in government contracts, loans, subsidies, and tax credits. Mashable Trend Report: Coming Soon! Decode what’s viral, what’s next, and what it all means. Sign up for Mashable’s weekly Trend Report newsletter. By clicking Sign Me Up, you confirm you are 16+ and agree to our Terms of Use and Privacy Policy. Thanks for signing up! Musk and Trump go through messy public breakup Credit: Roberto Schmidt / AFP via Getty Images Musk's relationship with Trump has significantly deteriorated in recent days. The billionaire announced that he was leaving his position as de facto head of the Department of Government Efficiency (DOGE) last Wednesday, just one day after he criticised Trump's tax bill as undermining its work. The split was presented as amicable at the time, with Trump presenting Musk with a golden key and words of praise. However, their love affair has quickly turned sour.Musk continued to lambast Trump's bill after his departure from DOGE, arguing that it will increase government debt by trillions of dollars. Strongly disagreeing with the president's characterisation of the proposed legislation as a "Big Beautiful Bill," Musk labelled it a "disgusting abomination" and has been calling for lawmakers to crush it.For his part, Trump has claimed that Musk is simply throwing a tantrum because the bill supposedly cut an alleged "EV mandate." The president stated on Thursday that he had asked the billionaire to leave his administration, and that Musk had been "wearing thin.""I took away his EV Mandate that forced everyone to buy Electric Cars that nobody else wanted (that he knew for months I was going to do!), and he just went CRAZY!" Trump claimed. Despite Trump's assertions, he did not abolish any EV mandate as there has never been any U.S. law which makes switching to an electric car mandatory. However, Trump has taken several anti-EV measures since his inauguration, including abolishing incentives encouraging EV adoption, pausing $3 billion in funding for a U.S. charging network, and introducing a $250 annual fee for EV users in his recent tax bill. Related Stories Trump's claim about Musk is an interesting contrast to his statements in March, when he praised the billionaire for not complaining about the supposed end of the non-existent EV mandate. The president made the comments while he and Musk co-hosted a Tesla ad on the White House lawn in an effort to boost the company's cratering stock prices.Tesla's struggling share value has now fallen again amidst Musk's feud with Trump, plummeting more than 14 percent on Thursday to wipe out over $150 billion in value."I don’t mind Elon turning against me, but he should have done so months ago," Trump wrote on Thursday.Meanwhile, Musk went all-in attacking Trump on Thursday, claiming that the president is linked to child sex offender Jeffrey Epstein and sharing posts calling for him to be impeached. Musk has also hit out at Trump's tariffs on international trade, predicting that they will "cause a recession in the second half of the year.""Without me, Trump would have lost the election," Musk alleged on X. "Such ingratitude."

Reddit a porté plainte contre Anthropic devant un tribunal de San Francisco, mercredi 4 juin. DADO RUVIC / REUTERS La plateforme Reddit a porté plainte contre Anthropic, start-up californienne d’intelligence artificielle (IA). Reddit accuse l’entreprise d’avoir utilisé sans autorisation des conversations publiques de ses utilisateurs pour entraîner ses modèles d’IA générative – parmi lesquels figure Claude, un modèle de langage et chatbot concurrent de ChatGPT. D’après la plainte, déposée mercredi 4 juin à San Francisco, Reddit reproche à Anthropic d’avoir entraîné ses modèles de langage à partir de messages « humains » postés sur Reddit. L’action en justice se base notamment sur un document de recherche publié en décembre 2021 par les équipes d’Anthropic et cosignés par le chef de l’entreprise, Dario Amodei. Le texte mentionne certaines conversations spécifiques de Reddit pouvant servir à l’entraînement de tels modèles. Celles tenues sur Wikipédia sont aussi mentionnées. La plainte allègue que malgré les déclarations publiques d’Anthropic, qui a assuré avoir bloqué l’accès à Reddit à ses systèmes automatisés de récolte des données, les robots de l’entreprise ont malgré tout continué « à se connecter aux serveurs de Reddit, et ce plus de cent mille fois » depuis juillet 2024, indique le texte. Lire aussi | Le gouvernement retire une vidéo générée par IA sur la Résistance, à la suite d’une erreur historique Anthropic conteste « Nous ne sommes pas d’accord avec les affirmations de Reddit et nous nous défendrons vigoureusement », a réagi un porte-parole d’Anthropic auprès de l’Agence France-Presse. Fondée à San Francisco par d’anciens ingénieurs d’OpenAI, Anthropic promeut de manière ostensible un développement responsable de l’IA générative. « Cette affaire porte sur les deux personnalités d’Anthropic : la personnalité publique qui tente de faire croire aux consommateurs qu’elle est une entreprise juste qui respecte les limites et la loi, et la personnalité privée qui se moque de toutes les règles qui gênent ses tentatives de s’en mettre plein les poches », accuse Reddit dans la plainte. Reddit demande désormais des dommages et intérêts, et une injonction pour obliger Anthropic à respecter les termes de son contrat d’utilisation. Ce dernier interdit depuis 2024, date d’entrée en Bourse de Reddit, l’utilisation de données issues des discussions Reddit sans qu’un accord, ou un contrat, ne soit signé avec la plateforme. Reddit, qui déclarait en octobre 2024 compter sur 97,2 millions d’utilisateurs actifs chaque jour, a déjà conclu des accords de licence avec d’autres géants de l’IA générative, dont Google et OpenAI. Ces accords permettent à ces firmes d’utiliser les contenus de Reddit suivant des conditions qui protègent les informations confidentielles des utilisateurs, et offrent une compensation financière à la plateforme. Lire aussi | Article réservé à nos abonnés Un pionnier de l’IA veut construire des systèmes non nuisibles à l’humanité Le Monde avec AFP

Upcoming (serious) Web performance boostBy: Adam Scott5 June 2025Progress ReportSometimes, just adding a compiler flag can yield significant performance boosts. And that just happened.For about two years now, all major browsers have supported WASM (WebAssembly) SIMD. SIMD stands for “Single instruction, multiple data” and is a technology that permits CPUs to do some parallel computation, often speeding up the whole program. And that’s exactly why we tried it out recently.We got positive results.The need for performance on the WebThe Web platform is often overlooked as a viable target, because of its less-than-ideal environment and its perceived poor performance. And the perception is somewhat right: the Web environment has a lot of security-related quirks to take into account—the user needs to interact with a game frame before the browser allows it to play any sound1. Also, due to bandwidth and compatibility reasons, you rarely see high-fidelity games being played on a browser. Performance is better achieved when running software natively on the operating system.But don’t underestimate the potential of the Web platform. As I explained in broad terms at the talk I gave at the last GodotCon Boston 2025, the Web has caught up a lot since the days of Flash games. Not only are there more people playing Web games every year, but standards and browsers improve every year in functionality and in performance.And that’s why we are interested in using WASM SIMD.WASM SIMD BenchmarksOur resident benchmark expert Hugo Locurcio (better known as Calinou) ran the numbers for us on a stress test I made. We wanted to compare standard builds to builds with WASM SIMD enabled.Note: You may try to replicate his results, but be aware that he has a beast of a machine. Here are his PC’s specifications:CPU: Intel Core i9-13900KGPU: NVIDIA GeForce RTX 4090RAM: 64 GB (2×32 GB DDR5-5800 CL30)SSD: Solidigm P44 Pro 2 TBOS: Linux (Fedora 42)I built a Jolt physics stress test from a scene initially made by passivestar. By spawning more and more barrels into the contraption, we can easily test the performance difference between the WASM SIMD build and the other.Without WASM SIMDWith WASM SIMDImprovement (approx.)Test linksLinkLink-Firefox 138(“+100 barrels” 3 times)2×Firefox 138(“+100 barrels” 6 times)10.17×*Chromium 134(“+100 barrels” 3 times)1.37×Chromium 134(“+100 barrels” 6 times)14.17×**Please note that once the physics engine enters a “spiral of death”, it is common for the framerate to drop to single digits, SIMD or not. These tests don’t prove 10× to 15× CPU computing speed improvements, but rather that games will be more resilient to framerate drops on the same machine in the same circumstances. The 1.5× to 2× numbers are more representative here of the performance gains by WASM SIMD.What it means for your gamesStarting with 4.5 dev 5, you can expect your Web games to run a little bit more smoothly, without having to do anything. Especially when things get chaotic (for your CPU). It isn’t a silver bullet for poorly optimized games, but it will help nonetheless. Also, note that it cannot do anything for GPU rendering bottlenecks.Be aware that the stress tests are meant by nature to only test the worst case scenarios, so you may not see such large improvements in normal circumstances. But it’s nice to see such stark improvements when the worst happens.AvailabilityFrom here on out, the 4.5 release official templates will only support WebAssembly SIMD-compatible browsers in order to keep the template sizes small. We generally aim to maintain compatibility with the oldest devices we can. But in this case, the performance gains are too large to ignore and the chances of users having browsers that are that far out of date is too small relative to the potential benefits.If you need to use non-SIMD templates, don’t fret. You can always build the Godot Editor and the engine templates without WebAssembly SIMD support by using the wasm_simd=no build option.What’s next?As I wrote in my last blog post, we’re currently working very hard to make C#/.NET exports a reality. We do have a promising prototype, we just need to make sure that it’s production-ready.I also mentioned in that article that I wanted to concentrate on improving our asset loading game. Preloading an entire game before even starting it hinders the ability to use Godot for commercial Web games. Once something is implemented to improve that issue, count on me to share the news with you.It’s either that, or we return to the old days of spam-webpages using the “Congratulations, you won!” sound effect when you least expect it. ↩

The murder of John Forde was the culmination to years of political, social, and criminal intrigue.   Get the Popular Science daily newsletter💡 Breakthroughs, discoveries, and DIY tips sent every weekday. Researchers have uncovered handwritten letters, court documents, and a coroner’s report related to the nearly 700-year-old cold case murder of a medieval priest. Published on June 5 in the journal Criminal Law Forum, the investigation draws on direct archival evidence from Cambridge University that is helping fill in the gaps to a high-profile true crime scandal that would make headlines even today. But despite a mountain of firsthand accounts, the murder’s masterminds never saw justice. The ‘planned and cold-blooded’ crime On Friday, May 3, 1337, Anglican priest John Forde began a walk along downtown London’s Cheapside street after vespers (evening prayers) shortly before sunset. At one point, a clergyman familiar to Forde by the name of Hasculph Neville approached him to begin a “pleasant conversation.” As the pair neared St. Paul’s Cathedral, four men ambushed the priest. One of the attackers then proceeded to slit Forde’s throat using a 12-inch dagger as two other assailants stabbed him in the stomach in front of onlookers. The vicious crime wasn’t a brazen robbery or politically motivated attack. It was likely a premeditated murder orchestrated by Ela Fitzpayne, a noblewoman, London crime syndicate leader—and potentially Forde’s lover. “We are looking at a murder commissioned by a leading figure of the English aristocracy. It is planned and cold-blooded, with a family member and close associates carrying it out, all of which suggests a revenge motive,” Cambridge University criminology professor Manuel Eisner explained in a statement. The location of the murder of John Forde on May 3, 1337. Credit: Medieval Murder Maps / University of Cambridge’s Institute of Criminology / Historic Towns Trust. A longstanding feud To understand how such a brutal killing could take place in daylight on a busy London street, it’s necessary to backtrack at least five years. In January 1332, the Archbishop of Canterbury sent a letter to the Bishop of Winchester that included a number of reputation-ruining claims surrounding Fitzpayne. In particular, Archbishop Simon Mepham described sexual relationships involving “knights and others, single and married, and even with clerics in holy orders.” The wide-ranging punishments for such sinful behavior could include a prohibition on wearing gold and other precious jewelry, as well as large tithes to monastic orders and the poor. But the most humiliating atonement often came in the form of a public walk of shame. The act of contrition involved walking barefoot across Salisbury Cathedral—England’s longest nave—in order to deliver a handcarried, four-pound wax candle to the church altar. What’s more, Archbishop Mepham commanded that Fitzpayne must repeat this penance every autumn for seven years. Fitzpayne was having none of it. According to Mepham’s message, the noblewoman chose to continue listening to a “spirit of pride” (and the devil), and refused to abide by the judgment. A second letter sent by the Archbishop that April also alleged that she had since absconded from her husband, Sir Robert Fitzpayne, and was hiding in London’s Rotherhithe district along the Thames River. Due to this, Archbishop Mepham reported that Ela Fitzpayne had been excommunicated from the church. Image of the Archbishop of Canterbury’s letters to the Bishop of Winchester on the subject of Ela Fitzpayne, from the register of John de Stratford. Credit: Hampshire Archives and Hampshire County Council. Raids and rats But who tipped the clergy off to her indiscretions? According to Eisner’s review of original documents as part of the Cambridge University Institute of Criminology’s Medieval Murder Maps project, it was almost certainly her ex-lover, the soon-to-be-murdered John Forde. He was the only alleged lover named in Archbishop Mepham’s letters, and served as a church rector in a village located on the Fitzpayne family’s estate at the time of the suspected affair.  “The archbishop imposed heavy, shameful public penance on Ela, which she seems not to have complied with, but may have sparked a thirst for vengeance,” Eisner said. “Not least as John Forde appears to have escaped punishment by the church.” But Forde’s relationship with the Fitzpaynes seems to have extended even more illicit activities. In another record reviewed by Eisner, both Ela Fitzpayne and John Forde had been indicted by a Royal Commission in 1322. The crime–assisting in the raid of a Benedictine priory alongside Sir Fitzpayne. They and others reportedly assaulted the priory a year earlier, making off with around 18 oxen, 30 pigs, and 200 sheep. The monastery coincidentally served as a French abbey’s outpost amid increasing tensions between France and England in the years leading up to the Hundred Years’ War. Archbishop Mepham was almost certainly displeased after hearing about the indictment of one of his own clergy. A strict administrator himself, Mepham “was keen to enforce moral discipline among the gentry and nobility,” added Eisner. He theorizes that Forde copped to the affair after getting leaned on by superiors, which subsequently led to the campaign to shame Ela Fitzpayne as a means to reassert the Church’s authority over English nobility. Forde, unfortunately, was caught between the two sides. “John Forde may have had split loyalties,” argued Eisner. “One to the Fitzpayne family, who were likely patrons of his church and granted him the position. And the other to the bishops who had authority over him as a clergy member.” Archbishop Mepham ultimately wouldn’t live to see the scandal’s full consequences. Fitzpayne never accepted her walk of shame, and the church elder died a year after sending the incriminating letters. Eisner believes the Fitzpaynes greenlit their hit job on Forde only after the dust had seemingly settled. It doesn’t help their case three bystanders said the man who slit the rector’s throat was none other than Ela Fitzpayne’s own brother, Hugh Lovell. They also named two family servants as Forde’s other assailants. Archbishop Mepham died four years before Forde’s murder. Credit: ampshire Archives and Hampshire County Council Turning a blind eye Anyone waiting for justice in this medieval saga will likely be disappointed. “Despite naming the killers and clear knowledge of the instigator, when it comes to pursuing the perpetrators, the jury turn[ed] a blind eye,” Eisner said. Eisner explained the circumstances surrounding an initial lack of convictions were simply “implausible.” No one supposedly could locate the accused to bring to trial, despite the men belonging to one of England’s highest nobility houses. Meanwhile, the court claimed Hugh Lovell had no belongings available to confiscate. “This was typical of the class-based justice of the day,” said Eisner. In the end, the only charge that ever stuck in the murder case was an indictment against one of the family’s former servants. Five years after the first trial in 1342, Hugh Colne was convicted of being one of the men to stab Forde in the stomach and sentenced to the notorious Newgate Prison. As dark and sordid as the multiyear medieval drama was, it apparently didn’t change much between Ela Fitzpayne and her husband, Sir Robert. She and the baron remained married until his death in 1354—when she subsequently inherited all his property. “Where rule of law is weak, we see killings committed by the highest ranks in society, who will take power into their own hands, whether it’s today or seven centuries ago,” said Eisner. That said, the criminology professor couldn’t help but concede that Ela Fitzpayne was an “extraordinary” individual, regardless of the era. “A woman in 14th century England who raided priories, openly defied the Archbishop of Canterbury, and planned the assassination of a priest,” he said. “Ela Fitzpayne appears to have been many things.”

Project Files: https://www.patreon.com/posts/130827616 . This is the 36th part of the tutorial series, where we are going to implement a Real Time Strategy game using Unreal Engine and C++. Today we are going to work on how to show the health bar of the character when player hover cursor over the characters in the game. We have already implemented a gameplay message that is broadcasted when player hover over a pawn and the HUD is listening to that message using gameplay messaging system. This event will be used to detect what character the player is currently hovering over and that event will be used to show the healthbar. Unreal Engine Gameplay Message Subsystem - How To Use: https://youtu.be/Qnxk6iiy7sU Full C++ RTS Playlist: https://www.youtube.com/playlist?list=PLNTm9yU0zou5_PYxEdjNbAgbVRn-daOga . Unreal Strategy game with Blueprints series: https://www.youtube.com/playlist?list=PLNTm9yU0zou4Eulmi8YIfzHiNZEzfbSMk ► 👇 𝐒𝐮𝐩𝐩𝐨𝐫𝐭 𝐓𝐡𝐞 𝐂𝐡𝐚𝐧𝐧𝐞𝐥 // 𝐁𝐞𝐜𝐨𝐦𝐞 𝐀 𝐏𝐚𝐭𝐫𝐨𝐧! https://www.patreon.com/codelikeme ►Patrons will have access to project files of all the stuff I do in the channel and other extra benefits Join this channel to get access to perks: https://www.youtube.com/channel/UClb6Jh9EBV7a_Nm52Ipll_Q/join Like my facebook page for more content : https://www.facebook.com/gamedevelopersclub/ Follow me on twitter : https://twitter.com/CodeLikeMe2 Follow me on reddit : https://www.reddit.com/user/codelikeme #CodeLikeMe #unrealengine #ue5 #ue4 #indiegamedev

Summer is the best time to start hosting parties, and if you’re planning on doing just that this year, you’re going to want to make sure you have everything you need to throw some ragers. What’s the most important thing you need for a great party in addition to the “vibe”? Oh, nothing. Just some amazing music and a way to share it. Case in point? A party speaker that’s up to the task that won’t force you to spend all of your savings. Sound like a plan Head to Amazon to get the JBL PartyBox for $249, down from its usual price of $349. That’s $100 off and a discount of 29%. See at Amazon Party all night for a great discount The JBL PartyBox is everything you need to get people moving and the party jumping. And it’s powerful enough to fill your space with 100 watts of signature JBL sound. It’s also compact enough to carry over your shoulder. It even comes with a padded strap so you can sling it across your back like a messenger bag. That makes it convenient for beach trips, park hangs, or just moving from room to room too. It also includes a built-in bottle opener, which sounds like a gimmick until you actually need one mid-party and realize how smart that feature is. Because someone’s going to have to bring a drink with a lid that doesn’t twist off, and that’s gonna harsh your vibe. This is more than just a speaker. It’s also a light show in a box, which you’ll soon find out when you start using it in earnest. Whether it’s a quiet night with friends or a full-on celebration, it’s a small touch that makes a big visual impact. And if you’re the karaoke type or know someone who is, you’ll love the wireless microphone that comes included. Tweak the bass, treble, and even echo effects, which makes this speaker double as your own personal DJ booth or karaoke machine. It’s also made to handle real life. With IPX4 splash resistance, it can stand up to light rain, poolside splashes, or accidental drink spills. The 6-hour battery life keeps things going long enough for most parties, and if you’ve got another compatible JBL speaker, you can pair them together for an even bigger sound experience. All this for under $300? You’ll want to get yours as soon as possible before the heat wave and the summer parties begin. See at Amazon