I'm not sure what the correct terms are, so I'll refer to in-app/in-client notifications as internal notifications and mobile-style out-of-app notifications as external notifications.
Based on what people usually refer to with the word "notification" in the context of social applications and messaging services, and your comment, I'm assuming you're talking about external notifications. If you mean all notifications in general, I've misunderstood your point and can ignore the rest of this comment. I do think that internal notifications are useful.
I'm not saying that external notifications are useless, but rather that I don't feel that they're as important as you seem to make it out to be.
Also, even if your Lemmy client doesn't support external notifications, Lemmy supports RSS, which you can subscribe to with a different application.
It should probably facilitate discussions then
Discussions do not have to be between only two people, others can continue where someone else left off.
People often need to continue conversations to clarify information & elaborate…
This is true, but it doesn't require notifications outside of the client. For example, I noticed your reply as Lemmy's web UI showed that I had an unread message.
I don't mind continuing a discussion over multiple days, though I'm not sure if this applies to everyone.
Shades of Mastodon users justifying suicidal design choices that were later rolled back here.
Could you elaborate? I don't use Mastodon, as I don't see the value in "micro-blogging" and prefer to follow topics rather than people.
As for the rest of your comment, I too disagree with blocking VPNs & Tor to fix their CSAM problem, but I don't see how that is relevant to this discussion? Though I do not mind if you want to discuss that instead.
Notifications are actually very important for people who treat platforms interchangeably.
How so? At least, I don't think that they're important to Lemmy, as it's not about real-time person-to-person communication, but rather discussion about topics.
The periodic table also broke backwards compatibility. Earth & air were split into many elements each, water is now a combination of two kinds of air and they just straight up removed fire & aether.
That doesn't explain why urls in code blocks are rewriten as well. When the image is surrounded by backticks, it shouldn't be parsed but rather displayed verbatim as the code block's content.
I'm not sure how or if Piefed's UI shows it, but posts are written in Markdown.
When you add an image, text gets added to your post or comment in the following format: . So, in your post the "image" is just the string , which clients (Lemmy's & Piefed's web UI and applications) replace with the actual image.
So, if your post/comment editor has an option with something like "source", "plain text" or "Markdown" in the name, you can enter a description for the image in the brackets right after the exclamation mark.
Fixed image example: 
The alt text is used by things like screen readers, and even normal browsers, if the image fails to load. So, something like the following might be better:
Logo of Unfinished Projects, with the tagline "In solidarity we can build a future that benefits us all"
If anything is still unclear, I'm happy to answer any questions you may have.
Up to three, with the following exceptions: Four is not acceptable. Neither is two, except if the next largest number happens to be a three. Five is right out.
Also acceptable are prime numbers divisible by a previously mentioned number.
A small nitpick, but could you do something about the image alt text in your post? A filename, especially a non descriptive one, is not exactly great for accessibility.
The G in guitar doesn't mean graphical. It means guitar, as you interact with the device by plucking strings, like in string instruments, like the guitar. So, a guitar is actually a "Guitar User Interface tar".
Which one?