Ecency is technically better than condenser, which should create the discussion of whether we should sunset condenser and use Ecency with a different color-scheme for https://hive.blog. Personally, I think this would also set a visual statement that Hive is truly not Steem anymore, by discontinuing the first application Steem ever had and going with something that is leaner & much faster.
In that case, paying a whole team 130k to maintain the primary native social app on Hive is worth it.
I haven't looked at it much but it doesn't look like a huge improvement from Hive.blog. Peakd on the other hand is light years beyond both. The only thing with Peakd is I wish there was a simpler normie friendly mode that it defaults to with the current advanced mode being suggested about a week later or even a month once the user gets more familiar with Hive.
Last I checked we are paying a significant amount for both front ends yet Peakd is by far the most popular.
By paying so much for these proposals we are just adding a lot more sell pressure to the Hive token for something I don't think is worth the money.
We are paying two teams to maintain two different front ends, one has a very small user base and one is used by the majority of Hive users.
From a joke I wrote near the end of March this year.
You check out my stand up I did in VR the other day? You might get a kick out of it.
I missed it! Going now...
Let me know what you think.
It's too late to throw tomatoes though.
Nailed it.
Peakd is great, but it's closed source. It's written in Vue, (which I'm quite experienced with by now, so it would be much easier for me to contribute than React code). It has more features, but lacks in clarity, UX design, simplicity and is not yet enhanced for speed. Open up Peakd and Ecency and you'll notice how Ecency is much faster.
Personally, I think Ecency is the better candidate for the default open-source social-interface for Hive. It will need more work for sure, but the fundamental code it's built on is A+.
I've got much love for Peakd and the team behind it, but it will most likely require a rewrite and open-sourcing it, as closed-source code is non-acceptable for hive.blog.
Problem is that rewriting it would take time and two dev teams working on two different open-source code-bases is not efficient. If they do want to rewrite Peakd, I'd advise on looking into making Peakd not only a "Hive" interface but something blockchain-agnostic with an independent revenue model.
Last but not least, IMO any project getting funded by the DHF should be open-source and specialised for Hive.
I agree entirely ... we want to do things like this. In the meantime there are some small ui changes even wording changes we could do very quick to make things easier.
뒈져~!
I think is 100% worth it to make it. But it should be idiot friendly for users like me, that want to make there own front end. I would wish for something as easy as a WordPress ( or other CMS) installation. So the technical foundation is done and the marketing can begin :)
With Smart media tokens / second layer/hive engine or whatever it can be a huge gamechanger if this works for the less technical user ( not fulltime developer)