Words
318
Reading
2 min
6y
Sorry for not replying sooner, I'm quite swamped with hf24 things.
I really appreciate these and just got done listening.
Thanks ! I'm always a bit like "is this really worth it ? It's pretty much a podcast where blocktrades and I talk about stuff who cares ?"
- Great !
- I feel like this could be solved by writing it in the json_metadata of posts And then we would index that in hivemind. But first we need to have all front ends add a field where users can select a language for their posts. But ultimately you mostly need to convince
@good-karma and
@blocktrades since you guys own the major front ends. Then you could open an issue on https://gitlab.syncad.com/hive/hivemind to request the feature. I also feel like that would be a good candidate for a machine learning project where you just add a language detector that works with hivemind so that the burden is exclusively backend and not on the front ends / users
3.4.: Not sure where it's at, but yeah I agree that we should work on the first protocol upgrade for communities, good thing is that it's layer two so it could happen in parallel to the regular hard fork development. - Nice !
- As we said, I'm in for a complete separation of the reward pools from the base token. Blocktrades doesn't seem to be as drastic as I am. Other than that there are probably more experiments that we could try running
Mhh I agree with you on the paywall, but it's a hard problem to solve while being decentralized. A first centralized version could be done where the content is encrypted by the hive-patreon front end and only decrypted by the front end if the user is set to send recurrent payments.
But that's a centralized solution and it's not great. I'll have to brainstorm this, I think it's hard but not impossible.
RE: Hive core developper meeting #10