Skip to main content

Blogging: The 6th Year

It's been 6 years since the start of this blog, I still remember that soul-stirring accident which made me decide to start blogging.


Looking back, I see the quantity and length of the articles have been decreasing exponentially, but the quality have not (hopefully). I don't think it's bad, at least what I can see from it are:
  • My skills have been developed, usually it's not worthy to write a dedicated article showing  how I solved a problem
  • Technologies have evolved, there are much less problems left for me to encounter.
 Indeed things have changed:
  • Blogger has got a much cleaner new looking, and there's finally a "jump break" button such that my scripts can retire now.
  • Ubuntu has become much more stable and reliable, no more time-killing tweaking to make it work on my machine
  • Many things I liked are deprecated or about to: flock, python 2, Google Desktop, Google Notebook, variant Linux QQ
  • Quite a number of new things emerged, developed and have become very popular, which, however, I don't think I could enjoy in any chances: smart phones, microblog, wechat and Windows 8
I'm still that guy 6 year before who liked to learn and taste new technical stuffs, I'd rather read some C++ documentation for a whole day instead of struggling among "Another sad day"-like messages in SNS.

Just switched to a simpler and cleaner theme, should be the time for a change.

And to you the kind reader, if you know that I know you, and you happen to be writing a blog about tech stuffs, please send me the link (again), since I might have accidentally deleted them in 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 »

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

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