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
I spent a couple years doing pyro shows, and found it interesting how the various show leads would plan the timings; proper cadence and shell size choice can really help make a show interesting before the finale
Basically setup and load the tubes with shells; lots of attention is given to safety buffers, and things like orienting the racks so they can't fall facing the audience.
Some states require electronic firing, so everything gets a squib tied into the fuse, other places you can hand-fire with a road flare, which is more reliable, but dangerous. Anything that doesn't launch needs to be re-squibbed or extracted.
Its also wicked exciting, and fireworks from directly below look entirely different. My first show hand firing 6" shells, I distinctly recall knee jerk yelling "what the fuck" over and over, grinning ear to ear; you can really feel the pressure wave from the launch. It also paid $10/hr
There is also an amateur fireworks association as a fyi; people still hand build shells :)
Edit: as for timing, they'd have patterns like, x3 3-inch shells, x2 6-inch, and 1 8-inch; color and pattern were intentional choices. For hand fire, they'd yell out the shell size to fire, one person per size
Someone I know in that industry described the San Diego event as being the result of playback scrubbing; by either dragging or accidentally clicking somewhere on the timeline. Obviously heard second hand, but its a close community so I generally trust it - Wikipedia says it was a corrupted file
They describe here [1] that somehow two sets of instructions were generated, but that doesn't really make sense why that would cause zero delays between cues
I found playing with AVR microcontrollers to be a nice intro to assembly, and it can be quite rewarding to get some physical response from your code, like a display or turning a servo. I did already have some electronics experience going in though
reply