Home privacy is a popular topic these days, as Flock surveillance cameras appear in our neighborhoods and AI voice assistants hang on our every word. But we also have more tools than ever to protect our privacy — as long as we use them.

Don’t worry, your smart technology is still (mostly) safe, but if you are worried about third parties spying on you or loved ones, you should definitely learn these practices, settings and tricks to better protect yourself. Here are the habits that make the most difference, including those I use around my house.

Read more: The Top Home Security Myths You Need to Stop Believing

1. Keep the shutters on your security cams and smart displays closed

When smart displays first started appearing, they came with cameras to enable video chats and similar features. When those cameras started making people nervous, makers began putting physical shutters and off buttons on their smart devices so people could quickly shut them down and confirm the cameras couldn’t be used remotely.

In my experience, these cams rarely get much use and are best left turned off permanently until you’re ready to make a video call to a family member. The same is true of the mics in some smart speakers, which you can shut off when not in use if you’re worried about the speaker listening in. For the record, while you can find a lot of internet rumors about eavesdropping speakers, today’s models require the wake word to start listening in, and accidents are typically confined to picking up similar-sounding words in conversations, music or TVs.

The same is true of security cameras. Look for cams that have shutters or “off” positions (like facing down) if you’re concerned about privacy.

2. Switch off opt-in and data-sharing features

I spoke with Laurie Selkowitz, partner in Greenberg Glusker’s Cybersecurity and Privacy Group, about increasing home privacy with smart devices to find some good advice. 

“The biggest mistake people make is treating smart home devices like appliances instead of connected computers. Once you think of them as computers that happen to live in your home, the privacy decisions become much more obvious,” Selkowitz said. 

“A good rule of thumb is to enable only the features you actually use,” she said. “Many devices collect far more data than they need to function, so turning off things like unnecessary cloud storage, voice history or activity logs can significantly reduce your exposure.”

You can often change how companies manage and share your home data, but the methods are typically buried deep in settings, so you need to know where to look. I can help with that.

Here’s my guide on Alexa settings you may want to adjust, including options that control how long Amazon saves your voice recordings and other privacy features to help make voice assistant use better.

I also have a complete guide on Ring security features you may want to turn off, including all AI features if those recognition capabilities worry you, automatic data sharing in your neighborhood for tools like Search Party and disabling Amazon Sidewalk so it won’t share your bandwidth with strangers.

3. Use local storage instead of cloud storage

If you use security cameras, you have two choices for saving video (and you really need to save video; otherwise, the camera isn’t much more than live views).

The first option most cameras offer these days is cloud storage. But many people don’t like the idea of trusting companies to manage their video data, and those cloud databases have been hacked or accidentally shared in the past.

The second option, local storage, is much better for your privacy. Local storage uses either a microSD card or a hub with a built-in drive to store video. You may have to clear out videos occasionally, but it keeps your data in your own hands. Lots of brands offer local storage if you choose the right setup, including Eufy, Lorex, Blink and Wyze.

Just remember, even if videos are stored locally, police can still confiscate them with a warrant.

Best Home Security Cameras Without Subscriptions in 2026

Advertisement

4. Close your shades on a schedule

People probably aren’t peering through your windows at night, but that doesn’t mean you should make it easy. Today’s smart shades can automatically close on a schedule or when the sun goes down, even if you aren’t home yet. That helps guarantee extra privacy and may even deter burglars scouting for a target.

5. Check old Zillow and real estate listings

If you recently moved into a new home within the past year or two, I suggest checking the old selling or rental listing pages for your address. In some cases, these get left up for years after the home has already changed hands.

Those old listings could be an unwelcome window into exactly where your address is, what your home looks like on the inside and even access points a burglar might want to know. Also, people may get the wrong idea and assume it’s still available to rent or buy — I’ve had more than a few people peer through my windows for just that reason.

It’s better for your privacy if you run a quick check on platforms like Zillow, Trulia and local real estate sites to see if your home is still there. Then you can request it be removed.

6. Blur your address on Google Maps

There’s another place your home shows up to anyone willing to look — Google Maps, especially when using satellite and street view images.

Well aware of this fact, Google offers an option on its website (not its app) to blur out your address for privacy. We have a complete guide on how to do that here, but it’s free and takes only a couple of minutes. Apple offers a similar service in its Look Around map app function.

7. Switch to open-source or third-party smart home controls

If you’re worried about big brand names having easy access to your data, you can still get a full set of smart home features by using alternative platforms. You have several choices, notably the open-source, build-it-yourself Home Assistant and the third-party, privacy-first Homey hub and platform.

The catch is that these platforms will take much more work to set up and customize, and they tend to be buggier and require more problem-solving than you’ll find on any brand app. But if you don’t mind tinkering, these are great ways to mandate privacy while getting the high-tech smart features you want.

8. Adopt a home VPN

We talk a lot about using VPNs (virtual private networks) on our browsers, phones and laptops for greater privacy and reduced risk of third-party data collection, but many of the benefits apply at home, too. It’s even easier to use a VPN at home because many home Wi-Fi routers come with VPNs you can use, or you can add a VPN to them for whole-house protection, which in our tests only takes about 10 minutes.

With a VPN, every device connected to your router, including your smart home devices, typically has its data encrypted when it sends data online, making it harder for companies to glean information about your activity and home habits.

Is it still safe to use foreign-made routers at home?

In 2026, the FCC banned foreign-made Wi-Fi routers for national security reasons — sort of. The reasons are complicated, and exemptions were quickly provided for top router brands like Netgear, so I don’t blame you if you don’t know what to think about router privacy. We spoke to several security experts, and unless you have to buy a new router right away, there’s not much to worry about. No sudden security threat has made routers any less safe to use than they were before, but as always, strong security practices will help keep you safe.

If you’re interested in off-the-grid options, check out my off-the-grid home security guide.

Tyler Lacoma

Editor / Home Security and Smart Home

Tyler has worked on, lived with and tested all types of smart home and security technology for over a dozen years, explaining the latest features, privacy tricks, and top recommendations.

With degrees in Business Management, Literature and Technical Writing, Tyler takes every opportunity to play with the latest AI technology, push smart devices to their limits and occasionally throw cameras off his roof, all to find the best devices to trust in your life. He always checks with the renters (and pets) in his life to see what smart products can work for everyone, in every living situation.

Living in beautiful Bend, Oregon gives Tyler plenty of opportunities to test the latest tech in every kind of weather and temperature. But when not at work, he can be found hiking the trails, trying out a new food recipe for his loved ones, keeping up on his favorite reading, or gaming with good friends.

See full bio

Advertisement

Framework, a company that makes modular repairable computers, said it has notified all of its customers that hackers stole their names, email addresses, phone numbers, and physical addresses, due to an incident at a company that provides business intelligence.

On Thursday, several Framework customers said on social media that they had received an email from the company notifying them of the data breach.

Framework’s spokesperson Eric Schumacher told TechCrunch that the breach affected “all customers,” but declined to specify a specific number. Framework computers are relatively niche products, but some estimates say the company sold hundreds of thousands of devices. 

According to the notification seen by TechCrunch, the company blamed the data breach on an upstream cyberattack at Metabase.

Metabase disclosed its own breach in a blog post on its official website, where it said that it was hacked by someone using an unknown security flaw, a so-called zero-day. The company said the hackers exploited the bug to give them the ability to access customers’ databases stored on Metabase’s cloud servers.

In its email to customers, Framework also included the email Metabase sent to the company, which says hackers accessed Framework’s cloud instance. The computer maker said it investigated the incident and found that hackers had stolen its customers’ personal data, but did not include their payment information.

Metabase did not respond to a request for comment.

Zack Nelson has a habit of taking brand-new phones and treating them the way most people accidentally treat their everyday carry. This time the victim is Samsung’s Galaxy Z Fold8, the shorter, wider passport-style foldable that opens into a nearly square tablet. He runs the usual sequence of scratches, grit, open flame, and the dreaded opposite-direction bend. What emerges is another quietly tough Samsung folder that refuses to fold the wrong way for good.

The outer glass on this phone is Gorilla Glass Ceramic 3, and scratches begin to appear at a Mohs hardness level of 6, as they do on most current flagship phones. Its inner flexible display, which is still coated with a layer of plastic that cannot be avoided, scratches at a super-low level 2, the same rating that foldables have had for years. You’ll notice lines left by coins, keys, and even the edge of a fingernail. The good news is that Samsung will continue to replace the inside screen protector for free once each year. After that, it’s $19.99, and underneath the pixels is a titanium substrate that is meant to help straighten out the crease, but to be honest, it doesn’t help the plastic surface on top, which is always scratched.

Samsung Galaxy Z Fold8 Unlocked Cell Phone + $350 Gift Card, 256GB, Cream

• SHOP NOW: Get an Amazon gift card when you order Samsung Galaxy Z Fold8. You will receive an email once your gift card is available after the product…
• CREATED FOR YOUR CONTENT: Any way you turn it, the new Galaxy Z Fold8 gives you a fuller viewing experience. Designed with your content in mind, this…
• WORLD’S LIGHTEST FOLD¹: Galaxy Z Fold8 is the newest foldable phone for content on the go. Unfolded, it fits movies and books for an immersive…

This phone has Advanced Armor aluminum framing, but the back is still glass. Now, the area around the dual 50 megapixel cameras is new, as it is constructed of plastic, which is unusual for a Samsung foldable device. If you ever need to change the lenses, you can easily take off the metal ring around them. There’s even a gasket in the SIM tray, which is nice to see given the IP48 rating. When you pour some dust on it and open and close it a few times, the majority of it stays out of the way, albeit some collects on the corner magnets, and the hinge continues to function normally.

The inside 7.6-inch display was irreparably damaged when he placed an open flame to it with a lighter, which occurred after around seven seconds. The 5.5-inch cover lasted around ten seconds before becoming dark and green, indicating that it was nearly done, although keep in mind that the titanium layer on the screen provides no effective heat protection.

When the phone is closed, it has almost no flex, and sitting on it in your pocket while folded is probably fine, but when you open it up and apply some serious pressure, the entire thing begins to bend. The glass back even lifts out of its frame, but nothing splits along the antenna lines, the screen remains intact, and the hinge holds together. Let go, and the back glass sort of reseats itself; the phone still folds shut and powers on normally. This is the first time a Samsung book-style foldable has passed this test, with the exception of the trifold, which was a one-off, and the bigger Fold 8.

Tom Stanton has spent years chasing a number that gravity itself seemed to forbid. On a quiet field somewhere in the UK, a 40-kilogram mass dropped a short distance, spun a carbon-fiber arm past 2,300 revolutions per minute, and sent a 4-gram projectile into the air at 776 miles per hour. That is nine miles per hour past the speed of sound. For the first time, a purely gravity-powered trebuchet crossed the barrier.

Medieval engineers created these machines to fling huge stones at castle walls. The basic idea is to hoist a large heavy weight, let it fall down, and then use the lever and sling to redirect that energy into a much lighter projectile. Unfortunately, physics gets in the way. A weight in free fall accelerates at a maximum of 9.81 meters per second squared; drop one from 2 meters and it smacks into the ground at around 6 meters per second. No matter how heavy you make the weight, the speed remains constant, and a typical arm is like a car with a bike chain stuck in first gear, with lots of torque at first but just enough to get it moving by the end.

Stanton devised a creative engineering solution to the speed problem. The counterweight is suspended from a pulley system with a 3:1 ratio, as a large diameter at the beginning propels the arm with plenty of force, and as it winds down, the smaller diameter end provides a significant jump in rotational speed. In the end, the drum was redesigned so that weight could be lifted up to 1.9 meters, storing more power in the system than previous iterations.

The arm has to be both incredibly light and super rigid. Carbon fiber was really the only option because it isn’t heavy enough to weigh down the entire system while yet being able to withstand punishment. Stanton used his homemade CNC mill to carve the piece, keeping the dust under control with a HEPA vacuum and a good spray of water. It weighs only 116 grams. Stress tests and numerous defective 3D printed prototypes revealed that it would buckle under the sling’s pressure, so he modified the design to compensate, removed material from the tensioned side, toughened up the opposite side, and added some extra bracing for good measure. Aluminum hubs connect the arm to a short counter-arm, keeping the spinning bit as balanced as possible.

The projectile now starts near the axle, wrapped firmly in a sling that unwraps at just the right moment. The entire system is mechanically released, using a spring-loaded catch that opens after a certain number of rope rotations. The release window is only a few milliseconds long, which is plenty of time to complete the task. Early iterations failed under stress, but the final pin-and-loop structure held up.

Testing was carefully increased, and he began with a 10 kg weight. The modified aerodynamic arm reached a respectable 1248 rpm and launched at 394 mph with an incredible 43.7% efficiency. Twenty and thirty kilograms passed thru without a hitch. 40 kg, on the other hand, sped the arm to 2336 rpm and the missile to a blistering 716 mph, falling only 51 mph short of the magic barrier. The machine eventually snapped, and the clasp shattered beneath the weight of 50 kg. Stanton reduced the projectile weight to approximately 4 grams, changed the drum taper once more, and returned to the test area with the 40 kilogram setup.

The final test is obviously the most important, since the arm spun up to 2342 rpm. Tip speed reached a staggering 274 mph. The high-speed footage was truly eye-opening, as the missile traveled 1.94 meters in 5.6 milliseconds. Crunching those statistics yields 346.4 meters per second, or a more than respectable 776 mph. To top it all off, there was a loud crack followed by a pleasant echo, confirming the sonic boom to everyone within earshot. Not one aspect of the machine came close to failing, or so we’d like to think.

I’ve been a fan of Zoner Studio since first reviewing it in 2025 – it’s a fusion of Lightroom and Photoshop-style tools for photographers, with some compelling advantages over both.

My team recently re-reviewed the photo editing and organizing software, complete with its big summer updates roll-out, where it earned an even higher score for 2026 (read our Zoner Studio review).

The 2026 MotoGP season returns from its summer break as a fascinating riders’ championship battle resumes at Silverstone, the home of UK motorsport, for the British Grand Prix 2026.

Just 24 points separates the top five riders in the standings, with 2024 champion Jorge Martin (Aprilia Racing) leading SuperFile Trackhouse’s Ai Ogura by 14. However, the duo will be nervously looking over their shoulders after seven-time world champion Marc Marquez (Ducati Lenovo) roared back into contention with three wins in the past four grands prix having recovered from a fractured foot. He is only 18 points off the summit, while Martin’s Aprilia teammate Marco Bezzecchi is a further four adrift with Fabio Di Giannantonio of Pertamina Enduro VR46 Racing in fifth following a consistent first half of the season.

RPCS3 is a multi-platform open-source Sony PlayStation 3 emulator and debugger written in C++ for Windows, Linux, macOS and FreeBSD. The purpose of the project is to completely and accurately emulate the Sony PlayStation 3 Computer Entertainment System in its entirety with the power of open-source community and reverse engineering.

Our goal is to preserve the legacy of the PlayStation 3 hardware and its vast library by bringing it and its exclusives to the PC platform. We want to achieve this by targeting and supporting multiple operating systems as well as being compatible with a wide range of computer hardware with realistic requirements.

What input devices can I use with RPCS3?

We currently support keyboard / mouse inputs and native DualShock 3, DualShock 4 and DualSense controllers. We plan to add additional input methods in the future as we implement more meaningful features to the emulator.

What PlayStation 3 peripherals can I use with RPCS3?

We currently have support for the PlayStation Eye Camera, however PlayStation 3 Move controller support is still under development.

Can I just insert a PlayStation 3 game disc and start playing games?

In its current state, RPCS3 does not support reading game data directly from PlayStation 3 format discs. PlayStation 3 discs are formatted in a very special way that can only be read with an actual PlayStation 3 system, or a compatible Blu-ray drive from select manufacturers. For more information on what Blu-ray drives are capable of reading games, please refer to the Quickstart Guide.

Where do I get PlayStation 3 games and software?

Typically, you want to dump your own PlayStation 3 games and software from your own console. We believe that this is the most efficient and safest way to migrate your disc-based games and digital games from your console to your PC.

You can also dump games using select compatible Blu-ray drives. Not every Blu-ray drive will recognize PlayStation 3 games due to how data is formatted on the disc. For more information on what Blu-ray drives are capable of reading games, please refer to the Quickstart Guide.

RPCS3 uses the GNU General Public License Version 2 (June 1991). According to the license, you are welcome to use RPCS3 and its source code for any purpose, but distributing RPCS3 requires that the source code be released and attribution given. For more details on how the GNU General Public License system works, please refer to GNU.org

High Resolution Rendering

One of the most anticipated features has just been added to RPCS3! High resolution rendering allows users to play at resolutions far exceeding what the PS3 could handle. If you thought your favourite PS3 games were starting to look a bit dated, just wait until you get to experience them in up to 10k! Although, we doubt many users will have the setup necessary to benefit from 10k today, emulation is all about preserving for tomorrow.

Performance

Rendering a modern PC game in high resolutions such as 4k, while beautiful, is quite taxing on your hardware and there is often a massive hit in performance. However, since most of the workload for RPCS3 is on the CPU and GPU usage is low, there is a lot of untapped performance just waiting to be used. All processing is done CPU side, and as far as the GPU is concerned it is simply rendering 2006 era graphics (yes, the PS3 is 11 years old now). We’re happy to report that anyone with a dedicated graphics card that has Vulkan support can expect identical performance at 4k.

Anisotropic Filtering (AF)

High resolution support wasn’t the only thing that was added in this update! Another reason for such a massive upgrade in visual fidelity is having full 16x AF support. This greatly improves how textures can look, especially when viewed at an angle. Take a look at the below screenshots of Ni no Kuni as an example of the default AF vs forced 16x. The difference is especially noticeable on the ground inside the gate.

RPCS3 Compatibility List

These are the current compatible games that have been tested with the emulator. This list is subject to change frequently.

What’s New

• Remove duplicated code in VKShaderInterpreter.cpp by @digant73 in #18832
• Add “Enable Mouse-based Gyro” setting to I/O config by @Windsurf7 in #18835
• SPU LLVM: Use 128-bit SVE2 for FMS by @Whatcookie in #18837
• SPU LLVM: Idiomatic FSM implementation for ARM64 by @Whatcookie in #18806
• SPU LLVM: SVE multiply optimizations (ARM) by @Whatcookie in #18789
• vk: Autogrow descriptor pools based on demand by @kd-11 in #18844
• Initialize rtmidi async by @Megamouse in #18843
• Make FFB direction encoding for emulated G27 configurable by @ZerNico in #18776
• usb_device: present wii instruments as PS3 instruments by @sanjay900 in #18796
• SPU LLVM: Use I8MM for GBH and GBB by @Whatcookie in #18833
• Update Submodules by @Megamouse in #18840
• HOTFIX: JIT/AArch64: advertise +i8mm to the LLVM target machine by @Rad0van in #18846
• SPU LLVM: Use TBL for AArch64 ROTQBY shuffles by @Whatcookie in #18818
• cellAudio: fix _mxr000 surmixer event-queue key constant by @Rad0van in #18850
• RSX: Add hardware spin_wait helper, use it in flush requests by @Whatcookie in #18830
• rsx: Handle mipmap sampling edge case when SNORM emulation is active by @kd-11 in #18860
• cellAudio: Fix _mxr000 event queue hack by @elad335 in #18857
• SPU/PPU: Implement PPU reservation priority over SPUs by @elad335 in #18854
• rsx: Use mip0 resolution scale when computing mipmap scaling factors by @kd-11 in #18866
• Qt: Add exit game shortcut by @Megamouse in #18869
• SaveStates: Fix lv2_timer serialization by @elad335 in #18878
• ffmpeg: remove directshow backend by @Megamouse in #18879
• Fix drag & drop of files on main window by @digant73 in #18885
• gui: Move download database actions from game list to Manage -> Database submenu by @Vishrut2403 in #18870
• rsxaudio: fix some VS warnings by @Megamouse in #18886
• gui: Play preview videos on row selection, not just hover by @thephilcoulson in #18721
• Use more std::move by @Megamouse in #18868
• Add integrity check to PSN Content, DLC and Game Update files by @digant73 in #18669
• Fix visual studio projects by @Megamouse in #18889
• Do not throw on hex_to_bytes error in iso get_key by @Megamouse in #18891
• Optimise PNGs across the repo by @Chubercik in #18831
• Use more std::string_view (Part 1) by @Megamouse in #18890
• gl: Maintenance fixes by @kd-11 in #18874
• Use opengl renderer in game window title by @Megamouse in #18895
• Use more fmt::split_sv by @Megamouse in #18898
• Stop playing gamelist movies when the window loses focus by @Megamouse in #18899
• Use more std::string_view (Part 2) by @Megamouse in #18901
• [SPU] Optimize CLZ on targets without AVX512 by @WalterKruger in #18900
• sys_rsx: Fix IOMAP syscalls argument types by @elad335 in #18909
• Fix std::string_view regressions by @Megamouse in #18908
• Qt: use readable strings for window visibility in gui settings by @Megamouse in #18907
• [macOS] Update runners to OS 15, raise minimum deployment target accordingly by @schm1dtmac in #18897
• Add user agent to curl requests by @Megamouse in #18912
• [SPU] Calculate FRSQEST exponent using arithmetic by @WalterKruger in #18905
• Add missing sanity check in savedata_op by @Megamouse in #18918
• Update pugixml to 1.16 by @Megamouse in #18904
• fix double path delimiter by @digant73 in #18923
• Use more std::string_view (Part 3) by @Megamouse in #18903
• [SPU LLVM] Calculate FREST fraction using vperm2d for AVX512 by @WalterKruger in #18931
• SPU Analyzer: Giga Block Crash Fix for Skylanders Giants by @chotchki in #18935
• SPU LLVM: Use SVE2 XAR for constant rotates by @Whatcookie in #18849
• [SPU LLVM] Refactor SHUFB to improve readability by @WalterKruger in #18937
• Update wolfssl to 5.9.2 by @Megamouse in #18946
• Update 7zip to 26.02 by @Megamouse in #18947
• [SPU LLVM] Additional SHUFB splat/special-index fast paths by @WalterKruger in #18945
• emulated turntable: allow to map motion sensors by @Megamouse in #18958
• Add more motion control mappings to turntable and ghltar by @Megamouse in #18961
• Fix consteval read_from_ptr and add sanity checks if possible by @Megamouse in #18963
• Propagate src_loc in write_to_ptr and read_from_ptr by @Megamouse in #18967
• SPU Precompilation: Add support for unaligned segments by @elad335 in #18968
• Fix TTY UTF-8 logging by @Megamouse in #18969
• settings: Default async with shader interpreter with no shader compilation hint by @AniLeo in #18956
• Fix cellKb when using key modifiers on linux by @Megamouse in #18938
• macOS: DJ Hero Turntable support (deck buttons, passthrough conflict) by @silvatyrant in #18957
• Fix out of bounds read in Dimensions by @Megamouse in #18972
• cellSysmodule implementation by @capriots in #18962
• [SPU ASMJIT] Vectorized 16-bit variable shifts for SSE2 targets by @WalterKruger in #18911
• SPU LLVM: Use ARM USHL for masked infinite shifts by @Whatcookie in #18816
• PPU LLVM: Fix core_lock locking by @elad335 in #18774
• SPU: Comparisons via multiplications for ARM, checksums via absolute difference, and rolled loops by @Whatcookie in #18824
• Fallback unsupported database SPU decoder on ARM64 by @cicerohellmann in #18651
• sysinfo.cpp: Relax TSC calibration constraints by @elad335 in #17909
• cellSysmodule: fixup by @capriots in #18977
• Fix VSH on ARM64: Memory management fixes by @elad335 in #18707
• cellSysmodule: fixup (part 2) by @capriots in #18978
• Move unsafe raw pointer write_to_ptr and read_from_ptr to write_to_ptr_unsafe and read_from_ptr_unsafe by @Megamouse in #18975
• Update Submodules by @Megamouse in #18980
• Extra logging for GUI notifications by @RipleyTom in #18988
• input: fix arrow key mapping roundtrip on macOS ARM by @Icnopandaz in #18920
• Bump global savestate version by @capriots in #18989
• VK: fix video_out_calibration_pass::get_fragment_inputs by @Megamouse in #18952
• Add OpenCV 5 Support by @hcorion in #18998
• Update fusion to 1.3.0 by @Megamouse in #19008
• Update curl to 8.21.0 by @Megamouse in #18943
• Fix PS1 classics shortcuts by @Megamouse in #19012
• [SPU LLVM] Refactor SELB to improve readability by @WalterKruger in #19002
• [SPU ASMJIT] Optimize xfloat compares and multiply by @WalterKruger in #19025
• IDM: Optimize search for concurrency by @elad335 in #19027
• sys_fs: Fix ENOTDIR check for paths ending with /dot or /dotdot by @elad335 in #19028
• Update fusion to 1.3.1 by @Megamouse in #19030
• PPU LLVM: Optimize vector NaN handling for AVX512 by @Yahfz in #19033
• PPU LLVM: Optimize vector denormal handling for AVX512 by @Yahfz in #19034
• [SPU LLVM] Replace constant float checks with LLVM’s KnownFPClass analysis by @WalterKruger in #19043
• PPU LLVM: Accelerates NJ handling in FTZ environment by @elad335 in #19040
• metainfo: Update screenshot preview by @AniLeo in #19044
• qt: Fix save manager crash when deleting multiple entries by @ProtoJay4789 in #19019
• Revert SPU Reduced Loop Optimizations to fix Arm64 regressions by @elad335 in #18979
• SPU: Revert LQX/STQX reduction by @elad335 in #19050
• [SPU LLVM] Use select in FMA to shorten its dependency chain by @WalterKruger in #19052
• pad settings: Fix for clearing bindings by @Megamouse in #19054
• Add more info to VFS exceptions by @Megamouse in #19055
• [macOS] Update to the latest MoltenVK 1.4.2 prebuilt by @schm1dtmac in #19059
• atomic: Fix BSD compilation by @AniLeo in #19061
• LLVM: Improve v128 constant extraction by @elad335 in #19064
• Fix: get_known_bits fix by @RipleyTom in #19051
• cli: allow to boot last savestate of a game by @Megamouse in #19067
• Qt: add guest memory dump utility by @canersaka in #19068
• Qt: move guest memory dump code to own class by @Megamouse in #19070
• rsx: Clean up the shader interpreters by @kd-11 in #19084
• Update llvm to 22.1.8 by @Megamouse in #16807
• rsxfp/interpreter – Implement missing texture functionality by @kd-11 in #19090
• Fix package install failure warning message by @Megamouse in #19096
• Fix recording encoder selection by @Megamouse in #19063
• Fix DLC installation by @Megamouse in #19097
• SPU/ARM64: Fix PS1 classics and RawSPU Games by @elad335 in #19088
• vk: remove unused setting by @Megamouse in #19099
• Replace some abort() calls with fmt::throw_exception by @Megamouse in #19094
• Remove outdated LLVM ifdefs by @Megamouse in #19092
• Fix value assignment in iota16 by @isztldav in #19105
• Fix 1st regression on black textures in Sonic Generations by @digant73 in #19091
• Add game invite handling to friends overlay #18417 by @primetime43 in #19108
• UI/UX: Add Categories Broken and Completed to Filter Game List by @Darkhost1999 in #19106
• add missing vids and pids for wii MPA devices by @sanjay900 in #19111
• Allow to skip empty strings in fmt::merge by @Megamouse in #19110
• rsx: Implement proper fix for incomplete image reconstruction in the texture cache when WCB is disabled by @kd-11 in #19104
• rsx: Fix interpreter error spam due to incorrect format lookup by @kd-11 in #19113
• ci/bsd: Update FreeBSD to 14.4, use LLVM 22 while keeping clang-devel by @AniLeo in #19116
• rsx: fix some msvc warnings by @Megamouse in #19115
• [SPU LLVM] Shorten FI’s dependency chain and fix SNaN clamping issue by @WalterKruger in #19107
• ci/bsd: Compile with clang 22 by @AniLeo in #19119
• overlay: Add trophy list sorting options by @Vishrut2403 in #18965
• rpcs3_version: Bump to 0.0.42 by @AniLeo in #19121