We certainly didn't look into this before, but I'm going to make a reasonable assumption that Steemit only did this after being contacted by law enforcement in the US. If that's the case, I don't see much benefit to expending even the relatively trivial effort to display this presumably old data now. It's still out there, for anyone who wants to see it, on the blockchain, in any case, as you've already mentioned.
You are viewing a single comment's thread from:
Thank you for the reply.
I don't recollect the context of this enforcement action and it's rationale from law enforcement but it clearly was an unpopular move on chain in retrospect.
Was it limited to this account or where there more and are we going to take it on good faith from Steemit Inc at the time that the actions were taken against content that was justified in the court of law?
I don't know the answers to these questions but imagine they would be the manner of questions that could be asked. If there a no legal compulsion for Hive.blog, I don't know if there is any incentive to maintaining that baggage lest we have more vloggers point it out and share w censorship averse audience on LBRY.
Also, hate to bother but would you or someone be able to explain the a bit more detail technically as to how this action carried over to hive.blog and peakd but not down the board to other front ends.
Is it that both share codebase w condenser and that is how it was transferred? Thanks in advance
I can't be sure without looking at the code, but yes, I'd guess that this was something included into the condenser code.