5 ms·
Somewhere far down the page it says that somewhere down the line we might be able to add our own RSS feeds :/ Not really interested until then.
by Aeolun 6y ago
Somewhere far down the page it says that somewhere down the line we might be able to add our own RSS feeds :/
Not really interested until then.
- CharlesW 6y ago> …it says that somewhere down the line we might be able to add our own RSS feeds Even then, what this really means is that when you "add an RSS feed", it'll be added to Brave's back-end system so they can continue to own the distribution. This demolishes the creator/consumer relationship, which is an incredibly sleazy thing to do to content creators. Imagine the HN outcry if Chrome worked the same way, and could no longer fetch web pages directly. I will personally never use a so-called news reader that inserts itself as a centralized middleman between myself and everything I read.
- jonathansampson 6y agoWhat do you mean by "own the distribution"? Brave passes the content through a privacy-respecting CDN. It goes to great lengths to knowing nothing about who is accessing what. If you don't mind sharing, please elaborate on your concerns.
- CharlesW 6y ago> What do you mean by "own the distribution"? Brave passes the content through a privacy-respecting CDN. Yes. Brave [EDIT: the company] is unilaterally putting itself between the creator and the consumer, usurping the task of serving the RSS content without the permission of the content owner. Among other problems, this destroys the ability of creators to get even basic readership metrics for people who might choose to use Brave. Imagine that Brave [EDIT: the browser] started copying and serving your entire web site in your name without your permission, rather than just your RSS. Does that help you understand why this is a problem?
- jonathansampson 6y agoI think there are many issue with this take. Brave is a web browser, putting itself between the creator and the consumer is what it does, by definition. It's the User Agent. In the case of Brave Today, however, only a preview of the content is shown; when the user clicks, they are directed to the source itself (unlike AMP or some other pervasive middle-man). Serving RSS content doesn't require permission; the public feed itself is permission. It's created for the purpose of content syndication (it's in the name). Brave shows only a preview of content (an image, headline, title, date, and maybe a sentence or two from the feed). For the actual content, the user has to go to the resource itself. As for measuring their Brave user-base, publishers were already in a tough spot. Brave reports itself as "Chrome" to these sites. Ideally, the publisher shouldn't need to know if their users are in Chrome or Brave. This feature (Brave Today) doesn't change this relationship in any way. Your hypothetical (if Brave starting copying and distributing, verbatim, websites) is definitely terrible. But that isn't even remotely close to what's happening here; Brave Today shows less content than search results on DuckDuckGo, Google, Bing, or beyond.
- CharlesW 6y ago> Brave is a web browser… I've clarified my comments above to disambiguate, thank you. > Serving RSS content doesn't require permission; the public feed itself is permission. So does Brave not understand the importance of feed metrics for creators? Or if it does, is the plan is to force creators to get metrics for Brave Today users from Brave?
- jonathansampson 6y agoThank you for clarifying. That said, I'm not sure I understand why a feed source needs to know if a viewer is accessing the content via Brave or Chrome. Regarding feed metrics from Brave, what information would we give over? Brave doesn't know who is reading what; we've made Brave Today in such a way that uses and requests aren't handled by the same entity at the same time. The goal is to have no knowledge, while yielding a personalized experience.