Podcasts are often distributed as 128 kbps mp3 or thereabouts. You should also download your favorite Youtube videos and forum threads, too, but let's save that for another article. Not to mention, as with any other material on the Internet, every day that passes is a day your favorite show might disappear for any number of reasons. The point is that being corralled into Spotify is bad, and the same would apply to any other exclusive distribution point no matter how technically good it is. You can ignore the "oh, but Spotify's not that bad" crowd, because that's not the point. Any other messaging that depicts Spotify-exclusivity in a positive light is pure spin and marketing, as the deal invariably removes control and choice from the listener. The only situation in which this can possibly be interpreted as a benefit for the listener is when the exclusivity deal literally saves the podcast from going bust, and even this has caveats. This is because Spotify wants to pump up their subscriber counts and is offering cash incentives to podcasters for exclusivity. Over the past year or two, more and more podcasts have been moving to Spotify and pulling their material from their other outlets. I see there is a new SQLite release today.Stable release 3.16.Back to writing Download your podcasts (§) My feeds.DB is still at 390 Mbytes, for 140 RSS feed sources. Look into QuiteRSS\data\settings and copy the INI and DB files OUT to new, meaningful names when QuiteRss is off. Somehow I think that such precautions should be spelled out on initial installation of new versions. I found a November FEEDS.db in a back up disk for late November, my only other non-corrupted DB file other than one which had been copied to QuiteRSS-,db so I didn't lose more than a month of back feeds. Test all files such as feeds.db by Copying QuiteRSS-.db to FEEDS.db every so often, (FIRST having backed up the FEEDS.db.) Saving As Name-year-month-day.suffixextension allows a quick sort of the collection of filss in the QuiteRSS directories and the back up dirrectories. Save QuiteRSS.ini, a 300 line settings list to QuiteRSS-.ini about the same schedule as the Feeds.OPLM pages With QuiteRSS off, copy Feeds.db to QuiteRSS-.db and so on, every week, or every two weeks So, save "Feeds" which is Copy the feed addresses (OPML) to "QuiterSS-YEAR-Month-Day.OPML every week or two,(or less often if they don't get added to or subtracted from very much). "I would recommend to backup the files feeds.db and QuiteRSS.ini on a regular base in the future." Be aware that if the db is corrupted you may export corrupted data. You can use the db browser for an export as well but I would not recommend this way. The standard way to export data from a SQLite db is a dump command from the comman line using sqlite3,exe. I don't know if you are familiar with SQL. You are right! The feed export and import only handle the subscriptions in an OPML file. An example:ġ000 records in QuiteRSS should lead to a db size of around 1 MB. If the number of records deplayed in QuiteRSS nearly meets the db size in KB then the db is fine. The physical deletion is handled by the clean-up.įrom my experience the following rough estimation fits quite well. They are not physically deleted from the db, So they are still in the db. The reason why your db is that big is that f, e, deleting duplicates means that those records are marked as deleted. If you additionally configure QuiteRSS to store the db in the memory a big db may slow down QuiteRSS. But the more records you hold in the db the more the SQL queries get slowed down. First of all there is no other db size limit.than the record limit set by SQLite that you will never reach.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |