>>/9613/
been attacking lifelog for several minutes, now.