Regular notes (kind 1) are intended to be relatively short. They are also plain text only. They are ideal to have show up in a continuous feed.

Long-form notes (kind 30023) are meant to be just that: long. Not ideal to show up in a continuous feed. Additionally, they support markdown for more dynamic formatting.

Not all clients need to support all note kinds and certainly not in the same feed.

For instance, Habla.news ONLY supports long-form. There's nothing wrong with that. That's what the client dev has decided to make a client focused on. Olas is a client that ONLY shows image-specific notes (kind20). Cool. Fountain has a feed that only shows notes that mention podcasts, because it's a podcast client first, with social interaction enabled by Nostr.

Meanwhile, Amethyst tries to pack in as many different note kinds as it reasonably can, so that the user who wants a single client that they can see most everything on will be served. However, it won't do any one thing nearly as well as a client dedicated to it. You CAN use Amethyst to view Nostr livestreams, but you would probably have a better experience on zap.stream. You CAN use Amethyst to view an image-only feed, but you would probably have a better experience on Olas. You CAN view long-form notes on Amethyst, but the experience is probably going to be better on Habla or Highlighter. You CAN see marketplace listings on Amethyst, but you have way more options for filtering and browsing by category if you go to Shopstr.

So no, you're not going to see your long-form note on every Nostr client, nor should you.

Also, you are not broadcasting your notes TO clients. You are broadcasting them to relays, and the clients fetch the note kinds that they support from those relays.

Sidenote: I was able to see your article on Primal just fine here: https://primal.net/e/naddr1qvzqqqr4gupzpztv8m5x99xel8qfac6hxd9w7jly77pg2z92nqgddyud8ns9fnp3qqxnzdenxcer2dehxvmnwvpkzj4xx9