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.
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.
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.
yes, there are various other browsers still supporting proper ad blocking
I like having TLS in my browser
SwiftKey? seeing the same here
it’s clearly 3, stop spreading misinformation
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.
I can sell you a copy of lemmys source code, are you interested?
sure they do, you’re one of them
you can enable end to end encryption, it’s optional. I don’t think it’s enabled by default.
until 0.19.4 is released, clients are supposed to suppress comment contents when the comment is either marked as removed
(moderator) or deleted
(creator).
they might decide to show contents to site admins or community moderators anyway, but some clients did not implement this properly and show the original content to all users.
this is of course not something that should have been available to everyone in the first place, which is why this is being fixed in 0.19.4.
depending on the client, you should still see some kind of indicator above the comment text that shows it was removed or deleted, in this case removed.
won’t be the case for much longer, the next lemmy release is removing that.
i suggest you remove this quote and summarize it with fewer details if you need to have it there in the first place. you’re effectively advertising for them now and undoing the moderator action of removing this advertisement.
The OEM version is working fine, as the drivers are embedded there. My point was that without this recovery partition you tend to run into issues on newer devices, as the MS bundled drivers get updated only infrequently.
even on Windows 10/11, I’m still frequently hearing about issues at work where the necessary ssd drivers are only included in the default windows installer (not the recovery shipped with the device) like half a year later. at least with Dell this seems to be a common theme.
reporting absolutely helps. it increases visibility for content that slipped through automated moderation and having more reports for content indicates urgency.
here’s also some more context and explanation about what’s going on:
https://fedi.fyralabs.com/notes/9psdqurvye
https://fedi.fyralabs.com/notes/9psnooe6p1
https://fedi.fyralabs.com/notes/9pth6oh3xr
based on the sticker logic, it’s clearly not
at that point you’ll just discourage any new users if they have to gamble on whether or not their content is actually seen by anyone. account age really isn’t a good indicator of anything other than soemone being dedicated enough to spam. considering this isn’t the first wave of csam attacks, i can assure you that whoever is targeting lemmy with this is determined enough that account age won’t deter them for long, they’ll just have to slightly adjust their playbook.
that doesn’t do anything, they’ll just register accounts in advance and wait some days.
we’ve even had spam recently from accounts that had been dormant for months, although it was a different kind of spam.
that would explain the google fine in russia