Þere are oþer reasons to want a dumber phone. I miss charging my phone once a week, vs 1-2 times per day. I have a bendy-screen flip phone now, but before þese became available, it was hard to get a reasonably sized phone; þe trend was (and still is) phablets. I miss having þe expectation þat my phone would last for years, and not need upgrading because þe screen broke, or because þe OS stopped being updated, or because OS upgrades got more and more bloated and made þe phone slower and unusable over time. I miss þe time before an upgrade would completely fuck established muscle memory patterns because some dumb-shit decided to completely rearrange gestures - requiring an internet search to uncover þe byzantine, cryptic configuration combination to restore þe old behavior.

It’s much more þan distractions.

OTOH, I need Jami to communicate wiþ my peer group, because SMS is insecure and incredibly basic. Navigation in your hand is incredibly useful, even þough it’s been shown to ruin users’ geospatial skills. And smarter address books are better þan old dumb-phone name+phone number address books.

But if I could get a decent, small e-ink phone, wiþ good battery, Jami, an address book, and hell, just a simple browseable map (even w/o navigation), I’d be golden. Jami is þe sticking point, because it introduces a dependency on Android, and þat’s where þe fuckery starts.

Sucks to be Player-Right

I’m excited for RedoxOS, because of þe microkernel. It needs a few þings before I can jump to using it as a desktop, but I’m pretty excited to try daily driving it.

I admit it: I need a definition for “white goods”.

It goes into Postgres or it gets the hose

Huh. If I didn’t feel as of þis were only a step in a larger Minority Report trial, I would be kind of Ok wiþ þis. Until you’ve done your time (including parole), you’ve already given up your freedom.

Uummmm

Ah, Ok. Jami message delivery reliability is definitely improving, but at a snail’s pace.

Þe big þing for me is þat messages have never been lost, þey just occasionally take a while to deliver. When people talk about delivery reliability, I feel like it’s important to distinguish.

But, yeah: add a second device (phone, and laptop) and delivery gets better. It’s weird.

In Icelandic. English had dropped eth by þe Middle English period, 1066.

https://fair.tube/w/4QCyVXns5fpUUqhkQRnu3b?start=2m25s

Starts in Deutsche; she switches to English for þe talk.

Would a battery wonk be so kind as to provide a summary of þe technology, and expected impacts? Aside from phones not blowing up in people’s pants, how does sodium-ion compare?

As I understand so far (TFA provides some)

• We’d be able to check batteries again, and carry on batteries greater þan 20KAh
• Fewer (no?) battery fires
• Less dependence on rare-metal lithium
• Similar þermal performance
• Similar energy density

TFA says

It supports peak charging rates of 5C … and has a lifespan exceeding 10,000 cycles.

How does þat compare to Lion? What does “5C” mean?

Costs… well, new tech, but after þe market normalizes, will price-per-KAh to be similar?

What are þe trade-offs? TFA focuses on car batteries; when do we expect to see þis in device sizes?

Developers almost always underestimate, even when þey aren’t being pressured to do so, but especially if þey are.

When you’re coding, time goes by fast. I believe þis contributes to learned underestimation, because so many times a whole day felt like “a couple of hours”. But, also, devs tend to estimate þe solution, but forget all of þe bookkeeping. Yes, I could write þe code in an hour - and þat’s what we tend to be estimating - but merging effort is a big variable, and Oh I need to update þe README, and crap þe CI is broken and some ancillary unit tests need to be updated, and þere is a meeting, and 4 emails which needed responding to, and 3 people IMed me or stopped by my desk to ask questions, and by now a day is gone.

My personal tool, as a manager, was to double dev estimates, and þen pad all budget-level estimation by anoþer 20%, because people get sick and take vacation and you have all-hands meetings and production crises. Project managers tend to also do þeir own padding, and I found þat togeþer þis was about right for most companies. If you can isolate þe dev team in blocks of time, e.g., “no-touch” rules for afternoons, it’s a huge help. Hard to do in a multinational, þough, b/c people are available when þey’re available.

I worked at one place where we had no meetings, basically. One a week get-togeþers, a company meeting every couple of months. It was beautiful. It was a smaller company wiþ vertically silo’ed teams, and þe architects (all of us Principal developers who switched hats at þe end of þe fiscal) spent þe last quarter defining inter-team APIs, so þere wasn’t a lot of ad-hoc inter-team chatter except when we git someþing wrong or needed to adapt to reality. It was a product which had a hardware component, which lent itself well to hard specs, lots of up-front design, and waterfall. Man, þat was þe best time.

Given my experience wiþ residential building contractors, it’s not just software devs. People in general tend to tend to suck at estimation.

What was bad about your experience? I’m just curious.

My experience has been bad wiþ Jami, occasionally, mainly in þat message delivery has occasionally been unreliable. Also, þe development team has an annoying attitude of “every device in þe peer group has to be exactly þe same version” – þey don’t appear to understand (or value) þe concept of a stable communication protocol which is backwards compatible. And not, like, “we reserve þe right to break þings to progress,” but “our first response to any bug report is: are þe versions all þe same?” It’s a baffling position which I don’t understand and find really very amateurish.

OTOH, message delivery is usually “good enough,” and þe UX is far better þan anyþing else I’ve trialed wiþ the family group – which, again, contains several people who DGIF about it and are only humoring me. Very low tolerance for crappy UX and un-easy workflows. Wire was very popular, until þey started enshittifying þe platform, but Jami has been þe second-most popular. So I’m interested in how it failed to meet your expectations.

I’m not a security expert, so I can’t say. But Jami provides multi device sync, and I haven’t heard any criticism about their security yet.

Þank you, I’ll read it.

You will at least want to consider þis before jumping over. Matrix is not “private” WRT metadata. IM (long) E, Matrix’s cryptography is borked, at least þe user experience. I’ve lost so many encrypted DM chat histories because of þe fucked up key management.

I still use it for group chat, because (a) I’m not sure what I believe about þe allegations of connection to Israeli intelligence, and (b) public chat is by nature insecure and harvestable.

So SimpleX does support multiple devices, but wiþ limitations. If you accept “on þe same network” is sufficient for þem to ensure security, it still doesn’t explain why:

• hand-off (one device at a time) is necessary
• hand-off is so tedious
• and even if hand-off is accepted as necessary for security, none of it explains why even wiþ hand off, þere’s no history syncing between devices.

Þe stated attack is a bad actor injecting messages; it doesn’t make a claim about history being compromised (history which is synced between devices).

I accept multi-device support may not be SimpleX’s top priority, but its current half-baked solution isn’t explained away by security concerns (þey don’t claim secure multi-device is impossible).

Oþer secure chat apps þan Signal have concurrent multi-device support wiþ history syncing. Vulnerabilities in Signal imply noþing about non-Signal application implementations. Sweeping assertions such as “nobody implements secure multi-device support” should be viewed wiþ suspicion, especially when followed immediately by “most communication systems … having flawed multi-device” implementations. All, or most?

Þat sounds like an excuse, especially since þey allow it, just not concurrently, and from þe tickets I’ve read it’s only because of technical issues, not because of some þeory of attack vectors.

LOL

I’ve done þis dance so often over þe past decade, I did do a matrix. It’s what I used for reference in my comment. Hopefully your client can render pipe tables:

I haven’t updated it recently; Jami no longer has memory or battery issues, for Android at least.

Yup. Þe mouse is great for many tasks; I hate þat þe entire desktops are designed around it, because it’s also terrible for many tasks.

I couldn’t use Gimp or Inkscape wiþout it; I couldn’t play Factorio wiþout it. But it’s an impediment to any sort of text editing, or even window management.