Sure. Could be stored as transfer memos for all I care but think it could be argued that perhaps the user wants to generate discussion around the subject of a tweet.
No, not transfer memos. JSON transactions like Splinterlands cards. Just text, not posts.
Oh duh. Idk custom_json slipped my mind. While at the same time you want users to be incentivized to engage, so if the devs wanna stake up to allocate a portion of the reward pool for that would make sense.
But yeah not just mindlessly posting whatever boring or spammy tweet out there. Maybe it can work like initial tweet share is a json and the moment a user engages that tweet it becomes a post that can thus be discussed.
I think that could work. Just spitballin here
Nothing beats brainstorming.
I was thinking of a simple immutable back up service.
But creating a fluid two-way communication channel between Twitter (back end) and Hive is tricky if you want anyone using any Hive front end or Twitter to have an equal opportunity to engage. If it has to be more or less a one-way street, then I'd prefer to see a funnel from Twitter to Hive than vice versa.