Shouldn't there be a comma after "business"? I read it wrong the first time.
No. That would not be correct, grammatically speaking.
Curl is just the hobby
31–40 of 90 posts
Re: Curl is just the hobby
#32> I would personally perhaps protest against the use of PUT for POSTing JSON, but nobody asked me. Just wondering, if the resource ID is known, I thought PUT is the recommended method? We usually use POST for creating a new resource for which you don't know an ID yet.
Auth requests are for a new session ID, not a new user ID. It's a (C)reate in CRUD, not an (U)pdate. POST - Create, GET - Retrieve, PUT - Update, DELETE - Delete
The protocol could be:
CREATE /xxx
READ /zzz
UPDATE /yyy
DELETE /abcd
Re: Curl is just the hobby
#33Earlier quoted context omitted.
It is and it's a best practice. I've never heard anyone complain about this. Most security scanning software will ding any site that doesn't use HSTS
You don't see why Firefox refusing to connect would be annoying? I don't care whether the blog about curl is encrypted in transit or not and I do care about a forced change to chrome to see the content.
I can visit it in Firefox 123 just fine. Tests like [1] say the site works on everything from Firefox 31 to Firefox 73.
You're probably the target of a MITM attack. Or you've done something weird, like taking a job with an employer that MITMs your web traffic then refusing to install their MITM certificates.
[1] https://www.ssllabs.com/ssltest/analyze.html?d=daniel.haxx.s...
Re: Curl is just the hobby
#34Off topic but I find it wild that SF has API ads on bus shelters. Is that unusual/right in a dev hotspot, or have I been well underestimating just how intrinsic the tech culture is there? (I’m an Australian, so I guess my question applies to the US as much as SF)
I think it's a Bay Area thing.
Google's {First 10-digit Prime in Consecutive Digits of e}.com ad is a classic in this genre (https://www.hanshq.net/eprime.html)
Re: Curl is just the hobby
#35Imagine having a hobby project, installed on billions of devices. MBA: they must be making 10B$/year? Engineer: no, this is just a hobby
A bit unfair as the main reason it is installed on billions of devices is that it is FOSS.
It's like giving to charity and then being aggravated that it was used to generate lots of money, you can't retroactively change your mind. Although they can always stop updating curl if it is that bad for them.
Re: Curl is just the hobby
#36> I would personally perhaps protest against the use of PUT for POSTing JSON, but nobody asked me. Just wondering, if the resource ID is known, I thought PUT is the recommended method? We usually use POST for creating a new resource for which you don't know an ID yet.
According to RFC 9110: - POST: Perform resource-specific processing on the request content. - PUT: Replace all current representations of the target resource with the request content. I interpret this as the only immediate side-effect of PUT is supposed to be replacing the target resource with the request content. Everything else is POST, but that does not mean that we can't use POST for everything. Thus, JSON via PU…
You should've added the patch specs too, for completions sake (it's to modify an object, not replace it - leaving unset attributes the same as before the operation)
Re: Curl is just the hobby
#37Earlier quoted context omitted.
It is and it's a best practice. I've never heard anyone complain about this. Most security scanning software will ding any site that doesn't use HSTS
You don't see why Firefox refusing to connect would be annoying? I don't care whether the blog about curl is encrypted in transit or not and I do care about a forced change to chrome to see the content.
Common misconception, but Https / TLS provides a combination of gaurantees, and the one cannot work without the other:
Encrypted transit but you might be talking with the hacker on the other end == worthless.
And with plaintext transit you cannot prove integrity during transit AND also not prove talking with the proper endpoint.
In short: Browser really is warning you that something is fishy. Don’t shoot the messenger.
Re: Curl is just the hobby
#38> I would personally perhaps protest against the use of PUT for POSTing JSON, but nobody asked me. Just wondering, if the resource ID is known, I thought PUT is the recommended method? We usually use POST for creating a new resource for which you don't know an ID yet.
> Just wondering, if the resource ID is known, I thought PUT is the recommended method? Recommended for what purpose? The set of recommendations I'm familiar with is: GET: requests without side effects POST: requests with side effects PUT: never use other: never use POST gets special treatment from browsers for various security risks. Otherwise, methods don't differ. You can use PUT as part of an effort to feel like…
PUT's can have request bodies, GETs can not.
Re: Curl is just the hobby
#39Off topic but I find it wild that SF has API ads on bus shelters. Is that unusual/right in a dev hotspot, or have I been well underestimating just how intrinsic the tech culture is there? (I’m an Australian, so I guess my question applies to the US as much as SF)
NYC has Mullvad VPN ads in the subway.
Re: Curl is just the hobby
#40Off topic but I find it wild that SF has API ads on bus shelters. Is that unusual/right in a dev hotspot, or have I been well underestimating just how intrinsic the tech culture is there? (I’m an Australian, so I guess my question applies to the US as much as SF)
Sydney Airport will frequently have some hyper-specific ads around it. This happens pretty much everywhere.
I occasionally see tech/API ads on the London Underground. You often see ads for all sorts of niches that would probably be smaller than developer and developer-adjacent people.