Browsing projects on #Sourcehut reminds me of what FLOSS development looked like 15-20 years ago. Ugly interfaces that were just thin layers above the code, barely any README (let alone wikis, or any form of easily accessible and structured documentation), and let's not mention accessibility on mobile.
How are we supposed to build the foundations of tomorrow's FLOSS if we use tools that look even more outdated than Craigslist? How are we supposed to have any credibility when we tell people "stop using Github, try Sourcehut instead"? How do we expect to create user engagement? How do we expect somebody who's not a developer to use software that doesn't even come with an easily accessible documentation?
@blacklight Impossible to decide where to start replying to this multi-branched thread (and, oh the irony, Mastodon doesn't do a good job at showing those branches), but 10000 % agreed with what you said.
A few folks monopolizing the replies essentially saying "#Sourcehut is just fine" illustrates the problem perfectly.
Some thoughts:
@blacklight It's clear that some hardcore F/LOSS users couldn't care less about the very concept of UX, dismissing it as bloat. We need to build bridges with people who have the vision of open, decentralized technology that creates delight and can reach "the average user". @humanetech is a huge source of inspiration to me.
@blacklight F/LOSS folks are often worried about finding "the open alternative to X", without reflecting one second what problem does X resolve, if any.
And this is a bad strategy, because capitalism will keep producing X'es endlessly and relentlessly, and the F/LOSS community will always be doomed to pursue impossible goals.
What about solving the problem of "having an online presence" and "being in the social network kids these days find cool"? That's what 99 % of small businesses want.
@blacklight Damn, even autonomous social centers ignore the #fediverse. It's easier to find them in Twitter than it is to find them here. While Mastodon has advanced the #fediverse a lot, there are still some rough edges.
But fixing those require designers and UX people, which are nowhere as privileged as coders. And therefore, it's more difficult that the find the time, the energy, the incentives to help us.
Especially if we are assholes to them, or dismiss their work.
@blacklight It saddens me to see that the state of the conversation is still so poor. But it inspires me a lot that there are people voicing their concerns and even patiently arguing with obtuse folks. I don't think I would have so much patience.
In other words: thank you ❤️
@astrojuanlu @blacklight
> It saddens me to see that the state of the conversation is still so poor.
because people disagree here and instead are happy with sourcehut not being yet another github clone?
it's not that i don't want nice usable software, it's that my idea of nice & usable is different. implement aria stuff to help accessibility? fuck yeah. add meta tags to have other tools process my stuff? of course. add shitloads of JS so that a page can't be used in a browser like netsurf or with js disabled? fuck off. maybe "the browser" just has outlived it's days as application platform.
this "make it ez" line of thought has brought us shit like systemd and consolekit and i hate it. things can be usable without being technological dumpster fires. you wrote yourself that we shouldn't imitate things in "floss". imitating shit to make it more sexy for more adoption is the opposite.
> even autonomous social centers ignore the #fediverse
of course they do, their members are probably in to virtue signal like 99% of people are everywhere. a fringe social media network doesn't help with that, so it's ignored.
@astrojuanlu i don't even want to argue with you 🤷♀️
i just don't see why having a radically different UX from mainstream is a bad thing. i think it's a good thing that free software isn't constrained by what is "trend". i think those radically different approaches are an unique selling point.
things like sourcehut which are not "fancy" also enable people to to use it which might have problems using github etc.
i'd venture that composing mails is likely more easy than navigating the github ui if you are handicapped.
the gamification by github has always deterred me (and i know from others) from publishing my things there, as they never will get many stars. the commit graph facilitates a style of work which very likely is bad for mental health.
it's no surprise that many long running projects are often just a repository somewhere and a mailing-list. it's a surprisingly efficient style of work while keeping people sane as there is no virtual pressure like a commit graph.