RE: I Am #AliveAndThriving Today! || #IAmAliveChallenge || Daily Off-Grid Jungle Journal Entry: Day #1168 - 14,000 HP Today, and Trial-Error-Progress with the Payout Scripts - Lower Puna, Far East Big Island, Hawai'i - Wednesday, October 8, 2025

You are viewing a single comment's thread:

Maybe you also want to say that future digital archaeologists will eventually find #DeepEngage which is an app for digital archaeology !INDEED! πŸ€”πŸ€― However, Hive apps themselves aren't built on the blockchain itself though, but would be a good idea for future Hive projects! πŸ€“πŸ€―πŸ˜…

!WEIRD
!HOPE
!HUG



0
0
0.000
19 comments
avatar

Well, if Engage still exists, then the forked version with no expiration time would be very helpful indeed. I'm curious how a Hive project could actually be build on the blockchain. πŸ˜πŸ™πŸ’šβœ¨πŸ€™

!HOPE
!HUG
!INDEED
!WEIRD

0
0
0.000
avatar

I wonder what would happen in the medium-term to long-term if #HiveEngage and multiple forks of it exist at the same time !INDEED. πŸ€”πŸ§˜β€β™‚οΈπŸ€―πŸ˜…

!WEIRD
!HOPE
!HUG

0
0
0.000
avatar

Well, if they all actually worked, then I'd love to see it. πŸ˜πŸ™πŸ’šβœ¨πŸ€™

!HOPE
!HUG
!INDEED
!WEIRD

0
0
0.000
avatar

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

0
0
0.000
avatar

Yep, that's very possible, and I'd probably prefer using them too. πŸ˜πŸ™πŸ’šβœ¨πŸ€™

!HOPE
!INDEED
!PIZZA
!WEIRD

0
0
0.000
avatar

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

0
0
0.000
avatar

That would be an excellent practice indeed. πŸ˜πŸ™πŸ’šβœ¨πŸ€™

!HUG

0
0
0.000
avatar

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

0
0
0.000
avatar

That sounds reasonable to me. πŸ˜πŸ™πŸ’šβœ¨πŸ€™

!HOPE
!HUG
!INDEED
!WEIRD

0
0
0.000
avatar

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

0
0
0.000
avatar

Indeed, which is exactly why it should be forked abundantly. πŸ˜πŸ™πŸ’šβœ¨πŸ€™

!HOPE
!INDEED
!WINE
!WEIRD

0
0
0.000
avatar

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

0
0
0.000
avatar

That may be so, and perhaps it will be Bjorn who does the First Fork. We shall see. πŸ˜πŸ™πŸ’šβœ¨πŸ€™

!HOPE
!INDEED
!PIZZA
!WEIRD

0
0
0.000
avatar
(Edited)

It may be expected that borniet is one of the people on Hive who would fork #HiveEngage (and launch an instance of it) the first time, but it might be no other than you yourself who would actually do it! πŸ€”πŸ˜ŽπŸ˜†πŸ˜

0
0
0.000
avatar

While I understand that sentence, it is not logically consistent or coherent. πŸ˜πŸ™πŸ’šβœ¨πŸ€™

1HOPE
!HUG
!INDEED
!WEIRD

0
0
0.000
avatar

I accidentally typed "would" !INSTEAD of "might" on "it would be" on my previous comment !INDEED. πŸ€”πŸ€― We can now continue our conversation here normally! πŸ€―πŸ˜†πŸ˜…

!LOLZ

0
0
0.000
avatar

OK, I understand, and no worries. That sounds like a good plan, though how would we continue our conversation here abnormally? πŸ˜πŸ™πŸ’šβœ¨πŸ€™

!INDEED
!LOLZ

0
0
0.000