I did all of that on an M1 MacBook Air and now on a M2 without any problems whatsoever. Only caveat the Airs have is that you can't attach more than one external screen without some workarounds[1]. If you don't rely on that the machine should be more than capable of what you're looking for!
Here you can find a podcast interview with Internet Hall-of-famer Daniel Karrenberg[1] about RIPE and the ATLAS project (don't worry the page being in german, the interview is in english language): https://requestforcomments.de/archives/280
Based on the extensive user agent library of Piwik (https://piwik.org/) DeviceDetector is currently the fastest user agent parser and device detector in Rubyland (benchmarks are in the readme).
We built it for the statistics feature of Podigee, our little podcast hosting platform.
First, it's actually not that simple :) We tried out like a whole lot of podcast clients (30+ I think) and 'are recognized by most podcasting clients' is certainly not true. That's why we recommend the following to client developers: If your OS allows it subscribe to the OS default (which is often pcast://) but also define your own schema (like mypodcastclient://). This allows us to have a 'Open device default app' link that on Android shows all installed clients that subscribe to pcast://, but also to specifically start a client with its schema.
Second, 'It also doesn't get any easier than just offering the naked RSS feed.' is also not true. We talked to a lot of people and subscribing to a podcast is a nightmare for people that don't get (and don't want to get) the concept of what an RSS feed is. And copying and pasting links from a webpage to an application is already an obfuscation (and a real pain in the ass on a mobile device) for the 'normal' user, so why not add a more user friendly obfuscation :)
However, the button is an experiment and we'll see if and how people will use it. Until now the feedback from podcasters and listeners is nothing but positive.
I think another big factor in podcasts getting more popular these days is that the content and quality of podcasts are getting better. Today you don't need equipment and staff only radio stations can afford to produce high quality good sounding content. A computer with an USB mic and Audacity together with a tool like Auphonic [1] are enough to get good sound. The internet makes it easier to research stuff and prepare content collaboratively without being in the same room.
Because we strongly believe that there is a bright future for podcasting a friend and I started Podigee [2]. Our aim is to make publishing a podcast easier and faster so beginners can get an easy start and more experienced podcasters can focus on producing high quality content without worrying about publishing software and infrastructure.
Additionally we support a movement that was started here in Germany called Podlove [3]. They provide open source software like a Wordpress plugin for publishing podcasts and a web player which is currently completely revised (and will be pretty awesome after that). Besides that they also try to establish new standards and promote old ones that are not widely used (like paged feeds). Currently we (I do most of the coding) are working on a new kind of subscribe button [4] which will make subscribing a podcast a lot easier for listeners. We have a lot of podcast client developers on board to support subscribing through the button and we have high hopes that this will push podcasting even further. The button will see an official release in the coming weeks.
I was looking for something like this some time ago to integrate a form into a static website. Ended up building a less user friendly version of this. Really nicely done, I think I will use it if I ever need something like this again.
What they claim to do is basically what everybody is already doing. SSL between email servers can be considered standard, as well as SSL or at least StartTLS between client and server.
De-Mail is another thing which was introduced some years ago now. In short: Messages are encrypted on the client side, then decrypted on the server, then again encrypted and sent to the recipient where it is decrypted again...Imagine your post-office opening you mail before forwarding it to the recipient.
Along with some other things no sane person would ever suggest to do with email, De-Mail is a complete farce...
TL;DR: I'm from Germany, and my opinion is that this is the most brutal kind of PR bullshit you can get...