I wonder if this would be a simple (limited) example of defeating the watermarking? Surely there's no way SynthID is persisting in what is now a handful of pixels.
What? Since when was asking questions to clarify someones position considered "pushing back?"
Can you help me understand what about the questions make you uncomfortable?
I am completely unaffiliated with Kagi. I find it concerning that we've come to a world were we can't ask questions without it being taken as something hostile to the person/people/idea being questioned. Is that not what science is?
If you don’t think “you can just audit the binary with tools” is pushing back, then I don’t know what is, and especially so when you’ve framed the invitation with “I'd rather listen”.
I’m reminded of the number of times I’ve had vendors sit across the table from me and argue that our fixed requirements for <whatever> are just a preference or a nice-to-have. This generally doesn’t bode well for their prospects.
Fair enough. I personally did not read push back in the questions/statements asked/made.
> Trust with regards to...?
I took this to be a good faith ask for clarification
> Orion doesn't have any telemetry... You can audit the application's behavior with standard tools to verify that it isn't "phoning home", etc...
I took this as a statement if what I could do, not specifically what I should do instead of getting it open sourced.
Maybe I read it with more good faith intention and curiosity than I should have. I see your point on how that could be perceived as push back, but I landed somewhere different from where you might have.
That statement also said you have to audit binary even if the code is open source. Which isn't entirely true as other comments pointed out - reproducible builds - but the idea doesn't seem like pushing back to me. It was to point out that open source doesn't automatically imply any level of trust when it comes to security/privacy.
HALIC is by far the best lossless codec in terms of speed/compression ratio. If lossy mode were similarly available, we might not be discussing all these issues. I think he stopped developing HALIC for a long time due to lack of interest.
Its developer is also developing HALAC (High Availability Lossless Audio Compression). He recently released the source code for the first version of HALAC. And I don't think anyone cared.
Well said. (I too want that.) I found my first reaction to `MutableArray` was "why not make it a persistent array‽"
Then took a moment to tame my disappointment and realized that the author only wants immutability checking by the typescript compiler (delineated mutation) not to change the design of their programs. A fine choice in itself.
A little annoyed, this seems like is has nothing to do with the ICE arrests...
> The city suspended its Flock system because city officials could not guarantee they wouldn’t be forced to release data collected by those devices someday, she said.
Key part is "someday". Seems like the article is implying that flock may have shared this data with ICE which led to the arrests... but there is no proof supporting this...
> On Thursday, a Skagit County Superior Court judge ruled that pictures taken by Flock cameras in the cities of Sedro-Woolley and Stanwood qualify as public records, and therefore must be released as required by the state’s Public Records Act, court records show.
This is the more likely reason. What do folks here think about this ruling?
IMO it seems obvious that this should be public records/data, but would love to hear alternative positions to this.
I can't stand this type of "journalism"/sensationalism.
> Redmond’s Police Department was not among those listed in the report, and has never allowed external agencies to access their Flock data without requesting and receiving permission from the police chief first, according to an Oct. 24 statement by Lowe.
So because the arrests were near a Flock Camera the "journalist" is connecting the two? Even with the statements an information to the contrary?
This wouldn't be the first time Flock was used by ICE and would not be the first time Flock allowed ICE backdoor access against the wishes of the local government or police department in Washington. https://jsis.washington.edu/humanrights/2025/10/21/leaving-t...
So making the connection isn't a leap and seems like a pretty pragmatic action taken to reduce ICE's ability to surveil communities.
The journalists didn't make this connection, it was a topic of discussion at the city council meeting. And the result of that discussion was to suspend the cameras anyway, out of concern that ICE could end up with the the Flock data, even if they hadn't already. It would have been odd for the journalist to report on the outcome and leave out the event that prompted it.
I think we need to revise our understanding of expectation of privacy. The 'you have no expectation of privacy when you are outside' bit was formed before we had everything recording us and before face recognition could track us.
At the very least I think any kind of face recognition should require probable cause.
Its an interesting question indeed. You're saying there might be some expectation of privacy even in public?
The line here is a little different. I could point a camera out my window and record every license plate that drives by my house, and that would be allowed because its recording public activities, and the data I collect would be private—its mine from my camera.
The question here is if a public/government agency pays a private company to setup cameras in public, for the benefit of the public, then should that data collected by those cameras not also be public?
The courts seem to agree that it should be public, and I fail to see why it shouldn't be. Maybe I should read the opposition briefs on it.
If your neighbors were across the street and had their blinds open could you point your camera at their window and take pictures?
License plates were designed to be read and visible and they show that the vehicle is registered, but what about inside the vehicle? Do we have privacy in there?
What exactly does 'in public' mean? And why shouldn't someone have privacy from being recorded and their movements tracked even if they are in public?
None of these things are a given. The rights we have are because we decided they were important. There is no reason we can't revisit the question as situations change.
Might make sense to revisit the constitutionality of license plates, rather than try to attack public recording.
They're demanding you show your "papers" registration at all times without articulable suspicion you've committed a crime/infraction. The fourth amendment arguably protects us from the government requiring us to show us our papers at all times when we're travelling in the most common form of conveyance.
> The question here is if a public/government agency pays a private company to setup cameras in public, for the benefit of the public, then should that data collected by those cameras not also be public?
This is how NASA operates with the data/images collected from the tax payer funded operations it runs. There is a period of exclusivity allowed for some projects to allow the people to work with the data, but anybody can go down load high res imagery once it has been released.
Awesome, thank you for the input. I suspected NASA was operating this way, but I had no idea there was a period of exclusivity. In the case of NASA, the private companies are those like JPL and the sorts I guess?
I assume it is/was similar with other data collected, like weather data/radar, oceanic current/buoy data, etc?
I read about this regarding Hubble imagery, but pretty sure it applies to all missions funded by tax payers. The teams requesting time from the platforms are granted exclusive time to work out what they need so they can publish their papers for credit and what not.
One of the great things here is that most of the teams are so focused on their specific criteria in the data, they sort of lose the forest in the tree. Once that data has been released to the public, more and more interesting things are being found in the existing data rather than requiring new observations. It's space, so most things only need to be imaged once per sensor. It's not like setting up a trap camera hoping to see big foot the one time he strolls past. The universe changes on a much slower scale so the data is still relevant for much longer.
> Once that data has been released to the public, more and more interesting things are being found in the existing data rather than requiring new observations.
Really highlights the value of the data being public, which I feel is often overlooked now a days. Hard to tie KPIs to value that comes like this.
You're saying there might be some expectation of privacy even in public?
There should be. I like how this is handled in Japanese media, where there is such an expectation - people's faces are blurred unless they opt in, and publishing photos/video without redating people's identities is not just a social misstep but grounds for a lawsuit if it causes distress for the subject. You need a release for any commercial use of photography, and non-commercial publication (eg Instagram or your art blog) can still get you sued if it infringes on others' privacy.
P.S.: To put it another way, a major purpose law is to clarify and codify the expectations the people. Not just expectations of privacy, but expectations of when we have liberty to observe or record.
We expect that our faces might be captured on someone's vacation photos in public, surviving as an anonymous and unconsidered background detail, and that we can take our own photos like that without getting permission from everyone in the background.
In contrast, we don't (didn't?) expect all the photos to feed into a mega-panopticon that that does facial-recognition on all subjects and cross-references us over time and space while running algorithms looking for embarrassing, criminal, or blackmail-able events.
> You're saying there might be some expectation of privacy even in public?
Sure. The expectation is that your every move in public is not being recorded and stored on a central system that the government, and by extension various kinds of bad actors, can access.
In a society where the government's role is to defend its citizenry rather than participate in their exploitation, this would be an easy choice.
US governments (both federal and local) face some challenges here, because "defend its citizenry" is not really one of its main goals.
> I could point a camera out my window and record every license plate that drives by my house, and that would be allowed because its recording public activities, and the data I collect would be private—its mine from my camera.
Maybe you shouldn’t be allowed to do that. Permanent persistent recording of the public feels very different than taking a photo every once in a while, and I feel it’s an infringement of privacy even when a single person does it.
Feels more like stalking to me when the government does it. The intent is to intimidate and put the observed parties in imminent fear of imprisonment if they do something those in power do not like. Coupling this with intentionally following them around, with the specific goal of en masse systematic targeting of those in transit, albeit with stationary cameras strategically replaced, has a lot of parallels to criminal stalking.
If you put up cameras on all the intersections on the way of say an ex went to work, and started logging when they were coming and going, it's hard for me to believe a prosecutor wouldn't be able to file that under some stalking-adjacent statute. The fact that they're doing the same thing en masse doesn't make it more generalized, it's just a larger scale of high specificity.
I think it's less of a revision and more a return to a core meaning.
Privacy isn't a mechanic, it's a capability, and most reasonable people DO expect, implicitly, that that they can travel unremarked under most circumstances.
I think most people would agree that a government drone swarm specifically tasked to follow you everywhere in public (loitering outside buildings) would be an invasion of privacy. Especially when it is illegal not to be wearing some equivalent of license plates.
Maybe I need to write a news filter/browser extension that rewrites rage-bait articles to have titles and content based only on the meaningful content/facts, and less the speculation/insinuations.
From what I read, the pressure from activist groups on Redmond’s city leadership began before the Skagit County ruling. So it is probably unrelated. But I think it’s still a bad outcome for Redmond. Why wouldn’t you want law enforcement to be able to observe public spaces (which these cameras are monitoring) and identify or track suspects? We want our city services (like policing) to be efficient, right? We want criminals to be arrested and face consequences, right? We all want safe cities and neighborhoods, right?
I think the Skagit county ruling is likely to be appealed. There is a lot of information that governments can redact for a variety of reasons, despite FOIA or state/local transparency laws. It seems obvious that there’s a case for law enforcement to be able to access footage but to avoid handing over that kind of intelligence to the general public, where criminals could also abuse the same data. And I just don’t buy the argument that surveillance through cameras is automatically dystopian - we can pass laws that make it so that data is only accessible with a warrant or in a situation with immediate public risk. There are all sorts of powers the government has that we bring under control with the right laws - why would this be any different?
As for Redmond turning off its cameras - this is just fear-mongering about ICE. In reality, it’s just sanctuary city/state resistance to enforcing immigration laws. Redmond’s police department confirmed they’ve never shared this camera data with federal agencies, but that doesn’t stop activist types from making unhinged claims or exerting pressure. In reality, it’s activists of the same ideological bias as the soft on crime types that have caused crimes to go up dramatically in the Pacific Northwest in the last 20 years. They’re happy to see law enforcement hampered and the public put at risk - the ICE thing is just the new tactic to push it.
Your first paragraph doesn’t just beg the question, it outright harasses it.
…and identify or track suspects?
For starters, we’re all suspects when those cameras are running. Granted, AI-driven facial recognition is 100% accurate, so if you have nothing to hide…
> Redmond’s police department confirmed they’ve never shared this camera data with federal agencies
The problem with this is, that in the age of put-as-much-data-as-we-have-in-some-us-megacorp-managed-cloud this does not mean anything anymore. I may sound paranoid but it's just the truth. There is an abundance of general evidence for this, but even more, there is evidence that Flock data has been shared with parties in the US government who weren't "allowed" to access them.
Your sentence makes it sound like they have a document somewhere in their office that has not shared with anyone else. But that's wrong. They have a document on servers ran by a shady company (prob. AWS, Azure, Google), managed by another even shadier company (Flock). The police department has no idea who can see it, and who can't.
I can only speak for myself, but I do not have a problem with enforcement of immigration laws at all. What I do have a problem with is how it is enforced [1,2] and how the general surveillance is handled, especially by Flock [3,4] and the US Government [5], but, to be honest, in the whole US.
> Why wouldn’t you want law enforcement to be able to observe public spaces (which these cameras are monitoring) and identify or track suspects?
Yeah, why wouldn't I want that? Or Flock "helpfully" proactively flagging AI-generated "suspicious vehicle movements" to LE for investigation? What could wrong there?
> We all want safe cities and neighborhoods, right?
Was it hard not to end that paragraph with a "Won't somebody think of our children?"?
What database were you using? For example with SQL server, by default it clusters data on disk by primary key. Random (non-sequential) PKs like uuidv4 require random cluster shuffling to insert a row “in the middle” of a cluster, increasing io load and causing performance issues.
Postgres on the other hand doesn’t do clustered indexing on the PK… if I recall correctly.
Postgres is not immune to uuid issues, just less sensitive, uuidv4 still does not play well with btree indexes, bloating them and impacting their performance.
Slightly tangential question: Why doesn't the government "own" the intellectual property for their citizens to vote?
I'm all for free markets and capitalism, but I think its not clear to me why some fundamental responsibilities and operations of the government can be contracted out. Is there a way this make sense to anyone?
Having just gone through really yak shaving Aerospace into a spot that I'm happy with, I'm curious how folks on here manage having so many overlapping keyboard shortcuts?
Maybe it's just me, but I want to map to many things to some combination of hjkl just for the ergonomics...
Aerospace's modal feature sort helps solve that shortcut conflict... How are others dealing with this?
They’re not, is the impression I get. I usually run into a shortcut conflict within the first few minutes of actual day-to-day use.
I switched to Aerospace about a year ago. I hide everything behind a leader key: alt+space. That brings me into Aerospace’s normal mode. I have a few alt-shortcuts there for quick access: e.g. alt-{hjkl} for moving between panes. But most things are in a dedicated mode. I have a ‘go-to’ mode and a ‘move-to’ mode. Once in either mode, pressing any letter or number will go to/move a pane to space corresponding to the letter/number. So for instance, if I want to move my terminal to space ‘t’ then I type `alt+space g t`. To move to the space I type `alt+space m t`.
I’ve been enjoying this setup because it feels like a natural extension of my terminal setup: zellij/tmux with leader key ctrl+space and helix (also modal) inside.
One thing I constantly struggle with in Aerospace, though, is its tendency to keep windows hidden after switching screens. You have to hunt for them in the bottom-right corner and just hope you can drag them back into view.
I tried Aerospace but the default was to map all alt keys to 26 different workspaces, eradicating all the built in emacs-like key shortcuts available in every app.
That plus there's zero tutorial on the basic key mapping, just a bunch commands and no hints about where to look for how to use it...
It is the most hostile piece of software I have encountered in years and I just spend the past few weeks mucking with sway and hyprland on Linux, and mucking in Linux bootloaders so that I can enter the disk encryption password both by serial port and the physical keyboard.
So I solved it by deleting aerospace and waiting to try a different rolling window manager, which will be Rift. I suspect in the end I'll just write my own tiling window manager. It certainly seems like there's one for every person who has ever had the whim to do so...
I did something similar. I use Karabiner and I mapped the right Option key on my external keyboard to Option+Shift (A1), and right Control key to Control+Option+Shift (A2). I've configured Aerospace such that if I want to change focus, I use `A1 + hjkl` to move the focus around, and if I want to move windows around, I use `A2 + hjkl`. I use `A1 + ui` to switch workspaces, and `A2+ui` to move windows between workspaces. For shifting focus between monitors its `A1+m,` and moving between them `A2 + m,`
By far these are the shortcuts I use most often and if there are apps with conflicting shortcuts, I change those to something else. I haven't thought about it much but I'm sure I can extend this pattern further for better ergonomics. It works great so far.
Meh (ctrl alt shift) and hyper (ctrl alt shift cmd). And I bind caps lock to meh on long press and esc on tap.
This gives me plenty of easily reachable hot keys. Eg I can switch between spaces with meh + number. I have terminal hot window bound to meh + space. Moving focus between windows is meh + hjlk.
After playing with it for all of 30 seconds, my thoughts are:
1. It's ridiculously fast. Not that it matters that much, Aerospace is fine for me.
2. I somehow doesn't require any accessibility permissions... so it "just works" after running the CLI...
3. One thing I immediately noticed, is that it looks like moving a window to be accordion can be done in the same workspace?
So far I'm very impressed... not sure if I'm impressed enough to switch yet though... but being in rust does make it slightly easier for me to contribute
Or is it purely because the models just don't understand pixel art?
reply