Adding an OPML Endpoint to My Aperture Instance https://janboddez.tech/articles/adding-an-opml-endpoint-to-my-aperture-instance
I had to modify the WordPress plugin’s behavior a bit, by the way. Made it accept feeds sans `xmlUrl`, but only if they are of `type="microformats"`. If that sounds awfully specific, _it is_. Especially since they entire `$feeds` array is filterable already. (That would be the other change. Had to do so to allow for multiple OPML sources—I know.)
I should maybe, at one point, look into Yarns, too. Requires only WordPress—Aperture requires quite a few other “building bricks.” While WordPress is far from ideal, its HTTP API and WP-Cron are so easy to expand upon. https://wordpress.org/plugins/yarns-microsub-server/
And properly fork Aperture, so that I can have source names added automatically, and maybe store an RSS/XML feed even if I choose "microformats," for the sole purpose of adding it to the OPML (for the sole purpose of syncing it to my blogroll). #NerdAlert
Being able to modify a source's URL would be cool, too, but I understand they're shared by multiple users. Like, each user has multiple channels, and sources and channels are linked many-to-many, and a source name is stored in the pivot table, because every user (i.e., channel) could name the same source something different. (And the same goes for site URLs, should I want to add those.)
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!