Correct some typos

This commit is contained in:
Nathan Fisher 2023-05-29 19:28:30 -04:00
parent c350de1d8f
commit 21668f26a3

View file

@ -15,7 +15,7 @@ Meta(
],
)
---
Daniel Stenberg is a well known figure in the Free Software and Open Source worlds. Not only is he the author and maintainer of Curl, one of the world's most used pieces of software, he has somehow managed to make a living developing Curl pretty miuch exclusively. I have a lot of respect for the guy. He recently wrote a blog article about his response to a pull request which would add Gemini support to Curl. He wasn't exactly kind to Gemini. This has bothered a lot of folks probably more than it should.
Daniel Stenberg is a well known figure in the Free Software and Open Source worlds. Not only is he the author and maintainer of Curl, one of the world's most used pieces of software, he has somehow managed to make a living developing Curl pretty much exclusively. I have a lot of respect for the guy. He recently wrote a blog article about his response to a pull request which would add Gemini support to Curl. He wasn't exactly kind to Gemini. This has bothered a lot of folks probably more than it should.
Thrig.me had a great point for point rebuttal.
=> gemini://thrig.me/blog/2023/05/29/http-client-person-from-gemini.gmi The HTTP client person as seen from Gemini
@ -31,7 +31,7 @@ Here's the thing though. Why does this hit such a nerve?
That's just it. Frame his blog post from the standpoint of the maintainer of what is likely the most important piece of networking software in existence. He has rightly pointed out some ambiguities in the spec. What's interesting is that he makes sure to point out that none of his criticisms likely prevent it from being useful to it's community.
> This is not a protocol designed for the masses to replace anything at high volumes. That is of course totally fine and it can still serve its community perfectly fine. There seems to be interest enough to keep the protocol and ecosystem alive for the moment at least. Possibly for a long time into the future as well.
No, I think what he's saying and the recommendations he gives should be taken as "this is what would have to change for me to accept Gemini support into Curl". I don't completely agree with him, as the mre fact that we all seem to do just fine talking to each other tends to show that writing a client isn't really all that hard. But it's his piece of software, and hist decision. Does that take anything away from Gemini? Probably not. I don't think that having Gemini in Curl would have given Gemini a shot in the arm or anything. I don't really think it would have even seen much use, to be perfectly honest. The spec is simple enough that one can put together a client in POSIX shell in just a few lines of code. In fact, here's the Makefile recipe for this capsule which hits Antenna with the feed after I publish a post.
No, I think what he's saying and the recommendations he gives should be taken as "this is what would have to change for me to accept Gemini support into Curl". I don't completely agree with him, as the mere fact that we all seem to do just fine talking to each other tends to show that writing a client isn't really all that hard. But it's his piece of software, and his decision. Does that take anything away from Gemini? Probably not. I don't think that having Gemini in Curl would have given Gemini a shot in the arm or anything. I don't really think it would have even seen much use, to be perfectly honest. The spec is simple enough that one can put together a client in POSIX shell in just a few lines of code. In fact, here's the Makefile recipe for this capsule which hits Antenna with the feed after I publish a post.
```
publish:
echo "$(submit_url)" | eval openssl s_client -connect warmedal.se:1965 -crlf \