Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
_jzlw
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
31.
▲
by
_jzlw
11mo ago
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.
32.
▲
by
_jzlw
11mo ago
That music when you click "int" is awesome. Reminds me of the good ol' days of keygens.
33.
▲
by
_jzlw
11mo ago
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):
34.
▲
by
_jzlw
11mo ago
Smoke signals in space. I love it.
35.
▲
by
_jzlw
11mo ago
> 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 np
36.
▲
by
_jzlw
11mo ago
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 l
37.
▲
by
_jzlw
11mo ago
Didn't Boy Scouts start letting girls in years ago? Why are they whining about it now.
38.
▲
by
_jzlw
11mo ago
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.
39.
▲
by
_jzlw
11mo ago
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.
40.
▲
by
_jzlw
11mo ago
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 --glob
41.
▲
by
_jzlw
11mo ago
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 e
42.
▲
by
_jzlw
11mo ago
Um, that sounds like a massive privacy breach and could potentially help with doxxing and stalking. Edit: It's also visible for private accounts.
43.
▲
by
_jzlw
11mo ago
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.
44.
▲
by
_jzlw
11mo ago
> 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 yo
45.
▲
by
_jzlw
11mo ago
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?
46.
▲
by
_jzlw
11mo ago
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...
47.
▲
by
_jzlw
11mo ago
> 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
48.
▲
by
_jzlw
11mo ago
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. Was
49.
▲
by
_jzlw
11mo ago
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 a
50.
▲
by
_jzlw
11mo ago
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.