You are viewing a single comment's thread from:
RE: The Tragedy of the Steem Commons
puts a balm on the rash
chisels off a barnacle from the post
You were saying?
Yeah, it does seem like there needs to be something to communicate these kinds of things. It was already jarring enough when the first apps like zappl and steepshot were (and still are) polluting feeds without any options. It's why musing was the first one I really liked, that allowed (optional) for disjoint interactions, and has the most flexibility for doing whatever they want without affecting other parts of the ecosystem.
No, no, the barnacles are the ones with the rash.
I do like the decision by Musing to switch to structuring things as comments by default, and SteemHunt moving to their own voting system. I just wish they would figure that out before they launch it the wrong way.
I don't know how to cope with dApps that just want to make minimal posts, though. It seems like either posts should remain the basic structure and we should get a front-end for blogging that filters them out, or we need a major structure update. The comment hack doesn't work all that well.
Technically all posts are comments but what we call "posts" are comments without a parent author. Also funny enough the parent permlink field in a post creation transaction on the blockchain is hijacked to be used as the root tag which in my opinion is a little dirty. For the uninitiated here is a root post transaction and here is a comment on it.
The observation is to say that we already have quite a bit of by-convention interpretation done by frontends, with the precedent set by steemit.com. At this point new frontends and dApps need to just deal with this.
So I totally agree with preserving backwards (or sideways?) compatibility. If we think of Steem social media posts as the basic container format, with expectations of some level of social offering, legibility and so on, then dApps need to extend that format, not substitute it.
How to do that though is going to be a challenge to dApp operators but it should be something they are up to to make a successful dApp. You are just reading the writing on the wall here - dApps that don't recognize what you've said end up annoying the vast number of their users, and their non-users but those other Steem users they need to take into account.
Idea for a next post: how dApp owners can actually solve some these issues.
I might make an "everything that goes into a well-formed post" post at some point but I don't totally understand it myself yet. Right now I'm just reading and analyzing posts; one of my projects for this week is learning how to construct them.
As for the issue of trying to force non-present information out of voting, I think the SteemHunt method of building your own independent system is really the only functional one right now. Maybe eventually enough dApps can agree on what they want that the can collectively make an SMT when they're available.
Yeah. I was imagining that dapps only pay attention to their own content. That would make the most sense :P. I think maybe hivemind can easily handle such filters?
It's going to be interesting to see what use people make of Hive once it's more clearly available. The docs suggest that it does a lot of things I'd love to have, but at some point it's going to have to be put into practice. I don't understand the weird soft-launch thing.