💾 Archived View for bbs.geminispace.org › u › mike › 3063 captured on 2023-07-22 at 17:54:10. Gemini links have been rewritten to link to archived content

View Raw

More Information

➡️ Next capture (2023-09-08)

-=-=-=-=-=-=-

Re: "Warning Gemini Support in curl"

Comment in: s/Gemini

While it would be nice to have Gemini support in curl, there does seem to be some resistance. I think this is healthy as a mature project, or any project for that matter, like curl shouldn't just accept a pull request adding an entirely new protocol without going into the details of the specification and asking for a robust set of tests. I feel like this pull request requires the continuous efforts of multiple engineers if it's going to succeeed.

As an alternative that a lot of people are probably already familiar with, gemget does a nice job and works today. However, I'm not saying I wouldn't want to see Gemini in curl as well :)

☀️ mike

2023-07-12 · 10 days ago

3 Later Comments ↓

🧇 Acidus

I'm not a C programmer, or otherwise I would.

Wait, isn't Lagrange written in all C... [looks to @skyjake ]... I'm just saying...

☀️ mike

Yeah, I have the same problem in that I'm not fluent enough in C to work on an update of this magnitude. I could possibly help out a bit if a more experienced C developer takes the lead.

🚀 skyjake

Thanks for the vote of confidence @Acidus, but I'm not in position to push this forward... As I understand it, the work is mostly about putting together a test suite and documentation. That kind of work is not that complicated but certainly time-consuming. However, the remaining ambiguities in the Gemini specification make it somewhat more difficult to create a comprehensive test suite.

2023-07-13 · 9 days ago

Original Post

🌒 s/Gemini

Warning Gemini Support in curl — Greetings everyone, The Gemini feature for curl is at risk of being closed: [https link] Is there anybody able and willing to continue with this pull request?

💬 ERnsTL · 4 comments · 2023-07-12 · 10 days ago