Well, if they all actually worked, then I'd love to see it. πππβ¨π€
!HOPE
!HUG
!INDEED
!WEIRD
You are viewing a single comment's thread from:
Sort: Β Trending
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
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
That sounds reasonable to me. πππβ¨π€
!HOPE
!HUG
!INDEED
!WEIRD
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