Perhaps these folks should work together to make patches to the dataset to remove the problematic images?
E: But also make sure every image in the dataset is properly licensed. This would have eliminated this entirely from the get go. Playing fast and loose with the distribution rights to these images led to this problem.
700 CSAM images, even one is damning, but hundreds are often referred to as a cache or horde, normally anyone caught with that can wave bye-bye to thier life.
google should be fully accountable for possesion and distribution, perhaps even manufacturing.
Please, feel free to extrapolate for me whether the "unspecified vulnerability" referenced in the article was introduced more or less than five years ago.
The point was the whole phone has been vulnerable to a multitude of RCEs for five years, so it doesn't really matter if its the latest exploit, its a silly request.
Thank you! Here in my place, we organize a lot of firework shows for celebrations. Hence my brother-in-law - which is a passionate but not a prefessional - told me, why don't you make a software like that? So I took the challenge!
Would you like to contribute? I am actually looking for someone who wants to help me integrate maps from OpenStreetMap into FireShow.
Wish I could, but I never learned c++! Maybe now could be the time lol Maps are a great idea, and even better if you can incorporate terrain height and obstructions.
With a map you could also plot out the safety perimeter. Every jurisdiction is different, for example in my state if I recall it was something like 100' feet per inch of shell size, and the fire mashals would use a wheel to confirm it.
A random other thought might be to offer the user estimates for number and length of squib and control cables for the various rack runs