Relay monetization

[ondra-novak]

hi

any idea where to get ads to publish on my relay in order to somehow cover operating costs and keep it free for users?

mosts ad sources are web only that are not applicable here.

[shocknet-justin]

If the solution is to be workable then the first ad should be an ad for that ad space.

[ondra-novak]

I had an idea that I would add dynamically generated events between the results of the REQ command, which would be the result of a keyword search in the ad database. These ads would be added to the results as ad hoc generated events - for a particular position, like third, sixth, etc... The problem is that I don't have any ad provider

[shocknet-justin]

I don't follow why you couldn't use AdWords or web ads in general. Put their content into events as appropriate on the fly.

With selling space you're typically selling views, or clicks, which are measured by web servers... So absent that you need to sell the space directly, which could itself become an interesting marketplace.

[ondra-novak]

Aren't. AdWords limited to webapps only? As a relay provider, I have no website and events are displayed out of my reach

[ionextdebug]

You can implemented my idea of "Decentralized Advertising Network" (https://gist.github.com/ionextdebug/62267472c5cd60ab31698dec82af4c77)

OR YOU CAN SELL PLANS

I started some days ago to write a profitable relay, but now I am without time to do continue it (maybe I return after some weeks or months, maybe not).

The core idea of my Profitable Relay is basically: you can sell permissions/rights for clients, for example:

• You can sell the right to the relay connect to your relay
• You can sell limits of publishing or requesting events
• You can sell limits of storing data
• You can sell rights to use specific NIPs

You can use a simple database schema to define the list of relays and the rights of each relay. The database system can be PostgreSQL or MongoDB, or any other. One table, and verification of right in backend logic.

NAIVE Example of table schema (please, this is only an example to ease understand and application):

client_name	client_ip	right_nip_01	right_nip_02	right_nip_03
nostr-twitter-client	127.0.0.1	1	1	1

Being 1 for true and 0 for false (Have this client the right to use the NIP 01 in my relay? true/false or yes/no)

With this table you can verify in your backend if the client has the right. If yes, then it will use your relay, if no, then you answer with "Please contact [your contact] to buy right to use this NIP-0x" (it's just an naiva example, you can do it professionaly and automatized).

Now I am working in another project, maybe in future I return to do profitable relays.