3 ms·
> Regarding feed metrics from Brave, what information would we give over? There should be none to give, which is perfectly aligned with your goal to have no kn
by CharlesW 6y ago
> Regarding feed metrics from Brave, what information would we give over?
There should be none to give, which is perfectly aligned with your goal to have no knowledge.
Brave [the company] should consider interfering with RSS metrics as verboten has interfering with web page metrics. That means that clients/user-agents should grab feed updates from the original RSS, using ETags and Last-Modified to avoid unnecessary fetches of unchanged feeds. (Caching for temporary unavailability is normal and fine.)
> …I'm not sure I understand why a feed source needs to know if a viewer is accessing the content via Brave or Chrome.
You brought this up, but it isn't a concern I've expressed. Brave Today would ideally have a uniquely identifiable user agent for RSS metrics, but I don't know that it's necessary.
(That's all I have to say about this. Thanks for listening.)
- jonathansampson 6y ago> You brought this up… Sorry, I thought that's what you meant by "this destroys the ability of creators to get even basic readership metrics for people who might choose to use Brave" earlier. > Brave Today would ideally have a uniquely identifiable user agent for RSS metrics, but I don't know that it's necessary. That's definitely something I could see a publisher requesting in the future; we've done something similar with custom headers in requests, standing in for a unique user-agent string.