Tag: ttrss

How I listen to podcasts in 2018

Me listening to podcasts in madrid

I had quite a bit of time to read and listen to podcasts during my holiday in Portugal and Spain. One of the posts I read was Adrian talking about current his tech stack.

But I thought it might be good to talk about how I finally sorted out my podcast setup as it includes many parts of my current tech stack.

I listen to podcasts and audiobooks quite a lot. If I was still using last.fm I could likely quantify exactly how much but through my setup I’ll reveal a rough number at the end.

Listening devices

I listen to podcasts in the morning via Xbian running on Raspberry Pi 2 (considering switching to rasplex but Yaste remote supports Plex and Xbian as a audio endpoint/upnp renderer) which I bought a long while ago. This is setup in my room via ethernet and connected to a small amp and stereo speakers, one in my bedroom and one wired into the bathroom. I decided to do this after trying Bluetooth and FM speakers but they were just too quiet or unclear. Nothing beats a dedicated non-battery device. The wiring could do with a clean up. The Raspberry Pi is also connected to a audio splitter with one going to a FM transmitter.

This broadcasts to my little micro-hifi in the kitchen which I got from ebay over 10 years ago; its handy for multi-room synced audio without messing around (although I considered using a Chromecast audio and other things). The small amp in my room is connected to a TpLink HS100 smart switch meaning I can turn it off when leaving easily and quickly. I have only set it up for local wifi access not remote access, because frankly why would I need to this?

When not at home I use Google Pixel 2, I decided to get the 128gig version because I had enough of dealing with space issues. I have plex client installed and I have a plex pass (life time subscription), so can sync podcasts and audiobooks with ease. I do have it on my Nexus 7 and 5x too, but don’t carry them around much. I find Plex client is pretty good and doesn’t eat too much battery. Syncing seems seamless but with offline support sync support and 12gig of mobile 4G data. Because its using Plex at the backend, plex will save position no matter what device, as I’m logged in using the same account.

I also have Chrome Plex client on my laptop, meaning I can keep on listening when at work. Yes I listen to podcasts and audiobooks while working. I know many find this unthinkable but it works for me.

Plex Media Server

I’ve had Plex mediaserver running for quite a long time now and the advantages of having a gigabit internet connection and decent vpn (zerotier) means I can stream, sync or download podcasts and audiobooks without any fuss to my own devices. Plex media server keeps the position and checks for updates to the server filesystem.
Plex indexes the podcasts and audiobooks as audio and with some tweaking works quite well, although it can get confused when podcasts numbering and dates. It would be great if it had a audiobook and podcast indexer to pull much more metadata.

Podcatching

Unfortunately Plex media server doesn’t actually support podcasts which would be great if it did but its a pain to get working and not worth it for me. Especially because I have a complete Ubuntu stack its running on.
Because of this I use to download the podcasts from the web using a native ubuntu app. I tried Gpodder and Rhythmbox but they were resource hungry when downloading 30+ podcasts. Then tried VLC but it seemed over kill just to download podcasts. So tried some command line programs including Podfox and podcatcher. In the end I used Podget then setup a cron to trigger it every 2-4 hours. I also have Podget clean up the podcasts every 3 months.

One of the biggest things which drove me nuts was adding and updating rss feeds. Someone says you listen to the guilty feminist podcast, and would have to update server configs, etc. But using my Tiny tiny RSS install, I now have all the podcasts added to the master subscription list and generate a custom RSS feed aggregated for podcasts. I add the generated feed to Podget and the next time its updated, it will automatically add new items.

Because its done via TTRSS, it means I can add & remove the feed via any TTRSS client including the one my phone or using the web interface via my VPN (I only expose the web interface that way).

Small pieces loosely joined

It sounds like a lot of work but honestly it works well and means I can remove a part of it and it will still work. Remove Podget, could be replaced with anything including VLC, etc. Plex could be replaced with Emby or another mediaserver. TTRSS could be anything self-hosted. Using Plexpy to log is under my own terms and the data is only shared and useable by me.

I do wish I could get to this type of space with so much more of the services I use. Right now, I’m quite impressed with how smooth everything works.

Looking forward

I’m looking at a way to tag and generate a feed out of the tags in TTRSS, instead of adding it to a hierarchy. Sometimes a feed could fit between two or more places. I’d also like to improve plex’s indexing around podcasts and audiobooks. Podget generates a m3u playlist file but not found much use for these yet. I also wish the plex input for kodi was less heavy.

I just added the Recode podcast while writing this post and I looking at my plex client on my Pixel 2. Podget downloaded all the episodes over my gigabit connection in about 6mins flat, the podget won’t remove them till a few months old but I can easily remove them via plex or directly from the file system over the VPN.

As promised, looking at Tautulli (what use to be PlexPy). Over the last 3 weeks I had 83 plays or 22 hrs 14 mins of playback.  The last podcast I listened to while on the Madrid Metro to the airport at 7:30am was Rob Reid’s Always on podcast – Episode 23: Rodney Brooks | Robotics & AI – Their Present & Future

Not enough detail?

If you are interested in any detail, just comment or tweet me for more info.

 

Docker & Tiny Tiny RSS sorted finally

TTRSS Php error

I have had on my task list for a long time to fix two problems with my Tiny Tiny RSS setup.

  1. Fix the problem I’m having connecting to TTRSS in a browser since a upgrade
  2. Sort out a decent RSS reader for Ubuntu

Originally it was working fine then a upgrade broke the web interface for me and many others. The confusing and joyful thing for me, was any application which talked to the API was unaffected. Meaning my Android clients were fine including the one on my eink tablet. However all the RSS clients on Ubuntu would either not connect to ttrss, were generally rubbish or wouldn’t work in later versions of Ubuntu (like RSS Owl). The advice seemed to point to using a browser extention.

The first problem was something to do with the PHP which seemed pretty easy to fix but all the solutions assumed you were running it all on a standard webserver and had control over everything. Of course I was running it within Docker and had no idea where config.php was or even where docker had installed anything.

After actually sitting down and looking around my server as a sudo not myself (its the first time I actually dedicated time to do), I found the Docker install and learned what docker was actually doing. My ttrss docker image is actually located under /var/lib/docker/aufs/mnt/{random hash}/var/www/ttrss/.

Under that I could find the config.php file and make changes so it was only accessible over my Vpn connection – yeah, I thought this was very clever but maybe obvious to everyone else. So the only way to hit the web front end of my ttrss install is via my Vpn but API calls are done without the Vpn.

As I found the root of ttrss, I was also able to finally install feedreader which is hightly rated by many. The problem I’ve always had is feedreader complained that it needed a certain plugin installed under ttrss’s plugin directory, which previously I couldn’t find to install. Of course now I know where it is and could copy it there, I was very pleased with myself. Next stop brunch at Ezra & Gil and wait for Feedreader to pull down full text for 8500+ items.

https://twitter.com/cubicgarden/status/929712805053435904

Tiny tiny RSS experience a week later?

I have had quite a bit of feedback from my post about moving away from Feedly to a self hosted solution called Tiny Tiny RSS.

Some interesting questions have emerged from people and to be fair it certainly deserves a follow up.

I made my instance of TT-RSS available on the public netw, because I didn’t see the point of installing my VPN software on my eink reader. I also installed the official TT-RSS app which is a 7 day trail before you buy the full version for 4 pounds. I haven’t bought the full version yet because the app doesn’t seem to work well when offline? It would be great if the app understood if the device was offline and automaticilly disabled the update feeds option. It currently doesn’t seem to do this well… I much prefer Greader for this, but ttrss app isn’t far behind.

Simon commented he paid for Feedly because of the IFTTT options, but it seems weird to pay for this  because you can easily turn most of TT-RSS into a another feed and IFTTT has a RSS option which you can use to trigger most things. This reminds me of my work along while back about pipelines.

Because of this, I have been thinking about feeding Greader with the RSS from my TTRSS install. The only real disadvantage is nothing would be synced to the server? This is also something I’ve been thinking about with a linux desktop reader like thunderbird because I can’t seem to install a TTRSS reader which works.

I tried a few but each has had problems.

Feed the Moneky looked very promising but when I finally get the appimage loaded, it shows nothing? Feedreader looked great and after finally getting flatpak working, I’m faced with the error that I need to install the api-feedreader plugin in my TTRSS server. How I do this when I’m using docker is a question I have no answer for, except it seems I need to use another docker container?

So generally its going well but hitting a few points which need straighing out. It would be so useful to compile supported applications into a wiki page.

Oh I found this useful when understanding about appimages, snap, flatpak, etc.

Host your own RSS aggregator?

hosting Tiny Tiny RSS

It started with me getting fed up with Feedly trying to up-sell me to their premium subscription. I mean I get it but $5/month to host a simple RSS aggregator? This seems quite a hefty price (even with all the extras it provides, which I never really use).

So I first looked for alternatives to Feedly and found quite a lot. The main thing for me was having a Sync API, so I’m not reading the same stuff across my different devices. My thought was with a standard API, it wouldn’t matter what client or platform I use (although I’m using Linux and Android mainly). Standard I thought… boy was I dreaming.

After a lot of looking and reading I said screw this, I’m self hosting my own copy of tiny tiny rss, which seems very popular with people like myself trying to do the same thing. It seemed quite straight forward and I decided it was time to give rkt or docker a try as there was a docker image for it.

In a evening I had it setup, running and working with my exported feedly OPML file, while watching a film and cooking. Its currently only available to my network but I’ll likely make it externally available (without my VPN) once I got it setup with a SSL cert and 2 factor auth. I did notice my fav RSS reader on Android did support ttrss then somewhere along the line they pulled support for it. So I’ll try out the android app created by the author of ttrss, but the comments are… well.. interesting?