15,619 karma · joined October 17, 2013
With the arrival of AI, many of us will need to career change anyway.
There's an article about it here https://biggo.com/news/202510160717_IRS-Fact-Graph-Public-Re...
These were artifacts from the IRS Direct File program (RIP)
Maybe your project could (re)productionize this dataset.
(you'll probably point to DIVX but that was an experiment with a terrible business model, not a technological failure)
It's right there in the article, look how proactive they're being!
You'd be better off just mugging them in the parking lot.
If a company chooses to list its stock on a blockchain instead of the NASDAQ, then, sure that could have the same value as a traditional stock assuming it confers the same rights.
Crypto tokens are just some meaningless entries on a blockchain.
> The failed leaks highlight a broader challenge: building a generalized exploit that works reliably across PHP versions and deployment configurations is difficult. The kit’s B1 layout was calculated for the official php:8.4.26-apache image with a 128 MB memory limit. Other instances like our Roundcube honeypot ran the same PHP version from a different build, with additional extensions and a 64 MB memory limit. These differences can affect heap layout and memory reuse, potentially preventing the leak from working as expected.
It sounds like it's hard to put together a generalized write-once-run-everywhere version of the exploit, so you need a human or an expensive LLM backing each attack and trying to adjust for the particulars of that target's deployment.
1) A motivated human eager for $500 and internet cred can exploit a vuln (perhaps using AI tooling to help)
2) The vuln is not easily exploitable at scale by driveby bots.
"You're absolutely right, that drug was lethal and that's on me. I'll add a note to check human toxicity for all compounds in the future. To verify the safe dosage, I'll administer a high dose and then check smaller doses until the patient survives — not guesswork, grounded, load-bearing experiments."
(10) To lower morale and with it, production, be pleasant to inefficient workers; give them undeserved promotions. Discriminate against efficient workers; complain unjustly about their work.
(11) Hold conferences when there is more critical work to be done.
(12) Multiply paper work in plausible ways. Start duplicate files.Much of the low-hanging fruit has been picked but there's still interesting experimental work happening. Just in the past few weeks LZ reported an [unconfirmed] detection of dark matter https://www.newswise.com/articles/lz-experiment-sees-surpris...
OP did not say that, has clarified his intent. At this point I think you are the one willfully misinterpreting the discussion at hand, either so you can "win" at internet pedantry, or perhaps so you can feel better about the evil panopticon you have helped build.
For the rest of us, I don't see why it's supposed to be acceptable that Google hoovers up all our data, but a horrible violate when Samsung does the same thing. ¯\_(ツ)_/¯
Yet here you are with the "WELL AKSHUALLY..." brigade.
Do you work in bigtech?
As a deliberately hyperbolic example: "We're not selling child slaves, we only offer a marketplace where clients can bid for the use of the labor of our child slaves."
The problem is the intrusive violation of privacy involved in building giant databases of personal information on every person on earth, not that someone-other-than-Google is doing it.