# Dual M.2 Expansion Bay Module

**URL:** <https://community.frame.work/t/dual-m-2-expansion-bay-module/45850>\
**Category:** Expansion Bay\
**Created:** [February 24, 2024, 10:58am UTC](https://community.frame.work/t/dual-m-2-expansion-bay-module/45850 "2024-02-24T10:58:00Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![chubby-laptop](https://avatars.discourse-cdn.com/v4/letter/c/b9bd4f/32.png) [@chubby-laptop](https://community.frame.work/u/chubby-laptop)\
**Post date:** [April 26, 2024, 4:14am UTC](https://community.frame.work/t/dual-m-2-expansion-bay-module/45850/15 "2024-04-26T04:14:45Z")

</div>

@Josh_Cook - saw your reply on my other thread about framework curating stuff like this; replying here just to keep that about the general problem.

> [@Community expansion bays - how will/should Framework curate discovery?](http://community.frame.work/t/community-expansion-bays-how-will-should-framework-curate-discovery/49717/7):
>
> I have done as much validation as I can without using the Expansion Bay interface, as I’m still awaiting documentation from Framework.

I’m still confused. Totally get things take time, I’m just hoping to understand what the actual status of this is - is there a concise way to describe what is/isn’t done, and whatever your current (spitballed) guestimate of a realistic ship date?

---

_[View the full topic](https://community.frame.work/t/dual-m-2-expansion-bay-module/45850)._