Core dev meeting #49 summary

in #core2 years ago

image.png

Hello,

I"m sorry. It seems there was an issue with the recording hence, this is one of those "summary only" meetings.

Luckily not much happened, so you're not missing out by not having the full recording.

Dev sync

On my end I am done with my changes for the next hard fork, and will slowly transition towards publishing code for hivemind + communities. We spoke briefly with Bartek on which merge requests to prioritize, I'll be picking up a fix for the setTitle / setRole on communities first and then move on to other things.

On @blocktrades' front, pretty much everything is summarized on his recent post: https://peakd.com/hive-139531/@blocktrades/3rd-update-of-2023-building-on-haf

We had a bit of back and forth as I was wondering how ICEBerg worked under the hood and how it would affect my own pull requests.

Issues regarding muting on posts

@guiltyparties brought attention to an issue where people were avoiding communities because if you get muted in a community you end up muted everywhere.

After some discussions regarding how we can tackle that (including a breaking change that would allow people to move their posts out of a community). We realized that the core issue is that in hivemind, the muted state is just a true or false value without any details, so if you get muted on a community, the post will be marked as muted everywhere.

I'll be in charge of implementing a better solution where the muted tag has details on why it was muted and "where" it is supposed to be muted, that way if a community moderator mutes it, it's only muted within that community and nowhere else.

start block for HAF

@imwatsi asked if it was possible to set a "start" parameter in haf so that it only syncs data after a specific block. There was some discussion on the challenges to tackle that as some data would be missing (you see an account doing a trasaction but because you started at a later block you never see when the account was created, creating a bunch of broken links). So while this is a good idea, we'll need to see how we can implement that.

And that was pretty much it for this meeting. I highly recomment checking out @blocktrades' post if you haven't there's a lot of details there.

Have a good one !

@howo

Sort:  

Thanks always.

When does the work on 'bonds' happen?
We've been asking for ~3 years, now.