actual, verifiable digital ownership… using a distributed database technology that is designed to require a massive amount of computing resources to update.
I think where some of us who work in spaces using databases to verify something in critical business processes get stuck in accepting that blockchain has value is that our jobs have always been to verify “ownership” as quickly and efficiently as possible. We typically do this by defining a canonical source of truth and our success is judged on how many milliseconds transactions take and the datacener or cloud costs.
Saying that everything about blockchain is “dumb” isn’t a very nuanced analysis… but it’s a understandable reaction to hearing the hype that blockchain is going to change everything for years.
I’ve never seen anyone argue that the massively distributed nature or the public read access of blockchain technologies aren’t interesting. It’s the tradeoff that has to be made in speed and costs that make it hard for many of us to see any value in the approach for most applications.
I’m not directly involved in either project beyond reporting bugs and suggesting features yet, but I follow both projects closely. My sense is that the Mbin community is prioritizing collaboration around UX improvements while Kbin is focusing on scaling/performance issues… which makes sense as kbin.social is more than 10x the size of fedia.io (https://fedidb.org/network/instance/kbin.social vs https://fedidb.org/network). I opened a bug about the UI for altering link images at https://codeberg.org/Kbin/kbin-core/issues/1365. When I tested the same steps in Mbin, the issue i was seeing in Kbin had already been solved in Mbin.
Kbin is a great PHP implementation of ActivityPub for reddit-like communities, but requiring all major changes to be made/reviewed by a single person is a real bottle neck.
It would be great if Kbin could figure out some form of goverance/delegation that would allow more contributors, but there doesn’t seem to be much interest in that type of change so for now we have 2 project with different priorities and governance models… and that isn’t necessarily a bad thing.