Invite only. If I'm running a federated service for me and my family, the moderation is going to be astronomically better than anything big providers are doing because a couple minutes of moderation by me every week is astronomically more on a per user basis than what someone like Google or Facebook is doing.
Drew's point is that people who can have or acquire that expertise are force multipliers — it's easy _enough_ that one person can run a node that carries less-technical users into the ecosystem. But I don't think we're really there yet, and worse the value isn't there in federated social media to offset the costs of time, money, and change.
We've seen distributed networks capture enough imagination and be usable enough to get mass adoption, but they did things like distribute tremendous proprietary media libraries on the cheap and without permission.
Services like Mastodon aren't as easy to spin up for a group as, say, running Napster was, or even seeding a torrent is now. But people, even non-techincal ones, either put up with those services' occasional unreliability or recruited more technical users to work them on their behalf because the relative value was so great.
So to me the problem with federation is making the value exceed the cost. It's a squeeze from both sides. We won't get there until an ActivityPub service is as easy to stand up as running an app on your device, AND the value of running one is large enough to make it worth the trouble.
It feels like messaging should be where the value end should have already taken off, but federated group chat is still a rat's nest of incompatible or feature-starved services. Federated social is still just on the wrong side of complexity and the value it provides honestly isn't that great to a mass audience.
Not for 99% of the users, for now. But there is an increasing faction that is taking issue with what any company does with their data.
At first, caring about one's own data was mostly a political thing. Now, abuse of data is getting so ridiculous that how much time you spend in the supermarket queue may depend on the aggregated data supermarkets have on you (and yes, supermarkets often aggregate their customer data via third-party reputation aggregator companies). Not to mention credit interest rates, insurance premiums, visas, and airport security checks. Soon people will too realize that taking their data off from ad networks is a good way to save money. At that point, one either goes silent or searches for a limited, well-protected social network.
Sandstorm is/was most of the way there; it makes installing server apps really easy (assuming a hosting provider installs Sandstorm for you).
Perhaps extend that one or two levels into the graph, with exponential decay. So if you invite someone, and that someone turns out to be a spammer, they get banned, you get banned, and I lose posting privileges for a week. And the person who invited me loses some privileges for a day. Etc. Add some level of manual review and algorithmic detection of clusters of accounts that exist only to invite other accounts that invite spammers, and...
... well, did anyone ever try this out? What are the obvious holes in this system that I'm missing?
Another feature that I wish other places adopted is a public moderation log (https://lobste.rs/moderations) where users can see all the actions by the mod team. This helps keep the mods accountable.
It's worth not just "a shot", but lots of earnest attempts.
I research in that direction: http://mro.name/ShaarliGo#install--update
Yes, protection against a million fake accounts is the key scientific problem to solve (Sybil attack).
Our university lab has worked on this problem for 15+ years, its hard. Early indications are that ActivityPub and federation are not going to scale. Bot attacks are too ferocious for amateur admins. Big instances attract more people, however a single instance fails to scale.
Nobody knows how to build trustworthy self-organising systems with "self-governance". Somehow you need to deduce the reputation of others from their signed interaction history. Their privacy needs to be protected, but you can still calculate a reputation score. After 20 years of scientific progress around "distributed reputation systems" with 100+ scientific articles they have one thing in commons: they don't protect from the Sybil attack.
Server federation is not going to help if there is no trust fabric to build upon. The effortless onboarding plus mobile-first requirement of today means you even need to have smartphones talking to eachother directly, P2P-style. <plug> thankfully students in our lab now have carrier-grade NAT traversal operational between Android devices. Google: "Technology Stack for Decentralized Mobile Services" (quotes required).
If you are, while i think email has proven that moderation is much much easier at scale if the attackers are spammers (astroturfing is a bit of a different story though)
That's the point though, design for the lowest common denominator has been the modus operandi for the giants because it gets them the most profit. There is no proof that this is the way to create the most "useful" social network. Often I'm tired of the "organic spam" that users with easy access create non-stop in a lot of the communities I'm in. A technical barrier to entry isn't necessarily a bad thing in this case.
One of the reasons amoral commercial efforts like fb won is because this modus operandi happens to harmonize standard commercial MO with what a network is.
There's definitely value in alternative MOs. As you say, a technical barrier to entry can have its uses. Wikipedia is a nice example. I don't think simplifying the editor UX to an intuitive one would necessarily be useful. But wikipedia needs a throttle on editing.
I'm not sure this relates to federation though. Niche communities don't need to be federated.
No that is not true. Judging from my experience with various subreddits anything above 100k quickly becomes trash. You don't need as many users as possible.
>One of the reasons amoral commercial efforts like fb won is because this modus operandi happens to harmonize standard commercial MO with what a network is.
For what facebook wants to be i.e. a profile for all your contacts that is indeed the case. For hobby/activity related communities that's not true.
>I'm not sure this relates to federation though. Niche communities don't need to be federated.
It does relate to federation because right now if I open a new subreddit I am bound to the wishes of the company and they can change the UI in such a massive way that any community that benefits from long-form text posts quickly dysfunctional. I have noticed the gradual decline in content and comment quality on reddit since the redesign and the push for mobile app usage and it's slowly creeping into every subreddit out there.
With a federated alternative to reddit I could launch a server on my own and have control over how the community evolves over time( or rather, people who have the community's best interests in mind can in general). I hope someone takes what Mastodon does and make a reddit alternative.
... the problem with that is there are a lot of damned smart people who are good at what they're good at precisely because they view "wrangling tech" as a complete waste of their time.
Artists and musicians are a really good example, and are the key reason I use Twitter (pretty much the entire indie game industry lives on that platform), but this principle also extends to doctors, lawyers, scientists, teachers, historians, practically everyone in all the sciences, trades, and humanities ... except computer programmers. I've had aspirations towards being a polymath, and one of the bitter things I've learned about the programming-autodidact death march is how much of what someone learns isn't important fundamental knowledge, but is just byzantine details that will evaporate half a decade later when the software in question goes obsolete. It's excruciating to waste time learning something like that (which will become worthless) when I could be learning core programming fundamentals -- or could be learning something in a different field like drawing that will stay valid for the rest of my life.
I was a desktop developer looking-in-from-the-outside at web development, and I timed my entry into the field specifically to avoid the hot mess that was the API differences between netscape (yes, Netscape Communicator 4.5) and IE 6 at the time. As a programmer with enough of a nose for bad code smell, I took one look at that and thought to myself "this is completely insane." I could have knuckled down, busted the books and gotten all those api minutiae down just pat. Just in time for jQuery (or future browser versions) to show up and render them irrelevant forever.
It wasn't insane because it was a mess - it was insane because it was definitely going to go away, and soon. And once it did go away all the time I'd spent learning and mastering it would have been utterly wasted, sure - but wasted at the expense of not doing something else that's more important. That's time I could have spent learning the piano. Or a foreign language.
Now - not all programming is like that - eventually you've gotta bite the bullet and decide something's "good enough to get the job done". Many tech stacks actually end up in a nice sweet spot where they're coherent enough to learn quickly, and stable enough (in the sense of an API) to get out of the way and let you approach long-term projects without the ground shifting under your feet. But if you just blindly vacuum up proficiencies as they come off the treadmill you'll quickly discover you're doing nothing else with your life.
--
This is the relation most humans have with tech. Especially the smart ones who are really into something else.
It's a means to an end - and can work wonderful magic. But it demands a price.
One of the big things facebook did is you couldn't customize your page. No autoplaying midis with seizure inducing gifs. Also helps with brand cohesion.
Federation gives people freedom. Quite frankly users cannot be trusted to maintain a good experience if given freedom.
The power of Facebook, Twitter and such is largely their feed. The feed is an answer to point #1: grandpa simplicity. The feed is the thing that needs to be protected from points #2 & 3: identity and culture.
The feed is that will motivate participants, content creators, etc. IE, many will create content for the feed. Reddit/Digg/HN upvoting were a simple way of doing the feed that proved this point and paved the way for Facebook & Twitter. A lot of mass adoption services created after went extreme. Feed only. The Tinder UX is a feed of datable people, for example. Spotify's importance is being solidified by being a feed. Importance in spotify's context is largely "being the place where music gets popular."
One way or another, the feed issue must be addressed. New content UIs will either have a successful feed or transcend the feed some way.
I'm not sure how this relates to federation. A feed seems a centralizing element by nature. Successful federated systems of the past (the the WWW) tended to leave the feed ("discovery," in a pre-feed context) to someone else... which turned out to be google, fb, etc.
However the labyrinth is is designed, what matters is how the feed works.
First movers always take the majority of the market share if there are no compelling reasons to use a similar service.
'Privacy' itself is barely a feature - people do care, but it's rarely #1 on their list.
Techies viewing this from the more strategic, systems perspective have to get into the headspace of individuals to see it from a 'user centric' perspective - because the answer to many of the questions lie there.
For starters, very few people care that Facebook for example is 'centralized' - they care about the material value offered to them 'right now' which is to say, access to their friends, posts, information etc.. Everything is is a distant second. Issues that do not directly affect their experience an even more distant third.
The same seems to be pretty much true of "federation".
That rules out my children's grandparents then.
You could have stopped there, that's pretty much the only reason. But that has little to do with federation though. And yeah the ugliness and bad UX problems of free software - software that's freely unusable - have been known for literal decades.
Because they get free money from the Federal reserve through cheap loans and government contracts and money attracts people. They can use the money to saturate the media with their brand until everyone ends up using them. Then they can use the money to crush all potential competitors.
1. Among other things, because of a dead-simple user experience that lets even grandpa post content after a few clicks. Federation, if it adds any level of complexity past the grandpa UX, would defeat the goal.
2. Next, identity. If grandpa can post, so can the bots, how do you ensure accounts don’t go to fake entities? What if an account has to pass a quality threshold before it can publish in public, but can be used privately any time. HN has similar model, but here you limit public posting until 10 random other users have seen and upvoted the new user’s post. Add to that possible additional authentication for payment of a pro feature, or a human check mark, and you’ve put a hurdle on spam.
3. To keep culture from running amuck provide positive and negative feedback. Public content has a span problem, not so much private behavior. Content ratings and discussion licenses can come into play as well, where any group can limit posts to PG content, or discussion that gets moderated automatically or manually if it passes certain thresholds.
Happy to suggest more if needed. I run https://www.dreamlist.com