It would've been extremely helpful, collaborative and synergistic to reach out before, not after :( In fact it is very surprising to me that @good-karma decided to go his own way with all of this without even reaching out. Right now our devs are extremely busy with our own backend and our own features, but if you want to reach out again in a couple of week I'd appreciate it.
What it would be good to know in the meantime is if ecency is considering to remove the link-changing practice that they have currently, and why do they feel the need to do so if they are all about decentralization, anti-tribes, and letting users engage in the frontend of their choice :/
It's good to hear from you by the way, I think we've been on chain for a very similar time and it's always nice to see some old timers thriving and working with amazing projects! I hope you are doing great Melinda!
As you can imagine Ecency Devs have been extremely busy, too. It will be easy for them to remove Leo, but too bad after the work that has gone into including threads.
We have both been here for a long time! What a journey it has been! ♥️
If it's easy, then I'd recommend doing it because anyone sending Threads from ecency is not earning $LEO, so ecency is only affecting users who send threads from their frontend.
Thanks for mention! When we started integration we learned about both dbuzz and threads, after some tests we realized we could offer dedicated UI and also boost usage of these both short form content feeds by including into Ecency. We don’t normally ask Hive communities individually if we can show content from their community. Few people reported their main threads not being indexed by Leo backend which seem to have predefined rules for indexing which is fine and maybe intentional. We will be removing option to publish into threads so it won’t cause issues to your backend.
Leo seems to be restricting Waves.
Leo is not restricting anything, but there are incompatibility issues from the Ecency frontent, causing errors over the Threads backend.
Can we get Leo Devs together with Ecency Devs to get this sorted?
It would've been extremely helpful, collaborative and synergistic to reach out before, not after :( In fact it is very surprising to me that @good-karma decided to go his own way with all of this without even reaching out. Right now our devs are extremely busy with our own backend and our own features, but if you want to reach out again in a couple of week I'd appreciate it.
What it would be good to know in the meantime is if ecency is considering to remove the link-changing practice that they have currently, and why do they feel the need to do so if they are all about decentralization, anti-tribes, and letting users engage in the frontend of their choice :/
It's good to hear from you by the way, I think we've been on chain for a very similar time and it's always nice to see some old timers thriving and working with amazing projects! I hope you are doing great Melinda!
As you can imagine Ecency Devs have been extremely busy, too. It will be easy for them to remove Leo, but too bad after the work that has gone into including threads.
We have both been here for a long time! What a journey it has been! ♥️
If it's easy, then I'd recommend doing it because anyone sending Threads from ecency is not earning $LEO, so ecency is only affecting users who send threads from their frontend.
Thanks for mention! When we started integration we learned about both dbuzz and threads, after some tests we realized we could offer dedicated UI and also boost usage of these both short form content feeds by including into Ecency. We don’t normally ask Hive communities individually if we can show content from their community. Few people reported their main threads not being indexed by Leo backend which seem to have predefined rules for indexing which is fine and maybe intentional. We will be removing option to publish into threads so it won’t cause issues to your backend.
As for links, Khal also mentioned something similar earlier, replied there few minutes ago: https://ecency.com/hive-167922/@ecency/re-khaleelkazi-2023528t83411929z