Fun fact: They also ship curl.exe, which is different from curl in PowerShell, as the latter is an alias to Invoke-WebRequest. That's one of the insanest decisions they could make during one of the sanest ones.
Most of the companies behind it (including NextCloud itself & IONOS) are providing a document cloud to their users already & are used to maintaining Open Source, so I would indeed assume some seriousness here.
That sounds like you might like VyOS. I found it to be relatively easy to achieve exactly what I wanted, but went back to a GUI as it turned out I wanted a pet and not start a farm.
The DC side is fully isolated except through a capacitor that is there to reduce EMI interference and is specifically built to "fail safe", except for the cheapest no-name imported power supplies. (https://www.pcbaaa.com/y1-capacitors-function-application-an...)
The main problem is the bugginess in combination with the featurelessness. Usually you can work around bugs in some way or another, but many of the bugs in Boxes seem to come from the fact that control is taken away from the user in the first place, and there's no way around it except touching the source code.
Being wrong is one thing, on the other hand knowing that they don't know something is something humans are pretty good at (even if they might not admit to not knowing something and start bullshitting anyways). Current AI predictably fails miserably every single time.
After what happened with Honey, I guess this probably means: they replace ads on pages with their own, pocket most of the money, and extort the sites who would have earned money with the ads into partnering with them.
Two different implementations might make two different local times out of that, e.g. due to not being aware of changing DST/timezone policies. Hence the recommendation of separating between user/clock/calendar time (which must be exact to a human) and absolute/relative timestamps (which must be exact to a computer).
Also, ads. I guess the shorter the time is between clicking the play button and the ad starting, the more people will have "seen" more of the ad before deciding that the video isn't worth watching the ad.
So the Debian maintainer complains about the upstream project (which they decided to maintain the package for) bringing "crap" and having "utterly misguided" development? And somehow people say that this is the reasonable person here, basing a major change of a software's featureset on such an opinion?
Independent from whether the original change is good or bad, so much of what's wrong with Open Source is people trying to work against each other instead of together...
Yeah, and out of that fear, people often use stacks that require vast amounts of knowledge to actually keep things working at all, at any scale. Kubernetes is the best example where I don't trust me to keep the wheels on because it's scalable.
Communities are moderated based on how good you feel there, if it's the most ad-friendly, how good everyone stays on-topic, or other mostly social & subjective criteria. Judicial systems aren't about any of those things.
Go uses the package name to retrieve the pagacke source - a package named github.com/example/whatever will be downloaded by basically cloning it with git & then checking out the specified version as a tag.
That's in itself a really simple system and doesn't rely on a single third party, but obviously comes with the ownership issue (unless when pinning a specific commit) - in my opinion a good compromise.
I don't really understand how "hosted" and "internal" go together here - does this mean that a) the devices I need certificates for must connect to your servers, and that b) your servers could theoretically sign certificates for devices which do not exist? If so, especially for the latter point, this IMO isn't really useful for any real-world application, as the most important things of a CA is control.
Absolutely agree, the new design makes it so much more modern & easy to use for the average user.
I have the feeling that many complaints here are about specific workflows or specific advanced features, but instead of trying to please everyone by doing everything MZLA has built a really nice email client that just works for the majority of its users and now is in a shape where it might even attract new ones.
Yeah, they've also switched their complete concept around before, going from a simple web code editor to a deployment-based hobby hoster, already breaking the use cases (and simplicity) for many users.
I totally agree and would say that openly criticising such decisions is important, so that companies are a bit more careful with introducing usecase-breaking changes - including changing their business model in a way that makes it not viable anymore for many users.
Such things really make a company seem unreliable, but unfortunately it seems to have become common with the "ship early, break often" mentality especially in the start-up world.