Today I learned that it's possible to resteem a comment/reply (sort-of)
Not sure why I never thought to check this before, but I had always just assumed that this was not possible without a hardfork.
I was wrong. The resteem doesn't show up in the account's followers' feeds or in the account's blog, but the blockchain already supports resteeming a reply to a post.
Maybe useful (eventually), if we want organic conversations to happen more quickly on the blockchain.
Of course, this is possible if you manually create the corresponding
custom_jsonoperation. Only the author and the permlink need to be specified for the reblog operation. For the chain, a comment is the same as a post, only with adepth > 0.In the conderser, the reblog button is simply hidden. So if you create the operation without the condenser, this is not a problem.
The last current hurdle is Hivemind, as the resteems of comments are not processed. Therefore, they cannot appear in the feed.
Yeah, when I thought about it today, it seemed obvious that it should work (and it did), but for some reason I always thought it was blocked.
So, that branch should obviously be removed from hivemind and replaced with an option to filter by depth in condenser (and other front ends). Although, the subsequent code adding the resteemed content to the feed could also depend on the existence of fields from the top-level (like "Title"), so it might not be quite that simple.
I also wonder why this was not taken into consideration. These code lines have been there from the start. If we wanted to include them now, the entire database would have to be re-synchronised.
A title would actually be missing (with the current condenser). However, it could be replaced by the title of the root post if the comment was not given a title.
My guess is that the original implementers were concerned about spamminess. There was sort of a militant attitude about "quality content". I guess this would have been fine if we had enough "quality content" to attract lots of readers. But that has almost never been the case.
My own opinion is that velocity trumps quality for drawing attention. I'd rather have a feed that feels like vibrant bazaar than one resembling a pristine chapel that nobody visits. Therefore, I like Twitter's current approach of welcoming both long and short-form posting.
For Steem, if someone doesn't want to see the resteemed replies, I think it's a good idea to have a filtering option in the front end, but I don't see a reason to filter it at the blockchain. If a feed is spammy, then people can just "unfollow" or turn off visibility or resteemed replies.
Ugh. I hadn't thought of that. So you almost need to find a way to double-up the infrastructure and do a hot cutover once the resynch finishes.
This is what I was thinking, too.
Yes, this is an alternative. When requested by the frontend, it could be specified whether comments should be retrieved in the feed or not. Or they are retrieved in any case and only not displayed in the frontend. There are various approaches.
It happens only on Hivemind.
I can't remember why I assumed a re-sync. No comments have been resteemed yet. So, nothing would have to be replayed... I'll have to take a closer look again... my list is getting longer and longer... :-)
Sorry, yeah, if I'm not careful, I think of everything behind the API endpoint as "blockchain". Lazy way of thinking about it.
Well, at least 1 comment has been resteemed, but none that anyone cares about. 😉
Yeah, i try to find my comment i made years ago. This would be great, like on Twitter / X.
Not eventually - It would definitely!
Exactly what I had in mind.
Yeah, but first there needs to be an app/web site that's aware of them and gives them some sort of visibility. Ideally, I guess there would also be changes at the blockchain and/or hivemind level so the resteems show up in the feed and blogs without much computation.
This function would have many advantages. Although there are fewer and fewer articles worth reading, there are many good, helpful and productive comments. It would enrich my feed if I could share good comments.
There are also many users who rarely publish an article, but are very actively involved in helpful discussions.
That might also be an attractive feature for @the-gorilla's template/interface.
The hivemind changes would be a stumbling block for me at the moment. Perhaps something for the future but I don't have any of that side of things configured on my computer yet.
That is my problem. I have no idea what it looks like in the engine room of this whole BC story. I don't know which programming languages are used and which are compatible with each other. Nor do I know which code snippets pull, process and output which data and where exactly.
I also have no idea how this hierarchy is structured here. For example, who decides which changes or new functions are then implemented on steemit.com and who then installs them.
I can only throw ideas into the room from the user's point of view. Whether and with what effort a realization is possible at all.
Of course, it could also be that this is how it works:
Me: Hi guys, couldn't you search for sand grain 126 and connect it to sand grain 5443? That would be cool.
All: Fucking idiot. We're standing here on the beach at Copacabana in Rio. There are trillions of tons of sand here. Good luck with the search. When you find these two and they fit together, give us a call.
Werden auf X tatsächlich auch Kommentare im "Feed" (oder wie das da heißt) angezeigt?
Das war mir bisher gar nicht bewusst.
Ja schon, ist halt bei X derzeit auch vieles wieder im Umbruch. Die haben da ja jetzt auch Communities und so Zeug. Jetzt habe ich auch den damaligen Post dazu gefunden.
Das war so im Zuge mit dem Steemquote Projekt/Idee/Ansatz. Da ging es auch um die Möglichkeit einen Kommentar/Artikel mit einem Zitat, Kurzhinweis, wtf resteemen zu können.
Twitter war bis zum großen Zensurfiasko echt eins meiner Lieblingstools im Internet. Halt als das noch voll oldschool war mit max 160 Zeichen ohne Bildanhänge, Links, etc. Das war so geil.