[HN Gopher] Some early results for feed reader behavior monitoring
___________________________________________________________________
Some early results for feed reader behavior monitoring
Author : zdw
Score : 22 points
Date : 2024-06-12 01:11 UTC (3 days ago)
(HTM) web link (rachelbythebay.com)
(TXT) w3m dump (rachelbythebay.com)
| brudgers wrote:
| Some background here,
| http://rachelbythebay.com/w/2024/05/27/feed/
| m463 wrote:
| why are all the links to the site http instead of https?
| asimops wrote:
| There is no redirect in place. They also have a http rss feed
| where all links are http. Maybe the poster uses this feed.
|
| PSA: If you change the feed to https, it will also serve all
| links as https.
| ziggy_star wrote:
| So even the well intentioned feed readers misbehave sometimes. I
| guess there is a spec but no proper test suite ever emerged?
|
| On the flip side should RSS become a thing again thus
| incentivizing bad actors what recourse is there? Or just from
| poorly written ones?
|
| Seems to be a missing piece.
|
| With torrenting there is either a tracker enforcing ratio or
| gossip between clients - so bad actors are quickly flushed out of
| the system. Maybe that's a fertile place to draw inspiration
| from. I'm not sure.
| x0x0 wrote:
| If I were betting, I'd bet many of the supposed bugs are
| readers working around incorrectly-implemented servers. If the
| feed doesn't update, but it's because of a server bug, your
| users are still left unhappy. In a perfect world the readers
| would note which servers are implemented correctly and which
| you can't trust last-updated / etags etc... that's a lot of
| work.
___________________________________________________________________
(page generated 2024-06-15 23:01 UTC)