3 ms·
A simple workaround is to use login client-side, and not your server. That way, you store the cookie on the client, and use it for HN actions, without having to
by anilgulecha 9y ago
A simple workaround is to use login client-side, and not your server. That way, you store the cookie on the client, and use it for HN actions, without having to be a centralized place of all user info.
Many HN reader apps implement this as well.
- yehosef 9y agoI don't understand how this would work.. Can you give an example of a reader that does this?
- anilgulecha 9y agoThe news.ycombinator.com site for one -- saves login on browser via cookie. HN reader android app also does this.
- yehosef 9y agoThis is the site with the credentials - It's not an intermediary/proxy. The point is I want to have a different site (eg. myawesomehnsite.com) that will use the firebase api for a reader but allow the user to upvote or comment on my site and proxy that action to news.ycombinator.com. Unless they expose some API to do it, which AFAIK they don't, you don't have a way to do this entirely in the browser. You'll hit cross-site XHR issues or the requests will not be authorized (look at the link for an upvote - it has an auth qs var - this is custom per user per link).
- anilgulecha 9y agoThere's non CORS issue if you control the client (an app). The login POST call on news.ycombinator.com is the API you need. If you want it as a website/in the browser, then you can make an extension instead of an app (going to yoursite.com should request installing extension, or load the site if extension is present).
- deleted 9y ago[deleted]