When in solid form even the smallest amount can convert the whole batch to the much less effective version.

Blog Post: https://runta.com/blog/introducing-frontierharness-eval/

The tasks and methodology: https://github.com/runta-dev/frontier-harness-eval

>paintboth1234 uBO Team wrote:

>The project is FOSS. Anyone else who wants to deal with this disgusting site is free to make pull requests with working solutions themselves.

[0] https://www.reddit.com/r/uBlockOrigin/comments/1vgcjg5/about...

>GpuRamDrive

>Create a virtual drive backed by GPU RAM.

https://github.com/prsyahmi/GpuRamDrive

Fork with AMD support:

https://github.com/brzz/GpuRamDrive/

I always interpret the rule [0] "Otherwise please use the original title, unless it is misleading or linkbait; don't editorialize." as applying to stories like this one.

Adding the words [in mice] would not only be the acceptable exception the rule is referring to, but probably necessary. This would align the title properly with the article contents and avoid giving people false expectations about human results.

[0] https://news.ycombinator.com/newsguidelines.html

An open source developer had disabled pull requests and other operations on their repository because they were fed up with harassment. They gained a reputation for being extremely disagreeable at that time. I was unaware of this and simply assumed that was how the project worked. I had to do some minor investigative work to find their email address and I sent them a polite, low pressure email with my unsolicited patch and made it clear it was fine to use it or ignore it. They thanked me, explained the situation, even apologized for the difficulty, and said locking things down was the only way they knew to cope with the situation, and of course applied the fix.

[0] https://github.com/Roadmvn/C-Full-Offensive-Course/blob/main...

An interface like above to sort things would probably be quite helpful as well.

[0] https://peter.sh/experiments/chromium-command-line-switches/

Put the parameters into the url so searches can be bookmarked, like zip codes, terms, filters, and other aspects can be shared easily as well.

Description search both include (like i7, 16GB) which is good for electronics and exclude for example exclude "repair" or "needs repair" which is helpful for many things.

Category specific filters, vehicle millage range, year

Keywords classification filters like pickup, delivery, payment methods, how many days you have to pay if known, etc.

You are probably already thinking along these lines for some of them, just an encouragement to implement. Yes categorization/filters can be fuzzy(commas, which word or plurals used, etc), so feel free to put the [beta] or [experimental] tag until a recipe that gets most of the stuff works.

Thanks for building this, I bookmarked it and already shared it with a few friends.

This is answered from their Project Roadmap over on Github[0]:

Recently Completed: macOS (beta)

Under Development: MLX support

[0] https://github.com/lemonade-sdk/lemonade?tab=readme-ov-file#...

https://output.jsbin.com/gihukasezo/

or

https://jsfiddle.net/9kLsv3xm/latest/

or

https://pastebin.com/Sa8RmzcE

I think the *BSD are also good, at least from an educational standpoint, with their relative simplicity and low system requirements. Since there is a lot of integration making a from scratch distro might take less material, but it could be supplemented with more in depth/sysadmin exploration.

This causes a fatalistic chain where the video has a captcha, and if you don't answer it in 5-15 seconds it goes to the next in the playlist and the process repeats. This turbo charges uncontrollably down the series of videos.

The solution is within seconds remove the &pp= (or go back a few pages and do so) this gives you as much time as you need to solve the captcha. Or remember to copy the search result link instead of clicking on it and clean it up.

I wrote to youtube about this bug where playlists don't wait for you to answer the captcha and never heard back from them, which is what I expected, but figured I'd try.

[0] https://www.usenix.org/conference/nsdi22/presentation/reda

[1] https://www.youtube.com/watch?v=sTT_XPfYudg

    /* Dead subpixel (Thanks M) */
    .content[role=main]:before {
        content: "";
        position: fixed;
        top: 126px;
        left: 242px;
        width: 1px;
        height: 1px;
        background: #f0f;
        z-index: 9999;
    }

    /* Hair */
    .content[role=main]:after {
        content: "";
        position: fixed;
        top: 150px;
        right: 150px;
        width: 140px;
        height: 200px;
        border-radius: 50%;
        box-shadow: 2px 0 rgb(60, 24, 24, 0.3);
        transform: skewX(-30deg) scale(0.6);
        pointer-events: none;
        z-index: 9999;
    }

    .thing.comment[id*=c] {
        transform: rotate(1deg);
        margin-top: 30px !important;
    }

    .comment p a{
        font-family:Comic Sans MS, Impact,serif;
    }

Everything Is Fields By David Tong (Early 2027)

Six Math Essentials By Terence Tao (November 2026)

The Proof in the Code By Kevin Hartnett (June 2026, Preorder Available)

[0] https://www.quantabooks.org/

Since with the Microsoft extension, it was just waiting until enough examples were woven into the discussion to overcome the back and forth that was preventing "biting the bullet".