who's your registrar? that sounds like GoDaddy levels of pricing.
Cloudflare, porkbun and others can get you a .com for $10-$11/yr
207 karma · joined February 6, 2019
Cloudflare, porkbun and others can get you a .com for $10-$11/yr
Cloudflare's equivalent for that is instead called "workflows" [1] for those resumable/retryable multi-step functions for durable execution.
(naming is kinda confusing, I had to build out a redundancy system across all these providers)
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
> 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!
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.
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
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?
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...
> 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
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
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 ^_^
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
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 ^_^
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.
It's a holdover from previous posts where there were more clearly defined deprecations.
but yes, in this case it's more of a behavioural change of defaults, so they just picked the closest vaguely mapped retired/deprecations tag.
"retired" is probably a followup to functionality that was "deprecated".
I agree "breaking" would be clearer
> It is in the works. The billing team has been sprinting to fix a lot of debt in this area. I don’t have a date.
it's something I feel is finally viable to combat at zero cost to the user.
This plus webmcp would allow it to serve as a form of automod too on websites that you authenticate with (imagine a world where your social media profile has an automod of its own powered locally. can use this to steer your feed or to mute/block/moderate as needbe). Even without WebMCP I have been working on making it autodetect html elements and extract UGC (comments/threads..etc) automatically to moderate (since my initial tests with a small group found some websites with frequent UI changes would break if hardcoded or if they did a lot of AB testing)
Even better, the concept would allow you to also use it to hide certain spoilers (imagine sports or new movies that just came out and you want to not have to hide away from all socials).
didn't find any contacts on your new HN account, but in a few weeks will be able to reach out to you with it fleshed out. :)
We have a community of nearly 14k that we will distribute this to
I wanted to make FOSS codegen that was not locked behind paywalls + had wasm plugins to extend it.
Essentially if you dismiss someone's argument as false just because it may have had a fallacy within it, that reasoning is itself a fallacy.
Some fallacy-seeking people ironically ignore this and just dismiss anything when they have the "gotcha, you made a fallacy therefore everything you said can be concluded as false" moment.
> Fast mode usage is billed directly to extra usage, even if you have remaining usage on your plan. This means fast mode tokens do not count against your plan’s included usage and are charged at the fast mode rate from the first token.
You get a good credit score and still live within your means while also getting additional points + bank covering any fraudulent activity if the card got stolen.
Of course this method probably won't work for people that feel they would rather just cut themselves off from temptation fully or those without access to banking systems, which I sympathise with.
I found the feed with it enabled is much better than disabled and I have it finetuned to be more in line with the niches I care about.
I am also very proactive with marking channels or content I don't prefer with the "Not interested" or "Don't recommend channel" as well as going through and pruning any content I don't want from my watch history directly.
It's not perfect but it's orders of magnitude better than my logged out or watch history disabled account (though not sure if they have since updated it to not show anything at all)
Your account might have triggered some flag sometime back and relies on users vouching for your comments so they can become visible again.
C# Native AOT gets rid of the JIT and gives you a pretty good perf+memory profile compared to the past.
It's mostly the stigma of .NET Framework legacy systems that put people off, but modern C# projects are a breeze.
I've been building in my spare time a spam/scam blocking extension and was also playing around with the experimental in-browser LLM feature for this (alongside Aho–Corasick, Naive Bayes and other classifiers)
It's great to see more people tackling this head on, kudos
> If a malicious website reads the clipboard, what good is knowing an arbitrary password with no other information?
Even if assuming unique username+url pairings, clipboard history can store multiple items including emails or usernames which could be linked to any data breach and service (or just shotgunned towards the most popular services). It's not really a "no other information" scenario and you drastically reduce the effort required for an attacker regardless.
> If you're talking about a malicious desktop app running on the same system, it's game over anyway because it can read process memory, read keystrokes, etc.
The app does not have to be overtly malicious, AccuWeather (among others) was caught exfiltrating users' clipboard data for over 4 years to an analytics company who may or may not have gotten compromised. Even if the direct application you are using is non-malicious, you are left hoping wherever your data ends up isn't a giant treasure trove/honeypot waiting to be compromised by attackers.
The same reasoning can be used for pretty much anything really, why protect anything locally since they could just keylog you or intercept requests you make.
In that case it would be safer for everyone to run Qubes OS and stringently check any application added to their system.
In the end it's a balancing act between convenience and security with which striving for absolute perfection ends up being an enemy of good.
> Sidenote: Most password managers I've used automatically clear the clipboard 10-15s after you copy a credential.
That is true, good password managers took these steps precisely to reduce the clipboard attack surface.
Firefox also took steps in 2021 to also limit leaking secrets via the clipboard.