-
Notifications
You must be signed in to change notification settings - Fork 518
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feedbin custom IP/host #944
Comments
Sounds reasonable. Perhaps the right call is to add a separate Feedbin-compatible type of account, which is basically the same but has a text field for entering the URL for the server. |
What is the status of this issue? I can easily self-host, have the infra available. I'll also gladly make a donation for this feature. |
Thanks for the offer of a donation — but we’re not taking any money. :) We would like to get to this feature, but we have some other larger priorities at the moment (Feedly syncing, iOS app, etc.). |
+1 looking forward to this feature. |
Hi, What is the status of this issue? It would be super nice to implement it~ |
How many people that have commented on this issue have an actual working self-hosted Feedbin installation? |
I got it working with docker two years ago only to find out that I cannot use a custom URL with NNW. I have a machine running Mojave (cannot update due to other dependencies) and at the moment feedbin is my only option if I want to keep NNW sync'd with my phone (latest ios). I guess I have to wait. |
Well, I swapped to FreshRSS. I got clients for it on Windows/macOS/Android (what I use). Not using iOS, YMMV. Reeder also works well with FreshRSS, but its not FOSS and paid too. Still, its what I used in the meantime. |
I just set up a self-hosted Feedbin instance to find out that NNW doesn't support my instance. |
Hi,
Would you be so kind to add the ability to add a custom HTTP(S) for Feedbin server? Feedbin server is FOSS, so this way one can have a complete self-hosting FOSS stack with Feedbin plus NetNewsWire (and whatever other clients).
The text was updated successfully, but these errors were encountered: