OP Here, sorry for not being clear. And happy for feedback on our presentation, docs, my article and ofc the code itself. It has been under developed since over 5 years, and was used in production right from the start. Now we are at a point that it is used by several different companies and even more individual users.
Here is some context and info about the framework that I am quoting from our README to provide you with context:
Rama is a modular service framework for the Rust (programming) language.
The framework is intentionally explicit. Your network stack is built from services, layers, transports, protocols, and state that you compose yourself. That makes the shape of the system visible in the code, instead of hidden behind framework magic or configuration.
This makes Rama a good fit not only for proxies, but for network services where the stack itself matters: how traffic enters, how it is decoded, where state lives, what gets inspected, what gets transformed, and where it goes next.
Whether you're inspecting traffic for security analysis, writing a web service, emulating clients with custom user agents, controlling connection behavior for advanced testing, or building high-performance proxies, Rama provides a clean and composable Tokio-native foundation for network services in Rust.
Rama is used in production for network security, data extraction, API gateways, routing, and other networked systems.
The blog doesn't explain what Rama is, but it's a network library (?) for Rust: https://ramaproxy.org/
Is it a proxy or more? It seems more despite the name.
OP, I am very happy for you releasing, but I see you have zero upvotes. I think explaining what something is is key in any blogpost. And sorry to say, but the triplet in your text gives AI vibes even though it's a completely legitimate way of writing and I am sure you did write it yourself.
Yes the blog post was written completely by me. Not entirely certain what triplet you are referring to, or what that might be, but your suggestion is spot on. Going to add a comment with more context of what rama is as a comment myself. Appologies. Not yet used to promoting projects myself...
I totally get it. The triplet was ‘a framework now ready to be used, explored, and built upon by the worldwide community.’ AIs love to claim something is ready or production ready (kinda primed me for thinking AI when I read that), and the triplet is the comma-separated clause, clause, clause.
Why not email HN / dang and ask for a boost? They are very nice and sometimes do, and if it got off to a poor start but is a valuable post, no harm asking. I don’t know the Rust ecosystem enough to judge this, but, good luck.
Thank you very much. We will see, I have been on this for 5 years, if it takes another 10 years for the wider global community to discover rama, so be it. We have patience.
No clue how an AI would write it, but that is sadly how I write, sentences that are perhaps ending a bit too... late. I like my comma's and my em dashes... always have... Used to blog a lot more, trying to pick it up again, with this blog article being hopefully the first of many more to come.
And yeah mostly want to highlight the fact that is ready for production because sometimes people are worried for < 1.0 projects, but want to make sure that people know that we and plenty of other companies are already using it in production for serious projects, not just a hobby or R&D thing.
Our aim is to solve a real world problem with this, so that we can all stop reinventing the same duct-tape mess and instead have a shared foundation that we can all build upon. Such that if there is something to improve or a mistake it has to be fixed once and all rama users benefit from it. While still ahving the flexibility to use and stack your different services however you wish.
OP Here, sorry for not being clear. And happy for feedback on our presentation, docs, my article and ofc the code itself. It has been under developed since over 5 years, and was used in production right from the start. Now we are at a point that it is used by several different companies and even more individual users.
Here is some context and info about the framework that I am quoting from our README to provide you with context:
Rama is a modular service framework for the Rust (programming) language.
The framework is intentionally explicit. Your network stack is built from services, layers, transports, protocols, and state that you compose yourself. That makes the shape of the system visible in the code, instead of hidden behind framework magic or configuration.
This makes Rama a good fit not only for proxies, but for network services where the stack itself matters: how traffic enters, how it is decoded, where state lives, what gets inspected, what gets transformed, and where it goes next.
Whether you're inspecting traffic for security analysis, writing a web service, emulating clients with custom user agents, controlling connection behavior for advanced testing, or building high-performance proxies, Rama provides a clean and composable Tokio-native foundation for network services in Rust.
Rama is used in production for network security, data extraction, API gateways, routing, and other networked systems.
The blog doesn't explain what Rama is, but it's a network library (?) for Rust: https://ramaproxy.org/
Is it a proxy or more? It seems more despite the name.
OP, I am very happy for you releasing, but I see you have zero upvotes. I think explaining what something is is key in any blogpost. And sorry to say, but the triplet in your text gives AI vibes even though it's a completely legitimate way of writing and I am sure you did write it yourself.
Yes the blog post was written completely by me. Not entirely certain what triplet you are referring to, or what that might be, but your suggestion is spot on. Going to add a comment with more context of what rama is as a comment myself. Appologies. Not yet used to promoting projects myself...
I totally get it. The triplet was ‘a framework now ready to be used, explored, and built upon by the worldwide community.’ AIs love to claim something is ready or production ready (kinda primed me for thinking AI when I read that), and the triplet is the comma-separated clause, clause, clause.
Why not email HN / dang and ask for a boost? They are very nice and sometimes do, and if it got off to a poor start but is a valuable post, no harm asking. I don’t know the Rust ecosystem enough to judge this, but, good luck.
Thank you very much. We will see, I have been on this for 5 years, if it takes another 10 years for the wider global community to discover rama, so be it. We have patience.
No clue how an AI would write it, but that is sadly how I write, sentences that are perhaps ending a bit too... late. I like my comma's and my em dashes... always have... Used to blog a lot more, trying to pick it up again, with this blog article being hopefully the first of many more to come.
And yeah mostly want to highlight the fact that is ready for production because sometimes people are worried for < 1.0 projects, but want to make sure that people know that we and plenty of other companies are already using it in production for serious projects, not just a hobby or R&D thing.
Our aim is to solve a real world problem with this, so that we can all stop reinventing the same duct-tape mess and instead have a shared foundation that we can all build upon. Such that if there is something to improve or a mistake it has to be fixed once and all rama users benefit from it. While still ahving the flexibility to use and stack your different services however you wish.