Q1 what's the point of saving urls to centralized rss feeds on hive, i found manually not working one by checking few old urls, is there use case for this? how you query it from hive? Is it usable only for notifications from live stream?
Q2 what's the point of spamming hive so much, transaction count? can be reduced significantly by simple grouping, also py code above(probably not actually used already) I think would crash on 5+jsons/block. Generally tx count means nothing in this case with centralized app broadcasting data. You can make it more or less, with line of code.
Q3 does indexing happens on hive or centralized database?
The big success so far is Podping. This is now deployed and in beta and being used by four major podcast hosting companies and by Podcast Index itself.
how it's used? live stream of notifications that can be achieved same way podping does by any other centralized app? Is there anything that makes podping better? so before they were streaming rss feeds now they stream hive?
What's the benefit of using hive instead of just building API?
:)
RE: Podping & Podcasting 2.0: Funding to put Hive at the center of global Podcasting infrastructure