Another feature, is the ability to lock your "premium" content to subscribers. This means you can post as much, or as little, with no bearing on the reward pool, whilst retaining the potential to earn from people willing to pay for access to your premium content!
How does this work? Does premium content remain off chain?
Images are locked on our end as they are not on chain. Post body/text is not locked for now and remains on chain as a standard post.
Does that feature play well with other frontends? Of course you're aware when one posts on Hive, the content appears 'everywhere' on Hive, all at once. So I'm wondering what the locked image would look like if the consumer is viewing on Hive blog or PeakD? Still locked or not visible at all without any indication of an image being there? A link to liketu? How does this work? Is the paywall universal even if/when another frontend does not/cannot provide the functionality? Is this too many questions? Should I stop now and allow you to attempt to explain? Would that be a good idea?
Lots of reasonable questions.
We have not done too much work on making the experience palatable other than on our own platform thus far, and will be spending the following weeks and months improving on that.
I'll go ahead and suggest an embeddable universal solution. Just an idea off the top of my head so bear with me here. One could utilize your paywall service, upload an image with paywall applied, then go to their favorite frontend, produce their post, embed the image and functionality. A consumer with 'special abilities' could then access the product utilizing their frontend of choice, interact accordingly, without having to leave the comfort of their living room (preferred frontend in this case). Would something like that be next to or near impossible to achieve?
Possible, though a little more engineering involved. Not totally adverse to working this in. It would feel some what invasive to have to deal with paywalled content (remember it's pictures that are paywalled, words are not) when you are using a "show all on chain" kind of front-end. We leaned on tailoring the experience to use our front-end because we wanted to get the proof of concept working in an environment we have some control of. Ultimately, as our resources expand, we would pay attention to how posts appear on other front-ends too.
Point taken.
Excellent. I produce digital art. So of course I'm interested in displaying a lower quality version that still gets the point across and placing the full version designed for downloading behind a paywall then offering access for the low low price of whatever I decide is fair, for instance.
The NFT scene is, neat, I guess, but I'd much rather utilize a subscription service since the artwork only plays one important role of many involved in creating my content. So far on Hive I've yet to stumble into any potential solutions suitable for how I like to do business. I like the consumer to be able to access everything, all in one space, but so far each service demands the consumer bounce around from site to site and back if they forgot a step like voting. Far too many clicks and steps involved in something that should be a seamless experience. A blurred image that's impossible for the consumer to see doesn't quite fit in with the way I prefer to present my work and is like offering someone unfamiliar with my brand a mystery box. It's next to impossible to make money if they don't know what they're buying.
I'll keep my eye on your service though and see how things take shape. I'm sure on your site itself, everything would work well together, but unfortunately there's the potential of the product appearing disastrous elsewhere on chain and that could result in chasing away new potential followers, customers, and the like. Common growing pains of Hive though. Even basic formatting of text can look different depending where it's viewed. Some frontends display images larger than others. Content can appear 'perfect' in one space then look like Frankenstein in another.
Anyway, that's not a complaint about your service. I look forward to seeing yours in action and simply felt like offering some food for thought coming from the user experience side of things.
I obviously don't know how they are implementing it, but I can easily imagine a simple protocol of requesting a signed message (eg. via Keychain) before an image is provided. Other front ends could choose to replicate the same thing, but it wouldn't play so nicely with those that don't choose to implement it.
I'm leaning towards an embeddable solution, if it's possible, but I wouldn't know, since I can only develop ideas, not apps.
Hey, hey, good2see you! Will you ever post again?
Been thinking about it. Good to see you as well.
Wow 😳 impressive