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...

Comments

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 ...

GameConqueror 0.09 -- Linux Game Hacking Tool

If you are a game hacker If you've been looking for a `CheatEngine for Linux` Then you can't miss this. ============================================== GameConqueror is a game hacking tool for linux, it's written in PyGTK and uses scanmem as its backend. It's supposed to be with most useful features of CheatEngine for Linux. Currently, I've implemented almost everything about scanning, involving variant data types and scan types: Data Types: int{8/16/32/64}, float{32/64}, unknown type(int or float) and unknown width(will try each of them), byte array and string Scan Types: equal, greater, less, changed, unchanged, increased(by), decreased(by) This should be enough for most cases, so I decided to release it at the current status. ============================================= Here's how you can get it PPA (for Ubuntu users) https://launchpad.net/~coolwanglu/+archive/scanmem (I've not test it in 32bit environments or Jaunty, do please inform me if it doe...

Fix Google Security Code

Google Security Code (http://g.co/sc) is one type of 2-step verification. This is particularly useful when security keys and passkeys are not available. I have been using it in my LXC containers, until today I found out that it stopped working. It just kept saying "The code is invalid". It is easy to rule out some factors: The code works on other browsers on my laptop. The code works on other devices that are directly connected to the router. So it appears that Google also checks IP addresses besides the security code. Recently I have IPv6 enabled, so most devices that are directly connected to the router have both IPv4 and IPv6 addresses. But I only enabled IPv4 for my LXC containers. So I guess when a code is generated by device A and used by device B, Google should be able to check that device A and device B are closely located. But in my case, IPv6 address appears on device A but not on device B, which may look suspicious. To fix the problem, I just needed to disable IPv...

WangLu's Notes

Search This Blog