On the offchance that you’re not already familiar with the recent prompt injection tricks that meta’s latest toy is so vulnerable to, this is an interesting thread investigating the contents of the vm filesystem dumps that it can be made to regurgitate: https://neuromatch.social/@jonny/117324790823856750
I was particularly entertained by the hard-coded list of “ideas”.
Via catturd2.bsky.social (probably no relation),
https://gizmodo.com/fbi-warns-ice-agents-not-to-trust-any-woman-willing-to-date-them-2000814283
Something something domino meme leading from “eron gjoni can’t handle being dumped” to “women in long dresses and who cover their hair declared national security risks”.
The memo implied that ICE officers should be wary of any woman that knows they’re an ICE agent, especially if they go out of their way to seem cool with ICE agents or identify themselves as tradwives. (Those are conservative women who dress like the women in The Sound of Music, but without the opposition to the Anschluss. They’re rare enough in reality that the going rate for a professional matchmaker to find one is reportedly $25k).
“These profiles were incorporating imagery of a ‘traditional wife’ aesthetic and listing specific interests in an attempt to appeal to… individuals in law enforcement,” the FBI wrote. “The objective was to lure affiliated law enforcement personnel into an online or in-person interaction under the guise of a date, after which the individuals would be publicly exposed and doxed online.”
Flock camera is image available on ddossecrets.
https://ddosecrets.org/article/flock-alpr-camera
Very brief observations from micahflee:
https://bsky.app/profile/micahflee.com/post/3mvo2bss3sk2v
This Flock camera is running obsolete, end-of-life software.
- It’s on Android 8.1, released in 2017, support ended in 2021
- It’s on Android patch level 2018-06-5
- It’s running Linux 3.18, released in 2017
This shit is like 8 or 9 years old, and full of vulnerabilities.
Flock was founded in 2017, apparently made their golden camera image within 12-18 months or so and never updated it since. They might not even have the ability to fix it in-house anymore, even assuming it wasn’t a one-off contractor job in the first place. I know the embedded development is a shit show, but somehow it never ceases to disappoint me how lazy and incompetent the entire goddamn industry is.
Fucking android?
AI-native. A desktop that loves you back has to know you.
If you are interested in vibe code and want your hardware to love you back, buttplug.io has always been there for you.
My goddamn desktop environment and window manager is there to do a job, not pretend to be my friend whilst burning the goddamn world down.
What the fuck is wrong with these people. Do they ever use a computer to do anything other than flirt with claude. Why can’t they just use windows instead.
while explicitly forbidding it for communication, commit messages and assets
This is absolutely the best bit of the policy, and clearly shows how much thought went into the whole thing. Everyone knows that ai generated art is shit, so that’s forbidden, ai generated summaries are just inadequate so that’s forbidden too, using a chatbot to communicate with someone is deeply fucking insulting, so that’s forbidden as well, but… uh… using the bo-bot to write your code for you is apparently a-ok! for reasons! in a project which is primarily a a collection of code! 🤠
I can’t imagine why there’s acrimony. The whole thing is entirely coherent and well considered 🤗
Looks like there might be a bit of an openai vs anthropic dick waving competition over mathematical proofs. I haven’t had time to digest all of this yet because it is a bit hard for me to read, but there are a few interesting nuggets in there such as making it clear that the ai firms treat this as a marketing exercise (no surprises there). They’re also apparently trying to obscure the amount of human assistance involved (again, no surprises).
Levent had been told by Sebastien “very little human input” had been used. This turned out not to be true. Over the course of the call, as members of their team sent Sebastien corrections and details over their internal chat, it emerged that an entire team had been working on the problem, that this was one of a number of things that was tried, that work had started on the unforced problem, that the team first set the model on easier problems, including Euler, that even the prompt that had been shown to me had been written by prompting Codex, and that an insane amount of compute had been used.
The main statement is here: https://cims.nyu.edu/~tristanb/statement.pdf
Associated stuff linked from here: https://mastodon.social/@tristanbuckmaster/117233413705701198
Do note that the author made heavy use of llm assistance for their work, and does consider it to be the future of developing mathematical proofs… this isn’t human vs ai.
His willingness to get elbow deep into the entrails of awful ai tooling is certainly much appreciated.