Skip to content

Notes tagged: indieweb

In reply to https://jan.boddez.net/notes/561d98de2a. Now syncing `channel_source` pivot …

In reply to https://jan.boddez.net/notes/561d98de2a.

Now syncing channel_source pivot column values across channels, which isn’t perfect but works. I’d prefer a source_user pivot table instead of having everything tied to channels first (and use channels as taxonomies, really). But that would be a major change, and baby steps and all.

In reply to https://jan.boddez.net/notes/d66f3eab22. Also, while I know …
jan.boddez.net

In reply to https://jan.boddez.net/notes/d66f3eab22. Also, while I know …

In reply to https://jan.boddez.net/notes/d66f3eab22.

Also, while I know the idea is to manage all of this from within a client app, I just spent a Saturday afternoon making it darn easy to copy and move sources from and to different Aperture channels, because that’s were I actually handle these things. (Because my client of choice—which I was thinking of somehow integrating into the service instead—just isn’t there, yet.)

In reply to https://jan.boddez.net/notes/5b2b850bb4. During this first attempt …
jan.boddez.net

I’m adding an _Unread_ “channel” to my Aperture …

I’m adding an Unread “channel” to my Aperture fork and for a moment there did not know how to stop the pagination cursor from using the order entries are added to a channel—I’m specifically not looking at one channel! And then I figured it out. I’m already ordering entries on date published rather than date added anyway, and because entry IDs are unique, ever-increasing integers, I can use those rather than “order added.”