291–300 of 303 posts
Earlier quoted context omitted.
Is Apache installed by default on Windows and MacOS? I find that very hard to believe :) Also, regular users tinkering with httpd.conf? Really?
It is on MacOS. And read my comment again - I agree that expecting users to tinker with httpd.conf is ridiculous.
Earlier quoted context omitted.
> I don't understand why you would ever want this to be a desktop app. I thought you were going to say that it needs to be a website+mobile app for maximum adoption, and I was ready to say that you have a point but full-weight desktop apps still have their place. Then I looked up FreshRSS, and it's an aggregator that you host yourself? Any answer to the question "how can we get more regular users to adopt a service"…
Isn't Apache installed by default on at least all desktops nowadays? Obviously, people should be expected to tinker with httpd.conf, but something fully automated running on top of Apache isn't beyond imagination - and the installation could even be handled automatically if required.
For websites I want to follow that don't provide an RSS feed I wrote a 30 line python script which runs in daily cronjob and creates me an an XML feed that I can import locally in my reader (newsboat). Easy and it works great.
do you have this python script in some kind of github/bitbucket repo? would you mind to share it? Newsboat is awesome!
If other users are anything like me, then to really revive RSS you have to think more multi-device.
Assume the user will want to get to their feed of stuff to read from their phone, tablet, or laptop.
Assume the user will want to listen from their phone most of the time (iphone or android), but maybe their watch while exercising, their car stereo while driving, and through speakers like Echo or Sonos at home.
Get these things to sync up nicely and I bet people wouldn't mind a bit that RSS is underneath somewhere, making it go.
Earlier quoted context omitted.
>the bandwidth is dominated by the RSS feed Exceptionally low cost per hit, as opposed to overall bandwidth. Overall bandwidth will probably fair off worse as you say due to the polling nature of RSS. I think in general RSS readers could do a better job of fetching heads and checking whether or not there is a change worth fetching, that would save a tonne of bandwidth. Also in general, I would be tempted to make an R…
>> the bandwidth is dominated by the RSS feed > Exceptionally low cost per hit, as opposed to overall bandwidth. I don't understand. I'm telling you that my RSS file literally dominates my bandwidth usage in GB. > I think in general RSS readers could do a better job of fetching heads and checking whether or not there is a change worth fetching, that would save a tonne of bandwidth. Yah! Agreed. > It should just be a…
> Yah! Agreed.
You could also reduce the number of ``s you keep in rotation to a more manageable number.
>> It should just be a short `` and a link to the main article (which would still allow you to potentially monetize your content or gauge interest more accurately).
> No, I want people to be able to read it offline. I'm not trying to monetize anything.
It should still be much more lightweight than it's HTML counterpart. Should be almost nothing to it, next to no markup, no styling, no scripts and a highly compressible piece of data.
I don't understand how you're racking up massive bandwidth. Can you put some numbers to it:
* Bandwidth usage for RSS
* Bandwidth usage for webpage
* Hits to RSS
* Hits to webpage
* Links for both
Earlier quoted context omitted.
Since I'm considering to switch from TTRSS to something else, may I drill a bit? (the website is a tad short) I heavily rely on nested categories in TTRSS (Youtube -> News for news channels for example), while the website says it has categories, can they be nested? And most importantly, does miniflux handle about 700 feeds well? It would help a lot if I could lower the update rate of some feeds that only update once…
No nested categories. They're all flat. Miniflux is ultra minimalist and "opinionated," which I ended up preferring to all the others. YMMV! If you're looking for a ton of features or customization, look elsewhere. It's also wicked fast, resource-light, and the code is really easy to grok if you want to hack in anything. But, the update rate is a single global setting[1]. I wouldn't be surprised if it could handle fa…
I don't need much customization, I simply rely on a lot of features for daily convenience. Either way, it seems good enough and I might be able to work around it (or submit a patch if I'm not lazy).
Update rate is merely a concern because I don't want to spam some hosts with repetitive updates for no reason, might be worth another patch.
I don't understand why you would ever want this to be a desktop app. Try FreshRSS[1], it's awesome. It works well on shared hosting and it runs on SQLite. TTRSS only gave me trouble. Threw all kinds of strange errors at unexpected times. I don't know how many times it died on me after an upgrade. I eventually gave up and found FreshRSS. Been running (and updating) it over a year, without a single problem. One of the…
Last week I discovered Cappuccino [1] (macOS and iOS app) . * Interface is native, * Free, with some (paid) premium options, * 3 visualization options (preview, web, browser), * Import and export your OPML configuration, * Native desktop notifications, * Premium daily email summaries, * Premium push notifications. It was also recently released on May 7, 2018. [1] http://cappuccinoapp.com
Not free, but no subscription either.
Earlier quoted context omitted.
It is on MacOS. And read my comment again - I agree that expecting users to tinker with httpd.conf is ridiculous.
Is there a typo, maybe? Your previous comment says "Obviously, people should be expected to tinker with httpd.conf", emphasis mine.
Earlier quoted context omitted.
How do you consume / aggregate the content you previously consumed via Google Reader?
Found out I could live without most of it. Now I visit Reddit and HN more.