Both method and mechanisms are very different now.
Anti-censorship features of Hive are on the consensus level.
True, that things gets more complicated nowadays when part of API endpoint is a non-consensus front-end oriented social layer such as hivemind.
Node and front-end operators can chose to ignore those features. I'm (same as @pharesim) running on defaults, inherited from Steem (now changed to be independent for obvious reasons)
I see a lot of improvements needed for those mechanisms to improve transparency and decentralization.
In a long term I believe this will be replaced by some sophisticated mechanisms relaying on a web of trust.
yeah man were supposed to have that DIY Decentralzied Voice KYC free p2p ID system that letsyou verify up to 3 otehr people in a web where you submit face selfies every few weeks or days and you have VERIFICATION witnmesses at least thats what I see we could have (The stuff we all BELIEVED @dan was doing at block one as $750 million dollar CTO lol but he ACTUALLy just created an idea and allowed US to create the plan spread across all our brains
just do what dan led us to believe hed do for voice, but on hive, where we need a validator node system where you can tie your owner keys to some system where yoru recovery account can restore your account after 1 year or 2 months or 6 months of inactivity and where you can get people to verify if you still have your account, selfi verification, youd end up with validator node wars , but youd try to create alliances and allow binter blockhain communication, we could allow a Keybase.io system where you verify who you are by having a verification of like 7 different social media accounts . I dunno tehers SO many ways to do this i want to try them all
I just dont think dan will deliver on this, maybe but voice doesnt even let me make posts just comments. and i geta 700 voice daily reward , ghey if that was $700 a day id be happy .
what we need is to finish this silly dream dan has, he is innovating less and less the larger and larger his company gets. But WE can be nimble quick and jump over the candle stick ;)
I am not a coder, and seem to have misunderstood, from your comment, that the API mechanism was being applied on both forks, with the difference that Steem was adding catalogs to what is not passed to front ends.
However, I am learning, and what I am learning today is that folks that are competent to work with APIs have undertaken what I consider to be vast improvements in how censorship is going to be implemented going forward.
I am grateful for your considerations, and for sharing them with me here. I hope trust can be unnecessary, just as I hope spam will stop. I'd much rather users themselves be enabled to choose what is censored from their feeds, as that best enables free speech and dissent in a world that seems hell bent on duplicating the Chinese model of total information control, where any information not mandatory is forbidden.
The centralized platforms are all headed in that direction. Since I, and many I have read say so, are here because of censorship, enabling users to be the only censor of their feeds strikes me as the most potent recruiting campaign possible.
Seems to me it's just the right thing to do, as well.
Thanks!