|
I agree that getting rid of federation is not the answer. However, it will be little more than a source of neato developer projects as long as new projects try to get users to think about it, let alone understand it, nevermind actually needing to understand it to use a product to its full potential. People who don't care about federation, conceptually, will never care about federation, even if it yields tangible benefits they care about otherwise. They will prioritize user experience, interface, branding appeal, reliability and speed of operations like finding people in-app, and all of that other stuff that FOSS social media, and many other types of FOSS projects, de-prioritize. That is why FOSS alternatives are still alternatives despite being free, and largely technically superior. The disconnect is rooted in differing perspectives. Developers, naturally, use more sophisticated means of evaluating software than end users, much the way nutritionists evaluate food. We consider interfaces and user experiences to be means of interacting with software, and consider the software on a whole, yielding only so much weight to usability. Since software plays such a huge part of our lives, spending a little time wrangling it doesn't seem onerous. To nearly all end users, the interface/experience is the software. Even people who do care about federation conceptually may not even be willing to deal with admin > 0 for their social media accounts. It's not ideal, but it's reality. Currently, federation hardly matters more to people than HTTP/2 does. Trying to use it as a selling point for general audience software is a failing strategy. So who cares? Social media is a hell of a lot more useful with a critical mass of users... other users are what make it "social," rather than merely "media." If developers are nutritionists, designers are chefs. Calculating proper nutrition to keep us alive and functioning is arguably more important to making food delicious and enriching our sensual lives. But if you take a large group of people and offer them their choice of food either constructed by nutritionists or constructed by chefs, the chefs will win every time. Many of the nutritionists will be mystified by people's lack of ability to prioritize critical body functioning over beautiful sensual experiences. (When I was in culinary school, a fellow student was a career-changing nutritionist saying she was becoming a chef because she was tired of "being the bad guy taking away all the things people loved.) The key is actively enfranchising people who specialize in knowing what users want. Spending an afternoon in Gimp making a punny logo is not branding. Customizable color themes are not UX. Deeply considering, and probably researching users needs and expectations and then trying to meet them is the only way forward for FOSS social media. People are willing to give up some flavor benefits for food that's significantly more nutritious, but we need chefs to help us make it as tasty an appealing as possible, and then spin the hell out of the benefits. It's the only way forward. |