GeorgeHahn

There’s one incoming, https://baochip.github.io/baochip-1x/ It would be great to see more.

Is that true on the pro? I trialed one maybe a year ago and got the impression that the company had stopped supporting third party devs.

I had a hang that sounds similar to yours the other day, and it appeared to retrain on the next boot. Does that line up with what you've seen?

I agree, the input devices leave something to be desired. I dream of grafting a MBP keyboard and trackpad onto my FW13.

It's plausible that broad concern about recycled plastics would be valid.

This study[1] found that the recycled plastics analyzed were fairly toxic. I recall another that found the same for recycled synthetic clothing, but I was unable to find a reference.

1. https://www.sciencedaily.com/releases/2023/11/231110112511.h...

That doesn't fit the bill:

Output voltage (four charging modes): PDO DC5.0V-3.0A or 9.0V-2.77A PPS 3.3-5.9V-3A or 3.3-11.0V-2.24A

5V output at 5A is pretty unusual.

I'm a Boox device owner and can confirm they declined my request for the GPL source code.

I enjoy this simply to have sunset, sunrise, and moon phase on my wrist. The added precision from the finetune watch face is a nice bonus.

How does this compare with Fermyon's WebAssembly platform?

I love this idea! Thanks for sharing, I'm looking forward to trying this out day to day.

I wrote a server that bridges Subsonic clients to my Spotify library. I like that it lets me to stream anything on Spotify but I can still fill in favorites that aren't available.

This appears to share lineage with Umbrel. I haven't looked deeply enough to make any particular claims, but I feel fairly confident that one of these projects is violating someone's copyright.

For an example, compare https://github.com/meienberger/runtipi/blob/master/scripts/a... with https://github.com/getumbrel/umbrel/blob/master/scripts/app.

I suspect they're referring to the more recent Sensor Watch: https://www.crowdsupply.com/oddly-specific-objects/sensor-wa...

Quick review: I have one of the early units and I've really enjoyed using it. It's totally hackable, well documented, and I fully anticipate using mine for the next decade or longer. It's far from a smartwatch - it's more like you're sitting in on the Casio product meeting where they wrote the original F-91W specs. The year-scale battery life remains, but it comes with the ability to fully customize the watch behavior. For me, that meant adding sunrise/sunset and moon phase faces. I might build a quick-timezone switcher in the future.

Firefly III has a documented API [1] that can be used to build import tools. I used it to build a Plaid importer [2].

1: https://api-docs.firefly-iii.org/

2: https://gitlab.com/GeorgeHahn/firefly-plaid-connector

As a current candidate, I'd be interested in hearing more about your interview experience.

Autodesk has shared some information about how they solved this when building AutoCAD Web, which is a wasm app derived from their desktop codebase.

Video: https://www.infoq.com/presentations/autocad-webassembly/

Would it be possible to get an updated recipe link? I was hoping to try this, but it looks like the paste has expired. Thanks!

In addition to products mentioned by others, Espressif parts are used in a few of the new LIFX devices.

I use BookStack (https://www.bookstackapp.com). MIT licensed & easy to self host.

It's fast and has good search, a good editor, and uses simple hierarchical organization + tagging. I like that it gets out of my way and does a good job of handling everything from code snippets to freeform thoughts to recipes.

BookStack is best for things that 'look like' documents. Mobile editing could also be better - you have to click a maximize button to get a usable view of the editor and the editor UI still takes up a lot of space. It is web based, but it is very lightweight and I have found it very easy to host.

I could see this being a great home server - it could easily run NAS, Plex, a firewall, and some misc containers. It may be a cheaper option for robotics projects that don't need the compute ability of a NVidia Jetson.

Pretty awesome board:

- Intel J4105 (2.3Ghz Quad-core, fanless!)

- Up to 32GB DDR4

- M.2 SSD (4 x PCIe 2.0)

- 2 x GbE

- 2 x SATA 3.0

- HDMI 2.0 and DP 1.2 at 4k

- 2xUART, 2xI2C - both at 3.3V

- 110x110x43mm

- Expected to ship in late November, price will be above $100

Snapcast would likely work better for this use case - it handles audio endpoint synchronization.

https://github.com/badaix/snapcast

running a compute-intensive AI model

For what it's worth, I made the same mistake and have since discovered that ZFS on Linux is a smooth experience. Raided a pair of SSDs and now enjoy a (single) real command line and native docker containers.

Have you verified that CH_PD stays low when the ATTiny is asleep? I'd consider putting a 10k pulldown on the CH_PD line so it defaults into powerdown mode. Do you have a multimeter? Insert it between VCC and U1 and between VCC and US1 to verify your sleep currents [1].

The 3.3v regulator could certainly be improved. Once you've verified that your sleep currents are within the expected range (<1mA), consider swapping it for something more efficient. A board like [2] should work reasonably well if you set UVLO to the minimum value of 0.3V [3]. This should get you to a few months of battery life.

A large capacitor (500+uF) on VBATT will stretch this a bit further. You want something with low ESR (the batteries should be around 400 milliOhms total; try to stay under 100 milliOhms). Anything here [4] would be pretty reasonable (supercaps are also a good option).

If you want to go even further, switch to an ATtiny85V and run it directly from the batteries. (This will work with your ATTiny85 as well, but you'll drop below its operating voltage while there's still a fair bit of usable charge left in the batteries.) Instead of wiring to CH_PD, you can wire it to the enable pin on your regulator (unfortunately not exposed on [2]; it's pin 6 on the TPS61200). You'll need to level shift the ATTiny<->ESP8266+sensor signals. The advantage here is that the ATTiny power doesn't take an efficiency hit from a converter and the ESP8266 and sensors can be 100% powered down when not in use. This is what I'd do if creating this as an original design on a single board.

[1] https://openhomeautomation.net/esp8266-battery/ [2]: https://www.sparkfun.com/products/10255 [3]: https://www.circuitsathome.com/dc-dc/tps61200-board-modifica... [4]: http://www.mouser.com/Passive-Components/Capacitors/Aluminum...

There are three big things to look out for on the software side. Are you using deep sleep? Are you putting your sensors into shutdown mode between measurements? How long does it take to take a measurement, connect, and report?

On the hardware side, consider using a switching power supply. Many cheap/small ESP8266 breakouts use inefficient linear regulators. You may also consider adding a big capacitor across the battery +/- lines. This will help smooth out the large current pulses consumed by the device, which can be quite important as the battery voltage starts to drop.

The ESP8266 is pretty power hungry, but you should be able to get much more than two weeks on those batteries. Even in the worst case scenario, I'd expect about three months.

I'd be happy to take a look at your schematics and code. (email in profile)

Pretty easy to download on a desktop as well: https://github.com/coursera-dl/coursera-dl

Here's a video full of these! https://www.youtube.com/watch?v=RRQaXDafs_Y

Unfortunately, it appears to be a design problem on the Microsoft side: https://github.com/Microsoft/BashOnWindows/issues/111#issuec...

I had a similar experience with Lenovo. I was unable to use my device for nearly six months, during which I went through about four returns. They kept sending my laptop back broken! They sent it with a range of issues - initially, they failed to fix the intermittent display flickering, afterwards, it came back with a keyboard containing dead keys, dead LED indicator lights, and missing screws. In the end, I called and told them they were going to pay me for the laptop and we'd part ways.

I will never buy Lenovo again.

I have amazing small/medium business support from Dell on my monitors. If I see a dead pixel, slight backlight fade, or any other issue, I can call Dell and have a new monitor sent overnight to my door.

I think many of us who use Windows take for granted the number of tools we use to cover over our pain points.

I use Msys2, Cmder, a bunch of custom tool builds, and some Powershell scripts. This setup works great; I'm productive with it and my command line feels fantastic. However, I have been tweaking my setup for years. WSL makes all of that learning, setup, and tweaking unnecessary.

All of your tools are available out of the box, and you don't have to configure anything, hunt down binaries, or make your own builds.

This isn't about making you and I more comfortable - we already are. This is about making it easier for other devs to find a happy setup on Windows.