Looked at this a couple of days ago and it looks impressive! However, it does saddens me to see the elasticsearch api compatibility being behind a license, I had hoped this was also going to be open after discovering the functionality existed in the first place.

I guess having the cake and eating it too is actually not feasible in this case.

With that said I will indeed have a go at this and test and see if I can replace elasticsearch in our stack.

Good job guys!

Elasticsearch compatibility is provided through a separate component. We believe that this should be a commercial solution. As a commercial entity we need to figure out ways of making money. This is one of them along with SaaS.

What is your use case?

Is this because of the elastic search license or simply the project author chose to commercialize this functionality?

Interesting idea. However I do like the approach bankid did using qrcode [1] this does not however match a domain but matches a particular vendor that shows up after you've scanned it and asked to enter your security code. This way you can always verify the vendor is actually the website you are trying to log into.

[1] https://www.bankid.com/en/utvecklare/guider/teknisk-integrat...

We do this at work, albeit much larger scale than this and I'm the only one who spends any time on upgrades, replacing failed disks and so on. Honestly, apart from upgrades every 3-ish months I don't spend any time at all on this, it's all chugging along without intervention.

Things don't fail as much as they used to, at least not from using something mature as minio and of course hardware can fail as they do specifically spinning rust, which is non trivial to replace if you have hot-swap capable servers in the first place.

I don't possess any decade worth expertise in either minio or running this kind of setup so personally I believe you are exaggerating that this is even worth calling challenge at all.

But that's just my take :)

So I’m sure you’d be more than happy to volunteer your services to NixOS and be responsible for the setup, including when there are issues (which will inevitably happen regardless of tools and technologies used), right?

It’s so easy, after all.

I'd volunteer to do it, if they paid for hardware, colo and transportation for initial install. After things settle down, it takes no more than half an hour or so every month.

Pretending to know how much work something is when it's not your area of expertise is a bit silly.

Actually, yes, it is easy, after all :)

This is simply not true, it's negotiated between the client and server and defaults to 100 usually. 6 is the limit for http 1.1 not http/2.

Source: https://developer.mozilla.org/en-US/docs/Web/API/Server-sent...

ESD safety is an important topic, particularly in industries where sensitive electronic components are involved. However, there are many misconceptions surrounding ESD safety, especially when it comes to the use of cardboard and cotton clothing.

Cardboard, for example, is often thought of as a safe material for packaging and handling electronic components (motherboard boxes included). However, it can actually generate a significant amount of static electricity, which can damage sensitive components. Similarly, cotton clothing is often thought of as a safe material to wear in ESD-sensitive environments, but it can actually generate static electricity as well, polyester is generally considered preferred over cotton.

It is a common misconception that electrostatic discharge only causes damage if you can feel it. In reality, ESD can cause damage to sensitive electronic components even if you don't feel anything.

In fact, the damage caused by ESD can be more insidious when it is not noticeable. This is because when ESD is felt, individuals are more likely to take precautions to prevent it from happening again. However, when ESD is not felt, individuals may not even be aware that damage has occurred, leading to potential failures or malfunctions down the line.

I would advise anyone working electronics in any capacity, it's important to keep ESD in mind, as many sporadic issues are more than likely related to electrostatic discharge in some capacity.

> Cardboard, for example, is often thought of as a safe material for packaging and handling electronic components

And that's why everything comes in anti-ESD bags

I've used it with much success, it works pretty well but there's a lot of quirks and gotchas, nothing major but it can be cumbersome.

if only there were an open source and easy to use pdf library with pdf/a support :/

It looks like the IETF has some tools for this. A quick search revealed https://github.com/ietf-tools/ietf-at

The mentioned RFC PDFs are generated with Weasyprint which gained PDF/A support apparently last year. https://www.courtbouillon.org/blog/00028-weasyprint-56

That's what semantic versioning is for, breaking changes are inherently allowed in major version bumps.

In theory, yes.

In practice, here are a couple of examples:

A thread in relation to "replace `fgrep` with `grep -F`": https://news.ycombinator.com/item?id=33189503

How people feel about Python's handling of Python 2 vs Python 3: https://news.ycombinator.com/item?id=34227760

Semantic versioning isn’t really usable for typed languages as the majority of fixes would be considered breaking changes.

Being able to declare major changes in a version number says nothing about whether it's a good idea to make them.

I highly doubt you can count minified as "compiled" Minification is a form of compression. Compilation is a form of conversion from a high level to a lower level interpretation and that is fundamentally different.

But then again I'm not a lawyer :)

The intent is for attribution to be kept with the code. If your minifier removes the attribution you’re likely in violation.

And the minifier’s job is to remove things like comments which is right where the attribution is likely to be.

Now if a third party thing like a cloudflare CDN were minifyer for you and removed it then who violated the license?

There is an informal standard in which copyright notices are annotated with a leading "/*!” to let minifiers know that they should be preserved.

See https://stackoverflow.com/questions/11248363/the-purpose-of-...

If the CDN is just a part of your architecture that you voluntarily setup then you’re likely the one violating. Even if not the CDN very likely has an indemnification clause in their contract which would shift that liability back to you.

Hey, Substack CTO here. We actually don't minify or modify the files in question at all and simply link to the versions hosted on the public jsdelivr CDN (which includes a link to the license right at the top of the file)

First off: weird take, and one that would be unlikely to hold up. But secondly: what is that supposed to matter, anyway? That is, why are you litigating the definition of the word "compiled"? No finding, whether for or against your argument, would have any bearing on questions about compliance with the terms of the MIT license, so the word's definition and its significance is null. It's a total red herring and a distraction to bring up in any discussion on the topic.

I figure compilation is a big tent and this counts, but imagine

--rename-properties WARNING: renaming properties requires deeper analysis, considered compilation in the US