I get you -- when I was doing investigative reporting about policing and technology, the Intercept's energy was basically "great pitch, but we want you to do 8mo more work before we'll talk; good luck not being able to afford rent in the meantime".
But, friend, with love -- shit talking about what people are doing or not doing is not the answer. Lead by example.
> But, friend, with love -- shit talking about what people are doing or not doing is not the answer. Lead by example.
Why do you assume I'm not doing? Having said that, my options are limited to obtaining the lion and sun flag and participating in a demonstration. Quiet solidarity in other words. Shit talking about people who have a platform and are not using it because Israel is absolutely valid and legitimate.
That by the way is the danger with a singular obsession with one conflict, which, objectively, is not even the deadliest conflict in its region, let alone the world. Everything is either viewed through the Israel prism, as in "we're not going to express any solidarity with Iranian protesters because the fall of the theocracy might benefit Israel", or, it gets ignored entirely because there's no clout to be gained on social media.
Just to be clear, I never said I disagreed with you. But I've seen a lot of infighting happening in these spaces that stems from shit talking -- people who can no longer work together anymore because of how the shit talking bifurcated the work instead of building layers between.
Yeah, my experiences match yours and I very, very much work with messy data (FOIA data), though I use postgres instead of duckdb.
Most of the datasets I work with are indeed <10GB but the ones that are much larger follow the same ETL and analysis flows. It helps that I've built a lot of tooling to help with types and memory-efficient inserts. Having to rewrite pipelines because of "that one dataframe API" is exactly what solidified my thoughts around SQL over everything else. So much of my life time has been lost trying to get dataframe and non-dataframe libraries to work together.
Thing about SQL is that it can be taken just about anywhere, so the time spent improving your SQL skills is almost always well worth it. R and pandas much less so.
I advocated for a SQL solution at work this week and it seems to have worked. My boss is wary of the old school style SQL databases with their constraints and just being a pain to work with. As a developer, these pains aren't too hard to get used to or automate or document away for me and never understood the undue dislike of sql.
The fact that I can use sqlite / local sql db for all kinds of development and reliably use the same code (with minor updates) in the cloud hosted solution is such a huge benefit that it undermines anything else that any other solution has to offer. I'm excited about the sql stuff I learned over 10 years ago being of of great use to me in the coming months.
The last product I worked heavily on used a nosql database and it worked fine till you start tweak it just a little bit - split entities, convert data types or update ids. Most of the data access layer logic dealt with conversion between data coming in from the database and the guardrails to keep the data integrity in check while interacting with the application models. To me this is something so obviously solved years ago with a few lines of constraints. Moving over to sql was totally impossible. Learned my lesson, advocated hard for sql. Hoping for better outcomes.
I totally understand the apprehension towards SQL. It's esoteric as all hell and it tends to be managed by DBAs who you really only go to whenever there's a problem. Organizationally it's simpler to just do stuff in-memory without having to fiddle around with databases.
I'm not understanding your point either, so here's how I'm interpreting what you're saying, in good faith: "she was in the way, so it was worth shooting her. fullstop".
So I'm struggling to understand why you seem to be okay with shooting someone for being in the way. So please explain to me why you think "obstruction" was worth shooting her.
She wasn't shot for obstructing federal agents. The series of events are as follows:
1. She obstructed federal agents
2. She resisted arrest/detainment
3. She accelerated into a federal agent
4. She was shot
I don't think that she deserved death. It's unfortunate that you are misrepresenting my comments. I believe that she made a series of bad decisions and was solely responsible for what occurred. I understand that we are living in emotional times but arguing in bad faith does not improve the situation. We should maybe stop this discussion as it doesn't seem that we are getting anywhere. I hope that you have a good day
My mom's dad was shot and killed by police. Absolutely nobody in my family knows anything about it, but the default is "he was a bad person and deserved it" or, "he probably did something wrong." The coroner's report shows his death as a suicide, despite police shooting and killing him. This was a time before cameraphones and before I was even born, so it's impossible for me, let alone anyone else to know what happened.
A lot of how you approach this discussion reminds me of the side of my family that defaults to thinking that the police did nothing wrong, or that their actions were justified or within policy, even without knowing the full facts (or, any; it's willful ignorance out the wazoo), plus a handful of assumptions. And, just -- a person died and that's all you can muster? Callousness and an air of benevolence?
So can you. Your past experience was terrible, but that's no reason to ignore or misrepresent what others are saying.
What GP and I are both seeing in the Renee video is assault with a deadly weapon on a law enforcement officer. Lethal force is a valid response. That doesn't mean she deserves it, but that she was doing something stupid without realizing just how stupid it was. Most of these protestors are the same, they're new to this and being tricked by anti-ICE activists into thinking it's completely safe without getting all the information.
"Deserved" is a stronger word than "earned" or "merited", there's a sense of satisfaction or entitlement (though negative) behind that word. Something like, to say that she deserved death means saying she should have died for what she did, that it was the right outcome. That's not what we're saying. It's more like, the actions the officer took weren't in the wrong despite the bad outcome. She made really bad choices, and she was the one at fault, but there were better possible outcomes given the exact same series of events and she didn't deserve to die. But it's not a surprising outcome either.
Another quick aside since I suspect this is a second point of confusion, "lethal force" does not mean "with the intent to kill", it means "force that is likely to cause severe injury or death".
> Another quick aside since I suspect this is a second point of confusion, "lethal force" does not mean "with the intent to kill", it means "force that is likely to cause severe injury or death".
It.. is not. I suspect that you have some fundamental misunderstandings of firearm safety and I would not feel safe at a range with someone who thinks this way.
It has been well established that ICE agents are intentionally stepping in front of slow moving cars to justify a claim of self defense.
They also intentionally bump into people and then claim they are being assaulted. Their superiors have made it clear that will face no consequences for this, and they have aggressive quotas to meet.
I'm currently looking to get a law degree and the education requirements are... silly. I've done a significant amount of law-and-law-accessories work over the past ten years and have had a nice career in sysadmin/sre/devops/ops work. Yet I need a(ny) bachelors to even get started and I don't even have an associates.
It truly feels like the only way forward is to waste several years of my life and exhaust myself to the bone to get a degree.
But more honestly, it comes from reflecting about the ways that knowledge gaps affect FOIA litigation/conversation/interpretation and the criminal litigation reporting/research/investigations I've done/beenapartof. A lot of law-and-law-accessories is learnable within context-and-scope, especially with attorneys to help interpret, but I would like to get past that point. It helps that it's all very interesting.. and people keep asking me when I'm going to become a lawyer, so, ope.
"Captcha" doesn't refer to any specific type of puzzle, but a class of methods for verifying human users. Some older-style captchas are broken, but some newer ones are not.
I'm aware. But I'm also aware that breaking these sorts of systems is quite fun for a lot of nerds. So don't expect anything like that to last for any meaningful amount of time.
Since before LLMs were even an issue, there have been services that use overseas workers to solve them, with the going rate about $0.002 per captcha. (and they solve several different types)
This is both true and misleading. It implies captchas aren’t effective due to these services. In practice, though, a good captcha cuts a ton of garbage traffic even though a motivated opponent can pay for circumvention.
True, cameras can be taken away or smashed after the fact destroying evidence.
With my phone I can stream video to a cloud so that it can't be deleted. The ACLU used to have an app specifically for this but it seems to have been discontinued. https://en.wikipedia.org/wiki/ACLU_Mobile_Justice
If you are ok with the low quality, you could use a radio to transmit fast scan TV to a nearby receiver. Use a repeater if you need to get some real distance.
FPV drones often use this and could be a good source of parts. Or encode the feed and send through a small portable ham radio if you want a challenge. https://irrational.net/2014/03/02/digital-atv/
reply