![]() They mostly function the same way-tap a few buttons and the article you're viewing will be stored in your account's queue so you can get back to it later-but their free offerings are a bit different, and each has a different advantage when syncing with your e-reader. The only two that currently sync with Kindle and Kobo are Instapaper and Pocket, both of which offer free and premium tiers. Kobo's software can sync directly with your Pocket account.īefore sending articles to your e-reader of choice, you'll have to pick a read-it-later service. Setting that up is easy, too: Create an account with either Pocket or Instapaper, set up the share extensions in your browser and on your phone, and tap some specific buttons every time you come across an article you'd like to read, and they'll be there waiting for you on your Kindle or Kobo. If you have an iOS device, a Focus mode for reading could help you weed out any distractions, but if you have a Kindle or Kobo e-reader, those devices create a much better space for dedicated, distraction-free reading that'll help you finally put a dent in your to-read pile. ![]() Sure, you could dedicate some time to sit down and clear your article backlog on your phone or computer, but those devices throw so many distractions our way with push alerts and text chimes they're rarely the ideal vessel for attentive reading. You can use read-later extensions from Pocket or Instapaper to save articles on your Kindle or Kobo with a single click so you can revisit them later. But it’s 2021 and you don’t need to be in a specific location or use a specific device anymore to read something. It'd be up to you from there to safely munge the CoreData object hierarchy in a way resembling the official clients, but at least you'd be able to linearize those updates against iCloud messages.Between appointments, meetings, time with loved ones, errands, and general to-do's, you might forget about that article you bookmarked in your browser to read when you had the time. Probably the simplest way to do this is to write your own Ubiquity+CoreData client libraries and present yourself as another device that wants to sync against the iCloud account. That's what I really want: the ability to sync Chrome with iCloud even if I currently have no active iCloud-attached devices. Now, the real challenge would be doing this syncing as part of some "syncing service" running on a cloud VM somewhere, that doesn't actually want to run thousands of headless copies of Safari. (And if you can't manage to make it do so, you can write a Safari plug-in presenting a locally-bound HTTP API that the Chrome extension can talk to.) OSA is no COM, but it works just fine for this sort of thing. If you want to manipulate Safari's container, you can prod Safari itself into doing so. Still, even with the way iCloud works, you don't need to directly prod the data. ![]() CalDAV calendar URLs from Calendars.app for iCloud calendars, and these CalDAV resources are writable if you want them to be. Safari bookmark sync, Notes and Reminders, Calendars, etc.) just stayed WebDAV-based with their CoreData databases being purely local+ephemeral, rather than migrating over into using full-on Ubiquity-synced CoreData stores. Ah, this is what had me confused: I was assuming that the parts of "iCloud" that preceded the creation of the Ubiquity sync protocol (e.g.
0 Comments
Leave a Reply. |