Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
lucideer
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
20 ms
·
391.
▲
by
lucideer
2y ago
Something odd about this story is looking at Alexander's Github activity history. He started being active on Github in March 2021 - around the start of this project - & since then has been extremely consistently very active right u
392.
▲
by
lucideer
2y ago
There's two opposing perspectives to consider here: 1. We don't know the details of the internal politics between the approved maintainers of this private repo, but, licenses aside if someone decided to make a private repo I creat
393.
▲
US Justice Department Will Request Judge Order Google to Sell Chrome
(forbes.com)
2 points
by
lucideer
2y ago
|
0 comments
394.
▲
by
lucideer
2y ago
There's an implicit assumption embedded in this comment that the Chromium project is indispensable, whereas I'm unconvinced it's even a net positive at all. Anyone who follows standards discourse would probably appreciate the
395.
▲
by
lucideer
2y ago
Seeing for years the views expressed here about Meta & TikTok, I think at least some of this must come down to a gap in understanding of web technologies. Meta & TikTok decidedly don't have monopolies, yet still come under fier
396.
▲
by
lucideer
2y ago
> It would be unreasonable to withhold an optional feature just because that optional feature is not universal yet. The "reasonability" of this is dependent on your goals. If an open ecosystem isn't a priority, then your
397.
▲
by
lucideer
2y ago
> the current GitHub requirement is an explicitly temporary restriction It seems reasonable to suggest that advertising a solution for public use at a point in time when support is at <2 systems is not an ideal way to encourage an o
398.
▲
by
lucideer
2y ago
> I am begging you to re-read the docs The gp was pointing out that the docs heavily emphasise (& therefore encourage) GHA usage & suggested language changes. If people are confused about what they need to use Trusted Publishin
399.
▲
by
lucideer
2y ago
> Are you just saying that to emphasize your confidence? [...] people like to reminisce about hand made goods. [...] I guarantee we can find a supplier of many varieties of decorative nails A nested HN thread is likely not the best pla
400.
▲
by
lucideer
2y ago
> Are you suggesting there is no provider of high quality nails at industrial scale? Nails was one of the examples cited by the gp, which I found funny since there is one famous example of nails being lower quality by definition as a
401.
▲
by
lucideer
2y ago
Whether it's a conscious strategy or an implicit outcome, planned obsolescence wouldn't be viable without centralisation. Centralisation is a tool of capitalism to achieve its goals.
402.
▲
by
lucideer
2y ago
This isn't true though. Neither in theory nor in practice. A broad set of individual product quality has consistently declined throughout the industrial era - not least, infamously, one of your own examples: nails. Many products have i
403.
▲
by
lucideer
2y ago
No. Centralization isn't needed to scale, it's just needed to exploit scale. Exploitation has become so commonplace it's replaced everything as the primary "desirable metric". I'm writing this comment on a pl
404.
▲
by
lucideer
2y ago
This seems like it would skew the data significantly for certain use-cases. Unless you're feature flagging to test infra backing an expensive feature (in which case, in a load-balancer / containerised world, bucketing is going to
405.
▲
by
lucideer
2y ago
That list makes for a nice slidedeck but the separation (like many things in tech) isn't as clear cut as the metaphor. "Something you know" (password) becomes "something you have" as soon as you store/autogener
406.
▲
by
lucideer
2y ago
Aegis is no more secure than storing your TOTPs in your password manager - 2 factors primarily protect against remote attacks, which don't have direct access, in which case the app your 2nd factor lives in is moot. If your threat mod
407.
▲
by
lucideer
2y ago
> JS of the era was a pain to use; CoffeeScript made writing and reading things much easier It didn't. Anything you learn / are familiar with will be easier to write - Coffescript was easier to write for people who learned Co
408.
▲
by
lucideer
2y ago
> that was computed Or comes from a set of known values. This stuff isn't that difficult. This doesn't require prescient knowledge of high timeout edge cases. It's generally accepted good security practice to limit busin
409.
▲
by
lucideer
2y ago
> I don't think it's that contrived to have a service that runs an expensive operation at a fixed rate, controlled by the user Maybe not contrived but definitely insecure by definition. Allowing user control of rates is defin
410.
▲
by
lucideer
2y ago
This! JQ is great because JSON didn't have a query language & needed one. JQ isn't the best query language - it's just the one that won adoption. DBs already have query languages that are mostly superior to JQ's.
411.
▲
by
lucideer
2y ago
I think you may be underestimating the volume difference in paying users you're likely to get with a one-time vs subscription model. Looking at similar apps on the market, I suspect you would earn more revenue overall with a one-time p
412.
▲
by
lucideer
2y ago
The best model I've seen for this is to simply charge for major version upgrades. It's totally at the developer's discretion what they put into any given major/minor/patch version so you can demarcate development in
413.
▲
by
lucideer
2y ago
Agree with the sibling commenter here, this stance baffles me. Google have been caught breaking the law on data collection enough times at this stage that there's absolutely no reason to ever assume they aren't being as invasive &
414.
▲
by
lucideer
2y ago
> That's the FSFs spin This implies your take on copyleft is an adversarial one, in which case implying your definition is canonical is disingenuous.
415.
▲
by
lucideer
2y ago
While I did make the point that "copyleft" is not a protected term & therefore can have many definitions, I've never heard your definition & it's certainly not the widely accepted one.
416.
▲
by
lucideer
2y ago
Yeah the license self-refers as "copyleft" (an unregulated term afaik), and they have been very careful to avoid usage of the term "open source" rather preferring to say things like "the source is open". Regula
417.
▲
by
lucideer
2y ago
"source code is open" implies "open source", and the License refers to itself as a "copyleft" license, but it's a newly minted license - IANAL does anyone know if this is open source or another Elastic typ
418.
▲
by
lucideer
2y ago
Looks like a bug in their light theme - it's using the dark theme's background. There's a theme toggle top-left to switch to the still-functioning dark theme. Guessing they probably started with a light theme then retrofitted
419.
▲
by
lucideer
2y ago
It seems odd at first until you realise that it's a host setting & a convention, rather than an inherent limitation. The familiar model of "centralised" Git hosts like Github come bundled with their own protocol-specific
420.
▲
by
lucideer
2y ago
Has anyone done a comparative breakdown between Radicle & git-ssb? This looks really nice & polished - love the web ui - but I know there's a pretty active network & community on SSB.
More ›