• 0 Posts
  • 216 Comments
Joined 3 years ago
cake
Cake day: July 9th, 2023

help-circle







  • Yeah this is a key realization that I suspect most investors aren’t privy to. With proven viable local, accessible, scalable, and energy-efficient 2TB infiniband clusters and routed multi-agentic stacks of open source models constantly nipping at their heals, achieving longterm market dominance for any of these AI developers is simply a tenuous prospect.

    The only legitimate option is to maintain a meaningful lead at the cutting edge of performance and/or offer a superior efficiency/value proposition via SLA guarantees. Beyond that, the brute force options are limited to things like short-term market manipulation (such as outbidding everyone else for existing talent pool, chip manufacturing capacity, etc) or suppression of competition via regulatory capture.

    In every case, above or below board, there is no permanent longterm global breakaway strategy, only treading water as long as investors are willing to inject enough funds to temporarily outrun market efficiency.

    Once that reality sinks in… pop.








  • It’s an extremely common small business pattern across North America. The “CEO” is usually the owner, evidenced here by absorption of non-fiduciary (unnecessary) liability of roles elevation. Only a handful of hires are traditionally qualified for their roles by education or experience. These few are usually found in client-facing roles and usually at least partially compensated by stake. Most employees are budget hires working well outside the usual expectations of their title.

    Employer abusiveness in these shops goes mostly unchecked. Wanting someone who can “grow with the company” with clearly no intent to grow them (i.e., no mentor, no reporting senior to justify the title “junior”) is code for a lot of things including this. Part of why these companies only prefer to hire younger or underqualified people is because they don’t want anyone who knows what they’re worth, how things are done better elsewhere, who might expose management incompetence, or who are simply less likely to accept abuse (because even if management hasn’t rationalized it totally, they do not intend to change).

    On the other hand, the subtle upside to lack of training and oversight is the opportunity for self-directed (and thus potentially much higher value) up-skilling and continued job-hunting, for those inclined.

    So companies like these are viable, but crucibles, and for most should only be considered a last resort.


  • (Not my field. The following is armchair speculation.)

    Why is [fusion] more economical than [solar/wind]

    TLDR — It’s not. For distributed/residential, bulk power generation, and light-duty transportation, solar has already won so decisively that fusion is not likely to catch up this century. But those aren’t usually the target applications.

    TMK, Fusion offers most of the known advantages of fission (smaller footprint, superior energy density + capacity, output that’s weather-independent and geography-agnostic, etc.) but with significantly better safety and waste profiles.

    Its versatility as a thermal source enables many industrial applications requiring temperatures difficult or impossible to achieve via electrification alone.

    The reaction itself is directly applicable to neutron production.

    There’s some even more far flung applications like outer planetary and deepspace space travel.

    And others. All to say, it’s for niche and future applications PV can’t touch.



  • While I maintain that repurposing OPFS as a measure of SSD usage by this method is unrealistic even under optimal conditions, I gotta admit I’m surprised by the lack of throttling and resource quotas.

    That is, assuming the API is enabled by default

    Typically niche-use-case and high-performance APIs that aren’t hidden behind experimental flags require user permission by default (a practice solidified by mitigations of other exploits like mining, fingerprinting, etc) so to find one open and apparently unregulated by default does seem unusual, if true.

    But if it’s gated by a flag or user permission, I don’t know why the fuck they’d bother to publish this.

    ETA: Either way, I suspect any user vulnerable to this exploit is likely already exposed to much worse from attacks that are similarly inelegant but far more reliable. Those users are already heavily profiled in many datasets. I mean, no one here… hopefully.


  • In this case, I agree that it’s a low priority patch. Here’s what you must do as an attacker. Decide for yourself whether it sounds practical for general deployment.

    Requirements: Fill OPFS storage with an arbitrarily large amount of data which at least exceeds RAM, but may require up to 60% of SSD, then lock up a thread with random reads while a worker thread hosts a model that you feed any detected latency clusters.

    Even if users don’t notice their fans maxing / battery burning / memory+storage disappearing and kill the tab themselves, this definitely will be the first tab offloaded by most browsers and OSes shortly after it is sent to the background.

    That means you have a brief window where you might get the chance to guess which sites a user is visiting. Your guess is likely far less than 89% accurate (PoCs illustrate in optimal conditions where models are often deliberately overfit to specific machine(s) and locale) outside a hyper-targeted attack, you will be lucky for coin toss levels of certainty for any guess.

    Is this an attractive attack vector?