ElliotM

I suspect that customer service bot is incorrect. As also noted on this page[0], all dark pool trades are published to the consolidated tape, which appears to be part of the polygon API.

As an aside, the behavior you’re seeing might actually be causal- a large print appearing on the tape likely causes automated systems to widen out their quotes. Or alternatively, if the trade is through the NBBO, you’re seeing the top of the book (the protected quote) being swept in compliance with RegNMS.

[0] https://www.finra.org/investors/insights/can-you-swim-dark-p...

> Unfortunately the SEC only requires them to report transactions within 15 minutes, not in real time.

TRF reports must happen within 10 seconds or be submitted with a late modifier [0]. An executing broker systematically submitting all reports 15 minutes late would be investigated pretty quickly.

You can buy access to the consolidated tape from a marketdata provider, although this is going to be pretty prohibitively expensive for an individual.

[0] https://www.finra.org/rules-guidance/rulebooks/finra-rules/6...

These numbers don't remotely pass a smell test. The same study claims 2% of Americans have been injured in a mass shooting, and cites 500 mass shootings a year.

2% of 340mm = 6.8mm injured in a mass shooting Conservatively assuming that's equally spread across all ages, and assuming a lifetime of 80 years, implies 6.8mm/80 = 85,000 people injured a year 85,000/500 mass shootings a year = 170 people injured per shooting

This is absurdly high - the Pulse nightclub shooting for instance injured 60 people.

It's obviously harder to analyze the number of people that 'witness' a shooting, but it also seems implausible that an average of ~595 people are witnessing each of these 500 shootings.

The problem here is that self-reported studies like this are incredibly unreliable. Interestingly, the same effect appeared in a pro-gun study, which cited an insane 2+ million defensive gun uses a year.

Try disabling everything labeled “suggestion” in settings. This drove me crazy too and pretty much went away after I disabled Siri and safari suggestions.

FWIW The data for Milwaukee appears incorrect - the traffic fatalities are for the county of Milwaukee while the density is for the city. Recalculating density based on the land area of Milwaukee county shows 3,934 people per square mile.

https://en.wikipedia.org/wiki/Milwaukee_County,_Wisconsin

Neat project but I'd be careful showing the Twitter (and Github I suppose) logo with the various colors. This is prohibited by their logo guidelines - https://about.twitter.com/press/brand-assets