neeksHN

Not for Workspace users. Still pinned to degrading 3.1 Pro they've been consistently tuning for the worse since Feb 2026

They need to find a way reinvent "channel surfing". Discovery via "flipping" has lead me to watch things I'd otherwise never would click in an app interface.

I've always been surprised that Netflix, and other services, don't create "live channels" (e.g "The Office" channel) of their libraries.

Super smooth on desktop, but a horrible experience on my handheld device.

I've never had a good mobile experience on any scrolljacking site, even the ones done by Apple or Google.

And you're engaging in some kind of ad-hominem fallacy -- refute the claims with facts, don't attack the messengers

I've gotten around this by disabling cookies and javascript on a per site basis.

These sites require blocking both javascript and cookies: NYT, Washington Post, MIT Technology Review, Wired, National Geographic and LA Times

These sites require only blocking cookies: Medium, Scientific American, Quartz, The Atlantic, Bloomberg and Harvard Business Review

The one downside is when the linked article is an "interactive feature/story" and it's a site which requires blocking javascript. It's an annoyance to temporarily allow such an article's source, but I'd rather have to deal with that than reaching their "free limit".

I'd much prefer if submitters choose more user-respecting sources, but until then I refuse to feel guilty over stopping these intrusive sites and their dark patterns.

The only source I wish was permanently banned is Financial Times -- every article is paywalled and provides no snippet.

Do you assume all HN users would reach the paywalls' read-limits through organic everyday use?

I felt forced to disable cookies and javascript on the following sites just after exclusively clicking on links submitted to HN: NYT, Medium, Washington Post, Bloomberg, MIT Technology Review and Harvard Business Review.

I'd prefer if submitters choose more user-respecting sources, but until then I refuse to feel guilty over stopping these intrusive sites and their dark patterns.

Chromium is the only app I compile that still uses Python 2, but I do know Google utilize's it in many repos. I'd love to read anything that would cover how they're planning to handle EOL. Will they maintain a legacy hard-fork, upgrade to 3 or ditch Python for a different scripting language for their build systems?

I'm always left perplexed when projects like these don't make F-Droid distribution a priority over the Play store. Regardless, I'll check it out if it ever finds its way to F-Droid.

As a catch-all you could start regexing messages' content and deny the abuser if one of their common patterns matched -- you'll still be in a never-ending game of cat and mouse.

There's also the possibility of false positives, which might mean some of your users' beign messages get rejected. Over time you could event start to integrate ML and NLP, which would hopefully limit the amount of manual oversight needed to detect spam in the future

> At trial, prosecutors must introduce credible evidence that is sufficient to prove each defendant guilty beyond a reasonable doubt, to the unanimous satisfaction of a jury of twelve citizens.

> This case was investigated with the help of the FBI’s cyber teams in Pittsburgh, Philadelphia and San Francisco and the National Security Division.

Assuming this never goes to trial, could the DOJ ever be compelled to release the evidence used to attribute the defendants? Or will it remain "pending arraignment" indefinitely?

I'd love to see an in-depth technical analysis of how they were able to substantiate these allegations

+1, very much looking forward to that Show HN.

Directus is always at the top of self-hosted CMS lists, but one of the reasons I avoid it and other PHP self-hosted headless CMS solutions is due to the difficulties(tech debt) of automating dev environments and CI/CD pipelines across different distros and OSes.

I would have possibly given Directus a spin if it didn't have hard dependencies on the following PHP system extensions: curl, gd, finfo, pdo_mysql and mbstring. Not to go too off topic, but I wish PHP extensions could be installed via Composer and Packagist (similar to how NPM handles native modules).

It'd be rather refreshing if one of the headless CMS PaaS solutions could follow an open model similar to WordPress/Gitlab