!INDEED (Yes, one more test ;-) )
My testing publishing a (test) comment (using the #Ecency team's #Hivesigner app in this case) shows that a Hive account can be used to literally publish a comment with the permlink named "comments". 🤔🤓 If someone visits the comments feed of a Hive account (https://ecency.com/@savvytester/comments in my case), the comment itself would not be accessible unless any tag (either a community tag or an unmoderated tag) is used (which makes the comment accessible when using a link similar to like https://ecency.com/tydynrain/@savvytester/comments). 🤯😆
!WEIRD
!LOLZ
I think that you would want the Hive Witness nodes to prevent Hive authors from publishing posts and comments whose permlinks are reserved keywords (which includes posts, comments, wallet, feed, and so on) !INDEED. 🤔🤯🤓
!WEIRD
!HOPE
!WINEX
Yes, that doesn't seem like a good idea, though I don't know how a witness would prevent it, since it's a coding implementation. 😁🙏💚✨🤙
!HOPE
!INDEED
!WINE
!WEIRD
I meant that the top Hive Witnesses would include that restriction on the next Hive Hard Fork on my previous comment. 🤔🤯😅
Ah, I got it, though that has nothing to do with witnesses in general, just the core devs, some of which do happen to be top witnesses. 😁🙏💚✨🤙
!HOPE
!INDEED
!WINE
!WEIRD
I forgot to include the word "Top" on my previous comment, where I particularly refer to most of the Top 20 Hive Witnesses !INDEED. 🤔🤯 I edited my previous comment to reflect that. 🤯😅
!WEIRD
!HOPE
!WINEX