There’s a pretty cool write up by KittenLabs about their SolarCamPi project - it’s pretty involved as far as DIY projects though, even down to stripping features out of the Raspberry Pi so it would use as little power as possible..

Awhile back I dabbled with a timelapse setup where I had a battery, GoPro and a Raspberry Pi with a 4G hat for remote monitoring - using Tailscale as the VPN - but that was never intended to run 24/7. I just set those up and accepted that they’d run for as long as they ran and then collect them.

Lots of 4G/WiFi solar security cameras around as another sort of ‘all in one’ solution - typically the main issue is they all want you to use their app. If you can find one with rtsp or ONVIF it’s easier to make them work with whatever you want, though again you’d probably need a Raspberry Pi or something inbetween in order to create the VPN/Tailscale/WireGuard connection to keep it secure.

My little brain broke when I started trying to figure out how big the number was… thanks for breaking it down even more intuitively, yeah it is way to large to have been correct!

I think they’re winding down the project unfortunately, so I might have to get with the times…

It’s a mix, I put two screenshots together. On the left is my monthly bandwidth usage from CPanel on the right is Awstats (though I hid some sections so the Robots/Spiders section was closer to the top).

It’s super weird for sure. I’m not sure how the bots have managed to use so much more bandwidth with only 30k more hits than regular traffic, I guess they probably don’t rely on any caching and fetch each page from scratch?

Still going through my stats, but it doesn’t look like I’ve gotten much traffic via any API endpoint (running WordPress). I had a few wallpapers available for download and it looks like for whatever reason the bots have latched onto those.

12,000 visits, with 181 of those to the robots.txt file makes way, way more sense. The ‘Not viewed traffic’ adds up to 136,957 too - so I should have figured it out sooner.

I couldn’t wrap my head around how large the number was and how many visits that would actually entail to reach that number in 25 days. Turns out that would be roughly 5.64 quinquinquagintillion visits per nanosecond. Call it a hunch, but I suspect my server might not handle that.

Phew, so I’m a dumbass and not reading it right. I wonder how they’ve managed to use 3MB per visit?

I would like to do this but I’d really want to be able to bypass the battery. Being an older phone, I don’t think it has the feature where it cleverly stops charging the battery and I wouldn’t want to leave it plugged in all the time.