When many sites are collecting these photos, it increases possibility of them leaking. Since these are also used for KYC process in crypto sites etc, this in turn increases risk of identity theft.
Isn't training material the biggest problem for truly open source LLMs (such that could compete with top tier models)? The computation part can be solved with money, but compiling a comprehensive training set that could be freely shared and free of copyright issues is pretty much impossible.
Do we need to bring Keybase[1] "back"? The original idea, mapping your social media presence to certain encryption keys.
In the future it will be increasingly difficult to prove in online context that you are not a bot. Being able to show that your social media (HN, GitHub, etc) presence goes way back would be an option.
"yes, there were regressions in some use cases of rsync in the 3.4.3 release. I quite deliberately tried to err on the side of fixing security issues for that release, and there were some valid (but unusual) use cases that got caught up in the changes"
Not sure if this is the future I want, but I've always thought the main idea of smart glasses is to automatically bring up information that is relevant in your current context. One part of this is to recognize who you are staring at.
"By integrating Ookla’s data products, including Speedtest®, Downdetector®, Ekahau®, and RootMetrics®, Accenture will help Communications Service Providers (CSPs), hyperscalers, and enterprises optimize the mission-critical Wi-Fi and 5G networks that power their digital core. [...] Ookla’s data platform is anchored by more than 250 million consumer-initiated tests per month, complemented by controlled drive, walk, and embedded testing options"[1]
"Only $99 to add 5G Backup to any UniFI network" and "Fully unlocked for any compatible carrier with SIM and eSIM support". Wonder if there's some catch?
It’s likely because the quick thought is that auth is just user table with hashed password.
Then when you really start thinking about it, the list of requirements grows.
Of course it’s still totally doable for an average developer, but takes time and mistakes can be catastrophic. And maybe the time is better spent developing stuff that differentiates you from others.
Kubernetes sounds like overkill, but I've been running microk8s for few standalone servers. This feels a pretty good match when working with agents. Codex can manage the cluster also over ssh, schedule new pods, check statuses, logs etc.
Why not replace the SMTP with an API and explicit permissions. When registering for a newsletter, I would explicitly grant the sender right to push stuff to my inbox. At any point I could revoke this right and the sender would get clear error message when pushing.
Old fashioned person-to-person email would work as it does. This would only apply to the app-to-user stuff, which in my case makes up >99% of my emails.
Put proper LLM into Siri. Encourage developers to expose the functionality of their apps as functions, allow Siri LLM to access those (and sprinkle some magic security dust over it).
Boom, you have an agent in the phone capable of doing all the stuff you can do with the apps. Which means pretty much everything in our life.
Sometimes easy performance trick is to split the CTE to separate queries, put the results to unlogged temporary tables and add whatever indexes the next step needs.
Obviously makes only sense for stuff like analytical queries that are not running constantly.
Somebody took a deeper look at Claude Code and claims to find evidence of Anthropic's PaaS offering [1]. There's certainly money to be made by offering a nice platform where "citizen developers" can push their code.
From Astral the (fast) linter and type checker are pretty useful companions for agentic development.
When pushed, I then start thinking and realise my mistake. System 1 vs 2?