Should watch the pre release video https://www.youtube.com/watch?v=QYM3TWf_G38 If what they're saying is true, this project is very much a pile of tech debt. They need to migrate whatever they can early before continuing work on the audio engine.

Been using redmi phones since those are the most personally usable features with great budget option. Current active one has IR blaster, stereo, display finger print, 3.5 jack and sd card slot. ~$190 in 2025 money

Software wise, it is manageable with help of shizuku & canta, as noted also in the article. The OS doesn't have good UI/UX but not bad either. Many of android material features are missing under the custom OS they provide and I'm not doing major rom modification since this is the daily communication & banking phone.

With advent of ai-based impersonation, I wonder why in-person reset is not the priority right now

It helps too that agent work is done server side so you can hog all the local resources for your thin client.

Isn't all uses native OS UI widget? But since the brand need to be experienced the same across platform, it overrides the native rendering and use custom styles instead.

Only using ubuntu rn, but when the server is mostly running docker, it is simpler upgrade nowadays with so little dependencies. But then the problem just moved to the container image updates.

Somewhat agree!. I think my main gripe is that there are no good-enough reader that: - without account integration - has good ux

Even some of the okay ones, most are, as tantacurl may say, janky.

Genuine question, does brave have ff's container extension? currently that's one of the thing that keeps holding me on ff. another big one is i test website on firefox so to not get carried away with features only available in chromium

Containers are experimental as of very recently. So they will soon, but expect it to be in development right now.

I also test on FF and I don't care much for chromium. I was just curious why the author chose to do this.

I've been lucky to discover git relatively late and sublime merge relatively soon. It seems like separating the concern of editing and reviewing code is making me consider each more as separate thing.

It also makes me more comfortable figuring out how a project's pull acceptance are like (maybe due to how fast local ui is compared to web-based git). On the other hand, I can only run some basic git cli commands and can't quickly comprehend raw text-based diff, especially when encountering some linux patches from time to time.