_jzlw

Didn't Mozilla basically say they would support it if Google does? Mozilla doesn't have the resources to maintain a feature that no one can actually use; they're barely managing to keep up with the latest standards as it is.

That music when you click "int" is awesome. Reminds me of the good ol' days of keygens.

Looks like it's a reskin of an older version of awesome-selfhosted, coupled with advertisements. At least they credited it appropriately in the footer, but I would suggest just looking at the original repo instead (or its web version):

https://github.com/awesome-selfhosted/awesome-selfhosted

https://awesome-selfhosted.net/

Slightly different, but here's an actually useful site:

https://www.trackawesomelist.com/awesome-selfhosted/awesome-...

Smoke signals in space. I love it.

> keeps your release process clean, reproducible

How does it do either of these two things, exactly?

> and locked down

It doesn't lock anything down, in fact it only serves a purpose if your CI isn't locked down. Your npm token should not be visible to anything except npm. If it is, then you've got far bigger problems.

At best, this only serves as a reactionary warning / damage control in case your CI is compromised, i.e. after you've already been pwned. Which is all well and good, don't get me wrong, but pretending it "protects" you from anything is giving a false sense of security.

I dunno, this reads overwhelmingly like the parents trying to deflect responsibility. Cries for help ignored, the thing about the medication, been going on for five years, and he mentioned he was reading other forums too, so it's not like it was just chatgpt egging him on or something. I don't see how you could even pretend this is chatgpt's fault and not the parents'.

Didn't Boy Scouts start letting girls in years ago? Why are they whining about it now.

Google's internal issue tracker, Buganizer (which the Chromium Issue Tracker is based on), refers to everything as a "bug". It's confusing, yeah. You get used to it.

This is still a problem with AVIF, too. Image viewers that support the format often don't support animated AVIFs, and even GitHub still for some godforsaken reason treats .avif files in a repo/PR as binary files instead of images. I think Discord just recently started supporting AVIFs, so that's progress.

PSA: You can run one git command and ignore this change and associated drama entirely. I don't care which you prefer, but let's not pretend like main "won" when sticking with master is as easy as:

    git config --global init.defaultBranch master

I acknowledge that Russian propaganda on Twitter/X is a problem, but that does NOT justify Elon up and deciding to disclose everyone's real location without notice or consent.

I know someone IRL who moved to another country to escape their stalker / abusive ex. This would absolutely put their life at risk. Even a country name, combined with other information, can be used to pinpoint someone's identity or precise location.

This move is reckless, inappropriate, and possibly even illegal in the EU. Honestly it should be (and used to be) unthinkable for a platform to do something like this, and it's insane that you believe otherwise. Frankly you should be ashamed of yourself for suggesting it's ok for a tech company to suddenly leak its users' PII.

Not to mention the propaganda posters can just use a VPN, so in trying to stop Russia you've only succeeded in giving up your own privacy and putting innocent people at risk. Well done.

Um, that sounds like a massive privacy breach and could potentially help with doxxing and stalking.

Edit: It's also visible for private accounts.

From a previous thread:

https://support.google.com/mail/answer/15604322?sjid=1029580...

> When smart features are on, your data may be used to improve these features.

> sorry we got caught violating your license

Oh, please. Do you not understand that OP shouldn't have needed to submit a takedown request in the first place? Add the repos' license files (and NOTICE files too, if Apache!) to your site like you're legally required to, or the next time this happens it won't be a HN post; it'll be a lawsuit.

Seriously, you're playing with fire and it's not doing anything to help your brand. People already look at Vercel with disdain, and this is exactly why.

They're claiming that these options allow Google to use your data to train its AI, but that's not what it says at all. Where are they getting that idea from?

Hardly something you can carry. Doesn't even look easy to roll around, and it definitely doesn't look comfortable to ride. Better off just buying an e-bike...

> have refused a copyright request to stop using this content without following the license

Of course they have. They're a company profiting off of people's work as a means to promote their service. Companies get away with this sort of thing all the time because they know that most of the time, just like in this instance, no one's going to actually enforce their license and sue them.

That said all they really need to do is copy the license text. Kindof strange they didn't bother to do that. They're already automating copying readmes off GitHub; skipping the license file seems like it puts them at unnecessary risk.

Great writeup.

Can't believe it's been eight years since WASM was introduced, and it still can't do basic stuff like proper multithreading. We shouldn't need to screw around with web workers and SharedArrayBuffers. Wasn't the whole point of wasm to break free from the shackles of JS so that we can write desktop-grade software that runs in the browser?

The goal isn't to make that specific information accessible; it's to get rid of all refusals across the board.

Going after the most extreme cases has the effect of ripping out the weeds by the root, rather than plucking leaf after leaf.

It seems like they ought to have at least clarified the context, though. "Large integer precision error in Bash command output rendering" doesn't mean anything to anyone. If anything, it sounds like a bug in Bash.