EmbeddingGemma 2: an open, lightweight multimodal embedding model
deepmind.google·6d ago
AI Engineering
Lobsters·Jul 31·5 min read
Dead Software Walking: The ongoing evolution of relayd(8) and httpd(8)
TL;DR
Active development of the relayd(8) and httpd(8) daemons has resumed, driven by user demand and a desire for improvement. This shift marks a significant evolution in their functionality and relevance within the OpenBSD community.
✦ Why It Matters
Consider contributing to open-source projects like relayd(8) and httpd(8) to enhance their capabilities.
Key Takeaways
- Explore contributing to open-source projects for skill development.
- Utilize GitHub mirrors to engage with the community effectively.
- Focus on improving error handling and security in your code.
- Stay updated on new features in OpenBSD daemons for better configurations.
Full Summary
Development of the OpenBSD relayd(8) and httpd(8) daemons had stalled due to a lack of interest from established developers. However, motivated by real-world use cases and a desire to challenge himself, a contributor began modernizing these daemons.
Key achievements include converting the imsg message system for better safety, improving error handling, and enhancing security features like stricter TLS cipher sets. The contributor also created GitHub mirrors to facilitate community engagement and streamline contributions.
Notable new features include support for the MKCALENDAR HTTP method and custom HTTP headers. Overall, these efforts have significantly improved the code quality and functionality of both daemons.