SatyrSack

TOS S1E27 "The Alternative Factor"

TL;DR:

Incorporating Tails into the Tor Project's structure allows for easier collaboration, better sustainability, reduced overhead, and expanded training and outreach programs to counter a larger number of digital threats.

I had no idea this issue had been identified. While I find this tool very useful, the project is seeming rather questionable to me now.

I just came across this linked to in the Obtainium README. It is sort of a Ninite-like webpage that allows you to quickly and easily add apps from a curated list into Obtainium on your device. Really useful when setting up a new device or something.

I do wish it was more like Ninite, in that you currently have to tap the "Add to Obtainium" button under each and every individual app that you want go add . I wish this site also allowed you to instead check a checkbox on each app that you want, and then press one button that would add all the checked apps to Obtainium for you.

Neat diagram that I hadn't seen before. I plan to keep this image saved so I can refer to it and make sure I am using adequate ports as I swap cards around.

https://knowledgebase.frame.work/en_us/expansion-card-slot-functionality-on-framework-laptop-16-rkUjGm7cn

I am interested in checking out the historical growth of a particular community. Lemmy Explorer crawls for data about the Lemmyverse every 24 hours or something, and that data is made available on their website. But I can only find where to download the latest data. Is there somewhere that I can find historical data? Does Lemmy Explorer archive these anywhere, or does it just overwrite the previous data each time it crawls?

Come hang out with us and joke around about wormholes and sociopathic parasites at !chevron7@lemmy.world

Our final assembly factory for Framework Laptop 16 and all of our sub suppliers are now up and running smoothly. We had a few bumps as we ramped, with an early material shortage on the RGB Macropad and product serialization and data systems issues delaying some of the keyboard versions. All of those issues are now resolved, and we’re on our way to utilizing full manufacturing capacity. We’re currently aiming for an approximately 5 day cadence between sending out “preparing your batch” emails from batch to batch, with a goal to speed that up to 4 days as we reach peak factory output. We sent out the email to Batch 4 late last week and plan to send the Batch 5 email this week. We expect to fulfill all Batch 5 and most Batch 6 orders before the end of Q1 and all current pre-orders before the end of Q2. We’ll be updating the timing that appears on your order in your user account to reflect this. We optimize manufacturing throughput by scheduling larger runs of each configuration, which means we will have anywhere from 1 to 4 different batches in the midst of fulfillment at any given time.

We also wanted to provide an update on the the open issues that we shared in earlier emails:

1. Keyboard deflection - We shared an improvement in an earlier email which involves adding five additional rubber pads around the Mainboard to provide additional support to the keyboard. In parallel to our manufacturing partner completing qualification testing on this, we’ve started dogfooding it internally in Framework. If you’re not familiar with “dogfooding”, it comes from the idea of “eating your own dog food”, or making sure you’re testing what you’re making before others do. As we mentioned in the earlier email, once we complete testing, assuming the results are positive we will roll this into new production and share a form for existing Framework Laptop 16 owners to request a kit of pads.
2. Secondary SSD may disappear - AMD has provided us with the necessary BIOS fix, which we’re now testing as part of an overall Framework Laptop 16 BIOS update. Our initial testing on it is positive. Once this BIOS is ready, we’ll share it into the Community first as a Beta release before the final release.
3. Display frozen after smart MUX switching - AMD has shared an updated graphics driver with us that has the fix for this along with some new features and performance improvements. This is also currently in our test process, and it will follow the same release path as the BIOS update.

Thanks again for your patience, and we’re excited to get your Framework Laptop 16 to you (or the rubber pads and software updates if you already have yours).

The first Framework Laptop 16’s are now in customers’ hands, with more Batch 1 units in transit to those who have received shipment notices. Both our factory and our fulfillment warehouse are now on Lunar New Year holiday, so the next set of units will ship and production will resume on February 15th in Taiwan. That will include the remaining Batch 1 orders along with the first Batch 2 systems. We’ll remain in continuous production from there, with most of our total factory capacity allocated to Framework Laptop 16 manufacturing.

The various modules that make up the range of Framework Laptop 16 configurations are also in ongoing production at our module suppliers. Our keyboard vendor ran into an unexpected component shortage on the RGB Macropad though that delayed the start of production on it. We expedited the missing component from a US distributor to avoid further delays in their China-based supply chain and it arrived just before the keyboard factory shut down for the holiday. Production of RGB Macropad will begin directly when the factory re-opens on February 19th (the New Year holiday in China is longer), after which modules will ship to our factory in Taiwan to be packaged and then to our warehouse to ship as part of laptop orders.

One other update we’d like to share is the deeper research we’ve done on feedback a few press reviewers had on keyboard deflection. We performed additional measurements on multiple units and found that there is some unit to unit variation, but that there is a greater range across the span of a keyboard in areas that could deflect more or less depending on the support structure below it. The target we’ve set is under 0.6mm of deflection when pressed with 400 grams of force, which puts the keyboard on par with the behavior on Framework Laptop 13. You can see a measurement below on one system with the keyboard aligned to the left, with some keys exceeding the 0.6mm limit:

The improvement on this that we’re currently testing is a set of five additional rubber pads in the locations marked in red in the image below. Our initial testing shows that with these in place, regardless of keyboard position, deflection is below the 0.6mm limit with 400 grams of force. Once we can validate that this is the best solution, we’ll roll it into production and ship rubber pad kits to those with existing Framework Laptop 16 units who are interested in receiving it. We’ll share a request form when this is ready.