janilowski
Joined 7 months ago
Joined 7 months ago
I assume what KingOfCoders suggested is to run an agent almost like an antivirus which I guess sounds somewhat interesting but you'd have to re-run it on every update and probably spend many more hours+tokens for such a system to work properly.
But perhaps once inference gets truly cheap repository maintainers should include AI security checks for new software as part of their pipeline? I think that would make sense. Especially for repos that are frequently pwned like npm!
Their watchlist was only ~450 people, and it was restricted to people relevant to the transport police. The system was also overt and clearly marked, there were alternative routes that avoided the cameras and even then they were on 3-6 hours per day.
The headline suggests this system is not only invasive but also ineffective. While I agree it's a privacy nightmare, I also think those idiotic deployment conditions set them up for failure. At least we know there aren't many false positives, it could've been worse.
Where exactly would the UI benefit from "drawing lines"? I'd say the visual hierarchy is rather obvious.
I'll say more: most separators people use in their UIs are completely unnecessary. They should be used sporadically when you don't have a better way of segmenting the interface.
> No visual differentiation between sections of the UI, no clear indication of what's tappable and what will happen on a tap
What section of the UI are you referring to exactly? From the screenshots in their blog post it seems to me like the visual hierarchy is preserved and without using the app at least I can form an immediate expectation as to the function of each button. (And what is clickable and what isn't)
> no indication of scrollable areas beyond content being cut off
What type of indication would you like to see here? I think most users intuitively understand that visual cue. An always-on scrollbar would introduce unnecessary clutter..
I generally agree with those reasons, although using a single thread may be less of an issue than it seems because of context compacting which should happen automatically when you're near the limit.
Do you use the official harness? OpenAI's models are generally best in class for token efficiency. It seems to me like they push for that much more than their competitors.
Must've never driven through the Alps I guess. There's something like this every couple km