MrKaplan

you'll want to follow https://github.com/LemmyNet/lemmy/issues/818 for that

Depends on the type of feature request.

For most feature requests the project issue trackers are likely the best place.

• Lemmy backend: https://github.com/LemmyNet/lemmy/issues
• Lemmy default web interface: https://github.com/LemmyNet/lemmy-ui/issues

Alternative UIs and apps have their own issue trackers as well.

If it's something that's just about configuration or something we have built ourselves !support@lemmy.world can be a good place for that.

Feel free to reply here though and I can tell you where it's best placed.

we currently have our own solution to send emails with a custom text explaining why people were rejected and what they can do next. we'll have to review whether the built-in solution would be capable of replacing this functionality adequately if we add rejection reasons to lemmy when rejecting the applications.

our current solution rejects applications and then deletes the user from the database to ensure that they can sign up again if they want, as denied applications only get deleted after a week or so and an appeal process would require support tickets and a lot more time to be spent by us on addressing those.

our application process is fully automatic and just depends on certain words to be provided and the email not being disposable.

The link is up there in the post for you to use.

The screenshot in my previous comment is directly from their abuse form at https://abuse.cloudflare.com/csam. Your email is specifically about their proactive scanner, not about abuse reports that are submitted.

They also explicitly state on their website that they forward any received CSAM reports to NCMEC:

Abuse reports filed under the CSAM category are treated as the highest priority for our Trust & Safety team and moved to the front of the abuse response queue. Whenever we receive such a report, generally within minutes regardless of time of day or day of the week, we forward the report to NCMEC, as well as to the hosting provider and/or website operator, along with some additional information to help them locate the content quickly.

they do, they just don't require you to be registered with them anymore for their csam scanner:

potentially identifying information, such as addresses, must be removed. images of the person must either be heavily pixelated or entirely cut out.

with the content i've seen it gave me more of an impression of being captures of a live stream, but that's just guessing

likely unrelated, but I already forwarded the PM reports we received on LW to .ee admins a few hours ago. probably just a "normal" pm spammer.

unless you operate the instance that is being used to send this material you can generally only work with the content that is being posted/sent in PMs. almost all identifying information is stripped when it leaves your local instance to be federated to other instances. even if there was a group of instances collaborating on e.g. a shared blocklist, abusers would just switch to other instances that aren't part of the blocking network. there's a reason why it's not recommended to run a lemmy instance with open signups if you don't have additional anti-spam measures and a decently active admin team. smaller instances tend to have fewer prevention measures in place, which results in a burden for everyone else in the fediverse that is on the receiving end of such content. unfortunately this is not an easy task to solve without giving up (open) federation.

I'm sorry, sometimes it's hard to tell whether people actually mean it. I can totally see people commenting that and being serious.

mentally ill people can have plenty of time on their hands to invest this much effort in harassing others. people claiming that this can't be harassment are effectively supporting the harassment, as that tries to further blame the likely victim of this. obviously this is just speculation, as we don't know the full truth.