整理了一下RSS和Podcast

之前Google Reader挂了之后我基本一直用Feedly，后来也开始用Google Now看新闻，用Google Podcast听Podcast。

这几天决定切换到自己的服务器上，有若干原因：

越来越不喜欢Google Now的自动推送。感觉我的眼界越来越窄。
Feedly经常遇到收费功能。
Google Podcast要关闭了。
我正好也有服务器了

RSS抓取用的Tiny Tiny RSS，这个之前就搭建好了，作为Feedly的备份。最近升级发现docker compose文件有若干变化，数据库版本也变了，稍微折腾了一下。

类似的还有几个

Miniflux
FreshRSS
NewBlur

不过这些其实都大同小异。主要Tiny Tiny RSS导入导出备份都挺方便。

手机端用的Feedme，直接支持Tiny Tiny RSS的API，也可以放Podcast

我的RSS源都很老了，有好多都没法用了，Feedly也不提示我。发现了两个不错的RSS网站

https://docs.rsshub.app/
https://feedx.net/

Podcast回头也得整理一下，不过目前问题不大。

Comments

Exploring Immutable Distros and Declarative Management

My current server setup, based on Debian Stable and Docker, has served me reliably for years. It's stable, familiar, and gets the job done. However, an intriguing article I revisited recently about Fedora CoreOS, rpm-ostree, and OSTree native containers sparked my curiosity and sent me down a rabbit hole exploring alternative approaches to system management. Could there be a better way? Core Goals & Requirements Before diving into new technologies, I wanted to define what "better" means for my use case: The base operating system must update automatically and reliably. Hosted services (applications) should be updatable either automatically or manually, depending on the service. Configuration and data files need to be easy to modify, and crucially, automatically tracked and backed up. Current Setup: Debian Stable + Docker My current infrastructure consists of several servers, all running Debian Stable. System Updates are andled automatically via unattended-upgrades. Se...

A Rocky Migration: Moving from docker-compose to Podman and gVisor

I've been running a few containers for several years. They were all running under rootless Docker with a single user. Initially, I planned to migrate the containers to VMs , but I couldn't get a stable workflow after about two months of effort. Later, gVisor caught my attention , and I decided to migrate to Podman with gVisor instead. The new plan is to run each container with --userns=auto and use Quadlet for systemd integration. This approach provides better isolation and makes writing firewall rules easier. I'm now close to migrating all my containers. Here are a couple of rough edges I'd like to share. Network Layout I compared various networking options and spent a few hours trying the one-interface-per-group approach before giving up. I settled on a single macvlan network and decided to use static IP addresses for my containers. To prevent a randomly assigned IP address from conflicting with a predefined one, I allocated a large IP range for my ...

Determine Perspective Lines With Off-page Vanishing Point

In perspective drawing, a vanishing point represents a group of parallel lines, in other words, a direction. For any point on the paper, if we want a line towards the same direction (in the 3d space), we simply draw a line through it and the vanishing point. But sometimes the vanishing point is too far away, such that it is outside the paper/canvas. In this example, we have a point P and two perspective lines L1 and L2. The vanishing point VP is naturally the intersection of L1 and L2. The task is to draw a line through P and VP, without having VP on the paper. I am aware of a few traditional solutions: 1. Use extra pieces of paper such that we can extend L1 and L2 until we see VP. 2. Draw everything in a smaller scale, such that we can see both P and VP on the paper. Draw the line and scale everything back. 3. Draw a perspective grid using the Brewer Method. #1 and #2 might be quite practical. #3 may not guarantee a solution, unless we can measure distances/p...

WangLu's Notes

Search This Blog