Skip to main content

Google Reader 总显示 "kept unread" 列表的问题 | Solution to the annoying "kept unread" list in Google Reader

不知道从什么时候开始我的Google Reader首页上总会显示一个kept unread列表，但是进去以后却是显示已读，此时点mark all as read或者挨个浏览这些item都没有任何效果。

今天在http://groups.google.com/group/google-reader-howdoi/browse_thread/thread/a68ae3f9a7761e26/11eb862ab44a67c3 找到了解法：

给每个kept unread的条目加星
去加星条目列表，挨个浏览每个条目（不要点mark all as read)
去掉这些条目的星

然后就正常了。 这个应该是Google Reader的bug吧。。。
There's been a "kept unread" list in my Google Reader home page for some time, and I didn't know why. In the list, each item seems be already ready, and clicking "mark all as read" or navigating each of them have no effect.

Today I found the solution on http://groups.google.com/group/google-reader-howdoi/browse_thread/thread/a68ae3f9a7761e26/11eb862ab44a67c3

Add start for each of them
In "starred items", navigate each of them (don't click "mark all as read")
Remove these temporary stars

Then that list would be gone. This must be a bug of Google Reader...
Labels:

Comments

Post a Comment

Popular posts from this blog

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 ...
Post a Comment
Read More »

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...
Post a Comment
Read More »

mkosi: First Impressions

I stumbled upon the Gentoo wiki page for systemd-nspawn , which in turn led me to nspawn.org , mkosi , and later systemd-sysupdate . mkosi quickly caught my eye because it's almost exactly what I wanted to build myself, as mentioned in a previous post . So, I decided to spend my "sysadmin fun quota" on it. Overview mkosi is similar to docker build or podman build , but it's designed for creating full OS images. It focuses on development and testing. For example, much like nix-shell , mkosi can quickly launch a sandboxed shell with a specific distribution and selected packages installed. The systemd project itself uses mkosi for testing across different distros. The re-introduction article  is a great read. Speed Note that this is by no means a rigid benchmark. My setup is an SSD with LUKS and an ext4 filesystem (without reflink support). Building Container Images mkosi is pretty fast. A simple mkosi command creates a fresh Debian image. I used the --incrementa...
Post a Comment
Read More »