yeah, they just don't have the thing to compete with existing social media, the normal people won't even care if their content is also partly owned by the social media platform through granting fair-use for the copyrighted object upon term and condition agreement.
moreover, the fact that web3 socialfi used web3 technology which majority of people don't really understand just adding layer of complexitiy.
here's the thing, content creator seek a platform that have big amount of audience which are the reason the platform could have so much content while the audience want platform that's easy to use and also big amount of content it's like circle, the web3 socialfi on the other hand lacking both content creator and audiences, unfortunately we've past that stage where content creator and audience are still seeking for a platform, instead everything already revolve around the giants of social media and too much content creator already invested their time in there so migration to a less popular web3 based social fi is not an option but just an expensive overhead.
On the
technical side there is just X number of lines of code not yet written preventing all "distributed" socialfi sharing all their content with one-another.
End-users need not be shown any supposed complexity, in fact could end up choosing which user-facing front-end to use based on how much of the underlying is successfully hidden from them.
However if the underlying strata used had a little extra some extant networks lack, extant ones could use it in ways that foil the use of those extras.
For example suppose something like HIVE but adding the ability for user reward to go to the front end they use; probably add optional for that only to mean to a trust account the front end cannot appropriate.
Suddenly some front ends could arise whose end users need not even be made aware of the underlying at all but any time their chosen front end chooses any earnings from posts they made through that front end could be suddenly awarded to them for supposedly any reason.
Maybe might want to have a max lock time or set of them, like maybe any not awarded before the second "Holiday Season" following posting ends the underlying will award anyway even if one's front end doesn't bother to show you you got any. A five year one could be in place too, so any time in first five years a user of a given front end has been a user of that front end that front end could award them a loyalty bonus, whatever.
Aribtrary reasons can be given by front ends for why they chose some particular moment to award a user, but in the long term the user is going to get it anyway despite their choice of front end.
Wow, a lot of complexity in that, so how about just use HIVE (aka STEEM-clone family) directly and just let front ends conceal all aspects their users might find "too complex"?
Facebook et all would still not be locked out of course; they could perfectly well create HIVE accounts for all their users, paste all posts of their users to it, and having the keys do anything they choose with any "proceeds".
I said technical, you did notice that? Because legal copyright, blah blah blah might make such technically almost trivially simple things crazy-complicated to deploy...
Also incentive considerations... how to incentivise pre-existing potential front-ends such as Facebook, X, etc etc etc to share the content their users post?
Any that target marketers, of course, could make
how much money advertising to marketers "for only X bucks per Y ticks of time all your posts made through us we will automatically post for you to Z number of other front ends, including our largest competitors who collude with us on this..."
-MarkM-
EDIT: You think Facebook et all have
content? How about the Disneys of the world get into it, "your treasured posts can be part of history, generations from now, along with such other family favourites as [our fine movie show etc collections etc etc etc]..."
