Can you link to a process for purging bot accounts?

Thanks for the rundown. Scary risks

Why would users from here migrate to Threads?

There are challenges with horizontal scaling due to the way that Lemmy is architected. Sounds like this will be a priority for them to improve

How do you send the GDPR request?

It’s so toxic most of the time. Same to you!

I’m hopeful that the federated approach results in better discussion overall. Seems like it could!

I was thinking in terms of helping build out a team to work on non-dev related work, as opposed to pulling away time from the devs, who I’m sure are heads down. Fair points though!

Thanks for the info! I’ll check out both GitHub repos and the matrix channel

Lol, it stays with all of us

Would the same apply to something like creation of a new website? Or a weekly newsletter, or similar? I was assuming that non-dev work would be coordinated outside of GitHub, but could be wrong!

Don’t mind my corpo speak man. Just trying to take the experience I have to help out.

I’m just talking about contributing time to helping develop a platform. Corporations are good at process - so yes, there are definitely lessons to be learned there that should be implemented in any platform that is quickly growing (eg: putting a team of volunteers together to help out)

If GitHub is the best way to get in touch for non-dev initiatives, then I’ll do that. Thanks.

That would be true for metrics/performance reporting, yes. It would make sense to build something that was opt-in for instance owners to submit data.

Regardless of the mechanism – there will need to be some way to evaluate the performance impacts of changes that are continually being rolled out.

Thanks :)

I’m talking about Lemmy as a product - not specific to any instance

The issue with that approach (too busy to build structure), is that it’s a never ending battle. There is never a good time. It’s an easy trap to fall into.

The best way to be successful with products like this is to invest time early in building out the team. By doing so, you’re multiplying output and limiting tech debt.

I would even be happy to help with helping build out the team (identifying gaps, key roles, volunteers) as that’s something I’m experienced with.

The GitHub repo will be focused on software-level initiatives, whereas I’m talking more about product-level.

If the team is that small, then they need more people involved in product ownership, which is what I’m interesting in contributing towards (as others are too, I assume)

Lol, what community was this

For sure. It’s super young. It’ll continue to grow most likely.

This is the huge problem with Masrodon imo. Twitter has all kinds of crazy algorithms, often bad and leaning towards hate/fear. Mastodon seems to be on the far other end with very little to drive engagement.

This is why a Reddit-type use (Lemmy) is perfect. The algorithm is mostly human driven with upvotes/downvotes.