It runs basically the same PebbleOS, so they’ll work with any app that works with the original Pebbles. They plan to keep using the community app hosting at https://apps.rebble.io/. There’s also GadgetBridge that’s compatible. Eric mentioned on HN the intention for an official open source library that can be used to make other companion apps too.

Yeah the mobile app is open source too https://github.com/pebble-dev/mobile-app

I had a 5 II too, used lineageOS for years, worked great. Doesn’t totally solve the battery or fingerprint reader. My screen got the dreaded green lightsaber too. Nail in the coffin was Australia turning off 3G so it can’t make calls anymore. (Wasn’t officially sold here so they didn’t bother loading it with VoLTE profiles)

Seems weird to have a separate app read sent and received messages? Is it poking holes in the Messages app sandbox?

Yeah fair. I tried setting it up, but honestly probably not worth the effort in home networks. Problem is browsers don’t know that the other end of the unbound DNS server is DoH, so it won’t use ECH. Even once set up, most browsers need to be manually configured to use the local DoH server. Once there’s better OS support and auto config via DDR and/or DNR it’ll be more worth bothering with.

Do you have the local unbound server respond to DoH so that the browser also uses encrypted client hello?

I don’t get the term ‘technical debt’. Most people seem to use it to say “We took shortcuts previously, so now we need to go back and do things properly”.

FIrst, it’s a bad metaphor. You take on debt to invest in long term things that will provide future benefits. Telling the bean counters that you need to stop working on useful features to ‘pay back technical debt’ is not making things clearer to them.

Second, you write software, what the heck are you talking about? Compare to civil engineering. If an area gets busier and the existing narrow wood bridge is no longer suitible, engineers don’t say “Wow what idiots built this road with no eye to future growth?” It was built with the needs and resources of the time. To improve it, the bridge needs to be closed, demolished, and rebuilt with planning, labour and materials.

Instead software is empherial. You don’t need to demolish what’s there. No need to build temporary alternative infrastructure. No need for new materials and disposal of the old. It’s just planning and labour to redo a piece of software. It always seems so whiny when people complain about technical debt, as if switching to a different build system is anywhere close to the difficulty of fixing real life; replacing lead pipes with copper for an entire city, or removing asbestos from buildings.

Main thing is the lug width. You could get a few straps on the smaller side and they’ll fit inside bigger lugs, just not look ideal.

Something that can be worth buying in person, even a mall key/watch repair stall would have a variety of types and sizes on hand and can find you something suitable on the spot.