I actually like this idea. Of broadcasting the "announcement" of the article to everyone in a Kind 1, that then embeds a link to the full article. I don't think we should be afraid of segmenting types of content to certain relays. I think that's the best way to scale in an efficient way and recreate a stack of applications and use cases via a protocol that separates them from platforms.
I think this is a decent segmentation tool, and I've had a similar feeling myself about the articles. Not that I wouldn't write them, but that I want them to live in a way that the entire network sees it, but that it doesn't necessarily show up as a huge note in front of all of my follower list. 🤔🤔
Thank you for being smart and reasonable.
Sounds to me like a client-side problem. If it’s a bad experience to dump long-form content into the feed, then clients should stop doing it, or at least give the user the choice via a setting.
Segregating notes to different relays by type feels like the wrong layer of the architecture. Clients that present data wrongly will happily continue doing so connecting to more relays rather than fewer.