Yes, there's a difference: US citizens have the right to enter the USA; visitors do not. US officials can deny a visitor entry arbitrarily, and the visitor has limited recourse to appeal such a decision. A visitor who does not cooperate with officials who want to search something is likely to be denied entry.
A citizen may only be denied entry if they're entering the country for the purpose of committing a crime, and if the government can prove that, they'll probably admit the citizen and immediately arrest them instead.
A US citizen cannot be denied entry into the country for ANY reason. A valid US passport is prima facie evidence of citizenship so once you show it the worst that can happen is you getting arrested.
> It is insane to me that judges consistently rule that the constitution doesn't apply because there's a "border" within 100 miles.
People keep misconstruing this.
The border search exemption only applies when someone is actually crossing a border, and it does grant broad authority to search whatever they're carrying with them at the time. The authority to do border enforcement within a 100-mile zone around borders does not grant a broad authority to search. It does grant a narrow authority to do things like traffic checkpoints, but those don't permit searches for anything smaller than a person without additional evidence.
I do think the ruling establishing the authority to run checkpoints other than actual border crossings was wrongly decided and harmful, but it's not what's at issue in this case.
To add to that, the ruling intentionally did not make a decision on two important distinctions:
1. Forcing you to unlock - in this case, Alisigwe unlocked their phone willingly after being asked.
2. Forensic extraction - the ruling does not give authorities the power to run a sophisticated off-site break-in on your phone without reasonable suspicion.
So if you are a US citizen, and you are willingly unlocking your phone at the border (or you don't have a passcode), the Fourth Amendment no longer protect you from a suspicionless manual search of the phone at the border
But what they can do is confiscate your phone, _image_ it, without the access attempt, and keep the phone as evidence until or unless they feel the need to apply for a warrant for the access.
No. They cannot keep the phone, and they cannot copy the phone data without reasonable suspicion under this ruling (connecting the phone to an external device to copy is considered advanced forensic and already has case law around it).
True, but Egbert v. Boule (2022) the SCOTUS determined there's no penalty established or monetary damages owed to you if Border Agents cross the boundary of the exemption and violate your Fourth Amendment right.
The remedy is disallowing evidence collected. This is the same for almost every case in which law enforcement searches without proper cause or a warrant.
And I don't know what that would be surprising. Where monetary damages are due they are because statute establishes them, or you can show some specific and direct financial harm (thus money damage is the remedy).
Doesn't stop further action based on your private data and retribution for evidence of anti-American speech or potentially-criminal travel patterns. In terms of government surveillance, evidence doesn't need to be submitted to court. It can be provided to a government surveillance contractor like Palantir or Flock for national security purposes.
The current Exectutive Branch has a history of keyword-search driven action, without a chain-of-command of proper review before action.
At least one American citizen has successfully been un-deported based on bad information resulting in deportation action. DHS has a Predictive Policing division willing to conduct unconstitutional, warantless parellel construction.
Warrantless surveillance is well established, and anti-American evidence may exist on your device depending on the reasonable suspicion provided by other Palantir-esque analysis of your online activity and your level of support of the ruling power. The law enforcement agent you encounter won't receive that context, just that the system they usually use flagged you as suspicious without your knowledge (depending on the jurisdiction you're in).
To your point, it only needs to be justified in court if you take legal action. Per Egbert v. Boule (2022), no remedy for American citizens seeking damages for unjustified violations of the First Amendment or Fourth Amendment when it comes to immigration enforcement-related action exists unless explicitly defined by Congress (which it has not, yet).
Edit:
> “People in the government violated my privacy by reading my private information”, on its own, is not a harm the court can fix.
Basically, the average American should treat Border Patrol agents like they're the Gestapo going after their private, Constitutionally protected information with no legal recourse for that potential violation of Constitutionally-protected right to privacy.
If you're rich you can fight it, but the SCOTUS will likely determine Border Agent overreach is something that just happens until Congress establishes a penalty.
To seek damages in court, you must spend more than taxpayer-funded legal defendants to begin to establish the specific harm.
Your next vote should consider an innocent-until-proven-guilty doctrine that provides potential American citizen victims of Border Patrol overreach a taxpayer-funded Consitutional lawyer in court and a trial in front of a jury of their peers.
Your tax dollars are already being used to harass and falsely detain Americans, might as well also spend your tax dollars on defending the innocent (which might be you next year). Maybe the American Government will stop falsely detaining citizens if it becomes more expensive for taxpayers.
Most of them do. They're usually constructed as restrictions on the government's authority rather than grants of rights to a specific group of people, and there are court rulings clearly stating rights like freedom of speech and freedom from unreasonable search apply to any person subject to the government's authority.
Non-citizens don't get the right to bear arms as far as I know.
This *1000. It's a supreme failure on our educational system and society at large that most Americans don't think about our government and our rights in these terms.
The Constitution actually takes away our rights. It has to, it lays out the powers the government has over us. Even the bill of rights doesn't technically give us rights---it explicitly details the ways our government cannot operate.
I find that decision a bit odd given that accumulating a string with a loop is also quadratic in Python if you use = instead of +=, or even if you use += when the left operand isn't provably unshared. I don't believe removing loops was seriously considered.
The footgun isn't `reduce` in particular, but failing to use `join`.
I suppose `reduce` as built-in is the footgun because it's too easy to reach for. Now if someone doesn't know about `join` perhaps they look up how to do it because they think 'surely there's a better way than a loop without an import'.
Doesn't reduce force the accumulator to be shared though? Both the reduce and the lambda are holding onto references to acc, which defeats any "single reference" optimizations.
If the s are small the usual geometric buffer growth mitigates that. Of course you can compute the final buffer size in this case, but often you have a bunch of dynamically-generated strings of different sizes.
def reduce(acc, f):
for v in self:
acc = f(acc, v)
return acc
The current acc goes out of scope each time you call f. There's no shared reference (assuming f doesn't sneak store it elsewhere, which for string combining, f should just be `return a+b`?).
Why is it still active? Even an interpreter with no lookahead could see that it goes out of scope immediately when f returns (it gets shadowed on that line), so as long as there's no guarantee about when finalizers get called, it should be able to mark it dead inside of reduce as soon as it's passed to f. Like move semantics here should be a general pattern for optimization, no?
Fair, I suppose there's no end to the level of insanity that a programmer can do in a dynamic language. I'd think it could perhaps still look to see there's no catch, but maybe eval makes even that impossible.
It might - let's assume it does. My point is that it's better to use the explicit optimized method for joining strings in a performance-sensitive context than to try to meet the conditions for an implicit optimization.
It's still pretty early, possibly buggy, and almost certain to get breaking changes without warning.
My original thought was to combine Lisp syntax and structural macros with C semantics and see how much extra abstraction that would provide, but variants of that idea have been tried before. They may have been compelling at a certain point in time, but I think a new systems programming language in 2026 should offer more, so it does.
Some features include: strong typing, protocols (similar to Clojure or Rust traits), non-nullable references, error values, bound error handlers (a bit like Common Lisp), optional lexical lifetimes, namespaces, and no mandatory runtime overhead relative to C.
It's self-hosted, which I've noticed several new systems programming languages announced recently are not.
The ones advertised on Meta platforms (and others like YouTube), at least the ones I've seen, claim to do so in a device that looks like it can't have more than a tiny battery and no cooling in there, or that they actualy show using standard AA batteries, or recharging inside an hour by solar energy, or other claim that thumbs its nose to the lawsof physics. But they must be real, after all that nice man left NASA to work on it and now the nasty commercial interests are trying to shut him down! I must buy one now while I still can!
The brand name that comes to mind is the Wicked Lasers Flashtorch, which uses a 65W halogen bulb that emits most of its energy as infrared, and a ~30 Watt-hour Li-ion battery. The old-fashioned light source is better suited to party tricks than illumination.
More modern, and also capable of improvised cooking are handheld searchlights from Acebeam and Imalent with many large LEDs, cooling fans, and even bigger Li-ion batteries. There are third-party videos of these and the older halogen type cooking eggs and setting fire to paper on Youtube.
What you're describing from the ads obviously violates the laws of physics. An alkaline AA would have a hard time cooking an egg on a dead short.
"May contain" labeling seems like the better solution to this problem. This should be allowed for allergens that are present in the manufacturing or packing facility but not intended to be ingredients in the product.
That's part of the problem. "May contain" doesn't provide legal protection and then if you make it a standard there needs to be testing for compliance which ends up as the same original problem and you just add compliance tits to your food product.
"May contain" should provide legal protection. It may be compliance tits in some cases, but that's better than forcing the addition of a compliance ingredient.
The term "missing person" calls to mind someone who is in serious danger, but a majority are something minor, like someone quitting a job without notice or taking an unannounced trip. The vast majority are resolved by finding the person alive.
Flock helping close 10K cases doesn't surprise me at all, but it doesn't meant those people wouldn't have been found without it. It may mean less work for the police, but the police don't usually put a lot of effort into a missing person without evidence they're in danger.
Google Maps has a better excuse for wanting to be an app than most since a primary use case on mobile is turn-by-turn navigation. That's possible to do in a web page now, but several features that improve the experience are not available in browsers.
I'm annoyed by a different thing ... It used to be when you searched for something, maps would always be a tab for results. Now it doesn't seem to be anymore...
What you need to do, in the modern Web, is to flip that around.
Anytime I need to search an entity with physical presence, I use Google Maps first. Maps is very good about getting the first result as intended and not showing superfluous non-matches. Maps will not chirp up with AI-generated responses. Maps will take me right to the place I want, and I can see a lot of profile info at-a-glance, and if I wanted their website, then Maps will give me their main website, and nothing else.
Whether it's a corporate HQ, a clinic, a local restaurant, or a geographic area, Maps can come up with a lot of relevant info and I don't waste my time in an enshittified Search. So I'm thankful for the Maps app and its mobile integrations.
I’m not sure how that’s a justification. If you want to app-wall the turn by turn directions, that would be one thing. The fact that turn-by-turn directions is better on mobile doesn’t rationalize lying about being unable to show photos, and auto opening the App Store three times every time you want to search for an address somewhere
A citizen may only be denied entry if they're entering the country for the purpose of committing a crime, and if the government can prove that, they'll probably admit the citizen and immediately arrest them instead.
reply