superfluid-stream-gated-jwt

[hellwolf]

This is a tool I think worth building:

Let's call it a superfluid-stream-gated-jwt toolkit, which:

1. helps to build netlify/aws lambda type of serverless function.
2. manages these secrets: a). a secret to generate jwt token, b) a list of apikeys for authorized users

It works in ways such that:

1. when an authorized user hit the server with a valid "apikey", it uses superfluid protocol subgraph to check if a stream exists, and if it exists then it generates a jwt token using the secret.
2. depending on the use case, it either return user the jwt token, or a http 307 synthesizing the destination resource url for jwt-gated access control

This is immensely reusable building block for many server gated resources that often easy to plug a jwt token auth module.

For creators, you could think of gate keeping contents for only your followers'!

[kasparkallas]

RPC might be as easy to query as Subgraph in this case.

[shreyaspapi]

@hellwolf

I am a bit confused when you use the phrases which is and which does because they seem to be two different things:

• Which is: The tool will be built and hosted on a serverless function, similar to AWS Lambda. Its primary purpose is to generate JWT tokens for authorized users (if the user is streaming to a certain address).
• Which does: This tool functions as a service, resembling AWS Lambda. It allows projects to incorporate customized authorization logic, such as user streaming at a specific rate or during a specific time period. When an authorized user with a valid API key sends a request, the service executes the project's specified custom code and returns a custom URL to redirect to their app for the user.

[hellwolf]

ah, sorry for the grammatical confusing, I rephrased a little. Hope it helps. It is meant to be a reusable toolkit, and a practical demo of using it is the key.