Thanks for sharing, a very good and important read!
#Blockcore Notes now supports #hashtag in the editor. To be released soon.
I don't have DM support built yet... haha, I will send a message in some days time.
Hear, hear! Same with Blockcore software I work on, I don't put any tracking at all, I have no idea how many is using Blockcore Notes or any other Blockcore software, except Blockcore Notes, which is on Chrome Web Store and give some limited statistics. This is the way, I fight tracking in corporate/enterprise setting all the time.
Awesome =) How to get added?
Hi friends, what do you want from Nostr clients that they don't have yet? It's primarily me working on Blockcore Notes so it's limited how much I can add, so what do you miss in whichever client you use?
Added display of aggregated sats from zaps on user profiles. Still working on improving the zapping support, there are some other issues with loading zapping on individual threads.

https://notes.blockcore.net/ ... first impression ... slow. And ... still slow ... I don't see content yet.
I'm working on different improvements and one of them is displaying zapped amount on profiles, but it appears your profile does not load any zap events. Does your LN-setup support NIP-57? Is it correct to assume that all zaps to you does not result in zap events on nostr relays?
https://notes.blockcore.net/ ... first impression ... slow. And ... still slow ... I don't see content yet.
I'm looking into it, debugging the code here. I zapped myself and it did go through and display, but I zapped your reply and original note, those does not display. Did they get through to you? It was 50 or 55 sats.
https://notes.blockcore.net/ ... first impression ... slow. And ... still slow ... I don't see content yet.
Thanks for feedback! Yes, I did have a look at how Twitter does it, Redditt and others. I'm considering perhaps having an option to render using different logic and layouts, might just be more confusing having more options. Blockcore Notes does allow selecting an individual event and then it renders it's immediate parent. It's just the first revision of layout, got more to do =)
Like this? They already have embedded capability, just need to transform the URL somewhat.

When that is said, it can become sluggish for really large threads as it renders everything at the moment, will be implementing more usage of virtual scrolling views in the future that will improve sluggishness for different views that currently render everything (except content like images, videos, etc.) when opened.
This is habla: https://habla.news/a/naddr1qq9rzd3h8y6nqwf5xyuqygzxljlrqe027xh8sy2xtyjwfzfrxcll8afxh4hh847psjckhkxwf5psgqqqw4rsty50fx
This is NostrBounty:
Look at the naddr1 in the url. I think Habla is addressing it correctly and NostrBounty is either wrong or has a new post, with a new id, for it. But I cannot find this new post anywhere.
It's likely two different posts, the latter has an derived identifier from the post itself while the first one has a custom identifier (which should be d-tag in the event). Some clients posts to Relays that doesn't implement NIP-33 and that can cause some issues.
Shouldn't be slow, if it doesn't load, it's likely a bug and not network or app logic. I know there is an issue sometimes when initially loading the threads that it doesn't render, I'll have a look at it.
Try the direct link to your thread here:
https://notes.blockcore.net/e/533b8cff73494e4e087b94a13e01866aecb9e23277ece8ec7d67f02c612dabab
What you think of threads on Blockcore Notes? Given it a go?
"Take Me Down To The 15-Minute City, Where The Woke Are Broke And The Food Is Shitty."
Tears in the Rain
The technology itself is not, right? FireFox has announced (and perhaps already implemented?) their own certificate store into their browser, which is one step towards more decentralization. Nothing stops us from making an Web5/Nostr web browser that has built-in custom DNS servers (which could be more dynamically selected by users) and certificate authorities. Then we're off sailing on our own sea without relying on any state-dependent root certificates or DNS root authority.