Almost half of all 18 to 34-year-old drivers are driving less, and nearly two-thirds would drive less if alternative transportation options were available, according to an independent study commissioned by Zipcar, Inc., the world's largest car sharing service.
The study of licensed drivers conducted in October by KRC Research revealed that 45 percent of Millennials (ages 18 to 34) said they had consciously made an effort to reduce how much they drive, and 64 percent would drive less if alternative options including public transportation, car sharing or convenient carpooling (ridesharing) were available in their area.
This document discusses building interactive widgets with the YUI (Yahoo! User Interface) library. It provides an example of creating a contact list widget with pagination using the YUI Module container component. Key steps include: 1) Setting up the basic HTML markup and dependencies; 2) Structuring the markup for the Module container; 3) Extending the Module class to create a custom ContactList widget; 4) Configuring properties like the number of contacts to display. The example demonstrates how to easily build reusable interactive widgets with YUI.
Collin County, Texas, Leadership and PlanningJWL Associates
This document outlines the agenda and contents of a strategic planning session for the Collin County Association of Realtors. The session aims to assess the organization's effectiveness and set its future direction. Key agenda items include reviewing the mission statement, identifying strengths and weaknesses, discussing trends impacting the industry, developing a business model statement, and crowdsourcing goals and objectives. Game changer trends addressed are demographic shifts, changes to the MLS system, and emerging brokerage models. The document provides guidance on implementing the strategic plan through approved strategies, benchmarks, and budgeting.
What comes after world domination with Daniel Stenberg, April 2025Daniel Stenberg
Open Source has in many ways already won. It is used in every product by every company, to a very a large degree. But we are not done. We can improve: we can take this further, we can make our projects better, we can enhance our communities and make sure it is done sustainably. The future is ours.
Tightening every bolt at FOSDEM 2025 by Daniel StenbergDaniel Stenberg
Things to do in order to sleep well while having your C code in twenty billion installations. A talk about what the curl project does to minimize security risks: Security, Safety, Reproducibility, Vulnerability handling and the processes and tooling around it.
As BDFL of the curl project, Daniel talks about what this project does to avoid it causing the world to burn. From code style, reviews and tests to signings, reproducibility, running a bug-bounty and becoming a CNA to filter bogus CVEs. curl aims to be top of the class in (Open Source) software security. Here's your chance to point finger and tell us what we should do better.
This document discusses using libcurl's share API to share data like cookies and DNS caches between multiple easy handles. It explains that some curl state is kept in the easy handle, so transfers using different handles may not be fully independent. The share API allows creating share objects that specify what data to share, such as cookies and DNS caches. Easy handles can then specify which share objects to use to share data between transfers and achieve better performance than using separate handles independently.
This document discusses curl security practices such as continuous integration testing on many platforms, custom test servers, tools used for analysis like Valgrind and Clang sanitizers, and "torture tests" that inject errors. It notes that while testing all combinations is impossible, common setups and architectures are tested. The curl bug bounty program is mentioned as paying $40,900 so far. An upcoming code audit and ensuring decreasing CVEs and fuzzing reports over time are discussed as signs the efforts are working. Recent CVE trends and introductions like "dynbuf" are also summarized.
This document provides an overview of curl, an open source command line tool and library for transferring data with Internet protocols. It discusses curl's history starting in 1998, its widespread usage across operating systems, CPU architectures, and planets. It also outlines curl's many supported features and protocols, large number of contributors and commits, extensive testing, and commitment to security and open development. The future of curl is discussed in the context of the growing Internet of Things and connectivity of everyday devices and appliances.
Daniel Stenberg gave a presentation on using Rust with curl. He discussed how curl has traditionally used C but now supports alternative backends implemented in other languages like Rust. He described challenges in integrating the Hyper, rustls, and quiche Rust crates but curl now supports HTTP/1-2 with Hyper and TLS with rustls in an experimental way. Future work includes improving test coverage when using Rust backends and potentially enabling them by default.
Daniel Stenberg goes through some basic libcurl fundamentals and API design and explain how easily you can get your first transfers going in your own application. libcurl is the defacto standard library for Internet transfers and runs on virtually all platforms. The language focus will be on C/C++ but the concepts are generally applicable even if you use libcurl bindings for other languages.
Daniel Stenberg gave a presentation about security best practices for curl and open source projects. He discussed how curl implements thorough testing, code reviews, fuzz testing, and monitoring of dependencies to minimize vulnerabilities. Stenberg also noted that curl employs a full-time maintainer, responds quickly to issues, and has an active bug bounty program to further improve security.
Daniel Stenberg discusses some of the most common mistakes users are doing when using libcurl and what to do about them.
Video: https://youtu.be/0KfDdIAirSI
Daniel Stenberg discusses the progress being made to enable HTTP/3 support in the curl tool and libcurl library. HTTP/3 uses QUIC as its underlying transport protocol. Several challenges remain, including fallback options, stability testing, and full browser/server support. Stenberg explains how to build curl with various QUIC libraries like Quiche and ngtcp2. HTTP/3 support in curl is still experimental but aims to provide a similar user experience to HTTP/1. Support may be included in future releases as QUIC and HTTP/3 specifications continue development and more servers/browsers are deployed.
This document discusses using libcurl's share API to share data like cookies and DNS caches between multiple easy handles. It explains that some curl state is kept in the easy handle, so transfers using different handles may not be fully independent. The share API allows creating share objects that specify what data to share, such as cookies and DNS caches. Easy handles can then specify which share objects to use to share data between transfers and achieve better performance than using separate handles independently.
This document discusses curl security practices such as continuous integration testing on many platforms, custom test servers, tools used for analysis like Valgrind and Clang sanitizers, and "torture tests" that inject errors. It notes that while testing all combinations is impossible, common setups and architectures are tested. The curl bug bounty program is mentioned as paying $40,900 so far. An upcoming code audit and ensuring decreasing CVEs and fuzzing reports over time are discussed as signs the efforts are working. Recent CVE trends and introductions like "dynbuf" are also summarized.
This document provides an overview of curl, an open source command line tool and library for transferring data with Internet protocols. It discusses curl's history starting in 1998, its widespread usage across operating systems, CPU architectures, and planets. It also outlines curl's many supported features and protocols, large number of contributors and commits, extensive testing, and commitment to security and open development. The future of curl is discussed in the context of the growing Internet of Things and connectivity of everyday devices and appliances.
Daniel Stenberg gave a presentation on using Rust with curl. He discussed how curl has traditionally used C but now supports alternative backends implemented in other languages like Rust. He described challenges in integrating the Hyper, rustls, and quiche Rust crates but curl now supports HTTP/1-2 with Hyper and TLS with rustls in an experimental way. Future work includes improving test coverage when using Rust backends and potentially enabling them by default.
Daniel Stenberg goes through some basic libcurl fundamentals and API design and explain how easily you can get your first transfers going in your own application. libcurl is the defacto standard library for Internet transfers and runs on virtually all platforms. The language focus will be on C/C++ but the concepts are generally applicable even if you use libcurl bindings for other languages.
Daniel Stenberg gave a presentation about security best practices for curl and open source projects. He discussed how curl implements thorough testing, code reviews, fuzz testing, and monitoring of dependencies to minimize vulnerabilities. Stenberg also noted that curl employs a full-time maintainer, responds quickly to issues, and has an active bug bounty program to further improve security.
Daniel Stenberg discusses some of the most common mistakes users are doing when using libcurl and what to do about them.
Video: https://youtu.be/0KfDdIAirSI
Daniel Stenberg discusses the progress being made to enable HTTP/3 support in the curl tool and libcurl library. HTTP/3 uses QUIC as its underlying transport protocol. Several challenges remain, including fallback options, stability testing, and full browser/server support. Stenberg explains how to build curl with various QUIC libraries like Quiche and ngtcp2. HTTP/3 support in curl is still experimental but aims to provide a similar user experience to HTTP/1. Support may be included in future releases as QUIC and HTTP/3 specifications continue development and more servers/browsers are deployed.