I've mentioned before: nostr:nprofile1qythwumn8ghj7mn0wd68ytnsv9ex2ar09e6x7amwqyvhwumn8ghj7mn0wd68ycmgv43kktndv5hhyetvv9usqgzn9kpsmllqnsf7wh5tz3wgy4cclsftqqplv8tpayrhwgw8llunevk4p6dz in Chromium is regularly ramping up to consume 40%+ of a beefy processor following the streaming update. Is it just me?