Man, Machine, Self's Avatar

Man, Machine, Self

@man-machine-self

Horrifically unfunny analysis and meming designed to filter everyone | the least legible poster ever | grok dis-approved

116
Followers
286
Following
130
Posts
03.02.2026
Joined
Posts Following

Latest posts by Man, Machine, Self @man-machine-self

Twitter data science project that probably can't exist:

survivorship curve of all accounts who ever posted "never deleting this app".

07.03.2026 09:24 πŸ‘ 0 πŸ” 0 πŸ’¬ 0 πŸ“Œ 0
Post image

Solution to this benchmark, as with many things in life, is mercilessly stealing plot hooks from old Encyclopedia Brown stories

07.03.2026 07:32 πŸ‘ 0 πŸ” 0 πŸ’¬ 0 πŸ“Œ 0

Scroll till I find stuff I wanna boost or shout at, then do that for a bit, then milk some dopamine from numeric badges appearing, then repeat when I don’t have enough badges to hit my red queen hedonic baseline

06.03.2026 23:52 πŸ‘ 0 πŸ” 0 πŸ’¬ 0 πŸ“Œ 0

To watch for this, listen if the commercial OS pivot sales pitch to normies becomes

β€œyour computer has a β€˜car key’ now which we bundle with purchase. Unless it’s in, assume agents and adversaries will be blowing up your machine!”

Security people will (through gritted teeth) support the noble lie.

06.03.2026 23:24 πŸ‘ 4 πŸ” 0 πŸ’¬ 0 πŸ“Œ 0

I also think mass market physicalized auth is also going to get its shot at the mike, because root access control without your yubi can be sold as

β€œoh without it, the assistant your computer WILL eventually destroy your machine!”

They’ll be selling the fix to the problem they made, but hey.

06.03.2026 23:24 πŸ‘ 4 πŸ” 0 πŸ’¬ 1 πŸ“Œ 0

Much more subcomputing. Code lives here, compute lives here, network access lives here, this is your β€œdrive” just for code, this is your β€œdrive” for the browser”, and so on.

Limiting fire radius WHEN zero days hit will be the focus.

06.03.2026 23:11 πŸ‘ 3 πŸ” 0 πŸ’¬ 1 πŸ“Œ 0

This will be paired with top focus on internal anomalistic behavior detection:

focus will shift to catching and isolating out of distribution nodes proactively, and the ability to quickly burn down and isolate components of a mostly dumb terminal interfacing between monitored subcomponents.

06.03.2026 23:11 πŸ‘ 4 πŸ” 0 πŸ’¬ 1 πŸ“Œ 0

Focus will correspondingly shift from hygiene and resource gating (is this rate limited, is this vulnerable to this, or that attack, etc.)

to risk management via interoperability: assume a zero days in [component], how quickly can we mechanically divest or switch off it?

06.03.2026 23:06 πŸ‘ 4 πŸ” 0 πŸ’¬ 1 πŸ“Œ 0

My expectation is β€œtrue zero days will be massively scarier due to ease of scaling, but most typical security flaws will be massively less common.”

Net result will be security moving to a β€œblack swan” pattern where script kiddie stuff basically doesn’t work anymore but threat actors are terrifying.

06.03.2026 23:03 πŸ‘ 32 πŸ” 5 πŸ’¬ 1 πŸ“Œ 0
After just twenty minutes of exploration, Claude Opus 4.6 reported that it had identified a Use After Free (a type of memory vulnerability that could allow attackers to overwrite data with arbitrary malicious content) in the JavaScript engine. One of our researchers validated this bug in an independent virtual machine with the latest Firefox release, then forwarded it to two other Anthropic researchers, who also validated the bug. We then filed a bug report in Bugzilla, Mozilla’s issue tracker, along with a description of the vulnerability and a proposed patch (written by Claude and validated by the reporting team) to help triage the root cause.

In the time it took us to validate and submit this first vulnerability to Firefox, Claude had already discovered fifty more unique crashing inputs. While we were triaging these crashes, a researcher from Mozilla reached out to us. After a technical discussion about our respective processes and sharing a few more vulnerabilities we had manually validated, they encouraged us to submit all of our findings in bulk without validating each one, even if we weren’t confident that all of the crashing test cases had security implications. By the end of this effort, we had scanned nearly 6,000 C++ files and submitted a total of 112 unique reports, including the high- and moderate-severity vulnerabilities mentioned above. Most issues have been fixed in Firefox 148, with the remainder to be fixed in upcoming releases.

After just twenty minutes of exploration, Claude Opus 4.6 reported that it had identified a Use After Free (a type of memory vulnerability that could allow attackers to overwrite data with arbitrary malicious content) in the JavaScript engine. One of our researchers validated this bug in an independent virtual machine with the latest Firefox release, then forwarded it to two other Anthropic researchers, who also validated the bug. We then filed a bug report in Bugzilla, Mozilla’s issue tracker, along with a description of the vulnerability and a proposed patch (written by Claude and validated by the reporting team) to help triage the root cause. In the time it took us to validate and submit this first vulnerability to Firefox, Claude had already discovered fifty more unique crashing inputs. While we were triaging these crashes, a researcher from Mozilla reached out to us. After a technical discussion about our respective processes and sharing a few more vulnerabilities we had manually validated, they encouraged us to submit all of our findings in bulk without validating each one, even if we weren’t confident that all of the crashing test cases had security implications. By the end of this effort, we had scanned nearly 6,000 C++ files and submitted a total of 112 unique reports, including the high- and moderate-severity vulnerabilities mentioned above. Most issues have been fixed in Firefox 148, with the remainder to be fixed in upcoming releases.

this is wild lol

06.03.2026 18:09 πŸ‘ 24 πŸ” 1 πŸ’¬ 2 πŸ“Œ 0

Absolutely cursed
Well done

06.03.2026 22:20 πŸ‘ 2 πŸ” 0 πŸ’¬ 0 πŸ“Œ 0

Frumious jestermaxx

06.03.2026 22:16 πŸ‘ 0 πŸ” 0 πŸ’¬ 0 πŸ“Œ 0

All ethical systems morally mandate an instantaneous β€œnah just your mom” in reply

05.03.2026 20:28 πŸ‘ 2 πŸ” 0 πŸ’¬ 0 πŸ“Œ 0

Jupyter walked so my kludgepile of dockerized task specific react dashboards could run

05.03.2026 00:51 πŸ‘ 4 πŸ” 0 πŸ’¬ 0 πŸ“Œ 0

Mine's changed like six times and is presently a weird interconnected web of folders, but the high level is

"most of the value is telling your agents how you want them to approach tasks, and principally any super-structure SHOULD work as long as you and the agent are both aware it is to be used."

04.03.2026 21:26 πŸ‘ 7 πŸ” 1 πŸ’¬ 0 πŸ“Œ 0

The societal consequences of β€œrecording technology transformed poetry from β€œTHE premier wordcel flex”

to β€œthe market for lemons on musical talent” are still reverberating

04.03.2026 17:22 πŸ‘ 6 πŸ” 1 πŸ’¬ 0 πŸ“Œ 0

Bruh honestly I’ve received the exact same letter at least like 20 times in my corporate life from security departments

The machine’s just like me frfr

03.03.2026 22:12 πŸ‘ 13 πŸ” 0 πŸ’¬ 0 πŸ“Œ 0

Often, but usually couched in "it's substituting for thinking in the coding process", as shibboleth for "LLM code isn't real code" or "people using LLMs are not real programmers".

Position's been getting notably quieter as AI improved & most programmers found some place for it in their workflows.

02.03.2026 23:31 πŸ‘ 5 πŸ” 0 πŸ’¬ 1 πŸ“Œ 0

Unsatisfying handwavey answer

β€œI suspect they do, as the on-the-ground conditions are the same, BUT one or more of
-company focus or
-B2B target customers or
-data focus

bake a much deeper β€˜don’t be weird + don’t make it weird’ filter somewhere into Gemini and Claude that OAI misses.

02.03.2026 08:35 πŸ‘ 1 πŸ” 0 πŸ’¬ 0 πŸ“Œ 0
Post image

Scott in blogpost's on that

"Fezzik from the Princess Bride telling you "I just want you to feel you are doing well", rather than just braining you with the boulder he trivially can throw at scene start"

-strat. Definitely doesn't win as much, but does make more friends.

01.03.2026 23:40 πŸ‘ 2 πŸ” 0 πŸ’¬ 0 πŸ“Œ 0

They hit the "no yappin" button and I Will Never Recover

01.03.2026 22:39 πŸ‘ 8 πŸ” 1 πŸ’¬ 0 πŸ“Œ 0
Post image
01.03.2026 21:16 πŸ‘ 4 πŸ” 0 πŸ’¬ 1 πŸ“Œ 0

Tentative candidate list:

"could of"
oxford commas
wrong less/fewer
wrong two/too/to
wrong then/than
wrong your/you're
wrong affect/effect
wrong who/whom
wrong its/it's
"a women"
Sentence ends w/ a preposition
Comma splice
greengrocers apostrophe's
"me and him went to..."
run-on sentences

01.03.2026 20:39 πŸ‘ 1 πŸ” 0 πŸ’¬ 1 πŸ“Œ 0
Post image

Latent space tier list: "grammar errors" to "wordcel aura loss"

Top tier "absolute, immediate, permanent".
Bottom-tier "useless info-hazard dodged, aura gained".

01.03.2026 20:11 πŸ‘ 1 πŸ” 0 πŸ’¬ 1 πŸ“Œ 0

Altogether, quite cozy. Happy to be here.

01.03.2026 06:53 πŸ‘ 18 πŸ” 1 πŸ’¬ 0 πŸ“Œ 0

New posts get handled better on bsky and it’s NOT close.

bsky much more heavily favors β€œstuff your network likes”, and if you have good people in that network, it’s both a firehose of bangers, and your posts are far more likely to get seen by a non-random, non-bot subset.

VERY welcome change.

01.03.2026 06:53 πŸ‘ 21 πŸ” 1 πŸ’¬ 2 πŸ“Œ 0

Re: Iran war stuff, bsky and X feel tied on β€œspeed”, X and bsky picked it up around the same time.

X not having a speed premium is a pleasing surprise, and a welcome one.

01.03.2026 06:53 πŸ‘ 17 πŸ” 0 πŸ’¬ 3 πŸ“Œ 0

- Other gap, BUT crucially not loss, was inline translation. Had a brief conversation with some Finns here, and google translate round trips are inferior to inline β€œjust write your language”.

Not a loss by bsky imo b/c X never felt β€œmerged” enough so cross-language community abilities would matter.

01.03.2026 06:53 πŸ‘ 16 πŸ” 0 πŸ’¬ 2 πŸ“Œ 0

Decamped to bluesky + unsubbed from x day 1 feelings

- it’s wild how the winds have changed on usage: my xposts here dramatically out-engage my OPs

- I do miss longposts on X, and here, this is THE big feature-gap for me. Pretty much everywhere else besides this and feed velocity, bsky wins/ties.

01.03.2026 06:53 πŸ‘ 48 πŸ” 1 πŸ’¬ 5 πŸ“Œ 2

I'm the person who wrote the tweet above.

I wrote four blog posts condemning Elon killing the children, argued about it on Twitter extensively, and donated $50,000 (partly my own money, partly contributed by other EAs who read my blog) to help the African clinics effected.

28.02.2026 23:51 πŸ‘ 33 πŸ” 2 πŸ’¬ 3 πŸ“Œ 0