A microblog of sorts. Collects bookmarks, notes, and likes.
Wanted to update my /uses page with game consoles, but then my browser froze. That said, I don’t actively use any of them, right now. (Not a collector, either. Just happy to (still) have them around.) And I’m not ready to list my fridge, oven, stove, washing machine, lawn mower or car, yet.
Bookmarked https://logicmag.io/security/party-at-my-house-darius-kazemi-on-human-scaled-social-media/.
At some point, though, I started to feel like the balance got out of whack, and I could do more good by putting my work on alternate networks and giving people a reason to get off Twitter.
In reply to https://jlelse.blog/thoughts/2020/06/blogging-german/.
That’s how I do it. English for “technical stuff,” Dutch for, say, (inherently more local) news and politics. (I kind of prefer Dutch—I’m simply better at it.) I would love to eventually “cross over” more often, and write about, e.g., the IndieWeb in Dutch, even though no one reads that blog anymore—I would get a handful of readers through Twitter, which I have left sometime last year. 🤷
Rootless Docker is fun, but you’d better set those environment variables in your systemd and crontab files as well.
In reply to https://jan.boddez.net/notes/f8721d52a5.
Up next: stuff all of these additional bells and whistles behind a couple user settings, and disable them by default. Then open up the instance for others as well, and make OPML import more robust.
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 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 at doing so, i.e., setting up Aperture, found a couple issues with my Docker-based installer, which I’ll address shortly.
But the ultimate goal would be a self-contained package, like a ZIP file, compatible with almost any hosting environment. (You know, like WordPress.)
In reply to https://jan.boddez.net/notes/665808ab18.
Could do both, obviously, and eventually offer a way to easily migrate from one to the other …
Was thinking of launching a (second?) public Aperture instance, but what I’d really like to see is a Microsub aggregator with an integrated, web-based reader and an API, a bit like Mastodon. One that uses a built-in polling mechanism, too, rather than a 3rd-party service (i.e., Watchtower).