• 3 Posts
  • 32 Comments
Joined 1 year ago
cake
Cake day: July 30th, 2023

help-circle
  • I can’t see a wristwatch defying physics. It likely has to calculate your position fewer times per unit time, thus gets an updated fix less frequently than a phone. Which may be good enough when on foot. Otherwise it would suck the battery dry if it works too hard for a frequent high res fix. (edit: see item 4 on this page Looks like you get one calculation per second which is possibly a bit too infrequent for cycling unless the app is good at using other sensors to estimate intermediate positions)

    When I said CPU load, I should have spoke more generically because indeed a dedicated chip is used. But that chip still needs energy. A dedicated GPS device would indeed help my situation, whether it’s a phone or otherwise. Getting an old dedicated satnav device isn’t a bad idea. The maps on those are far from useable but I recall some Garmins and Tomtoms had bluetooth and I think sending NMEA info is common. That might actually be a good way to repurpose an old obsolete dedicated satnav device – or phone that can be configured as such. There is an opentom project to put FOSS on a Tomtom.


  • what DO you want it to do?

    Essential: navigation (and update maps over Tor), VOIP over VPN, render locally stored PDFs (pushed over adb).

    Non-essential: XMPP (snikket), notes, calculator, take photos, scan QR codes, play from local music library

    GPS navigation is heavy because calculating a fix from GPS satellites is always CPU intensive. This means (on old phones) the always-on screen coupled with CPU load while navigating drains the battery quick, which is a compounding problem because old devices are less efficient. On top of that, the CPU heat degrades the battery and charging performance when it is most needed. I would rather not strap a power bank to my arm. In principle I should navigate with two devices:

    • a phone dedicated to receiving GPS, calculating the fix, and transmitting over bluetooth while screen is off (this could be stashed in a backpack)
    • a phone with screen on and mapping software running, GPS disabled, bluetooth receiving the fix from the other phone

    That would also mean when I stop for food or something I could charge both devices at the same time and they would each drain slower when used. Bluetooth uses much less energy than GPS. This approach is inspired by my PalmOS days, when a palm pilot had no GPS and there were dedicated separate tiny GPS→bluetooth devices. The tech exists but I think the GPS server app is either absent from f-droid or it requires a newer device (I forgot which).


  • I had some immediate objection to Organic Maps when I first heard of them. Was their website Cloudflared previously? ATM I don’t see what my issue with them was. Superficially they look like a decent 2nd option (which I say having not tried their software yet).

    The other demand that makes BIFL phones and even laptops difficult is web browsing,

    Web browsing is such a shit-show even with the latest Debian on a PC that I have almost entirely rejected the idea of browsing from a smartphone. I simply will not invest 1 penny of money or 1 minute of my time chasing garbage services with a garbage device. There have been rare moments where “Privacy Browser” on my old AOS5 phone manages to reach and render a webpage but I have mostly given up on that idea. Even captive portals are a shit-show so I usually cannot connect to public wifi. Fuck it… it wasn’t meant to be.

    Added: video codecs (if you want to watch youtube) are another area where old cpu’s can’t keep up,

    I’m on the edge of scrapping Youtube altogether because of Google’s hostile treatment toward Tor users and simultaneous relentless attacks on Invideous nodes. But up until a couple months ago I could usually fetch a video via Invidious and store locally. My 2008 Thinkpad has been able to handle every video fine so far. I have the Newpipe app on the phone but I’m not really driven to use the phone for YT videos.



  • Early flash memory had a severe bitwear/bitrot issue, but at some point (2015?) they made some strides on that. The best resilience is in the SSDs for some reason. I’m not sure how much SD cards improved, but I suppose a phone’s internal storage would be an embedded SD card.

    It’s a good point, so it would be useful to know if there is a year where bitwear is less notable on phones.

    It’s a shame Fairphone even has internal storage, which seems to go against their vision. But apparently Fairphone users can at least use the external storage as internal (if you neglect the apparent bug mentioned in that thread). I wonder if the internal storage is still needed for the boot loader in that case.


  • Firstly, Rooting/ flashing non-manufacturer firmware voids your warranty. A phone without manufacturer support is going to struggle to be BIFL.

    I just bought an all-metal sewing machine from like the 1960s. Of course the warranty is toast (though it was generous… like 25yrs or something). I would not say it’s not BifL on the basis of warranty expiry. It will likely last the rest of my life which could amount to another 50 yrs.

    Most of what I buy outlasts the warranty. Then I push it far beyond what’s expected. But indeed smartphones are such an obsolescence shit-show out of the gate they will be the hardest product to push the lifetime on.


  • I’m with you there. I have defunded phones for sure and minimized the role of phones. I don’t even use smartphones as phones (no SIM chip). I think the only absolutely essential use case for me is to run OSMand (navigation) because it’s far too impractical to get a paper map for every city I set foot in.

    OSMand is a resource hog. Crashes chronically when overworked. So maintaining OSMand seems to require keeping pace to some extent. Certainly the FOSS platforms will at least enable a phone to stay in play as long as possible – or so I hope.



  • It doesn’t and can’t exist, because the networks keep changing. You could have a 2005 phone that still is perfectly solid, but it’s a 2g phone and the networks now are all 4g and 5g.

    Indeed the amount of lifetime you get out of a phone depends on what you need. I don’t actually use a smartphone as a phone. My phone has no SIM chip inserted. Wi-Fi is not getting outpaced as quickly. If you have sufficient control over your device, you can reverse tether as well.

    This is how my old AOS 5 device connects (2 ways):

    ① AOS 5 → Wi-Fi → router w/usb port → USB mobile broadband stick → LTE(4g)
    ② AOS 5 → USB 2 reverse tethered → 16 year old laptop → router w/usb port → USB mobile broadband stick → LTE(4g)

    My AOS 2 phone (from ~2009ish?) can also still connect via method ① but I have no use for putting it online.

    What I care about is the phone-laptop connection so I can side-load f-droid apps, OSMand in particular. I will always be able to hack together a hotspot to update the OSMand maps.

    and the networks now are all 4g and 5g.

    You may have just helped solve a mystery for me. I was using an HSDPA stick to connect 2 yrs ago. Then one day I suddenly had no internet. Had to scramble to get another mobile broadband stick, which happened to be LTE – which worked. I bitched to the carrier. I thought maybe they pushed a faulty baseband update to my hardware and broke it. They claimed my modem just died. I thought no fucking way does a simple solid state USB device like that just croak. Maybe they pulled the plug on 3g and didn’t inform anyone.

    (update) Nope… Just checked and it was this year that they pulled the plug on 3g… just last month for one carrier. So my mystery is still unsolved. Though I don’t suppose it matters… what good is a 3g modem now? I wonder if there are any hacks to get a 3g modem talking to a self-hosted fake tower.


  • For some strange reason Tor users are able to reach this otherwise paywalled article, so I will post the text below for all those who are unable to reach it. It’s long, so using a spoiler:

    full article

    This article was featured in One Story to Read Today, a newsletter in which our editors recommend a single must-read from The Atlantic, Monday through Friday. Sign up for it here.

    The Instant Pot is, by all indications, a perfectly good machine—maybe even a great one. The IP, as the device is known to its many devotees, is a kitchen gadget in the most straightforward sense of the term: It’s a classic labor-saver, promising to turn ingredients into family meals while you clean up, tend to your kids, and do all of the other things you could be doing instead of keeping an eye on the stove. Once you get the hang of the electric pressure cooker, it seems to basically deliver on that promise, chugging along gamely through years’ worth of weeknight dinners of pork green chili or chicken tikka masala. Since its debut in 2010, the Instant Pot has sold in the millions and spent years as a must-have kitchen sensation.

    Sure enough, in 2019, when the private-equity firm Cornell Capital bought the gadget’s maker, Instant Brands, and merged it with another kitchenware maker, the combined company was reportedly valued at more than $2 billion. A few years and one pandemic later, the company filed for bankruptcy on Monday, weighed down by more than $500 million in debt after years of supply-chain chaos and limited success expanding the Instant brand into other categories of household gadgetry. Perhaps counterintuitively, that the Instant Pot remains a useful, widely appreciated gadget is not unrelated to the faltering of its parent company. In fact, it’s central to understanding exactly what went wrong.

    The Instant Pot certainly didn’t invent at-home pressure cooking, but it did introduce the concept to lots of Americans, and it did so in a plug-in, set-it-and-forget-it format that wasn’t as intimidating (or as explosion prone) as using a stovetop pressure cooker. If you weren’t sure how much you’d use the pressure-cooking feature, that was fine—the IP billed itself as a “multi-cooker,” and it also slow-cooked, steamed, sautéed, cooked rice, and made yogurt. At the height of its popularity, in the 2010s, you could get a basic model on Amazon for less than $100, so giving it a shot wasn’t much of a risk, even if you ended up using it only occasionally. As the device became more popular, it seemed to generate endless word-of-mouth praise for its ability to generate one-pot dinners, and Facebook groups, websites, and cookbooks sprouted up to teach new users how to get the most out of their machine.

    All of this amounted to the kind of public-relations coup that companies are constantly trying and failing to buy for their own new launches. Those failures are not infrequently a result of the products themselves; at this point, it’s very difficult to come up with a novel idea for a consumer good that addresses some kind of real and reasonably common issue. The average American just doesn’t have that many problems left that can plausibly be solved at the level of inexpensive gadgetry. The Instant Pot flourished because the company found a tiny bit of white space in a crowded market, and it sold a machine that did a serviceable job at helping out a particular type of very common home cook: someone who cooks regularly for more than one or two people, more out of necessity than because they find the process creative or relaxing. There was no slick branding exercise foundational to the Instant Pot’s success. The device was the brand. It still is.

    Therein lies the problem, or at least one of the problems. A device developed primarily to address a particular food-prep inefficiency has a natural ceiling to its potential market, and when one catches on as quickly and widely as the Instant Pot, it can meet that market ceiling in pretty short order. Arguably, it can exceed it—people who wouldn’t have otherwise seen themselves as Instant Pot owners buy into the hype. Predictably, after a decade of lightning-fast sales in the United States, things seem to be cooling off. Instant Brands does not release detailed sales figures, but from 2020 to 2022, sales of multi-cookers as a product category dropped by half, according to the market-research firm NPD Group. Instant Pots dominate the category. Very few people seem to need or want a second IP within five years of buying a first one. Why would they?

    From the point of view of the consumer, this makes the Instant Pot a dream product: It does what it says, and it doesn’t cost you much or any additional money after that first purchase. It doesn’t appear to have any planned obsolescence built into it, which would prompt you to replace it at a regular clip. But from the point of view of owners and investors trying to maximize value, that makes the Instant Pot a problem. A company can’t just tootle along in perpetuity, debuting new products according to the actual pace of its good ideas, and otherwise manufacturing and selling a few versions of a durable, beloved device and its accessories, updated every few years with new features. A company needs to grow.

    In the past few decades, the idea that every company should be growing, predictably and boundlessly and forever, has leached from the technology industry into much of the rest of American business. Recently, it’s become clear that those expectations are probably not sustainable even for companies that have produced era-defining software products. They’re certainly not sustainable when placed on the shoulders of the humble Instant Pot, which, despite being an object with a digital display and a wall plug, was never technologically innovative so much as it was a clever, useful packaging of existing components. This was not at all unclear during the product’s heyday, but private-equity interests tried to moneyball it anyway, as they are wont to do.

    When Cornell Capital acquired Instant Brands, in 2019, it merged the company with Correlle Brands, which it already owned and which makes a few lines of kitchenware, including Pyrex. It then began steering the brand into new markets with new products—it tried Instant-branded air fryers, blenders, air filters. None of the new product lines really worked out, because lots of other companies already do a fine job manufacturing and selling those things, and no one really had a reason to choose the Instant Brands version over competitors from Ninja or Vitamix or Honeywell, which specialize in those kinds of products in the way that Instant Brands does the multi-cooker. There was a lot of money, at least while interest rates were low, but there was no second good idea. Of course there wasn’t. Success on the Instant Pot scale is very seldom repeatable. It’s vanishingly rare for it to happen to a consumer-products company even once. But the pressures and expectations of private equity mean that that sort of astronomical success can still result in failure.

    The Instant Pot, for its part, is not dead. Cornell Capital has brought in a restructuring crew, and the brand’s Chapter 11 bankruptcy filing allows it to continue doing business while it seeks relief from its debts. The problem is how the debts got there in the first place—in pursuit of growth for its own sake, of increased output with no clear needs that the new output would address. Even if the Instant Pot were the greatest kitchen gadget of all time, it wouldn’t be enough to overcome that faulty financial logic.





  • I saw plenty of opportunities for enshitification and designed obsolescence.

    There was an APP! So of course the natural order of things is to move more and more functionality from the physical control panel to the app. Then periodically let the app die by obsolescence. Force people to buy new phones to keep up, but then one day the new app no longer talks to old pressure cookers. Make the next version connect to the cloud for programs, and share with the IP maker everything you do. Sell that data to Amazon and Google who want to know what food you’re buying.

    Then make the programs subscription based, so users have to pay a monthly fee to operate their cooker. Justify it by adding more and more programs. If someone does not pay their subscription, shut them down. Make the IP the biggest brick in the house.

    I was actually disturbed that there was a Google Playstore app. Sure, it was optional, but I did not like the fact that my purchase in part financed the creation of an exclusive closed-source app exclusively available to Google and Apple patrons. It should have been an f-droid app.