Hacker Newsnew | past | comments | ask | show | jobs | submit | _def's commentslogin

Why is that even needed, honestly? Like is "destroying or altering evidence" usually legitimate or what?

Deleting data according to a pre-defined schedule (often 90 days) is legitimate and standard. It's good that agencies do this, to limit exposure due to data breaches. And it's normal for courts to issue a preservation order for specific data relevant to a potential case.

It'd be better if the courts could actually deal with the case now instead of in 1-5 years, but alas.


> (often 90 days)

Not for government agencies. Data retention generally goes much longer than that, usually measured in years or decades, not days or weeks.


https://www.brennancenter.org/our-work/research-reports/poli... has a list of police body cam retention policies. 90 days is pretty common, though it ranges from 30 days to 5 years.

Documents are kept longer. But a court needs to think about the shortest possible retention time that any agency might have for any kind of evidence.


From your link's subheading:

> This chart includes categories for how long video is kept if it does not contain evidence of a crime [emphasis added]

So yes, some things are short (I did write "usually" for a reason), but even your link doesn't claim that video of a killing would be deleted in 90 days. It's evidence, 90 days would be ridiculously short for retaining evidence.

Even for people who don't think the ICE agents committed a crime, the ICE agents and DHS have claimed that this was the outcome from actions by a "domestic terrorist" which certainly makes it evidence of a crime from their own perspective.


The agencies in question are unlikely to face any accountability. The agencies that would typically investigate something like this are no longer independent and, instead, are headed by feckless Trump loyalists. It doesn't matter whether it's legitimate, it matters whether it serves their ends. If they cared about process or the law they wouldn't have been labeling the victim a domestic terrorist within minutes of ICE agents murdering him.

A future administration absolutely can and should prosecute every single ICE employee.

Dissolve it and DHS. Investigate every single ERO agent and prosecute those that meet the bar. Bar all of them from future public service. Prosecute agency heads.

They're all getting pardoned.

Federal pardons only work for federal charges, which murder isn't.

A future administration cold, but won't, choose to ignore the law about parsons just like this one is ignoring the law about murder and torture.


I believe they will try to use removal to get it into federal courts.

Does removal let a federal pardon apply to a state crime, even if it's tried in federal court?

Good question. I suppose Trump doesn't much care, he already attempted to pardon that lady who gave balloting material to Mike Pillow. He'll just go issue the pardons and let the courts sort it out.

Or he could have the DOJ charge all of ICE, get the cases removed to federal court, then do an Eric Adams job on them. That'd be a sight to behold.


Are pardons issued by a felon actually valid? It is for a future court to decide in a subsequent administration.

Unfortunately as long as that felon was elected president, yes.

The odds of that happening are zero.

Yes, but they might not stop the states from prosecuting them.

Sounds like federal government employees blocked access to the crime scene to state and local government employees. Presumably, this “order” is to help facilitate access without violence between federal and non federal government employees.

I get that this is tempting but it just means you'll slowly get dependent on things that will eventually break in ways you will have no capacity to fix. And disaster recovery is most certainly a manual task.

> you'll slowly get dependent on things that will eventually break in ways you will have no capacity to fix

If the commercial provider charging you $10 a month breaks it, you also have no capacity to fix it.

Your options are: send them an email, or unsubscribe and use something else.


Right but most of the time, in my experience they keep the lights on.

Keeping the lights on is fine.

But if they remove a feature I rely on, I can't put it back.

If they add a feature I hate, I can't remove it.

If they jack the price up, I have no real solution to this.

If they move features I rely on from the standard tier to the 5x more expensive pro tier, I have no real solution to this.

Why, yes, this is an echo of the old argument for open source software.


Yep. At one point I expected the software I needed to work for a reasonable time range, possibly up to a decade. Best if you could buy it once and use it from then on.

Now crap has turned into revenue sucking subscriptions, at most yearly licensing, feature flutter. And the worst is being bought up by VC/PE and milked for anything useful and thrown away.


> Now crap has turned into revenue sucking subscriptions

So much this. Each subscription is literally a small percentage of your revenue. You can't reinvest it ... it's just gone. Hopefully it enables more productivity ... but most likely, it is only marginal.


Why wouldn't I be able to fix these things? If I managed to build a thing from scratch (with Opus 4.5), I don't see why I wouldn't be able to fix it and maintain it in the future (maybe with Opus 4.7 or even better future models?).

Why would they "eventually break"?

In what situation would a simple script or helper app just suddenly rot away and stop working?

Of course it's POSSIBLE to vibe together a massive monstrosity of an everything-app, but that's not what the author is doing here (nor me).


If it's tied to web APIs, libraries, or OS version feature APIs that are deprecated it will suddenly stop working.

Non-subscription paid software will rot the same way too, so there's no change.

With a agentic llms I can just tell it to fix it. With a commercial solution I'm fucked and either have to find something else or pay for a license (or keep paying every month).


If you build enough things, you will also gain the experience to fix those things

> When the topic is dry and quantitative (Finance), the market is efficient. When the topic allows for tribalism and hope (Sports, Entertainment), the market transforms into a mechanism for transferring wealth from the optimistic to the calculated.

I get that the finance market is _more_ dry and quantitative than sports, but certainly not immune to hope and tribalism,


>I get that the finance market is _more_ dry and quantitative than sports, but certainly not immune to hope and tribalism

where is your paper?


Irrational Exuberance by Robert Shiller

I'll allow it!

They are human, that's all you need to know.


No sane country recognizes all the same rights and privileges of a citizen in a non-citizen.


All, no. But many, yeah. The Constitution and many of it's Amendments call out people or persons. The 14th Amendment even specifies what a citizen is, and in the next breath says persons cannot be denied due process by the States, not citizens.


Be specific. Which rights?



I recently learned about a shortcut you can enable for moving windows, is something similar around for resizing? On linux I do this via alt + left click and alt + right click

`NSWindowShouldDragOnGesture` setting allows you to drag windows at any point if you hold ⌃⌘

`defaults write -g NSWindowShouldDragOnGesture -bool YES`


I'm using Easy Move+Resize, though, I don't recommend using cmd as the only modifier (you're already using ctrl+cmd, so shouldn't be a big deal), since that screws up with cmd clicking on links to open in a new tab.


"Open Source" in this case means "ML models with open weights"

(not my interpretation, it's what the post states - personally that is not what I think of when I read "Open Source")


ML models with open weights? Like, say, Qwen?


Freeware models would be more accurate term, but people went with stronger meme for this one.


Are there useful open source "agents" already ready to use with local LLMs?


From the article:

    When BGP traffic is being sent from point A to point B, it can be rerouted through a point C. If you control point C, even for a few hours, you can theoretically collect vast amounts of intelligence that would be very useful for government entities.


On which guidelines are the solutions based on?


It's a mix of personal scars and peer review.

Experience: I draw primarily from 14 years in product companies, focusing on the specific friction points where I've seen Leads struggle (or where I struggled myself).

Vetting: I stress-test the dialogue options with a network of Engineering Managers and Directors to ensure the 'winning' paths reflect reality, not just theory.

That said, unlike C++, management doesn't have a compiler to prove you are 'Correct.' It is subjective. The feedback in this thread is actually highlighting some edge cases I missed, which helps me refine the grading logic


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: