Просмотр новости
Найдите то, что Вас интересует
Спутники
РН
SpaceX
Роскосмос
NASA
Three-part ecosystem
Дата публикации: 21-07-2026 13:43:09
There are three parts to the rss.chat ecosystem.
Writing. Today's rss.chat product is a group writing system, designed for a school department, a team of developers, a family, a magazine or group blog, or just as well, a single author. I don't think it would work well with 1000 users, because it doesn't implement the concept of "follow." And imho it's important that the people are colleagues, family or friends, people invested in real world relationships with each other, so they don't drop a turd in the conversation and just expect to walk away. I've found that dynamic works most of the time. But important point -- all kinds of writing tools can exist. Any social app can to be part of this, all they'd have to do is support inbound and outbound RSS and textcasting. Small pieces loosely joined and every part replaceable. And we do it with the web, we don't try to invent a new web. I will keep beating that drum because it's the difference between using twenty editors or one. As a writer I know that one is the best, with choice among 20 editors, because maybe somedays I feel like writing in a different editor. To make the web a real writing environment, you have to think like a writer. ;-)
Reading. This can be as simple as a current-day reader like Feedly or NetNewsWire, or more, using the new features in RSS.chat feeds.
The unknown: We're allocating in our minds (Claude and I) room for a fair number of unforeseen products created by independent software devs in the cracks between reading and writing, and in a larger world (search, navigating through structures, etc. We have really good thread support baked into the protocol. And a bit of docs about how the pieces fit together.
I'm thinking in these terms because I'm starting to work on how my reader will work. I have some ideas, not sure when I'll be ready to write about them. And to be clear there will be no requirement that you use our writing tool to use our reader or vice versa.
Every part replaceable.
Основное содержимое страницы с новостью.
It's even worse than it appears..
Tuesday July 21, 2026; 9:43 AM EDT
There are three parts to the rss.chat ecosystem. #- Writing. Today's rss.chat product is a group writing system, designed for a school department, a team of developers, a family, a magazine or group blog, or just as well, a single author. I don't think it would work well with 1000 users, because it doesn't implement the concept of "follow." And imho it's important that the people are colleagues, family or friends, people invested in real world relationships with each other, so they don't drop a turd in the conversation and just expect to walk away. I've found that dynamic works most of the time. But important point -- all kinds of writing tools can exist. Any social app can to be part of this, all they'd have to do is support inbound and outbound RSS and textcasting. Small pieces loosely joined and every part replaceable. And we do it with the web, we don't try to invent a new web. I will keep beating that drum because it's the difference between using twenty editors or one. As a writer I know that one is the best, with choice among 20 editors, because maybe somedays I feel like writing in a different editor. To make the web a real writing environment, you have to think like a writer. ;-)#
- Reading. This can be as simple as a current-day reader like Feedly or NetNewsWire, or more, using the new features in RSS.chat feeds.#
- The unknown: We're allocating in our minds (Claude and I) room for a fair number of unforeseen products created by independent software devs in the cracks between reading and writing, and in a larger world (search, navigating through structures, etc. We have really good thread support baked into the protocol. And a bit of docs about how the pieces fit together.#
- I'm thinking in these terms because I'm starting to work on how my reader will work. I have some ideas, not sure when I'll be ready to write about them. And to be clear there will be no requirement that you use our writing tool to use our reader or vice versa. #
- Every part replaceable. #
Схожие новости
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | What is RSS.chat for Howard Rheingold | 0 | 6.56 | 20-07-2026 |
| 2 | rss.chat isn't really a product | 0 | 5.62 | 26-07-2026 |
| 3 | How I see the network evolving | 0 | 5.62 | 27-07-2026 |
| 4 | RSS.chat has an API | 0 | 6.51 | 25-07-2026 |
| 5 | When the walls came down | 0 | 7.88 | 28-07-2026 |
| 6 | A peptalk for devs | 0 | 9.01 | 18-07-2026 |
| 7 | Dear podcast client devs | 0 | 7.47 | 24-07-2026 |
| 8 | How the web got gunked | 0 | 8.42 | 22-07-2026 |
| 9 | Вайб-кодинг без розовых очков: как я писала свой продукт с Claude | 2 | 6 | 08-07-2026 |
| 10 | Я хотел уйти. Но в итоге начал жить втроём. Звучит ... | 0 | 7 | 18-07-2026 |
Классификация: . Схожих патентов: 0. Схожих новостей: 10. Тональность: 0. Информативность: 10.76. Источник: scripting.com.