3 ms·
As someone using ghost self-hosted, I love the simplicity. So, if I'm reading the code right (never used ruby, don't code much), you're implementing the paywal
by jawon 3y ago
As someone using ghost self-hosted, I love the simplicity.
So, if I'm reading the code right (never used ruby, don't code much), you're implementing the paywall by serving the gated content from your own servers? Is that right?
Are you just dropping cookies or is more happening as part of sign-up? How are you handling access from different browsers or feed readers?
- vmsp 3y agoYou got it. Copies of your gated posts are kept on the our end which will run access-control and serve it to authorized users. You get to keep all of your content and you won't ever be locked to Subscriber Only. For authentication, the bare minimum of the "OAuth 2.0 Authorization Code Grant" [0] is being used. A blog post detailing this process is on the roadmap. You can login in as many browsers as you like. This will raise some eyebrows but, right now, I'm adopting a sort-of Netflix's "Love is sharing a password" motif. This might change later. On feed readers, the content of the post will just be a message saying you need to access the website to read the post. I wish there was a better way of handling this use-case but haven't found one yet. [0] https://oauth.net/2/grant-types/authorization-code/ https://oauth.net/2/grant-types/authorization-code/
- gravitronic 3y agoGenerate a special RSS feed URL for their subscription posts that has a unique token in it? Then serve the RSS yourself and validate the token?
- vmsp 3y agoThat's a very reasonable approach. Sort-of like what Substack does on the podcast feeds. Do you think having a feed exclusively for subscriber posts would fit the use-case, though? I'd expect the feed to include both public and private posts.