[HN Gopher] Show HN: Subscriber-Only - Paid Subscriptions for Je...
___________________________________________________________________
Show HN: Subscriber-Only - Paid Subscriptions for Jekyll
I want to show you something I've been working on for the past
couple of months. You can check it out at https://subscriber-
only.com If you want to post paid written content on the web,
you'll invariably reach out to Substack, Ghost or good old
WordPress. If you're a fan of static site generators -- like I am
-- you'll know that, by doing so, you'll lose the customizability
and simplicity you get when using a tool like Jekyll. Subscriber-
Only is -- in my 100% impartial opinion -- a good alternative to
using the mentioned platforms. You get to keep using Jekyll and,
with a gem and a couple of lines of YAML, you'll enable
subscriptions, subscriptions management, payment processing, access
controls and all other needed machinery needed to have memberships
on your site. I'm pretty happy with the way it turned out. Do
check it out and let me know what you think!
Author : vmsp
Score : 16 points
Date : 2023-05-17 11:57 UTC (11 hours ago)
(HTM) web link (subscriber-only.com)
(TXT) w3m dump (subscriber-only.com)
| xrd wrote:
| I'm excited about this. I signed up. Are there docs somewhere?
| xrd wrote:
| I'll read more here: https://github.com/subscriber-only/jekyll-
| subscriber_only
| vmsp wrote:
| That's exactly right. That's pretty much all there is to
| know. Your configuration tokens will show up in the site page
| as soon as you setup a payment method.
|
| Feel free to reach me at vitor@subscriber-only.com if there's
| anything I can help you with.
|
| Thanks for you kind words!
| jawon wrote:
| 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 wrote:
| You 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/
___________________________________________________________________
(page generated 2023-05-17 23:02 UTC)