The full analysis of this would need to take in account:
* Who actually determines the essential means and purposes for each processing purpose (and is truly doing it). Fashion ID case is quite relevant here.
* If terms which grant Meta these rights and user a lot of obligations would fall under unfair terms or unfair commercial practices directives. If they do then those aspects of the terms are invalid. These could, for example, affect requirement that the user must get consent from data subject for Meta's processing operations.
I've found Pro to be a lot better per "task" than the recently released Flash for code reviews and things (via OpenRouter running in pi.dev).
Flash makes a lot more initial mistakes, and then has to re-check stuff, and produces much more output compared to Pro. It often gets to the correct result, but the output volume is often 5x more than for Pro, and the initial outputs are often wrong, with the first few saying something wrong (like there's a bug, or the code won't compile when it does), and then saying things like "Wait, let me re-check:", and then it thinks a bit more and eventually gets to the right answer.
Your router doesn't care about their DNS settings. IP addresses are very easy to tie back to countries. The reason they say it's not reliable is because it's trivial to spoof the country, but even so, a lot of attackers don't even bother. It's sort of like the Nigerian prince scam calls: if you're wise enough to block Russia, you're not worth their time.
Your firewall vendor should supply you with country lists, just select the known bad ones and drop their traffic. If you have a consumer grade router, you will probably have to configure the blocklists manually.
We see a huge amplification of single mistakes by these automated "efficient" processes. Just yesertday there was a story on the front page of a completely innocent woman who kept getting the felony warrant treatment over a data entry issue.
It's not the first time.
We also see the cops use the flock system as another excuse to treat an encounter over an unpaid bill as if they were taking down Bin Laden - they seem to see "flock hit" as code for "lets try to kill this person".
I am not a criminal nor do I have some sort of fetish for being abused, therefore I don't want some typo to result in unstable, bloodthirsty thugs putting guns in my face. The inefficiency protects me somewhat from these things, and until these issues can be properly addressed, I don't want anything to be scaled to a higher degree.
Yes I'm aware that this means lazy cops won't catch as many speeders and people who have warrants to pay a fine. I don't mind.
I don't think it's possible to partially decode/render a PNG in a way similar to JPEG. The only exception I can think of is adam7 interlacing, which _does_ store the initial pass as 8x8 blocks, but I'm pretty sure PNGs with adam7 are rare in practice because they do result in larger files.
How about we just get on with it and delegalize ads already? They’re a net negative in every form, subsidizing disgusting companies that shouldn’t exist, infringing on everyone’s privacy (including your children! think of the children!!!!!), and making us jump through all kinds of ridiculous hoops to minimize our exposure to them. I don’t think the solution is more hoops.
What genuinely disappointing result. Long time pixel user here and I've been routinely buying these phones with the argument that you're getting the most value of any modern smart phone. Now? I'm just waiting for the pixel 10 family to drop in price. Happy to just wait.
I am working on yet another local code context tool [0]. But I am trying to go the extra mile by having extra features like better review, automated testing, performance work and everything being agent first. Still trying to find the gaps of where this tool can add value vs just using codex/claude directly. Making it faster, better & more reliable may not be the only direction. Apart from that, I have been tinkering with a lot of small experiments [1]
I actually think ai and llm use benefit a small minority at the expense of the vast majority, and i like the tech but im not impressed with its applications. Agree you can fight whatever fight you like, but those problems you listed with fascism have been around well before llm's came along and fighting llm use wont solve problems with fascism it may just stall it a little.
Tell me how to paradigm shift careers and I'll get out of your hair and stop shipping uninspired features.
But, right now I'm paralyzed with fear in how to make a successful career switch without starting from literally "new grad level." I have wisdom, so it doesn't feel like I should have to start at the bottom rung again. Egotistically, I don't even mind, it's just the salary hit that would be the main issue.
Maybe it's not even a paradigm shift (though, I've always wanted to work on film productions). I've sort of lost the passion for being an IC, but how can I make a transition to management without any management experience? Should I just apply for a managerial role and in the cover letter state management is my intended path for growth?
Warrants for historical search with warrant-free flags for ongoing issues seems like a nice middle ground. Convincing. Good article.
It seems that would easily impede a lot of abuse and it’s straightforward to believe that historical data is rarely so urgent as to not require a warrant.
A matter of defining historical as a sufficiently old enough thing but that seems feasible.
SCOTUS gets into it in their opinions on Chartrie, you should check it out.
They wrestle with the balance there of 4th amendment protections and mass surveillance. It's evolving and generally courts are moving to not allowing mass surveillance -or less so than they have allowed in. Courts have been split on it, and someone already pointed it out that SCOTUS will eventually come up with tests for it.
There were some really interesting parts of those Chatrie opinions that really will test the idea that someone in public gives up their right to any privacy - the fundamental underpinning of why governments can currently point cameras at public places and dont need a warrant to search that video.
Chatrie protected the aggregated viewpoint versus any single public moment - And SCOTUS said the aggregated viewpoint (mass search of location data with no specific person(s)) is not allowed under the 4th amendment. A very interesting precedent.
Gorsuch had an interesting take in that he argued that in Chatrie the location data was Chatrie's personal property and therefore protected from illegal searches from government.
There are a lot of similarities to how ALPRs work, and key differences. Mostly Chatrie deals with a private firms data collection of locations - google vs ALPRs are generally on publicly owned property and recoding things in public.
Still, many justices opened the door to the idea that the government can't mass surveil citizens. We'll have to wait and see how it all plays out.
I am very much of the opinion the government should need a warrant to search through ALPR data (and video for that matter). So, I am hopeful that the tenets of Chatrie extend to ALPRs, video, etc.
In these missed eclipse the moon is usually a little too up or a little too down. The moon revolves on a plane that is tilted respect the Earth's plane of revolution. These two planes of revolution intersect at the the two points called nodes.
If the new moon happens to fall on the node then you will get a solar Eclipse.
Cloned horses are becoming really common in polo — the best polo player in the world won the Argentine Open back in 2016 with six clones of his favorite horse [0][1]!
I like smart glasses as they are useful for quickly capturing life's moments (friends/family/experiences) and learning more about the world around you. When i did some solo traveling in Berlin i learned a lot about things I was seeing thru my glasses.
I think Apple if and when releases their smart glasses they could/should add a privacy feature. The feature would anonymize and or randomize all strangers faces in the pics and vids you take who are not in your network (Apple already knows many faces in your network now).
Though Apple may never release such glasses but Google via Samsung will purportedly be releasing theirs this fall.
Graft writes a structural map of your codebase into markdown, committed to git, so agents stop re-exploring the same repo every session.
graft build is tree-sitter only. works locally with any repo size.
Shipped Claude Code support as an MCP server first, six tools for pulling context.
It mostly didn't call them. Fell back on grep, got things wrong on exactly what those tools would've answered.
Moved to hooks: SessionStart pushes the graph in automatically, a post-edit hook re-syncs it after every change. No tool call to skip.
Real tradeoff: hooks only work on Claude Code. Cursor and Codex still go through the MCP server, same opt-in problem, unsolved there.
I'll be there in the comments. Thanks for listening :)