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.
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.
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.
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.
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 ^_^
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.
been cranking on this too but not just for snark but for spam/scam heuristics too.
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
On a similar vein is the "argument from fallacy" aka fallacist's fallacy. [1]
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.
It's explicitly called out as excluded in the blue info bubble they have there.
> 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.
While it's commendable, the reality is they should have already "figured out" how to play the system and just farmed the reward points from credit cards and immediately pay them off without incurring any interest.
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.
Out of curiosity, do you have watch history enabled/disabled?
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)
sidenote: just a heads up that I tried emailing you recently to let you know that you might want to contact the HN mods to find out why all your comments get set to dead/hidden automatically.
Your account might have triggered some flag sometime back and relies on users vouching for your comments so they can become visible again.
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
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...