behindsight

I presume the poster submitted this article in light of the recent AI safety discussions taking place, but as for this particular incident I haven't found an actual confirmation that $100M worth of inference was given out to the HuggingFace community.

This statement was also months prior to the acquisition by Nvidia, which again I was interested in seeing if they would still pursue this

Comment · 1 month ago

and the actual tweet from the HuggingFace CEO back in July

> In the spirit of transparency, here’s what I asked @OpenAI:

> • Radical transparency: let’s release the traces from the “rogue” agents so the entire research community can study what happened.

> • More capabilities for defenders: let’s commit $100M in compute from OAI to help the Hugging Face community build powerful cyber defenses with the best open and closed models.

> The first autonomous agent cyberattack is an unprecedented event. It deserves an unprecedented response!

https://x.com/ClementDelangue/status/2081056675558195657

Comment · 2 months ago

I agree as long as you are very upfront about it being a learning/stream of conciousness blogpost, then it should be fine to watch how someone's learning journey progresses.

The author does outline the steps they take to make it clear

> Third, I try to make it clear on my blog who I am and what my credentials actually are. Even if it’s not explicitly described in the post, I have my real name and resume available on my /about page, so I don’t think a careful reader could be easily fooled into thinking I’m an expert on 19th-century England or space physics or LLM economics or anything like that.

If however that part is hidden and it is some confidently incorrect or pseudo guru type of post that is polluting the web with misinformation, then that is a different story.

Maintaining a high signal-to-noise ratio is important to some people, and they may completely disregard the musings of people outside their field of expertise.

Comment · 2 months ago

OMP has this, it's called "/shake" where bloat from tool calls and such is turned into an artifact ref instead of remaining in the context.

There are other pruning or compaction strategies you can configure too.

You can also use "/btw" to have side tangent conversations with the current context but with the benefit that it will not bloat your current context after the tangent is done.

I wish other harnesses were prioritising this sort of flexibility with context management, but they're likely more incentivised on optimising their cache rates

https://github.com/can1357/oh-my-pi

Comment · 3 months ago

Wasn't it stated as being in "preview" prior to this?

If implementing non-trivial tasks on a preview model surely there is some anticipation of it not being the final stable release?

Unless you mean they should have appended a "preview" suffix on the endpoint for extra good measure?

Comment · 3 months ago

relevant xkcd: https://xkcd.com/2347/

but on a serious note it is a bit more than some guy's list, it's more of an initiative that was started by the Mozilla Foundation and is used by:

- browsers: Firefox, Chrome, Opera...

- password managers, Let's Encrypt, cURL

- Cloudflare

just to name a few.

Though yeah there have been privacy concerns and problems with projects that use outdated versions of the list outlined in Brave's paper (no affiliation):

> We present the first large-scale measurement study of how the public suffix list is used by open-source software on the Web and the privacy harm resulting from projects using outdated versions of the list.

https://brave.com/research/privacy-harms-of-public-suffix-li...

Comment · 3 months ago

the main reason they mentioned [1] for radicle.network is because their old domain radicle.xyz was blocked in some places by some lists that they think was because it may have hosted certain UGC that triggered some flags.

> Content about Radicle (explainers, guides, download links, blog posts) which is under control of the Radicle team. We will use radicle.dev for these purposes.

> Content on Radicle (repositories hosted on practically any node on the network) which the Radicle team has only very little control over, accessible via Radicle Explorer. Going forward, our deployment of Radicle Explorer will not be hosted on app.radicle.xyz anymore, but instead it will be hosted at radicle.network.

> The idea is of course that if there are complaints about or issues with radicle.network in the future, we hope that radicle.dev stays largely unaffected and people can continue to inform themselves about Radicle and learn how to set it up.

On a semi-related note, this is a good time to remind anyone that hasn't yet heard of the Public Suffix List (PSL) [2][3] to make sure you put your domains that may be hosting UGC in the form <usercontent>.<yourdomain>.<tld> (ie: eTLDs) on that list so browsers and other block lists are aware that the user provisioned subdomains are UGC and not from your site so it properly isolates cookies/site grouping and won't flag your entire domain as malicious.

1: https://radicle.dev/2026/04/23/domain-move

2: https://en.wikipedia.org/wiki/Public_Suffix_List

3: https://github.com/publicsuffix/list

Comment · 3 months ago

The blog's visual design is quite pleasant to read.

However I am a bit confused by the author's remarks

> I do NOT EVER consent to ANYTHING being done in regard to AI in my name.

> With newer sites like Bio Link and FediProfile I don't see the usefulness of Gravatar. If anything, I think it now has ANTI-features.

It's conflicting to mention Bio Link with the author's ideology since it quite prominently has:

- AI assistant to answer visitor questions based off of your "links, descriptions, posts, and a short knowledge base"

- AI site builder

Comment · 3 months ago

thank you so much for the clarification!

Yes, you're correct. The vouch button doesn't appear when viewing the thread context containing the `[dead]` comment. It only appears when clicking the specific comment directly via its permalink (or comment ID). I may have misremembered being able to vouch with the context to the comment being visible.

Thanks as always dang ^_^

Comment · 3 months ago

I have vouched a couple (~3-5) benign comments a while back and now I no longer have a vouch button for comments.

I don't know if the vouch threshold has increased or if the mods have removed my ability to vouch for other comments entirely.

Wondering if it was my good faith attempt to inform a user of their comments being auto-flagged [1] before I had any context that they were supposed to be persona non grata.

I can still vouch submissions though

1: https://news.ycombinator.com/item?id=46381180

Comment · 3 months ago

very well said, and I have been rooting for the team big time!

if you have an alliance hub for discussions with those also building open infrastructure tooling, please let me know!

have already been in the Mozilla AI discord since last year and had a great time being one of the 2 external participants during the name brainstorming for renaming any-llm ^_^

Comment · 4 months ago

Project Glasswing is already a thing, and the other labs have started their own initiatives too if they want to collaborate and work on securing closed-source software.

Still not addressed the moral clarity point being brought up, nor the ramifications of the Linux Foundation choosing which closed source projects to focus on and alienating their mission statement.

Again, your idea is noble but why should the Linux Foundation be saddled with it when those other options exist? OSS needs their focus as their mission outlines.