<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>hi, it&#39;s mike</title>
    <link>https://mike.puddingtime.org/tags/iphone/</link>
    <description>Recent content on hi, it&#39;s mike</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <managingEditor>mike@puddingtime.org (mike)</managingEditor>
    <webMaster>mike@puddingtime.org (mike)</webMaster>
    <copyright>© 2026, mike</copyright>
    <lastBuildDate>Sun, 20 Apr 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://mike.puddingtime.org/tags/iphone/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SyncTrain for Syncthing on iOS</title>
      <link>https://mike.puddingtime.org/posts/2025-04-20-synctrain-for-syncthing-on-ios/</link>
      <pubDate>Sun, 20 Apr 2025 00:00:00 +0000</pubDate><author>mike@puddingtime.org (mike)</author>
      <guid>https://mike.puddingtime.org/posts/2025-04-20-synctrain-for-syncthing-on-ios/</guid>
      <description>&lt;p&gt;A few years ago I gave Mobius Sync a try as a Syncthing client on my iPhone and iPad. That went about as well as you&amp;rsquo;d expect for an iOS adaptation of something that wants to be an always-on filesystem-watching daemon. It wasn&amp;rsquo;t really worth the stress of wondering what quantum state of sync everything is in, and I hated having to explicitly open it up to nudge it to sync.&lt;/p&gt;</description>
      <content:encoded><![CDATA[<p>A few years ago I gave Mobius Sync a try as a Syncthing client on my iPhone and iPad. That went about as well as you&rsquo;d expect for an iOS adaptation of something that wants to be an always-on filesystem-watching daemon. It wasn&rsquo;t really worth the stress of wondering what quantum state of sync everything is in, and I hated having to explicitly open it up to nudge it to sync.</p>
<p>It&rsquo;s even more annoying now that I&rsquo;ve got an Android-based DAP, and the Syncthing client I&rsquo;ve got running on that to keep my music files in sync comes with options like &ldquo;don&rsquo;t do this over cellular connections,&rdquo; &ldquo;don&rsquo;t do this when you&rsquo;re not connected to power,&rdquo; and a few other things that let you just sort of manage for yourself and accept the potential tradeoffs.</p>
<p>Today I came across <a href="https://t-shaped.nl/posts/synctrain-a-rethought-ios-client-for-syncthing">SyncTrain</a>, which is going to have a lot of the same problems <em>anything</em> that <em>should</em> be running in the background all the time(ish) on iOS is going to have, but includes a nice workaround: You can make an Apple Shortcut to give it a nudge to sync for 10 seconds if it fell asleep on the job. That&rsquo;s enough to check in with other nodes and pull in changed stuff. Since everything is on Tailscale, it ought to work wherever I have connectivity.</p>
<p>I&rsquo;m going to try it out to manage my org-mode todo lists and inbox via <a href="https://xenodium.com/plain-org-for-ios">Plain Org</a>, which can read files off the device storage.</p>
<p>I&rsquo;ve tried a few other things:</p>
<p>SMB shares on my NAS via Files.app. That has worked somewhat well, but there are occasional permissions freakouts.</p>
<p>sftp shares via Blink Term via Files. Also permissions freakouts.</p>
<p>iCloud, which is sort of mysterious (and not available to my Linux machines)</p>
<p>Besides letting you nudge it, the UI for Synctrain is pretty nice. It&rsquo;s clean and native-looking.  If you thought Mobius was all there was, SyncTrain is worth a look.</p>
]]></content:encoded>
    </item>
    <item>
      <title>On iPhoneography these days</title>
      <link>https://mike.puddingtime.org/posts/2021-11-21-i-took-my/</link>
      <pubDate>Sun, 21 Nov 2021 00:00:00 +0000</pubDate><author>mike@puddingtime.org (mike)</author>
      <guid>https://mike.puddingtime.org/posts/2021-11-21-i-took-my/</guid>
      <description>&lt;p&gt;I took my iPhone 13 Pro along as my sole camera for a quick camping trip
to Vernonia. I&amp;rsquo;ve only had the phone for a week and was pretty excited
about its new RAW format.&lt;/p&gt;
&lt;p&gt;I like the images I get out of it, but in a qualified sort of way that
I&amp;rsquo;ve felt about iPhone photos for a little while now:&lt;/p&gt;
&lt;p&gt;Computational photography is a wonder that can do some amazing things. I
have to do a lot less work to get a nice image out of an iPhone in weird
lighting conditions than I do with one of my Fujifilm cameras,
especially when dynamic range is challenging.&lt;/p&gt;</description>
      <content:encoded><![CDATA[<p>I took my iPhone 13 Pro along as my sole camera for a quick camping trip
to Vernonia. I&rsquo;ve only had the phone for a week and was pretty excited
about its new RAW format.</p>
<p>I like the images I get out of it, but in a qualified sort of way that
I&rsquo;ve felt about iPhone photos for a little while now:</p>
<p>Computational photography is a wonder that can do some amazing things. I
have to do a lot less work to get a nice image out of an iPhone in weird
lighting conditions than I do with one of my Fujifilm cameras,
especially when dynamic range is challenging.</p>
<p>A lot of the apparent magic makes sense when you consider that Apple&rsquo;s
engineers bias for one general display use case (screens)
and probably
put their thumb on the scales for tablets and phones. If I take one RAW
photo with a Fujifilm (or some other &ldquo;regular&rdquo;)
camera, and one with an
iPhone, the iPhone photo will be more immediately useful for mobile
sharing.</p>
<p>But I&rsquo;ve held that iPhone pictures tend to fall apart when you try to
work with them much. Fujifilm cameras also do some computational
photography: The dynamic range settings on an X-series camera are all
about applying variable ISO to different parts of the image to cajole
blown highlights and crushed shadows into usefulness. But the effect is
less noisy and messy than what you get on an iPhone when you take a
closer look. For display on small screens, you know, whatever: By the
time Instagram, Facebook, or Twitter are done forcing your images
through compression, there&rsquo;s probably not much difference (though I&rsquo;ve
been surprised when people pick out my Leica/full-crop images from a
Facebook album).</p>
<p>But I do notice that iPhone images come out a little &ldquo;crispier&rdquo; on the
edges from sharpening that doesn&rsquo;t always work that well, and when the
dynamic range is challenging there&rsquo;s more mush and noise.</p>
<p>I should probably burn the ink and paper to make a few 13x19
enlargements from this batch to see what I get. Maybe I won&rsquo;t notice any
meaningful difference, but some chunk of my photographs are destined to
be prints so it&rsquo;s a real use case for me.</p>
<p>I also think that from a &ldquo;most people&rdquo; point of view, I&rsquo;m not sure how
it is that there&rsquo;s a low- or medium-tier fixed lens camera market
anymore. Like, anything south of a Canon PowerShot G-series just doesn&rsquo;t
seem to make a lot of sense unless it&rsquo;s one of those super-zooms. The
iPhone seems to be plenty.</p>
<p>That said, I think there&rsquo;s a level of mobile photography triumphalism
that remains misplaced. I like the pictures I got this morning, but not
so much that I&rsquo;ll hand my travel photography over to a phone. My
Fujifilm cameras are purpose- made picture taking machines with a vastly
deeper amount of control and much more versatile output.</p>
<p><img src="/images/2021/89bad9a598.jpg" alt="">
<img src="/images/2021/45d278f63e.jpg" alt="">
<img src="/images/2021/9e84b98bf4.jpg" alt="">
<img src="/images/2021/ee516456c1.jpg" alt="">
<img src="/images/2021/38cc1b75de.jpg" alt="">
<img src="/images/2021/527526bbe5.jpg" alt=""></p>
]]></content:encoded>
    </item>
  </channel>
</rss>
