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
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
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?
people on mastodon need to mention a lemmy community to post there. you can’t see mastodon posts on lemmy unless they’re in a community. comments from lemmy are a pretty bad experience on mastodon I believe.
fwiw, every week or so there is a scheduled task that permanently overwrites contents of deleted comments.
fyi @freamon@lemmy.world
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.
it sure is possible, but not with the amount of work anyone would be willing to put into it.
you can just turn it off, see https://help.kagi.com/kagi/settings/general.html
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
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.
why is this a blog spam article badly copied from the original source at https://cointelegraph.com/magazine/china-dev-fined-salary-vpn-10m-ecny-airdrop-asia-express/ ?
in my experience it becomes hidden even from admins, at least on the instance it was removed on. i’ve seen this both on a remote user with remote content and also on a local user with remote content from the admin perspective and in neither case i still see any content on the user’s profile.
ncdu
makes it even easier if you want to interactively browse through folders to see which files exactly are eating up space
yeah, that I’ve seen as well, which seemed to correlate with expanding or failing to load images.
not stuttering but sometimes jumping around unexpectedly.
Jerboa is laggy on your Pixel 7? it’s perfectly smooth for me on my Pixel 5.
unless they changed it, play dev is a one time purchase, only apple takes a yearly fee.
it’s clearly 3, stop spreading misinformation