Open source or GTFO. :)

Seriously, Lemmy is AGPL. Any client you do and any functionality you build on top of it must be AGPL as well.

Now I am confused, are you able to make changes to the Lemmy codebase? A fork? If you want to find a way to fund development, why not just work with the current team?

As a concept, it could be a valid approach. But you need to put actual numbers to see if things make sense:

• What would be the monthly membership fee?
• What would be a reasonable SLA? If there is an outage on a Friday night, are the members okay if they wait until Monday to get it back someone online?
• What do you think is a good hour rate to pay for an admin?
• What should you pay for someone to stay on call?
• Can I run bots? How many? Does each bot count as a separate account?

I think you’ll see that as soon as you start asking people to put money and to feel like they “own” it, the demands will increase and so will the costs.

For reference, the one coop I am somewhat familiar is from Mastodon: cosocial.ca. Each member pays CA$50/year for an account. I think this is particularly too expensive. There are other cheaper “commercial” alternatives that charge less:

• omg.lol offers mastodon and some other services, for $20/year
• mastodon.green offers accounts at $2/month
• Communick offers Mastodon/Lemmy/Funkwhale/Matrix accounts for $29/year (Disclosure, I’m founder)

Ok, which part of “multiple metrics” is not clear here?

Every risk analysis will have multiple factors. The idea is not to always have an absolute perfect ranking system, but to build a classifier that is accurate enough to filter most of the crap.

Email spam filters are not perfect, but no one inbox is drowning in useless crap like we used to have 20 years ago. Social media bots are presenting the same type of challenge, why can’t we solve it in the same way?

Platforms like Reddit and Tumblr need to optimize for growth. We need to have growth, but it is does not be optimized for it.

Yeah, things will work like a little elitist club, but all newcomers need to do is find someone who is willing to vouch for them.

Just add “account age” to the list of metrics when evaluating their trust rank. Any account that is less than a week old has a default score of zero.

Why does have it to be one or the other?

Why not use all these different metrics to build a recommendation system?

Well, I am on record saying that we should get rid of one-dimensional voting systems so I see your point.

But if anything, there is nothing stopping us from using both metrics (and potentially more) to build our feed.

That would be only true if people only marked that they trust people that conform with their worldview.

The indieweb already has an answer for this: Web of Trust. Part of everyone social graph should include a list of accounts that they trust and that they do not trust. With this you can easily create some form of ranking system where bots get silenced or ignored.

You were so eager to come up with a jab at other people that you seem to have ignored the second paragraph. It is pretty clear that you could benefit from a bit of introspection to look what you could offer to the world, instead of just trying to put everyone down.

Wishing you well.

Most people want social media to read and talk about the mundane things that are interesting to them (like sports, or their hobbies, or some new cool bar they want to go on, or some interesting places to travel) instead of using it to doomscroll and display outrage.

If all you want from social media is a place that constantly keeps you anxious and reminds you of how little power you have to change the things you are so pointless worrying about… then sure, Lemmy is more than enough as it is.

An Apollo-like Lemmy client that is also implemented as a PWA

This would be amazing to be integrated with Voyager. People could migrate to Reddit via Fediverser and clone only their subreddits to the device.

It doesn’t have to be this way. There are instances focused only on basketball, soccer, American Football, Tennis…

It would be great to have people like you on https://fediverser.network. Follow the subreddits that you miss from there and use to promote the Lemmy alternatives.

And I hope to see you soon on [email protected]. :)

Yes. I do have someone who can take over Communick and has enough know-how to manage things or at least ensure that an orderly transition is possible.

Still, the best way to guarantee that Communick will be around for the next decades to come is by making sure that it becomes a viable business.

Sounds like something that could be useful for Lemmy itself, no?

If there is one belief that I’ve held for long is that we Free Software would be in a better situation than it is today if we simply dropped the whole idea “community”, “done by amateurs” and “volunteers in their spare time” and really start treating the whole thing as a professional industry. This whole xz crisis further exacerbated this belief.

Almost everyone takes this work for granted and this is why is not properly valued. We should raise the bar at all levels: someone who wants to contribute in a project needs to show that they can deliver everything, maintainers should not accept “half-baked” proposals because “it is better than nothing”, developers should be more than comfortable sending a quote with a proper rate to someone that requests a feature.

And if those people don’t want to do any of that, then let go see how much the commercial alternative would cost them.

We used Slack and we had a Confluence Wiki. No one bothered to keep Confluence up-to-date because everyone was just used to ask ad-hoc questions on Slack and get an answer by one of the respective team members. We “solved” this issue at one company with one reasonably simple policy: people were free to ask questions on Slack as much as they wanted, but the response should always have a link to the related Confluence page. You could even answer the question directly with a TL;DR, but the Confluence Page link should always be part of the answer.

Every time that there was an Slack response without a link to Confluence, the responder’s team would get a mark, and every month the team with the most marks would have to bring something to the rest of the company. Basically, it forced everyone in the team to step up their documentation game, and it got everyone in the spirit of “collaborative editing”: sometimes, people would just write create a page with a very basic paragraph. Another team member would use that to extend the answer and so on. In just a few months, every department had a pretty solid documentation space and we even got used to start our questions with “I looked for X on Confluence and didn’t find anything. Can someone tell me where I can find info about it?”

So, yes, you are right about the disconnect between “what experienced people want” and “what beginners want”, but even in this case it would make sense if most project managers used real-time chat platforms only for initial inquiries and triage, but used this inflow to produce long-term content in a structured document or wiki.