It’s a milk bottle warmer; you can see the milk bottle sticking out of the top.
It says “hot surface do not touch” in full, actually. Braille uses single characters to represent some common letter combinations (“touch” is “t” + “ou” + “ch”). The words “do” and “not” are each contracted to a single letter (“d” and “n” respectively).
Birds have peckers
Check the page tomorrow. Maybe different?
If you end up only considering a single branch, it would be a good idea to let app owners change which branch is considered “main”. Many apps have a main branch that stores the live code state, and a second development branch where all of the work is done. When an update is released, code is pushed from the development branch to the main branch. In this setup, it would make the most sense to show the most recent commit on the development branch rather than the main branch.
Also, Memmy is shown as having a recent commit 23 days ago - this commit was created by a bot here, and isn’t actually indicative of active development. It may be worth ignoring commits from depandabot when checking for the most recent commit, if that’s possible.
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
If you block the bot, you won’t see its comments. I personally find the bot to be useful in most cases.
Lemmy supports instance blocking as of version 0.19. Some clients also support instance blocking for pre-0.19 instances.
Lemmy doesn’t cater the All feed to you like other social media platforms - it doesn’t take into account which posts you open, which posts you upvote, etc.
“Karma police, arrest this girl”
Definitely misogynistic
An alarm clock with a warm-colored light on it, that slowly turns on over a period of time leading up to your alarm. Some smart lightbulbs can also be set to do the same thing, which is what I use.
The photo on the left is with makeup; the photo on the right is without. On the leftmost image the lips are more saturated and have more defined edges and there is more shadow around the eyes.