Live data from Hacker News

Winds 2.0: It’s Time to Revive RSS

getstream.io

201–210 of 303 posts

Re: Winds 2.0: It’s Time to Revive RSS

#201

Why has this become so complicated? I use Newsboat https://newsboat.org/ to read RSS, and follow about 100 very interesting authors that way. I just put the RSS urls into a text file and the self-contained 1.7mb program does the rest. Somehow it gets by without using a combination of Electron, Mongo, Algolia, Redis, machine learning (!), and Sendgrid. Maybe the comparison with a text-based RSS reader isn't fair and W…

Ah, that's great. It can work as a Newsblur client. I'll definitely give it a try.

Re: Winds 2.0: It’s Time to Revive RSS

#202

Why has this become so complicated? I use Newsboat https://newsboat.org/ to read RSS, and follow about 100 very interesting authors that way. I just put the RSS urls into a text file and the self-contained 1.7mb program does the rest. Somehow it gets by without using a combination of Electron, Mongo, Algolia, Redis, machine learning (!), and Sendgrid. Maybe the comparison with a text-based RSS reader isn't fair and W…

ehm, I don't think a console rss reader isn't complicated for the common non tech user

Re: Winds 2.0: It’s Time to Revive RSS

#203
post #38
post #16

Earlier quoted context omitted.

Agreed; it's impossible to self-host and is therefore a non-starter. For what it's worth, I've been pretty happy with FreshRSS ( https://freshrss.org/ )

All these services have free plans either if you have little traffic or if it's open source. So it's definitely possible to self host this (although maybe not completely trivial). Disclaimer: I work at Stream (but haven't really worked on Winds)

That's not self-hosting. That's paying a cloud provider for a lot of services I don't need.

To me, self-hosting means I can (theoretically) run everything I need, on my bare-metal -- a cloud provider or cloud service (eg, RDS) then becomes a choice, not a requirement.

Suppose you swapped out every piece with a free, local one -- it'd still have the problem of being way overdesigned for what I'd need. Even if the UI looks decent.

Re: Winds 2.0: It’s Time to Revive RSS

#204

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…

> 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.

Re: Winds 2.0: It’s Time to Revive RSS

#206

Why has this become so complicated? I use Newsboat https://newsboat.org/ to read RSS, and follow about 100 very interesting authors that way. I just put the RSS urls into a text file and the self-contained 1.7mb program does the rest. Somehow it gets by without using a combination of Electron, Mongo, Algolia, Redis, machine learning (!), and Sendgrid. Maybe the comparison with a text-based RSS reader isn't fair and W…

> Winds does some crazy cool stuff, but it's hard to see what that is exactly

Images, audio and video in content.

Re: Winds 2.0: It’s Time to Revive RSS

#207
post #202

Why has this become so complicated? I use Newsboat https://newsboat.org/ to read RSS, and follow about 100 very interesting authors that way. I just put the RSS urls into a text file and the self-contained 1.7mb program does the rest. Somehow it gets by without using a combination of Electron, Mongo, Algolia, Redis, machine learning (!), and Sendgrid. Maybe the comparison with a text-based RSS reader isn't fair and W…

ehm, I don't think a console rss reader isn't complicated for the common non tech user

I'd expand on this: do you know any non-tech user that uses any console application:

* knowingly

* not having been introduced to it by a techie

* not being forced to use it by their workplace

?

I don't know any...

Re: Winds 2.0: It’s Time to Revive RSS

#208

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.

Is Apache installed by default on Windows and MacOS? I find that very hard to believe :)

Also, regular users tinkering with httpd.conf? Really?

Re: Winds 2.0: It’s Time to Revive RSS

#209

Earlier quoted context omitted.

Not the guy, but one reason to avoid ubuntu snaps is that it is designed not to allow users to have complete control over software updates. With snaps, the developer controls the update process, not the user. Some people believe that the user should have the final say in what his or her system does. Snap goes against this. It's a great project otherwise. See: https://forum.snapcraft.io/t/disabling-automatic-refresh-f…

I'd add to that a general dislike of the "splitter" attitude taken by Ubuntu. Unity vs Gnome, Mir vs Waylaid, now Snap vs Flatpak. The latter works well, the former doesn't improve in any meaningful way. Why fragment?

Gnome 3 was quite widely disliked by a big part of the community. I'm not sure Unity was necessarily a bad idea.
Post reply on HN