RE: A Web2 Bridge for Hive idea
You are viewing a single comment's thread:
I am being selfish, because I have always so much to say. I'm looking at it from my perspective, but you remind me that not everyone uses HIVE for the same reason - as a vehicle of self expression.
Being able to "earn" (and be a patron of the content of others) is something I've written about on chain in the past. Much better than sending money down the tube in one off payments. But I think that's for emancipated accounts to consider, not these "bridged" accounts.
0
0
0.000
Please do be selfish, listeners will need speakers 😍
I've looked at the opportunities to "earn" too, I wrote a manifesto for The Ink Well community for a "readers and writers community" - where readers come to enjoy their writers, connect with them, support their work and form friendships with other supporters. It's great on Hive, you can consume and be paid for it if you want to invest a little money! And if you don't that's fine, too. But somehow we have to get those readers/consumers/curators to Hive.
I'd be interested to read your ideas if you want to link the post(s) 🙂
I originally wrote it years ago, I updated it for "current times" not so many moons ago.
I am grateful for every reader I have here. I joined a local writer's group to help with my fiction, and having the chance to be a speaker / listener in those small groups are fantastic. I hope I can lure one or more of them to Hive. :)
Great, I look forward to reading it!
Here's the manifesto I wrote. It's been updated by the current team for their purposes, and it has some very practical detail about the Ink Well community, but I think the introduction,readers' and investors' sections still stand.
I just had a read. Great! :)
Reading through the comments answered a lot of questions I would have had around the manifesto. Manifesto(s) aren't static things, they can have different versions, and being able to see that history is fantastic. Also, I thought I was following you already, but I wasn't... that is getting fixed now.