rss-bridge
rss-bridge copied to clipboard
[SteamBridge] Question about items
Let's have scenario. We have feed with discount (example https://feed.eugenemolotov.ru/?action=display&bridge=Steam&userid=76561198260599288&only_discount=on&format=Atom )
So time ago, there was a discount. My rss reader fetched item from feed. This item's id is http://store.steampowered.com/app/519860/
. Some time later, Steam stopped giving discounts. Ok.
Then, when discount appears again, there will be item in feed. But it will have the same id, and IMHO it won't appear again in my rss reader (at least as new item).
@JackNUMBER as you are bridge maintainer, any comments?
Not sure about Bridge-Request
label. Ignore this label.
I see the usecase. My RSS reader doesn't use ids. At the moment I haven't any solution, if you have feel free to contribute 😉 I will think about it.
@em92 I checked what it is possible to do, here my report.
To provide and use an ID we need a variable information (like a "sale start date") from the source or a storage in RSS-Bridge to keep a generated ID in memory. There is neither of them 😂
Then, the possible ways :
- generate a new id at each call (generated on the fly) → useless in any case
- generate the id from the price (kind of variable information) → if a new sale come with the same price, the ID will be the same
- generate the id from the current date (variable information) → each day the sale will the effective your rss reader will be triggered
- generate the id from the current month + the price → it's highly unusual for sale to be applied twice a month and if the case come you might have to buy it the first time ^^
In all way the id will not be really uniq (related to a specific sale). Then, the better solution seems the last one. BUT it's not elegant and it's a trick for a dedicated case.
@LogMANOriginal Any opinion?
Unfortunately there is no persistent state in RSS-Bridge with which you could determine if the state changed between calls. From the JSON data it looks as if each element under "subs" has its own unique ID. Maybe the ID changes for every sale?
Alternatively there seems to be an open Steam API that might be worth looking into: https://steamcommunity.com/dev
This service has a "Last Change Number" that looks unique: https://steamdb.info/app/519860/ But I'm not sure where they pull it from (maybe the API above?)
Is this still relevant? Im thinking we would need to find some unique information for it to produce a "new" feed item.
Is this still relevant?
Yes
This is a possible use case for #1380.
since the cache is now improved it can be used to store state