Worth noting is that what counts as an “active user” has changed between now and then. During the Reddit API exodus, an “active user” was a user who had posted or commented in the past month. Now, it includes users who have voted. If the 54k MAU record was set using the first algorithm, it is likely that the MAU using the new algorithm (which includes voting) would have been much higher.
Can a panther be born from two black panthers and not be black?
Based on my rudimentary high-school knowledge of alleles, the answer would be “yes” for some jaguar pairings, with a 25% chance of getting a regular jaguar in those pairings. It wouldn’t be possible for leopards.
I’m not an expert though so if I’m wrong feel free to correct me
OC isn’t claiming that the shift in the industry is solely Apple’s fault:
I don’t hate Apple but I do hate their influence
The reality is that what OC said is exactly what happened. Apple removed the headphone jack to coerce people into buying AirPods. Everyone else released their own wireless earbuds to compete, and also removes their headphone jacks for the same reason.
Swift’s extensions system has spoiled me, and I feel the pain of this whenever I have to write Java
Backend of the app or the lemmy server? if it is not stored on the lemmy server then there will be no way to delete it even if the app stores the token.
Apologies, I worded that badly. Lemmy uses an image hosting service called pictrs to manage the images you upload, which is largely separated from the rest of the Lemmy backend. Pictrs of course stores the delete tokens matching each image, but Lemmy doesn’t associate those tokens with the posts or comments they originated from as far as I know.
I’m a developer of a Lemmy client. When you upload an image to a Lemmy instance, the instance returns a “delete token”. Later, you can ask the instance to delete the image attached to the delete token. So as long as you keep hold of the delete token for a specific image, you’re able to delete it later.
Lemmy-ui (the official frontend) will give you the option to delete an image again shortly after uploading it. However, it’s not possible to remove the image after actually creating the post, as the delete token associated with that post isn’t remembered anywhere on the Lemmy backend.
As for other Lemmy clients, YMMV. The client I work on (Mlem) deletes images if you remove them from a post before posting it, but has the same pitfall as Lemmy-ui in that it won’t delete the image if you’ve already created the post.
It would be possible to locally save the delete tokens of every image you upload, so that you can request that they be removed later. I don’t know of any clients that can do this yet, though (if someone knows of one, feel free to mention it).
Edit: clarity
Same. I’ve made six accounts since I joined during the exodus, only two of which I actively use now.
There’s not an in-app key for it currently, no. Here’s what each of them mean:
_ - bot
deleted by creator
I don’t see why you’re being downvoted - whilst a significant portion of Apple’s claimed ‘carbon neutrality’ can indeed be attributed to carbon offsets, they have also made changes in other areas. Here’s a graph from Apple’s climate report that shows the supposed change in emissions between last year and this year’s watches.
Thanks for the info! We’ll look into it.
We’re sorry this happened! Users aren’t meant to be able to remove the info stack widget 🤔 Did the app let you remove the info stack widget, or did it bug out and remove all of the widgets itself?
Deleting the app and redownloading it from the App Store should fix this, but you’ll have to readjust all of your settings I’m afraid. I’ll add a ‘reset’ button for the interaction bar customiser in the next version, so that it’s easier to fix if this happens again.
This isn’t possible yet unfortunately. We plan to expand the functionality of the search tab to include post searching, but we haven’t got there quite yet.
Thanks for the help! Unfortunately those settings are unlikely to make any difference. We’d appreciate a screen recording if you’ve got the time, though
You can hide posts that you’ve read via the ellipsis menu in the top-right of the feed. Note that a post counts as read if you’ve opened it in the expanded view or interacted with it in some way, such as by upvoting the post.
Posts are not marked as read by simply seeing them in the feed. We’re aware of the ‘mark read on scroll’ feature that other social media apps have, and we’d like to implement this at some point. The issue is that we need to make an individual API call for every single post that is read, as posts can only be marked as read one-by-one using Lemmy’s API. Sending an api call every time a post appears on-screen could cause performance issues and would constitute poor API citizenship. We’re working with the Lemmy devs to hopefully get a way to mark many posts as read with a single API call, which would solve this issue.
To show only posts you haven’t read, you can click the ellipsis ‘…’ button in the top-right of the feed and select ‘hide read’. Note that this only hides posts that you’ve opened or interacted with in some way, not just seen. We’re planning on improving this at some point in future
Community-wise there’s !WomensStuff@lazysoci.al