Consumers are hungry for a new way of social networking, where trust and safety are paramount and power isn't centralized with a Big Tech CEO in charge...
"the company looked at the history of social media over the past decade and didn’t like what it saw… existing companies that are only model motivated by profit and just insane user growth, and are willing to tolerate and amplify really toxic content because it looks like engagement… "
I would love to contribute but I don’t have the experience for a fork. This is kind of the essence of the whole problem though. Plenty of unutilized contributors who could be driving this project forward but are having a hard time getting involved.
This sort of thing happens in every opensource project; the maintainer(s) have a vision for the product and whatever amount of time they can use to review contributions and PRs. Some PRs are utter messes, some are good but complex, others are good but either are not going to be supportable with the current manpower or will be superceded by codebase changes in the future. And then these contributors get upset their PRs aren’t being taken seriously. They as well are welcome to fork it and they could even use patches from the original branch as they develop their forks, and presumably implement them in production. But more often than not, they just move on because they don’t have much invested.
It’s every maintainers balance that has to be determined, and not everyone is going to be happy. They might want a slow development pace because fast paces require a lot of work to maintain. Simplistically saying “we need faster development to take advantage of surges in interest” is pointless if there’s nobody that’s willing to stand behind the extra QC and support those patches introduce. Drive-by patching is a huge issue because the contributors rarely stick around to fix bugs.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
I would love to contribute but I don’t have the experience for a fork. This is kind of the essence of the whole problem though. Plenty of unutilized contributors who could be driving this project forward but are having a hard time getting involved.
This sort of thing happens in every opensource project; the maintainer(s) have a vision for the product and whatever amount of time they can use to review contributions and PRs. Some PRs are utter messes, some are good but complex, others are good but either are not going to be supportable with the current manpower or will be superceded by codebase changes in the future. And then these contributors get upset their PRs aren’t being taken seriously. They as well are welcome to fork it and they could even use patches from the original branch as they develop their forks, and presumably implement them in production. But more often than not, they just move on because they don’t have much invested.
It’s every maintainers balance that has to be determined, and not everyone is going to be happy. They might want a slow development pace because fast paces require a lot of work to maintain. Simplistically saying “we need faster development to take advantage of surges in interest” is pointless if there’s nobody that’s willing to stand behind the extra QC and support those patches introduce. Drive-by patching is a huge issue because the contributors rarely stick around to fix bugs.