Having `source_user` rather than `channel_source` would clear up some of this confusion. And `entry_user`, perhaps, so that we can still filter entries in a user-specific (rather than channel-specific) way. Or we drop all that and just parse feeds. And filter dynamically, if we must. That’s what RSS readers do, I think—not sure. They don’t offer different channels. One category per source, and limited options otherwise. Ima look at FreshRSS’s code.
Would anyone want the same content displayed differently in different channels, though? I mean, probably not. (Wondering if there’s some sort of `hasManyThrough` with pivot data.)
“Really easy.” I’ve given the channels as categories some more thought, and editing sources outside of channel context isn’t too easy, either, _if_ you want to offer “channel-specific source settings,” like if the aggregator should try and fetch original web pages rather than save just the feed summaries. (In Miniflux, which knows only categories, and limits them to one per feed, this is a source-specific setting. Or rather, user-specific source setting.)
Not horrible at all (scratches aside).
“But it’ll never catch on!”
> Success in the IndieWeb is not measured by creating an app or platform with a large user-base[.] Success is achieved if even you yourself use your software regularly for your primary web identity.
Surely there’s quite a bit that can be borrowed from Aperture. Not sure if I want extensive filters and what not. (Maybe you should, you know, just unfollow feeds you don’t enjoy reading. Anyhoo, we’ll see.) Not sure if the JS modals are a keeper, either. Not a big fan of ’em, although they are interesting (and kind of work well here).
Think I’ve got it. All that’s left is the actually hard stuff: the interface for adding, editing, and categorizing feeds and channels.
Don’t really like explicit IndieWeb post types (or kinds), but you knew that. And, the spec seems to agree.
> [Post Type Discovery] helps avoid the need for explicit post types that are being abandoned by modern post creation UIs.
IndieWeb Adventures https://jan.boddez.net/articles/indieweb-adventures
Laravel’s scheduler would make all of this so easy. But: if I use the built-in `hourly`, `everyTwoHours`, `twiceDaily`, etc. schedules, lots of feeds would still get downloaded at the exact same time (_on_ the hour). So, I can either use `hourlyAt($minutes)` to spread things out a bit, with `$minutes` a random offset (and somehow skip rarely updated feeds that I deem “not yet due”). Or simply use `everyMinute` and something like a `next_check` column to only fetch and process overdue feeds.
In reply to https://jlelse.blog/thoughts/2020/11/minimalist.
Hehe, I’m not too big on consumerism—my laptop and smartphone are “budget models,” and nearly everything we’ve got, we got secondhand—either, yet can’t throw anything out! Can’t stand waste, I guess. Might one day blame it on my engineering background. ’Til then, I’m a self-proclaimed cheapskate!
So fascinating to see what a burning trash fire, Facebook and Twitter and YouTube have been this election season (disinfo, white nationalists, etc) compared to what I've seen here on the #Fediverse during this same last 90 days.
BREAKING: I cleaned my car today, for the first time in many months. (And didn’t even have to dry it, as it started raining right when I was finishing up. And applied a couple touch-ups to the leather on the driver’s side. Thing turns eight in a month, and it’s kind of starting to show.)
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!