I was thinking on my previous comment that the other forks of #HiveEngage would be used more often than the original Hive Engage app itself !INDEED. 🤔🤯😅
!WEIRD
!HOPE
!PIZZA
You are viewing a single comment's thread from:
Sort: Trending
Yep, that's very possible, and I'd probably prefer using them too. 😁🙏💚✨🤙
!HOPE
!INDEED
!PIZZA
!WEIRD
Those #HiveEngage forks should provide something to contribute to the original Hive Engage app in one way or other, such as by improving the code or donating some funds. 🤔🧘♂️🤗😏
!HUG
Maybe the original #HiveEngage app's source code (by arcange) will have some sort of FOSS license where every fork needs to have a visible link to the original Hive Engage project (the app itself and/or the code repository). 🤔🧘♂️🤓
!INDEED !HOPE !WEIRD !HUG
After all, #HiveEngage seems to be a unique Hive app with features which I think no other Hive blogging frontend offers so far. 🤔😎😏
!INDEED !HOPE !WEIRD !WINEX
Indeed, which is exactly why it should be forked abundantly. 😁🙏💚✨🤙
!HOPE
!INDEED
!WINE
!WEIRD
Whoever forks it the first time might get quite popular here on Hive. 🤔😎 Who knows that even if borniet is very busy right now, he would still be the first Hive dev to fork #HiveEngage? 😆😎😏
!HOPE !INDEED !WEIRD !PIZZA