By default ( and I’ve left my installation this way), Miniflux uses an sqlite database. For example, you can download the full content of an article (rather than an excerpt) by hitting “d” on the webUI, or using a checkbox on the feed definition. While there are fewer “bells and whistles” in Miniflux, the features that are implemented work well, and stay out of the way. Intentionally minimalist, there’s only one way to read your feeds, and it’s not the classic “ RSS-as-an-inbox” paradigm which Google Reader popularized. The developer, Frédéric Guillot also develops Kanboard, the geek-favorite Kanban tool, which I hope to feature in a future recipe/review. The github repo shows 400 closed issues, 240 closed pull requests, and over 1,200 commits. I stuck it out until something better came along, and then I broke it off… Hello Miniflux My recipe to run (and backup) Tiny Tiny RSS was complicated and fiddly, with workarounds for the app starting before the database, and for the incredibly slow upstream git repo.Įach of these issues I could have overlooked, but all combined, they had me unsatisfied with our relationship. TTRSS’s website currently lists two sponsors, one of which is a shady “pay-for-instagram-followers” organization. ( I do realize this is an issue of my own creation, and not specifically TTRSS’s fault!) I realized I was avoiding using the webUI because the volume of feeds I follow, and all the unread indicators, simply overwhelmed me and made it feel like work. (Some weren’t easy to use, like feediron) I realized that although it has all these cool features, I actually wasn’t using any of them. I hadn’t personally experienced the “ asshole dev” factor, but the forum thread re a migration from GitLab sums up the dev culture, and I don’t like it. I’ve turned off my Tiny Tiny RSS docker stack, and demoted it from the “Chef’s Favorites” back to the general menu, in favor of my new darling, Miniflux. It's been around for years and is very actively maintained.Until recently, if you asked me to recommend a self-hosted RSS reader, I would have pointed you towards every geek’s favorite, Tiny Tiny RSS.įor reasons I’ll explain below, it’s over. Other options I've tried always were missing maybe one or two small things, just enough to make it frustrating but not frustrating enough to bother writing a plugin. A good stable API: I muck around my feeds in Node-Red, mostly for push notifications if something important comes in.2FA cause I'm security conscious like that.Local Image caching/proxy: I have many images feeds that will randomly be deleted by the original author for what ever reason, but I still get to see what was what.Filters: Filtering feeds is important, especially for news services that have a fire hose feed.Labels: and auto labels, really great for organizing stuff.Plugins: Due to it's stability and age there a myriad of plugins that fix small simple stupid things I didn't even notice until I tried out other aggregators.Android APP: Fox's android app is hands down the best RSS reader app I've used.I took over maintenance of the plugin because it's so important to my RSS usage. FeedIron: Full text fetching through the FeedIron plugin.It's usually just small workflow things that I didn't notice until I tried to move to another feed reader What Is SelfHosted, As it pertains to this subreddit? Also include hints and tips for less technical readers. We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. ![]() Service: Blogger - Alternative: WordPress Service: Google Reader - Alternative: Tiny Tiny RSS Service: Dropbox - Alternative: Nextcloud ![]() While you're here, please Read This FirstĪ place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |