Article
Training mRNA Language Models Across 25 Species for $165
•
21
Dhruv
dhruv3006
AI & ML interests
None yet
Recent Activity
upvoted an article 8 days ago
Training mRNA Language Models Across 25 Species for $165 reacted to theirpost with 🚀 about 2 months ago
Most API tooling is stuck in 2010.
They still assume every API request is a form: with a fixed layout, fixed sections, fixed mental model regardless of how your API actually works.
But is UI useful? Why do we accept all this copy-pasting, clutter, and inconsistency as “normal”?
- Headers that are not needed.
- Bodies that are not used.
- Params scattered across requests
And somehow we call that “API documentation.”
Most API clients are optimized for filling out forms, not for designing, understanding, or maintaining APIs.
hashtag#Voiden was built around a different idea:mThat APIs are systems.
And since systems are modular, the API client should be modular as well.
In Voiden, everything is a Block: Endpoints, headers, query params, bodies, files. You assemble requests from parts, reuse them across projects, and version them like code.
No fixed forms, No fake simplicity, No pretending APIs are paperwork.
If you think API tooling should evolve past “better forms,” Voiden is worth a look.
Take a look here : https://voiden.md/
reacted to theirpost with 🔥 about 2 months ago
Most API tooling is stuck in 2010.
They still assume every API request is a form: with a fixed layout, fixed sections, fixed mental model regardless of how your API actually works.
But is UI useful? Why do we accept all this copy-pasting, clutter, and inconsistency as “normal”?
- Headers that are not needed.
- Bodies that are not used.
- Params scattered across requests
And somehow we call that “API documentation.”
Most API clients are optimized for filling out forms, not for designing, understanding, or maintaining APIs.
hashtag#Voiden was built around a different idea:mThat APIs are systems.
And since systems are modular, the API client should be modular as well.
In Voiden, everything is a Block: Endpoints, headers, query params, bodies, files. You assemble requests from parts, reuse them across projects, and version them like code.
No fixed forms, No fake simplicity, No pretending APIs are paperwork.
If you think API tooling should evolve past “better forms,” Voiden is worth a look.
Take a look here : https://voiden.md/
Organizations
upvoted an article 8 days ago
reactedto their post with 🚀🔥 about 2 months ago
Post
224
Most API tooling is stuck in 2010.
They still assume every API request is a form: with a fixed layout, fixed sections, fixed mental model regardless of how your API actually works.
But is UI useful? Why do we accept all this copy-pasting, clutter, and inconsistency as “normal”?
- Headers that are not needed.
- Bodies that are not used.
- Params scattered across requests
And somehow we call that “API documentation.”
Most API clients are optimized for filling out forms, not for designing, understanding, or maintaining APIs.
hashtag#Voiden was built around a different idea:mThat APIs are systems.
And since systems are modular, the API client should be modular as well.
In Voiden, everything is a Block: Endpoints, headers, query params, bodies, files. You assemble requests from parts, reuse them across projects, and version them like code.
No fixed forms, No fake simplicity, No pretending APIs are paperwork.
If you think API tooling should evolve past “better forms,” Voiden is worth a look.
Take a look here : https://voiden.md/
They still assume every API request is a form: with a fixed layout, fixed sections, fixed mental model regardless of how your API actually works.
But is UI useful? Why do we accept all this copy-pasting, clutter, and inconsistency as “normal”?
- Headers that are not needed.
- Bodies that are not used.
- Params scattered across requests
And somehow we call that “API documentation.”
Most API clients are optimized for filling out forms, not for designing, understanding, or maintaining APIs.
hashtag#Voiden was built around a different idea:mThat APIs are systems.
And since systems are modular, the API client should be modular as well.
In Voiden, everything is a Block: Endpoints, headers, query params, bodies, files. You assemble requests from parts, reuse them across projects, and version them like code.
No fixed forms, No fake simplicity, No pretending APIs are paperwork.
If you think API tooling should evolve past “better forms,” Voiden is worth a look.
Take a look here : https://voiden.md/
posted an update about 2 months ago
Post
224
Most API tooling is stuck in 2010.
They still assume every API request is a form: with a fixed layout, fixed sections, fixed mental model regardless of how your API actually works.
But is UI useful? Why do we accept all this copy-pasting, clutter, and inconsistency as “normal”?
- Headers that are not needed.
- Bodies that are not used.
- Params scattered across requests
And somehow we call that “API documentation.”
Most API clients are optimized for filling out forms, not for designing, understanding, or maintaining APIs.
hashtag#Voiden was built around a different idea:mThat APIs are systems.
And since systems are modular, the API client should be modular as well.
In Voiden, everything is a Block: Endpoints, headers, query params, bodies, files. You assemble requests from parts, reuse them across projects, and version them like code.
No fixed forms, No fake simplicity, No pretending APIs are paperwork.
If you think API tooling should evolve past “better forms,” Voiden is worth a look.
Take a look here : https://voiden.md/
They still assume every API request is a form: with a fixed layout, fixed sections, fixed mental model regardless of how your API actually works.
But is UI useful? Why do we accept all this copy-pasting, clutter, and inconsistency as “normal”?
- Headers that are not needed.
- Bodies that are not used.
- Params scattered across requests
And somehow we call that “API documentation.”
Most API clients are optimized for filling out forms, not for designing, understanding, or maintaining APIs.
hashtag#Voiden was built around a different idea:mThat APIs are systems.
And since systems are modular, the API client should be modular as well.
In Voiden, everything is a Block: Endpoints, headers, query params, bodies, files. You assemble requests from parts, reuse them across projects, and version them like code.
No fixed forms, No fake simplicity, No pretending APIs are paperwork.
If you think API tooling should evolve past “better forms,” Voiden is worth a look.
Take a look here : https://voiden.md/
published an article about 2 months ago
Article
List of Alternatives of Postman
repliedto marksverdhei's post 2 months ago
I really hope so - i thought mamba was already there.
reactedto their post with 🔥 2 months ago
Post
2175
Voiden Blocks: Building APIs Like LEGO
At Voiden, we believe API development should feel like writing clean, reusable code, because it IS code.
That’s why everything in Voiden is a Block, the smallest, most flexible piece of your API world. Your endpoints, headers, query params, JSON bodies, even file attachments, all are individual Blocks you can add, remove, reorder, and reuse.
Think of it as LEGO for HTTP: snap together Blocks to build clean, modular API requests that are easy to read, maintain, and share.
But it gets better. With Reusable Blocks, you create a Block once and import it everywhere you need it, just like importing functions in your code. Update the Block once, and changes ripple through all your requests automatically.
Why this matters:
- Save time & energy, no more repeating the same thing over and over
- Stay consistent, headers, params, and auth always match across your projects
- Keep your workspace clean & focused, add only the Blocks you need
- Collaborate with confidence , modular, maintainable API workflows
Voiden brings developer best practices — modularity, reusability, and version control to API development and testing, helping you build smarter and faster.
Want to see how Blocks can transform your API workflow?
Check out Voiden, open source and ready to use.
Github : https://github.com/VoidenHQ/voiden
At Voiden, we believe API development should feel like writing clean, reusable code, because it IS code.
That’s why everything in Voiden is a Block, the smallest, most flexible piece of your API world. Your endpoints, headers, query params, JSON bodies, even file attachments, all are individual Blocks you can add, remove, reorder, and reuse.
Think of it as LEGO for HTTP: snap together Blocks to build clean, modular API requests that are easy to read, maintain, and share.
But it gets better. With Reusable Blocks, you create a Block once and import it everywhere you need it, just like importing functions in your code. Update the Block once, and changes ripple through all your requests automatically.
Why this matters:
- Save time & energy, no more repeating the same thing over and over
- Stay consistent, headers, params, and auth always match across your projects
- Keep your workspace clean & focused, add only the Blocks you need
- Collaborate with confidence , modular, maintainable API workflows
Voiden brings developer best practices — modularity, reusability, and version control to API development and testing, helping you build smarter and faster.
Want to see how Blocks can transform your API workflow?
Check out Voiden, open source and ready to use.
Github : https://github.com/VoidenHQ/voiden
posted an update 2 months ago
Post
2175
Voiden Blocks: Building APIs Like LEGO
At Voiden, we believe API development should feel like writing clean, reusable code, because it IS code.
That’s why everything in Voiden is a Block, the smallest, most flexible piece of your API world. Your endpoints, headers, query params, JSON bodies, even file attachments, all are individual Blocks you can add, remove, reorder, and reuse.
Think of it as LEGO for HTTP: snap together Blocks to build clean, modular API requests that are easy to read, maintain, and share.
But it gets better. With Reusable Blocks, you create a Block once and import it everywhere you need it, just like importing functions in your code. Update the Block once, and changes ripple through all your requests automatically.
Why this matters:
- Save time & energy, no more repeating the same thing over and over
- Stay consistent, headers, params, and auth always match across your projects
- Keep your workspace clean & focused, add only the Blocks you need
- Collaborate with confidence , modular, maintainable API workflows
Voiden brings developer best practices — modularity, reusability, and version control to API development and testing, helping you build smarter and faster.
Want to see how Blocks can transform your API workflow?
Check out Voiden, open source and ready to use.
Github : https://github.com/VoidenHQ/voiden
At Voiden, we believe API development should feel like writing clean, reusable code, because it IS code.
That’s why everything in Voiden is a Block, the smallest, most flexible piece of your API world. Your endpoints, headers, query params, JSON bodies, even file attachments, all are individual Blocks you can add, remove, reorder, and reuse.
Think of it as LEGO for HTTP: snap together Blocks to build clean, modular API requests that are easy to read, maintain, and share.
But it gets better. With Reusable Blocks, you create a Block once and import it everywhere you need it, just like importing functions in your code. Update the Block once, and changes ripple through all your requests automatically.
Why this matters:
- Save time & energy, no more repeating the same thing over and over
- Stay consistent, headers, params, and auth always match across your projects
- Keep your workspace clean & focused, add only the Blocks you need
- Collaborate with confidence , modular, maintainable API workflows
Voiden brings developer best practices — modularity, reusability, and version control to API development and testing, helping you build smarter and faster.
Want to see how Blocks can transform your API workflow?
Check out Voiden, open source and ready to use.
Github : https://github.com/VoidenHQ/voiden
published an article 2 months ago
Article
Voiden is now open source.
reactedto their post with 🚀🔥 2 months ago
Post
157
Voiden is now open source.
Today, almost every company has it's open-source projects. It has become a norm.And there is truth to it, giving something back to the community should not feel like a grand gesture.
At this moment let us remind us ourselves of our origin story.When we started, the world didn’t need yet another Postman clone.It didn’t need another incremental improvement on X or a slightly faster version of Y.
We weren’t interested in polishing an existing category.We wanted to rethink what it actually feels like to work with APIs in the modern world.To build a tool that felt less like a cockpit of buttons and more like a bridge - between the developer and their intent.Voiden took the long way round.
It is, of course, far from perfect. There are a thousand things that could be improved, refined, rethought.And now it’s open source, which brings two feelings.
First, there’s excitement.The kind that comes from letting the world finally see, it it's truest form what we have accomplished, togather.And then there’s the other one.
The quieter awareness that every decision is now publicly visible.That somewhere out there, some very smart people are already forming an opinion about a choice we made.
This scrutiny is healthy. We do not want to become an ideological echo-chamber.Open-sourcing Voiden invites exactly that - healthy scrutiny.We can not be world class, if we can not defend, with utmost sincierity and gratitude, the choices we have made.We can not be world class if we can not learn from our own mistakes.
This was impossible without all of you, without each one of you.I am proud of all of you to accomplish this, and you should also be proud of this accomplishment.
Let us all remember this is not a destination itself, just a step to beocme something greater.
Godspeed.
Give us a star here : https://github.com/VoidenHQ/voiden
Today, almost every company has it's open-source projects. It has become a norm.And there is truth to it, giving something back to the community should not feel like a grand gesture.
At this moment let us remind us ourselves of our origin story.When we started, the world didn’t need yet another Postman clone.It didn’t need another incremental improvement on X or a slightly faster version of Y.
We weren’t interested in polishing an existing category.We wanted to rethink what it actually feels like to work with APIs in the modern world.To build a tool that felt less like a cockpit of buttons and more like a bridge - between the developer and their intent.Voiden took the long way round.
It is, of course, far from perfect. There are a thousand things that could be improved, refined, rethought.And now it’s open source, which brings two feelings.
First, there’s excitement.The kind that comes from letting the world finally see, it it's truest form what we have accomplished, togather.And then there’s the other one.
The quieter awareness that every decision is now publicly visible.That somewhere out there, some very smart people are already forming an opinion about a choice we made.
This scrutiny is healthy. We do not want to become an ideological echo-chamber.Open-sourcing Voiden invites exactly that - healthy scrutiny.We can not be world class, if we can not defend, with utmost sincierity and gratitude, the choices we have made.We can not be world class if we can not learn from our own mistakes.
This was impossible without all of you, without each one of you.I am proud of all of you to accomplish this, and you should also be proud of this accomplishment.
Let us all remember this is not a destination itself, just a step to beocme something greater.
Godspeed.
Give us a star here : https://github.com/VoidenHQ/voiden
posted an update 2 months ago
Post
157
Voiden is now open source.
Today, almost every company has it's open-source projects. It has become a norm.And there is truth to it, giving something back to the community should not feel like a grand gesture.
At this moment let us remind us ourselves of our origin story.When we started, the world didn’t need yet another Postman clone.It didn’t need another incremental improvement on X or a slightly faster version of Y.
We weren’t interested in polishing an existing category.We wanted to rethink what it actually feels like to work with APIs in the modern world.To build a tool that felt less like a cockpit of buttons and more like a bridge - between the developer and their intent.Voiden took the long way round.
It is, of course, far from perfect. There are a thousand things that could be improved, refined, rethought.And now it’s open source, which brings two feelings.
First, there’s excitement.The kind that comes from letting the world finally see, it it's truest form what we have accomplished, togather.And then there’s the other one.
The quieter awareness that every decision is now publicly visible.That somewhere out there, some very smart people are already forming an opinion about a choice we made.
This scrutiny is healthy. We do not want to become an ideological echo-chamber.Open-sourcing Voiden invites exactly that - healthy scrutiny.We can not be world class, if we can not defend, with utmost sincierity and gratitude, the choices we have made.We can not be world class if we can not learn from our own mistakes.
This was impossible without all of you, without each one of you.I am proud of all of you to accomplish this, and you should also be proud of this accomplishment.
Let us all remember this is not a destination itself, just a step to beocme something greater.
Godspeed.
Give us a star here : https://github.com/VoidenHQ/voiden
Today, almost every company has it's open-source projects. It has become a norm.And there is truth to it, giving something back to the community should not feel like a grand gesture.
At this moment let us remind us ourselves of our origin story.When we started, the world didn’t need yet another Postman clone.It didn’t need another incremental improvement on X or a slightly faster version of Y.
We weren’t interested in polishing an existing category.We wanted to rethink what it actually feels like to work with APIs in the modern world.To build a tool that felt less like a cockpit of buttons and more like a bridge - between the developer and their intent.Voiden took the long way round.
It is, of course, far from perfect. There are a thousand things that could be improved, refined, rethought.And now it’s open source, which brings two feelings.
First, there’s excitement.The kind that comes from letting the world finally see, it it's truest form what we have accomplished, togather.And then there’s the other one.
The quieter awareness that every decision is now publicly visible.That somewhere out there, some very smart people are already forming an opinion about a choice we made.
This scrutiny is healthy. We do not want to become an ideological echo-chamber.Open-sourcing Voiden invites exactly that - healthy scrutiny.We can not be world class, if we can not defend, with utmost sincierity and gratitude, the choices we have made.We can not be world class if we can not learn from our own mistakes.
This was impossible without all of you, without each one of you.I am proud of all of you to accomplish this, and you should also be proud of this accomplishment.
Let us all remember this is not a destination itself, just a step to beocme something greater.
Godspeed.
Give us a star here : https://github.com/VoidenHQ/voiden
posted an update 3 months ago
Post
244
The problem : Hardcoded URLs, tokens, and IDs make API workflows brittle and painful to maintain.
What devs do today
Duplicate values across files or manually swap configs for dev, staging, and prod - easy to break, hard to scale.
Why Voiden :
- Voiden Variables let you define once and reuse everywhere.
- Switch environments easily, keep secrets out of request files, and reuse dynamic values across requests.
Static requests → dynamic, maintainable workflows.
Use Voiden here : https://voiden.md
What devs do today
Duplicate values across files or manually swap configs for dev, staging, and prod - easy to break, hard to scale.
Why Voiden :
- Voiden Variables let you define once and reuse everywhere.
- Switch environments easily, keep secrets out of request files, and reuse dynamic values across requests.
Static requests → dynamic, maintainable workflows.
Use Voiden here : https://voiden.md
commentedon Differential Transformer V2 3 months ago
Good to see a V2.
reactedto their post with 🚀🔥 3 months ago
Post
1193
How do you handle test data in your API requests?
We know generating realistic, dynamic test data can be a hassle - most folks rely on scripts or manual copy-pasting, which gets messy fast.
At Voiden, we built Voiden Faker to generate fresh, realistic data right inside your HTTP requests using Faker.js expressions, no extra setup needed.
We’d love to hear from you:
- What’s your biggest challenge with test data?
- How do you currently generate or manage it?
- Would embedding Faker-like data generation inside requests help your workflow?
Try Voiden Faker here: https://voiden.md/ and share your thoughts!
We know generating realistic, dynamic test data can be a hassle - most folks rely on scripts or manual copy-pasting, which gets messy fast.
At Voiden, we built Voiden Faker to generate fresh, realistic data right inside your HTTP requests using Faker.js expressions, no extra setup needed.
We’d love to hear from you:
- What’s your biggest challenge with test data?
- How do you currently generate or manage it?
- Would embedding Faker-like data generation inside requests help your workflow?
Try Voiden Faker here: https://voiden.md/ and share your thoughts!
posted an update 3 months ago
Post
1193
How do you handle test data in your API requests?
We know generating realistic, dynamic test data can be a hassle - most folks rely on scripts or manual copy-pasting, which gets messy fast.
At Voiden, we built Voiden Faker to generate fresh, realistic data right inside your HTTP requests using Faker.js expressions, no extra setup needed.
We’d love to hear from you:
- What’s your biggest challenge with test data?
- How do you currently generate or manage it?
- Would embedding Faker-like data generation inside requests help your workflow?
Try Voiden Faker here: https://voiden.md/ and share your thoughts!
We know generating realistic, dynamic test data can be a hassle - most folks rely on scripts or manual copy-pasting, which gets messy fast.
At Voiden, we built Voiden Faker to generate fresh, realistic data right inside your HTTP requests using Faker.js expressions, no extra setup needed.
We’d love to hear from you:
- What’s your biggest challenge with test data?
- How do you currently generate or manage it?
- Would embedding Faker-like data generation inside requests help your workflow?
Try Voiden Faker here: https://voiden.md/ and share your thoughts!
posted an update 3 months ago
Post
206
The latest beta of Voiden - the API client built to treat API work like code - is now available.
This is a significant release that is addressing specific feedback we got + it expands some core capabilities and plugins, improving Voiden’s overall performance at scale.
What’s new:
🔹 GraphQL support :
You can now work with GraphQL APIs side-by-side with REST, gRPC, and WSS using the same file-based, version-controlled workflow in linux, windows and macOS.
🔹 gRPC and WSS (Windows support):
Full gRPC and WSS support is now available on Windows, bringing feature parity across platforms.
🔹 Faster performance for large OpenAPI specs :
Opening large OpenAPI files is now significantly faster. We fixed inefficient re-renders that weren’t noticeable in small specs but caused lag with heavy schemas. Rendering is now optimized using React hooks to avoid unnecessary updates.
Additional improvements:
🔹 Voiden now handles imperfect specs more gracefully
🔹 Project uninstalling and support for setting a default directory for project creation
🔹 .env files are now editable
🔹 Improved text contrast for error messages
Try the beta here : https://voiden.md/beta
Share feedback: https://github.com/VoidenHQ/feedback/issues
We keep building in public, and your feedback directly shapes what’s next.
P.S A stable release will follow soon, in the next days.
This is a significant release that is addressing specific feedback we got + it expands some core capabilities and plugins, improving Voiden’s overall performance at scale.
What’s new:
🔹 GraphQL support :
You can now work with GraphQL APIs side-by-side with REST, gRPC, and WSS using the same file-based, version-controlled workflow in linux, windows and macOS.
🔹 gRPC and WSS (Windows support):
Full gRPC and WSS support is now available on Windows, bringing feature parity across platforms.
🔹 Faster performance for large OpenAPI specs :
Opening large OpenAPI files is now significantly faster. We fixed inefficient re-renders that weren’t noticeable in small specs but caused lag with heavy schemas. Rendering is now optimized using React hooks to avoid unnecessary updates.
Additional improvements:
🔹 Voiden now handles imperfect specs more gracefully
🔹 Project uninstalling and support for setting a default directory for project creation
🔹 .env files are now editable
🔹 Improved text contrast for error messages
Try the beta here : https://voiden.md/beta
Share feedback: https://github.com/VoidenHQ/feedback/issues
We keep building in public, and your feedback directly shapes what’s next.
P.S A stable release will follow soon, in the next days.
reactedto sergiopaniego's post with 🔥 3 months ago
Post
3099
New REPL environment in OpenEnv available! ✨
Used in the Recursive Language Models (RLM) paper by Alex Zhang.
Ready for inference & post-training using trajectories. Handles long contexts:
> Run Python code in a sandbox
> Make recursive calls to LMs
> Explore data programmatically
> Return final result
Docs: https://meta-pytorch.org/OpenEnv/environments/repl/
Inference script: https://github.com/meta-pytorch/OpenEnv/blob/main/examples/repl_oolong_simple.py
Used in the Recursive Language Models (RLM) paper by Alex Zhang.
Ready for inference & post-training using trajectories. Handles long contexts:
> Run Python code in a sandbox
> Make recursive calls to LMs
> Explore data programmatically
> Return final result
Docs: https://meta-pytorch.org/OpenEnv/environments/repl/
Inference script: https://github.com/meta-pytorch/OpenEnv/blob/main/examples/repl_oolong_simple.py
reactedto their post with 👀 3 months ago
Post
1080
Voiden makes it easy to work with APIs that use API Key Authentication by giving you a clean and organized way to attach API keys to every request.
API keys are a common way for APIs to identify and authorize clients. With Voiden, every request sent to your workspace APIs automatically includes the correct API key - so the API provider always knows who’s calling and whether the request is allowed.
Each client or service uses a unique API key, acting as a secure identifier attached to every request.
How it works in Voiden :
When you configure API Key Authentication, you simply:
- Choose where the API key is sent (header, query, or cookie)
- Define the key name
- Provide the API key value
That’s it. Voiden takes care of the rest by automatically attaching the API key to every request in your workspace.
Try Voiden here : https://voiden.md/
API keys are a common way for APIs to identify and authorize clients. With Voiden, every request sent to your workspace APIs automatically includes the correct API key - so the API provider always knows who’s calling and whether the request is allowed.
Each client or service uses a unique API key, acting as a secure identifier attached to every request.
How it works in Voiden :
When you configure API Key Authentication, you simply:
- Choose where the API key is sent (header, query, or cookie)
- Define the key name
- Provide the API key value
That’s it. Voiden takes care of the rest by automatically attaching the API key to every request in your workspace.
Try Voiden here : https://voiden.md/