Meta (the parent company of Facebook, Instagram & WhatsApp) has been pushed to take a breather on their plans to analyse and train their upcoming AI features with users’ data shared on their platforms.

The move follows pushback from the Irish Data Protection Commission (DPC), Meta’s lead regulator in the EU, which is acting on behalf of several data protection authorities across the bloc. The U.K.’s Information Commissioner’s Office (ICO) also requested that Meta pause its plans until it could satisfy concerns it had raised. “The DPC welcomes the decision by Meta to pause its plans to train its large language model using public content shared by adults on Facebook and Instagram across the EU/EEA,” the DPC said in a statement Friday. “This decision followed intensive engagement between the DPC and Meta. The DPC, in cooperation with its fellow EU data protection authorities, will continue to engage with Meta on this issue.”

While Meta is already tapping user-generated content to train its AI in markets such as the U.S., Europe’s stringent GDPR regulations has created obstacles for Meta — and other companies — looking to improve their AI systems, including large language models with user-generated training material. However, Meta last month began notifying users of an upcoming change to its privacy policy, one that it said will give it the right to use public content on Facebook and Instagram to train its AI, including content from comments, interactions with companies, status updates, photos and their associated captions. The company argued that it needed to do this to reflect “the diverse languages, geography and cultural references of the people in Europe.”

Originally written by TechCrunch

A couple of weeks ago I found instructions on how to deny Meta to use your data and opt out of them using your shared content to train their AI. You had to fill out a form, with your details and give a brief note on why you don’t want to be a part of the process.

At the time, it seemed a bit ineffective, and I doubted that it would actually stop them, but it also seemed official enough, y’know? My thought was “yeah I’m covered I signed a contract saying they couldn’t do that”, but then contract was probably full of small print. I submitted it anyway.

I am not surprised that their plans to do this were going to cause outrage across the user-base. In a time where AI-gen is providing readers and users across the world with content, without anyone knowing how or where its been trained and getting its data from, Meta was always going to be the company that gets the most backlash.

Adobe had a similar issue the same week which they have since rectified in an overhauled Terms of Service.

My job takes me all over our beautiful city of Limassol.

Capturing properties like houses, apartments, offices and plots of land. It has become as often as every few days that I am out in my little red car scouring neighbourhoods for cheeky parking armed with my tripod, full-frame camera and occasionally the drone, too.

During each shoot, I might get back to the office and unload up to around 50 full-res, RAW photo files from the camera, and a handful more from the drone, also in RAW.

These files weigh in average at around 50mb each, meaning my trusty Macbook’s internal storage has to brace itself until I next get around to pruning out rejected photos – so, never – I try to avoid deleting photos if I can help it.

So up until just recently, this was my workflow. I had my 2023 photo library on my desktop PC, and the 2024 library on the MacBook I was given around the end of last year. Needless to say, I switched almost immediately to photo correction on the MacBook, meaning – yep, my libraries became split across two drives.

It was quite a simple workaround, actually. I basically re-imported all the photos from the desktop onto the MacBook. I think I lost metadata on all these photos this way, but I didn’t mind as they were outdated photos and had super simple edits on them anyway.

Everything totalled up to around 86gb of photos, with tons of metadata and Lightroom Classic edits. I’ve since decided to move everything onto a new 2TB external SSD, to lighten up the Macbook’s drive. So, now the fun begins!

Because of the way that Lightroom Classic works with catalogs and file references, moving photo files around involves quite the head scratch, and needs to be done carefully.

And that’s exactly what Todd Dominay helped me tackle with his article on how to safely move a Lightroom Classic catalog to a different drive. Thanks!

Sometimes your campaign just needs a refresh of ad creative, especially when running under a well-performing ad set.

Read MoreSwapping out Ads on well-performing Ad Sets