Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
hakre
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
18 ms
·
151.
▲
by
hakre
5y ago
The Bug Bounty Program effectively protects them from that. You wouldn't know how insulting that is before going through a good of paperwork that legally tames your desires.
152.
▲
by
hakre
5y ago
Germany realized that for sure, but the meaning is different: The period of peace enforced due to loosing the war is over. All good things count up to three like the colors in the flag.
153.
▲
by
hakre
5y ago
Well, many thousands of workers write and maintain software and eventually its release is under free software, getting paid by the hour. It's just working, why should we expect anything more? A worker can't do anything more and th
154.
▲
by
hakre
5y ago
> When you document how something behaves in any particular case programmers are going to use it, especially in a case like this where the behavior is actually useful. This is true and also the reason of the extraordinary warning and the
155.
▲
by
hakre
5y ago
In case of count this is more likely not because of a different web but the changes we can see for stdClass, arrays and the object model. And give peace a chance, it is not always love on first sight when something unexpected happens.
156.
▲
by
hakre
5y ago
Actually I would test the request first. And only if it doesn't work this would require the documentation, so would then test it after the functional test. If the documentation is even needed.
157.
▲
by
hakre
5y ago
That must be something fetch specific, per the HTTP specs IIRC, any status code should be passed to the application - and the way I read it - unfiltered. It is neither an error nor an exception, the request is successful. A DNS or server co
158.
▲
by
hakre
5y ago
> Use GET for everything that can be cached and repeated without side-effects As long as HTTP is concerned (which must not be specifically REST), HEAD needs to be supported next to GET, too.
159.
▲
by
hakre
5y ago
> I'm not sure it makes sense for an HTTP protocol standards to describe how browsers should allow it's input in the URL bar - two very different standards realms. Just as a small remark, HTTP protocol standards do - or have at
160.
▲
by
hakre
5y ago
good mention. an rtfm for everyone else.
161.
▲
by
hakre
5y ago
Only to yourself with all rights reserved to yourself, too. You then transfer the license to an oversea entity that then licenses back to your majority owned company. This is the professional business with software licenses as there is no p
162.
▲
by
hakre
5y ago
It's a multiple decade long process to bleed and drain out health-care in Germany. No one working there finds this fascinating.
163.
▲
by
hakre
5y ago
Well, even its late here, I could still have enough creative energy to insert the minus in there ... yeah, thanks for that. So now I feel really behind because sure, it's packaged in Ubuntu 20.04. Thanks again.
164.
▲
by
hakre
5y ago
Okay, call me lazy. Not for ripgrep, installed it early from sources. However your fdfind (fd) mention made me curious. Thought I give it an apt install on Ubtunu 20.04 LTS but dead end. So perhaps in debian-stable but not in Ubuntu. Just s
165.
▲
by
hakre
5y ago
Following the report, some have. But why be surprised? They grow a lot of greens out of such content. Why kill the golden cow unless you need to (because forced to)?
166.
▲
by
hakre
5y ago
Only in part: The marketing department needs numbers to report, newsletter subscription is one. So it pays at least one job.
167.
▲
by
hakre
5y ago
Previously on HN: The JSON5 Data Interchange Format ( https://spec.json5.org/ ) - 2 Years ago - 0 Comments - https://news.ycombinator.com/item?id=21113613
168.
▲
by
hakre
5y ago
The license states "Provided AS-IS". There is no right to damn the distributor to not make it not available (and as far as this is Chromium not even the project) - just that.
169.
▲
by
hakre
5y ago
No, software developers and package maintainers do. A distro is where it goes all together and normally under a license. Even licenses are different across packages in a repo, they normally all have a pretty clear wording how much you can h
170.
▲
by
hakre
5y ago
None that I can think of. History of projects is by the people who do/participate. If you want to remove the right to modify the project (which includes the history if shared as common on Github) it is not open source (free/libre)
171.
▲
by
hakre
5y ago
You can put it under proprietary reciprocal terms and void the right to copy when history is damaged. Copyright should cover that. You can't do this with lax permissive licenses nor with copyleft as they allow to modify the work, which
172.
▲
by
hakre
5y ago
> it's somewhat interesting that we don't consider the source code history in our OSS licenses Developing is in the burden of the single developer/project and which kind of version control system is used to produce release
173.
▲
by
hakre
5y ago
> Your license should cover the history, in that every source file should bear a license header, going back to the first commit. This is one way to do it. Problem remains when these important parts, even whole files - e.g. COPYRIGHT - ar
174.
▲
by
hakre
5y ago
> Versions of software can have different licenses, and the license for each version is the license that the repo was under when that version was committed. Not particularly wrong, just adding: There can even be additional licensing term
175.
▲
by
hakre
5y ago
Yes, unless you start talking about the article _after_ reading it. As the article is referencing the other, earlier article about the terror pigs in the same publication. It is similar entertaining btw.
176.
▲
by
hakre
5y ago
And under circumstances testing the own url parser _alone_ is only half (?) of the story. The other URL parsers within the system or in the line need to be tested, too. Which mathematically might not be possible. So next to the URL parser i
177.
▲
by
hakre
5y ago
It's a fantastic story written today. Each recipient can only receive it by realizing the ability to read it - whenever that time is to be found. This makes the more timeless properties interesting, perhaps. For example, those who own
178.
▲
by
hakre
5y ago
Aren't such collections online hate? The publication seems to be for entertainment. The "science" part of the mockery?!
179.
▲
by
hakre
5y ago
You normally take a cloud offering so that you can truly deny that you didn't know it was not state of the art.
180.
▲
by
hakre
5y ago
> If there is a problem with the deploy let's meet, fix the issue and most importantly learn from the problem, and document the incident for future reference. Not being on the same side should not be the problem, it's the solut
More ›