Colt McNealy’s Post

We're about to save a lot of time 🚨 The first LLM specializing in writing API calls is out. Gorilla can write your code and accurately invoke 1,600+ API calls while reducing hallucination. With a simple text input, Gorilla comes up with the semantically correct code and API to execute your task. It already reached 5k stars on Github and is licensed Apache 2.0.

Announcing the Release of My New Magic Onion gRPC Template I'm excited to announce the open sourcing of my new Magic Onion template for building gRPC services on .NET. This streamlined template makes it easy to spin up plug-and-play gRPC APIs with generic service and hub implementations. Key highlights: Built-in support for efficient MemoryPack binary serialization Modular client and server projects for flexible development Integrations with Redis for rate limiting and blocking Entity Framework Core ORM and custom query execution Shared types and interfaces for consistency JWT authentication and role based authorization The template includes robust and optimized libraries like MagicOnion, MasterMemory, Mapster, and more to provide a complete framework. Whether you're looking to create a new gRPC service from scratch or bootstrap your project faster, this template has got you covered! Check out the source code and documentation on GitHub to get started: https://lnkd.in/d4uNRbFP I welcome any feedback, feature requests or contributions from the community to help improve the template. Please star the GitHub repo to show your interest and support. Let me know if you end up building something cool with this template! I'm always happy to see what people can create. #grpc #dotnet #opensource #softwaredevelopment

So i was working on this personal project of mine, and I did not find a way to get a steady list of public proxies and test it against custom targets, which was way more important to me than just getting the list of proxies that you can get virtually from anywhere, so I created a custom package that does just that: Raven 🐦⬛ Raven is a HTTP proxy getter and tester, you can use it both in your project as a library or via docker as a fast cli tool to just get what you need fast. I have documented the need to know parts of the project, and i will continue working on it in my freetime, as there are improvements to be made. Raven is an Open Source tool that is free to use by anybody, anywhere. You can find Raven on my Github Repo: https://lnkd.in/g4JcGkPt

Ensuring the open source moment continues

Your contribution for the evening 🌟: Griptape👇 Co-founded by Kyle Roche and Vasily Vasinov, Griptape is a modular open source framework that allows developers to build and deploy LLM-based agents, pipelines, and workflows. Here’s why you should contribute to this repo: 1️⃣ With over 1,500 stars, contributing to Griptape means you can gain exposure and hands-on experience with LLMs and modular framework design, enhancing your skills in highly sought-after areas. You will also join the Griptape community, which allows you to connect with like-minded developers and experts in the field, expanding your professional network and potentially opening doors to new opportunities and collaborations! 💪 2️⃣ The repo is more accessible. At Quira, we rank Developers by their DevRank (more on this here: https://lnkd.in/eNtrs97F). We found that the median developer working on the repo belongs to the 90th percentile of GitHub developers. For reference, many of the open source companies we reported on have had a median contributor level of ~95th percentile. This means that you have a real opportunity to make an impact. ⚡️ 3️⃣ Returning contributors are a good proxy for the health of a repo and your chances to make a meaningful impact. Impressively, close to 60% of contributors merge a second pull request. This means that if you enjoyed contributing the first time, chances are you'll come back for more. 😉 You can check more of their open-source stats on Quira (https://lnkd.in/eguqtcWD) or access the GitHub page: https://lnkd.in/gPRRfAi2 📖

It’s been almost 3 years since I opened an issue stating that the names of the 𝗶𝗻𝗴𝗿𝗲𝘀𝘀-𝗻𝗴𝗶𝗻𝘅 and 𝗸𝘂𝗯𝗲𝗿𝗻𝗲𝘁𝗲𝘀-𝗶𝗻𝗴𝗿𝗲𝘀𝘀 projects are confusing (https://lnkd.in/gXGkTUFt). Both are Kubernetes ingress controllers based on the NGINX server, yet they have different features and are maintained by different authors (the K8s community vs. NGINX Inc.). Due to the very similar naming, many users confused them, which was confirmed by our engineers’ experience and the wider feedback I’ve seen on Reddit and other resources. I thought nothing was going to happen, and this feeling was reassured by a recent (February) comment from the Kubernetes community (https://lnkd.in/gKP93CxP). However, today, I learned that things had started going! 😯 🎉 As Brian Ehlert from F5/NGINX Inc noted, “At KubeCon Paris the Kubernetes Community ingress project revealed that it will be renaming and is taking suggestions.” Here’s the official announcement and the link you may offer your suggestion for a new name: https://lnkd.in/gwUeBsWA

What comes after open source? In any event it involves an understanding that open source was never really open.

Does the current versioning mean Strimzi is not production-ready? No, absolutely not! We realize the 0.x version might seem concerning and might deter some people. However, the version number itself does not say much about the project maturity or about how good the project is. Strimzi is production-ready! And you can check some of our production users on our website or in our ADOPTERS.md file as proof.

I'm building a Distributed Key-Value Store in TypeScript based on RAFT Protocol! 🚀 In the last four weeks, I've been deep into the world of distributed systems, crafting tf-raft for pure educational fun! 🤓 RAFT Protocol, is the backbone of systems like etcd, MongoDB, RabbitMQ and many others. Thanks goes to Ahmed Farghal's distributed systems' playlist for sparking this journey, it was the first time I hear about RAFT. Core Flexibility 🧩 I implemented the RAFT's core based on the principles outlined in the dissertation "Consensus: Bridging Theory and Practice", and made it fully independent, and isolated from the network and persistence layers. Initially I'm supporting gRPC and in-memory adapters for the network. jsonDB and in-memory adapters for the persistence and volatile states. 🚀 Milestones Unlocked: ✅ Leader Elections ✅ Log Replications ✅ Cluster Membership Changes Currently Crafting: 🔧 gRPC Adapter for Cluster Membership 🔧 Log Applier 🔧 Key-Value Store Client & Interactions 🔧 Log Compaction ( potentially ) 🔧 Documentation Check it out on GitHub: https://lnkd.in/d4xB2TV5 This project is just for pure fun and learning! 👨💻 Sharing it in the hope that it might be useful for anyone keen on delving into Consensus protocols or distributed systems to try it. Some references are in the comments. #DistributedSystems #RAFTProtocol #OpenSource

Heres, my first blog demystifying the fundamentals of gRPC, its use cases.✨ grpc provides multi language funtionality.⚡ I explained how protobuff is used as payload between servers and clients, how protobuff is binary means of transport.🤓 http/2 is used in place of http/1.1 to exchange binary data, which has obviously to go through a process of serialisation and deserialisation.🏹 http/2 maintains consistency in circumstances where bandwith is an issue and presents latency problem.🏹 Four types of functionalities are provided by gRPC - Unary RPC (client server single request) - Client streaming RPC (client sends stream of requests) - Server streaming RPC (server forwards a stream of messages to client) - Bidirectional streaming RPC (both sends a stream of messages) Check more info about it in the blog🙂 Happy learning.👋 #grpc #blog #mediumblog