example

joined 1 year ago
MODERATOR OF
[–] [email protected] 1 points 5 days ago (1 children)

that's odd, my (indirect, reported by others) experience with GlobalProtect on Linux was mostly fine, although when using SAML it only really works with the GUI version and not the CLI version

[–] [email protected] 10 points 2 weeks ago (1 children)

it doesn't seem to be server specific because once prompted there is no way to use the account again, even if you decided to just not use a server that may have these settings set.

[–] [email protected] 38 points 2 weeks ago (5 children)

no, you're also effectively locked out of any participation unless you provide an email address and phone number, which they won't even tell you about in advance but use dark patterns and gaslighting that they noticed "suspicious activity" to step by step first ask you for an email and then once that is validated they prompt you for a phone number. the only thing they don't do yet is ask for ID.

[–] [email protected] 5 points 2 weeks ago (3 children)

yes, there are various other browsers still supporting proper ad blocking

[–] [email protected] 86 points 3 weeks ago (2 children)

missed opportunity for inseals

[–] [email protected] 1 points 1 month ago

hello, your post has been removed from [email protected] for not being flagged as nsfw

[–] [email protected] 5 points 1 month ago

I like having TLS in my browser

[–] [email protected] 1 points 2 months ago (1 children)

SwiftKey? seeing the same here

[–] [email protected] 1 points 3 months ago (1 children)

reencoding is not required in advance, it happens on the fly if needed.

download still needs to be completed first usually, but you can save a lot of time if you compromise in quality.

[–] [email protected] 5 points 4 months ago (2 children)

it's clearly 3, stop spreading misinformation

[–] [email protected] 2 points 4 months ago

this is probably somehow related to changes introduced somewhere in 0.19.4, I've been seeing this for months at this point, as we've been on a 0.19.4 pre-release relatively early due to done federation issues

[–] [email protected] 3 points 4 months ago* (last edited 4 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.

 

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:

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

[email protected][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.

view more: next ›