deleted by creator

deleted by creator

deleted by creator

deleted by creator

The maintainer is going to use whatever platform they want.

Those who want support will use whatever platform the maintainer is available in.

If you’re an end user needing support but refuse to use the mechanism provided, you’re welcome to read the code yourself.

deleted by creator

deleted by creator

I don’t see how you intend to convince anyone to ditch Discord by deliberately misunderstanding a simple point.

Many support Discords expect people to chat in a channel, not DM. Many issues will be in the public, in a channel. There is simply no privacy issue here for the vast majority of problems.

Discoverability of past issues is another problem, but that’d still be problematic if you’re on Matrix.

I’m keeping my project’s community on Discord. People who use my stuff seem satisfied.

This thread shows that merely having a Discord acts as a good filter to inhibit users who aren’t going to be helpful.

I’ll simplify:

How is there is a practical privacy issue here when the purpose of the chat is public support?

There should be no expectation of privacy in a public support chat/forum to begin with.

Let’s not be unreasonable with dogmatism here.

deleted by creator

“Help, your library isn’t loading the Foobar files created in Bazfoo 2024” is not something that is sensitive data.

It is not my responsibility to manage random people’s baseless paranoia as a project maintainer.

What are you exchanging on Discord where this is an issue?

I’d hope your doctor isn’t joining your OSS project discord to conduct appointments or anything.

Running and managing a server takes a non-zero amount of work and is a commitment…if you’re actually serious about it.

That’s work wasted on sysadmining and not going into project development.

There’s just some really salty people who browse /All.

I’ve banned a couple of people who’ve been downvoting random things in my instance because they don’t even live near where my region targets (based on their post history).

For fun, look at the Tesla communities, it’s littered of random downvotes from salty people.

I’d eventually like to see a feature to limit voting to communities someone is subscribed to. Sure it can be worked around but it would take a smidge of effort. But there are probably a trillion more important things in the backlog.

Completely disagree on the scalability argument and I find it silly.

Most instances are small. Not everyone is going to run a 20,000 person instance where all 20,000 show up on the same day.

If you’re a big instance like lemmy.world, then sure, I can buy the scalability argument, but once you’re at that point you’ve likely established that there is an active and engaged admin team.

As a bonus, it even serves as a great asshole filter. If someone gets upset they had to wait a day for an approval, imagine how they’d act once they’re in.

deleted by creator

deleted by creator

deleted by creator

deleted by creator

deleted by creator