Hacker Newsnew | past | comments | ask | show | jobs | submit | wut42's commentslogin

Which site ? seems to work fine for me.


And Australia 2023 outage of Optus, also BGP related: https://en.wikipedia.org/wiki/2023_Optus_outage


Another Down Detector bullshit article.... it's getting incredibly tiring. Every time a provider (Phone, Internet or even cloud services) suffer issues ALL of them are reported as down.


Who downs detector the down detector? Or even better who is the redundancy for dd if the site is actually up?


Uh oh big broken now


That could track but people in the GitHub issue ( https://github.com/stylus/stylus/issues/2938#issuecomment-31... ) have found that no "other" version of Stylus has been released.


Amateur hour all around in that thread. I can't believe that people are actually, unironically recommending that you use a mutable git tag reference in package.json when they should be using a tamper-proof git SHA instead.


It may simply be Github and NPM going nuclear and just flagging everything just in case


Since the Github issue is turning into an unusable mess and I am currently experiencing emotions I don't have to unleash here...

There is an interesting comment by one of the older maintainers of stylus, Panya [1]. Taking this at face value, they claim to have published some malicious packages for research purposes about dependency confusion [2] (their link). This also fits with the comments of a few people claiming to be security researchers, [3] and [4], which at least say the same and point to three malicious packages published by Panya.

Based off of that, my own personal interpretation and simplest thesis is that Panya released some packages with questionable code. This triggered some security mechanism in npm and that system yanked packages they were a contributor of [5], because the account looked compromised or otherwise malicious. And then pipelines went red.

If this was an actual malicious act, or curiosity about security and security responses getting a fairly nuclear security response, I don't know. You need to apply your own security reasoning to this -- if you even want to trust this comment :)

I just wanted to collect the interesting comments in a place, because that ticket is getting impossible to navigate.

1: https://github.com/stylus/stylus/issues/2938#issuecomment-31...

2: https://medium.com/@alex.birsan/dependency-confusion-4a5d60f...

3: https://github.com/stylus/stylus/issues/2938#issuecomment-31...

4: https://github.com/stylus/stylus/issues/2938#issuecomment-31...

5: https://github.com/stylus/stylus/issues/2938#issuecomment-31...

5, also: https://github.com/stylus/stylus/issues/2938#issuecomment-31... (thanks to the sibling comment, I couldn't find that anymore)


Could be! Other comments (~~can't find them now as the issue got full of useless comments~~ e.g. https://github.com/stylus/stylus/issues/2938#issuecomment-31...) also noted that the GHSA bot have nuked a lot of other npm packages since days or weeks in the same fashion, so it could also be an AI scanner going full full nuclear.


Agree it would be nice if people would stop posting "help! how can I fix this?" and "I fixed it by doing X", they were valid comments at the beginning, but now more than half of the comments are just these two


Well, how else do people who never read and understood the tools they are using get help? Coding boot camps only teach so much lol.


The package was pulled at: 2025-07-23T03:03:01.239Z

And the GHSA advisory: 2025-07-23T03:03:56Z

So the GHSA was released after the pull (by a minute).


already exists, xsel and xclip does that, iirc.


clippy is a bit different from these - rather than requiring manual flags for MIME types, it automatically detects the content type. The idea is to make the CLI's copy/paste feel as intuitive as the GUI's.

I might tackle Linux (and Windows) at some point, but contributions are definitely welcome!


I don't see how you can "protect" against a large language model that cannot do browsing.


TMZ is a very respectable publication if you compare it to Entrevue...


CGNAT does not means unroutable IP, it just means you would only have assigned a small range of ports on a routable IP with others.


If you have CGNAT, the IP on your router's external interface is unroutable.

Just like how when you do NAT for your home network, your devices get assigned non-routable private use only address space.

Unroutable meaning not publicly routable. Of course you can route traffic through your own LAN to your Internet gateway.


Hetzner is famously notorious for this, but not enough for publications to pick up this. So by your definitions, YEARS of people talking about their experiences with this is nothing?


Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: