One of the original stated goals of DIP was to broaden the base of developers supporting the chain. Giving the upvu team a second bite at the apple before smaller or less established teams have had even a single chance seems actively counterproductive to that goal.
I see no reason these ideas need to be linked in a unified proposal, why not split them up as several different community proposals?
Therefore, we need to be able to provide editors provided by third-party platforms.
I don't understand what is being proposed here. If third party platforms provide editors can't they just spit out markdown code that users can then paste into the steemit UI? What sort of integration is being proposed here?
Currently, Steemit's tags are limited to 5, only English is available, and tags are used to select communities. For this reason, SEO (Search Engine Optimization) is not good
I think you should explain in more depth what is "not good" about this, why it matters, and whether you have ideas for how to measure the improvement you expect your proposal to cause.
- Thumbnail designation and Short description features
This seems like a good idea that could improve the experience of a lot of users. It also seems like it ought to also be pretty self-contained. It would make sense to me for DIP funds to be allocated for this, but it also seems like a good proposal to use in support of the goal of incubating new or not-already-established teams.
Thank you for your nice comments @danmaruschak. To be clear, we really do want other teams to actively participate in DIPs besides our team or the external developer group (@nodehub) we're trying to bring to the Steem ecosystem. We do not know if the 2nd DIP proposal will be accepted just because we raised it, we just hope that steady improvement efforts will continue in the Steem ecosystem.
Steem DIP is a meaningful initiative program that the @steemitblog team is attempting for the first time to develop the ecosystem, and Steemians with development skills must have a high participation rate so that the program can proceed steadily next year. We will gladly accept the outcome of any other DIP proposal submission team, even if our proposal is subordinated or even not accepted.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
From what I know, @danmaruschak you are also a good developer, with good insights and a lot of active experience on Steem. Why don't you submit a proposal and contribute to the Steem DIP's high participation rate? If your proposal is posted, I would like to actively support it!
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
I wasn't confident in my ability to scope and budget things so I didn't submit any fully-formed proposals, but I did submit a few ideas as community proposals, eg here and here. The way I thought things were going to work was that the @dip.team was going to review community proposals and do the scoping aspect and then invite developers to pitch to work on them. I thought I might put myself forward at that stage, but the part where community proposals got reviewed hasn't happened (yet?).
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit