![]() The only problem I can see here is that because a lot can happen at the same time, if the client relies on the timestamp being the exact point that data is read, it’s possible for a parallel write to have a timestamp before the read but is not yet visible to the read due to the way RDBMS transaction isolation works… only the matter of milliseconds, but still possible. Yep, good idea - I could return the server timestamp in all API responses. (Also, but you might label this ‘out of scope’, it would be cool to get data on which feeds are popular, so that relational recommendations (‘those subscribed to x are subscribed to y’) could be presented for example directly in AntennaPod for those that sync with your service.) My AntennaPod installation and the entry are then ‘conflicting’ However, the person owning/hosting the feed forgot to update their entry on, which thus stays xyz.com/rss. Because of the redirect AntennaPod updates the feed it follows. I as an AntennaPod user follow xyz.com/rss, and the feed changes address (to abc.com/rss) with a nice 301/308 redirect on the server. I’m asking because of the following scenario: And a related question, are the two datasets (‘the things you publish’ and ‘the things you consume’) separate or linked somehow?.Since you don’t do any processing or fetching URLs, I’m wondering: do you ‘aggregate’ data in a way? As in: are you able to provide/develop a list of popular feeds (average for the whole userbase)?. ![]() First of all thanks for working on this - it’s a great initiative.
0 Comments
Leave a Reply. |