sure they do, you’re one of them
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.
how about “silly”? “stupid”?
unlike on reddit, you can edit your post title here on lemmy.
no, they’re getting a lot of downvotes because it’s spam.
they’re not interested in legitimate discussion, they only need to promote the spam links at the end of the post.
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.
you sound like you’re not even washing coconuts
those aren’t actually gifs.
they’re frequently webms.
various people don’t care or don’t know the difference between media formats though, so they’ll just call anything remotely gif-like a gif.
nearly all talks are either in English or have English translations. not sure if they’re available on YouTube but you should be able to find everything on https://media.ccc.de
your app seems to be doing weird things then.
the original comment is by user @soundingcock@lemm.ee
, who spams links to gore in comments.
true, my comment was primarily from the perspective of the recipient of tracking links
I haven’t checked how reddit does this but just from the example it seems like there is no anti tracking from the use of urlcheck that you’re describing.
reddit appears to generate tracking link with a specific numeric identifier in their database, so instead of attaching a bunch of removable url parameters they instead do a lookup in their database and then redirect to the original destination.
this also means your app checking the redirect will need to fetch the url to determine the destination, which means their tracking still works just fine.
edit: a word
based on https://help.apple.com/xcode/mac/current/#/deve2819c518 it seems like users may need to explicitly enable sharing crash data with app developers.
I don’t know what the default for this is.
https://help.apple.com/xcode/mac/current/#/dev9a80ab71d seems to imply that you need to distribute your app via app store or testflight to be able to receive crash reports.
the majority of apps installed on my mac are not installed via app store, though many of them have app store variants.
i don’t know if the distribution channel matters or just having the app in app store is enough.
this article however also explicitly states this, so it appears that you do indeed by default not send this data to app developers:
users who download your app from the App Store will need to agree to share crash and usage data with developers.
I’m pretty sure this only goes to Apple, not to the actual developer.
I believe I’ve even seen devs specifically ask for copies of the reports from the crash reporter, as they wouldn’t receive them otherwise.
this doesn’t change the rest of your statement though, just afaik the recipient is different.
if you’re renaming from File.js
to file.ts
, which is also changing suffixes instead of just capitalization, then that couldn’t be explained by case sensitivity, unless it was a typo and you meant File.js
to file.js
I’ve been using case insensitive fs on macOS for years and the only software having issues with this is onedrive.
can’t say i’m surprised.
I didn’t say there were no use cases for this, but the average phone user will not need it. someone using samba on their phone would likely be capable of switching the network config to not randomize every time.
I can sell you a copy of lemmys source code, are you interested?