Here ya go:
http://pca.st/hYck

cc @ming13

🚀

Show notes https://github.com/artem-zinnatullin/TheContext-Podcast/blob/master/show_notes/Episode_2.md

In the rss feed, the tag only contains a brife description of what's the episode like. But it's much more convenient to put show notes inside the tag, so I can open those links while I am listening to the podcast. Just like Fragmented Podcast.

Pocketcast always gives handshake failed error, when I try to download episodes.

For better discoverability and a way to listen to episodes we could discuss to setup a very simple github page (maybe automatically generated by travis ci after having released a new episode) that basically displays episode shownodes with an html5 audio player

<audio src="path/to/episode.mp3" controls ></audio>

So basically the same as (or a replacement for) the README file in this repo, just as github page to enable html for audio playback.

What do you think?

Feel free to suggest new themes, please use GitHub emoji reactions to vote.

Show notes.

Currently feed.rss only mentions me as an owner

Which results in podcast players rendering only my name in the podcast description, we should update it and add Hannes and Artur there as well 🐱

First off: I'm loving the podcast! Thanks for doing it.

I notice the file sizes for the episodes are a lot larger than they need to be. An hour of conversation doesn't need to be 60 megs.

I think 128 kBit/s bitrate is enough for voice recording like a podcast. This will also save some bandwidth for both, our server and listeners.

I.e. episode 10 is 103 Mb with 128 kBit/s .... With 128 kBit/s would be something between 60 - 75 MB.
Not sure if we should reupload Episode 10 but at least in the future we should consider using lower .bitrate.

What do you think?

As we’ve discussed this internally multiple times — we want to move the repository from artem-zinnatullin/TheContext-Podcast to TheContext/TheContext.github.io. The main motivation behind this change is to make the podcast more abstract from individuals and be more like a community or a country (which reminds me, we should make our own flag and currency...)

There is a single hardcoded dependency we should account for — feed.rss. It is used via direct URL by podcast players and services as https://raw.githubusercontent.com/artem-zinnatullin/TheContext-Podcast/master/feed.rss. Moving it without losing subscribers requires providing HTTP 301 redirect and including a new tag (<itunes:new-feed-url>) in the RSS feed. Fortunately enough GitHub provides redirects on repository transfers. That means that

https://raw.githubusercontent.com/artem-zinnatullin/TheContext-Podcast/master/feed.rss

will be redirected to

https://raw.githubusercontent.com/TheContext/TheContext.github.io/master/feed.rss

Seems like it should work everywhere but it isn’t. Changes needs to be done via contacting support services and changing URLs in admin interfaces. Since I don’t have access to these accounts I cannot make it on my own.

• iTunes (@artem-zinnatullin) — will pick up redirects, but iTunes Connect change is also required.
• Google Play (@artem-zinnatullin) — support service intervention is required.
• Spotify (@sockeqwe) — support service intervention is required.
• Pocket Casts — will pick up redirects.

As far as I can see from analytics the majority of download hits is from AppleCoreMedia (iOS and Mac, i. e. iTunes), Pocket Casts and Chrome (for some reason).

What I propose to do:

1. Change the feed to contain the necessary tag.
2. Immediately move the repository.
3. Update services or request updates depending on a service.

One more thing. There is a destructive action regarding the website — it will broken for some time, but it is a second-priority issue.

We should reupload the old episodes on new domain because:

• Old Episodes can't play on all players (i.e. iTunes) because of github streaming issue
• No tracking

We have to update rss feed. Could this cause any issue if we change existing rss feed to update mp3 url?

Currently we don't have any CI for the project, but we should since we do everything through GitHub PRs.

As a first CI step we can add rss feed xml validation as suggested here #61 (comment)

Seems like Spotify opened tge door for everyone to publish podcast on spitify https://podcasters.spotify.com

What do you think? We already published on google play music and Spotify seems to publish a standalone app for android wear soon (November) which I would love to use for listening to podcast while jogging ;)

It'll be an episode mostly about RxJava and other Reactive things.

Guest is @akarnokd, one of the core developers of RxJava! David is most active developer of RxJava for last ~8 month (or more), also, he started development of RxJava 2 and works on some other Reactive libraries.

It'll be something like QA session, almost everything you wanted to know about RxJava can be discussed in this episode, so please submit questions: RxJava APIs, implementation details, performance, memory consumption, v2, other Reactive technologies, etc, etc

Current list of questions (order may be changed):

• Little bit about your background
• How you were involved into RxJava development?
• Schedulers.computation() is bottleneck? Threads count == cpu cores count and this scheduler is default for all time related operators…
• Do you think that including Schedulers implementations into the library was good idea?
• What is Reactive Streams?
• What is JDK 9 Flow API? Were you involved into its development?
• What is the future of RxJava from your point of view (enemies or friends with Flow API)?
• If you'll be able to change some things in RxJava v1, what would you change?
• What's the in depth and technical difference between subscribeOn() and observeOn()? How does calling them in different orders or even multiple times with different Schedulers affect the Observable?
• What is your opinion about Single? (and Completable)
• How to test asynchronous code that includes Observables with jUnit? How to use TestSubscriber?

Please submit your questions! (just check that there is no such question in the list above first)

UPD from @akarnokd:

My only request is to ask questions that you think can be answered without the need to write code verbally. If you have such questions, please consider asking it on StackOverflow. There is a high chance, depending on the complexity, that I'll answer it there too, and you may not need to wait till the podcast goes out.

Since pocket cast is a paid app, I'd love it if you guys added this podcast to play music!

Episode was divided into two parts, second part will be released in a few days after first.

Discussion before episode.
Show notes for Part 1.

cc @yole people may ask you some questions regarding things we've discussed :)

cc @Bodo1981

When I listen to podcasts I can use the same volume for all my podcasts except this one, where I have to almost max out the volume to hear properly. To be clear, this is more related to convenience for me as opposed to an "actual" problem. Would be happy to see it addressed though.

I use pocket casts with the volume boost feature.

// I'll be on vacation (first ****** time in my life, yay!) soon so I'm assigning discussion to you guys @sockeqwe @android10, deal with it

Build systems ... yay ...

Yay! Feedback is really appreciated 😸

Main planned theme is Testing (yay).

Feel free to suggest themes or questions to discuss or just ideas to improve the podcast. You can also suggest kind of "news" but not sure I want to make a news show, so, yeah 🐱

Please notice that we can't record 3 hours episodes so some of the suggested themes may be discussed in next episodes.

Thanks!

It should be as easy as going to https://play.google.com/music/podcasts/publish and entering your RSS feed.

Yo there, great episode, bad sound (@artem-zinnatullin bad as always lol), enjoy!

currently getting a "handshake failed" error.

It'd be nice if README's would be sorted by numbers.

Episode_001.md
Episode_002.md
Episode_010.md
Episode_099.md
Episode_100.md
Episode_999.md

Should we do it or not? cc @sockeqwe and listeners

Slack is the best chat I've used in like 15n years and it opens direct way to communicate with hosts and other listeners regarding and not regarding to the podcast.