Reeder (iOS) integration with TT-RSS (via Fever API)

[IvanRaide]

You can use your admin account. It makes no difference, as long as you simply enter your username as "admin" into Reeder.

I use it with admin as well, and it does work.
Would also like to say, GREAT JOB with this plugin!

[DigitalDJ]

Is there no way around that?

Still, thanks for the plugin, it's been incredibly useful.

There is no way around it, it's a Fever API limitation. It uses time to determine the latest synced feed opposed to the highest article ID.

If you use your patch you might get the accurate post times but marking all as read may have undesired results.

[benjennings]

Thanks for the fantastic plugin

Just a random question - why clone the Fever api rather than the Feedbin one? Reeder (on iphone) supports both and presumably the osx and ipad versions will too. The reason I ask is that the Feedbin api seems more developed - ie can add/delete subscriptions.

Keep up the great work

[DigitalDJ]

Thanks for the fantastic plugin

Just a random question - why clone the Fever api rather than the Feedbin one? Reeder (on iphone) supports both and presumably the osx and ipad versions will too. The reason I ask is that the Feedbin api seems more developed - ie can add/delete subscriptions.

Keep up the great work

You can't specify a custom server using Reeder's Feedbin access. Feedbin is a service provided at a fixed URL, Fever is self hosted. Providing support via Feedbin API + Reeder would require a Jailbreak tweak. I don't think Reeder supports adding/removing subscriptions anyhow (I could be wrong?)

[benjennings]

Now that's a fantastic reason!

As for adding/removing, Reeder added it for iphone for google reader I believe. But not for anything else as far as i know. I'm sure it must be on the list to do but getting everything shifted round for the google deadline must be very stressful for the developer!

Thanks for the answer

[morsedl]

Hi Folks!

So, it took me a bit to get this working -- turns out I was using http://<servername>/tt-rss/fever/ instead of http://<servername>/tt-rss/plugins/fever/ -- but I finally got it working. This is great, thanks so much!

However, part of my problem was that I was also trying to get this Fever plugin to work over https:// instead of http://, which simply did not work. I could not even see records of the attempt to connect in either /var/log/syslog, or the various /var/log/apache2/* files, or in the "ttrss_error_log" table (which has no rows in it).

So, my question is this:

Has anyone had any luck getting this Fever plugin to work over https:// (SSL)? I've been using tt-rss with https:// and prefer not to be sending usernames / passwords unencrypted over the wire.

I'm an experienced developer and would be happy to help get https:// working with this plugin. But I do not know where to start, as I have no information as to why it's not working. When I specify https://, Reeder does seem to try to connect and login because there's a couple of seconds delay between pressing "Done" and getting Reeder's error message ("Login Failed: Please try again.", which itself is not very diagnostic). This, and the fact that I see no record of activity whatsoever on the server side when trying to setup the Reeder Fever account using https://, leaves me unsure where to turn. Obviously, using the tt-rss web interface over https:// is working just fine for me. So, any suggestions and pointers are most welcome!

You can also email me directly at dm at-sign dougmorse period org.

Thanks!
Doug

[DigitalDJ]

Reeder rejects self signed invalid SSL certificates I.e anything that poses a security risk. There is no option to skip this check. You can use a free valid SSL certificate from Startcom.

[cfarence]

Would installing the SSL certificate in iOS allow reeder to trust it?

[MacDork]

He meant installing it on your server where your tt-rss is hosted.

[morsedl]

Hmm... Interesting point, thanks all!

My server does not use a self-signed certificate, rather one issued by CACert.org. However, CACert.org's certificate is not always pre-installed and I doubt it's a part of Apple's default set of CA issuers.

So, I'll try following the procedures at http://wiki.cylonmobile.com/home/add-ca ... -to-iphone to add a new CA to my iPhone.

I'll also check if CACert.org's certificate is already installed (if I can figure that out, which shouldn't be too hard). I'm sure my server's certificate was added at least as an exception, as the same certificate is used by my server to encrypted SMTPS and IMAPS, which are both working fine with the Mail.app of my iPhone.

[ZeGuigui]

Maybe you need an intermediate CA cert to add to your web server?
This is the procedure for StartSSL certificates (well the free ones at least!)
For apache: http://httpd.apache.org/docs/2.2/mod/mo ... echainfile

[DigitalDJ]

Adding CACert as a trusted CA should work. Alternatively, you could create your own CA, sign your certificates and add that. Alternatively, StartCom's free SSL certificates have compatibility with the majority of browsers and mobile devices (including iOS6)

[morsedl]

@ZeGuigui: Thanks! I'm pretty sure I already have added the CACert.org certificate to my server (in /etc/certificates) and it's referenced in my Apache2 configuration. It may be that I need to create a certificate containing both my server's cert and the cacert.org cert, that is, create a file with the full certificate chain (although I'm not sure how to do that, yet).

@ZeGuigui & @DigitialDJ: Thanks! I'll check out both StartSSL and StartCom. I'm looking for free, and it'd be nice to have my server's certificates signed by an authority more widely known / recognized than cacert.org.

[morsedl]

Hi again,

Hmmm... I just added CACert.org's root certificate to my iPhone by following these instructions:

http://wiki.cylonmobile.com/home/add-ca ... -to-iphone

but it showed up as accepted but untrusted. I installed the cert by emailing the exported .mobileconfig file to myself and installing the profile using the iPhone's Mail app. It turns out, though, that per:

http://nat.guyton.net/2012/01/20/adding ... ad-iphone/

one must install the cert using the iPhone Configuration Utility (IPCU) rather than an emailed .mobileconfig file; otherwise, the cert will be untrusted. So, once I removed the previous install and did it again using IPCU, the cacert.org root cert showed up just fine and as trusted on my iPhone.

However, still no joy: I am still getting "Login Failed: Please try again." when I try to setup a Fever account using https:// (rather than http://). http:// access sti;l works.

Any ideas?

Also, @ZeGuigui, @DigitialDJ, @MacDork, and @cfarence:

Can any of you, or anyone else, confirm that they are indeed using Reeder against TT-RSS with this Fever API plugin on their own server using HTTPS / SSL as opposed to HTTP / Plain Text?

Again, I am most grateful for all the assistance!

Doug

[ZeGuigui]

I do use reeder + fever API + TT RSS over https and no problem here! My certificate was issued by StartSSL.

Did you follow CaCert instructions on how to add the chain file to your http server? Can you give your domain name so that we can point a browser to it and analyse the certificate?

The procedure to add a "root certificate" is for company generated root certificates that are not signed by a trusted authority. I believe CaCert.org is a trusted authority and if your server config is OK you should not need all that mobileconfig stuff!