example

joined 1 year ago
MODERATOR OF
[–] example@reddthat.com 4 points 3 months ago (2 children)

it's clearly 3, stop spreading misinformation

[–] example@reddthat.com 3 points 3 months ago* (last edited 3 months ago)

if you're not community banned you might still be instance banned on the community instance, which wouldn't show up in your local instances modlog if the ban happened on a <0.19.4 instance. if the methods pointed out by other comments here fail I suggest you visit the instance of the community and check the site modlog there, searching for your user.

i suspect you're referring to your post to a lemmy.ml community and you have indeed been instance banned there for a limited amount of time.

[–] example@reddthat.com 31 points 4 months ago

sure they do, you're one of them

[–] example@reddthat.com 1 points 5 months ago (1 children)

Are those downvotes maybe coming from non-Lemmy instances?

As an admin you should be able to see the downvotes of the post that made it to your instance.

I'm wondering if some software might be broadcasting votes to all linked instances, while I believe Lemmy only sends them to the community instance and it's the community instance's responsibility to relay them.

[–] example@reddthat.com 2 points 8 months ago

The 90 days disclosure you're referencing, which I believe is primarily popularized by Google's Project Zero process, is the time from when someone discovers and reports a vulnerability to the time it will be published by the reporter if there is no disclosure by the vendor by then.

The disclosure by the vendor to their users (people running Lemmy instances in this case) is a completely separate topic, and, depending on the context, tends to happen quite differently from vendor to vendor.

As an example, GitLab publishes security advisories the day the fixed version is released, e.g. https://about.gitlab.com/releases/2024/01/11/critical-security-release-gitlab-16-7-2-released/.
Some vendors will choose to release a new version, wait a few weeks or so, then publish a security advisory about issues addressed in the previous release. One company I've frequently seen this with is Atlassian. This is also what happened with Lemmy in this case.

As Lemmy is an open source project, anyone could go and review all commits for potential security impact and to determine whether something may be exploitable. This would similarly apply to any other open source project, regardless of whether the commit is pushed some time between releases or just before a release. If someone is determined enough and spends time on this they'll be able to find vulnerabilities in various projects before an advisory is published.

The "responsible" alternative for this would have been to publish an advisory at the time it was previously privately disclosed to admins of larger instances, which was right around the christmas holidays, when many people would already be preoccupied with other things in their life.

[–] example@reddthat.com 1 points 10 months ago (1 children)

unfortunately, reports still do not federate to mods on other instances.
the related GitHub issue is https://github.com/LemmyNet/lemmy/issues/3781

 

Hello Reddthat,

Similar to other Lemmy instances, we're facing significant amounts of spam originating from kbin.social users, mostly in kbin.social communities, or as kbin calls them, magazines.
Unfortunately, there are currently significant issues with the moderation of this spam. While removal of spam in communities on other Lemmy instances (usually) federates to us and cleans it up, removal of spam in kbin magazines, such as those on kbin.social, is not currently properly federated to Lemmy instances.

In the last couple days, we've received an increased number of reports of spam in kbin.social magazines, of which a good chunk had already been removed on kbin.social, but these removals never federated to us.
While these reports are typically handled in a timely manner by our Reddthat Admin Team, as reports are also sent to the reporter's instance admins, we've done a more in-depth review of content in these kbin.social magazines.
Just today, we've banned and removed content from more than 50 kbin.social users, who had posted spam to kbin.social magazines within the last month.

Several other larger Lemmy instances, such as lemmy.world, lemmy.zip, and programming.dev have already decided to remove selected kbin.social magazines from their instances to deal with this.

As we also don't want to exclude interactions with other kbin users, we decided to only remove selected kbin.social magazines from Reddthat, with the intention to restore them once federation works properly.
By only removing communities with elevated spam volumes, this will not affect interactions between Lemmy users and kbin users outside of kbin magazines. kbin users are still able to participate in Reddthat and other Lemmy communities.

For now, the following kbin magazines have been removed from Reddthat:

To get an idea of the spam to legitimate content ratio, here's some screenshots of posts sorted by New:

!fediverse@kbin.social[Screenshot of posts in !fediverse@kbin.social sorted by New](https://scrot.de/img/M/e/hIpRDN7DbQ50S1ensKT1v4g1B.png)

!opensource@kbin.social[Screenshot of posts in !opensource@kbin.social sorted by New](https://scrot.de/img/E/g/mBmHFnkDd-I7RKotU-o0YBcji.png)

All the removed by mod posts mean that the content was removed by Reddthat admins, as the removals on kbin.social did not find their way to us.

If you encounter spam, please keep reporting it, so community mods and we admins can keep Reddthat clean.

If you're interested in the technical parts, you can find the associated kbin issue on Codeberg.

Regards,
example and the Reddthat Admin Team


TLDR

Due to spam and technical issues with the federation of spam removal from kbin, we've decided to remove selected kbin.social magazines (communities) until the situation improves.

[–] example@reddthat.com 1 points 11 months ago

that's not entirely accurate.

the main problem for non-kbin users, as @ono@lemmy.ca is using lemmy, is that kbin moderation actions, such as a moderator or admin removing spam will not federate to lemmy, as this is not implemented yet.
for a lemmy user, it appears that kbin doesn't have any moderation at all, while spam is being removed for kbin(.social) users at least.

for this reason, several lemmy instances have already either defederated from kbin or removed kbin communities from their instance.

[–] example@reddthat.com 2 points 11 months ago

it is generally possible to find the post on another instance through the search, at least through the default web interface. there is certainly a lot of room for improvement though.

[–] example@reddthat.com 3 points 1 year ago

indeed, original source is the wrong term, but at least it's an english derivation of it, which was only copied by the link in this post

[–] example@reddthat.com 3 points 1 year ago

it is indeed somewhat attributed, but it still very much looks like scraped content.

a very strong indicator is the inclusion of

Subscribe The most engaging reads in blockchain. Delivered once a week.

Email address

SUBSCRIBE

at the end, which on cointelegraph's page is separate from the content and provides a sign-up form.

view more: next ›