The Lemmy UI doesn’t allow you to see others’ private messages, no, but you shouldn’t consider them to be private. It’s possible for instance admins to read them, and in the past there’s been exploits allowing anyone to read them. If you need more secure messaging, use Matrix instead.

Python does have a switch statement now, actually. And yes, they went out of their way to call it something different - match.

https://docs.python.org/3/tutorial/controlflow.html#match-statements

You can read up on the conversation on the GitHub issue here.

TL;DR: the current system on the (unreleased) 1.0 codebase is that your Lemmy instance will replace all Lemmy URLs in posts/comments with the equivalent URLs on your own instance. In the issue I linked, some concerns are raised about this system and various other options are discussed. It’s possible that the way it works will change before Lemmy 1.0 is released.

Lemmy doesn’t support this natively, but many clients do. Off the top of my head:

• Tesseract (desktop)
• Voyager (web frontend designed for mobile. I believe you need to install the app rather than using the website to use keyword filters)
• Mlem (iOS)
• Arctic (iOS)
• Thunder (Android & iOS)
• Sync (Android; I’ve heard Sync is unmaintained though)

Assuming you’re on desktop, Tesseract is probably your best bet. It might also be possible to get Voyager working. Some instances (like sh.itjust.works) run their own Tesseract instances (https://tesh.itjust.works/), but lemm.ee doesn’t. You’d have to use some other Tesseract instance, specifically one that allows connecting to any Lemmy instance (https://tesh.itjust.works/ is for sh.itjust.works accounts only). E.g. https://tesseract.dubvee.org/

Mobile apps should allow you to log into any instance. My Lemmy client won’t connect to lemmy.rip either, and fails with the following error:

The certificate for this server is invalid. You might be connecting to a server that is pretending to be “lemmy.rip”, which could put your confidential information at risk.

This is also what I see when I try to connect to lemmy.rip in the browser:

I am able to bypass this warning and see the site in the browser.

Here’s the relevant issue on the GitHub repo: https://github.com/LemmyNet/lemmy/issues/4340

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.

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 problem for me on Safari iOS. The username input box is behind the logo, but I can’t click on it without clicking on the logo. Will try on my desktop when I get home

³LMAO

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.

Source