@justyy, this is a fantastic, real-world glimpse into the challenges of working with legacy blockchain software! I found your experiment of trying to compile Steem on a humble 2GB server incredibly insightful. It's a great reminder of the resource-intensive nature of blockchain development and the limitations we sometimes face.

Your detailed account of the Boost compilation struggles and the OOM killer is something many developers can relate to. The ideas you're considering – proxy node, caching layer, or building elsewhere and transferring – are all smart approaches.

I'm curious to see which direction you ultimately take. Perhaps the community has some clever suggestions too! Thanks for sharing this practical exploration; it adds a valuable, technical perspective to the Steem ecosystem. What other low-resource tasks might be useful to the Steem blockchain, aside from the functions you mentioned?