You're either going to have every node do redundant work with moderation, or they'll adopt a common blacklist, thus re-centralizing.
Operators that fail to self-moderate will be blacklisted by operators that don't, because when 1% of the content broadcast by a node is, say, CP, nobody in their right mind will think twice before blocking it outright.
People seem to be allergic to balkanization. They want the convenience of typing a search result, a movie title, or a name into the platform instead of having to jump over ten. Even Mastodon with its hybrid model is unable to attract a significant amount of users from Facebook or Twitter.
Open APIs probably won't result in significant competition, and even if they do the privacy concerns exist for small companies as much as for larger ones, see Cambridge Analytica which with open APIs would basically roam around freely.
You say this like it's a bad thing. A centralized list that's communally owned is a lot more like democracy than a private list that's got "AI/magic" sorting that's intended to raise profits at the expense of society.
In fact, government could get involved in legislating not the list, but common sense baselines on how such lists should be administered - setting the groundrules so to speak (mainly to prevent fraud/abuse).
Eg: adblocking rulesets.
Any government involvement should simple state that blacklist options stay open to consumers (allow interoperability) and force transparency.
what does it mean to scrape an API. I usually hear that word for html website scraping.
Cambridge Analytica used posts to get API access to all users (and friends-of-friends) who interacted with those posts, in order to incrementally build a copy of the complete social graph. The process is similar to scraping.
It increases the attack surface but publicly to everyone.
If we make the answer "no", then it won't be possible to build alternate UIs, because the Facebook UI will be able to show my friend of a friend my information, but an alternate UI won't be able to do so.
Different products/companies exist to fulfill each of these roles:
- host the firehose of tweets/posts/snaps/grams. Likely the husks of Facebook/Twitter/SnapChat/Instagram.
- filter/sort firehose for user given their preferences time/popularity/relevance etc.
- GUI to display posts to user by Web/Mobile/VR/SMS/Postcard etc. Aggregate social media readers do (did) this.
- GUI to (re)post/comment on/react to/edit/delete user content to the firehose. These already exist: HootSuite/Buffer
- firehose analysis for marketing, etc.
- firehose-level moderation/flagging/censorship/tagging
The problem is there is far more user value in vertically integrating some or all of these functions than there is in keeping them decentralized. Most users will prefer one product that filter/sorts AND displays posts to two products where one filter/sorts and the other displays.