A solar-powered, self-hosted version of Low-Tech Magazine
solar.lowtechmagazine.com
solar.lowtechmagazine.com
For my small solar powered installations I generally use a lead acid battery with a zero embodied energy cost. When I pull a starter battery out of a vehicle, instead of immediately recycling it I use it as a storage battery for one of my remote solar installations, sometimes adding it in parallel to an existing one. They can then perform for years as a bad, but useful, low current storage battery. Eventually something horrific¹ happens or a cell goes completely² and I recycle the battery.
So the lead and the sulphur spend a few years longer between reincarnations as batteries, but the embodied energy is zero for my use.
␄
¹ A camera/weather sensor station went offline after an unusually strong storm from the south. I suspect there was unprecedented wave erosion and dropped it off the embankment. When the site becomes accessible again I'll probably find it in a heap at the shoreline with ruined batteries from freezing. (Sometimes I lose the sulphur, but there is a world sulphur glut so I don't feel too bad.) Other causes of demise are failed solar chargers or stuck on loads, usually from wiring failures. (darned rodents)
² I'd like to make a lead acid charge controller which can detect a shorted cell and just call it a 10V battery instead of a loss, that would extend their lives. There is DC/DC conversion already happening at charge and discharge, so it shouldn't hurt efficiency significantly.
Although I gotta say, I think the criticism of 100% uptime is an ideological position, letting the perfect be the enemy of the good. In this case having their website always up would give it wider reach, and presumably convince more people to reduce their energy usage, which is the goal. But I can appreciate those who practice what they preach.
If the authors are here, you can further optimize your page.
For images I was able to reduce image-weight by 494 bytes, using lossless optimization, with optipng.
For the html, using zopfli to compress the page, I squeezed out another 3020 bytes. And although I didn't fix it up, the html code includes unnecessary remnants from pre-html5 like closing P tags, lots of end slashes, etc. I'd bet you could save a few KB (before compression) by removing it.
In all these are over 3514 bytes you don't need to read from disk, cache, encrypt, and send over the network using your 1-2.5W webserver.
For cryptography, you can save some cycles using ECDSA instead of RSA, and prioritizing aes-128-gcm over aes-256-gcm. And what about ChaCha? To me it seems logically inconsistent to spend extra cycles protecting this read-only low-energy site powered exclusively by solar. 128-bits are enough; in practice you only need to worry about side channels, not key length.
Just as an aside, on the topic of webpage optimization, here are some of my favorite tools: zopfli, pngquant, optipng, jhead, cwebp.
And here are some excellent resources:
* https://webpagetest.org/
* https://webspeedtest.cloudinary.com/
* https://developers.google.com/speed/pagespeed/insights/
Then when you're done, check for html errors with * https://html5.validator.nu/
* https://validator.w3.org/The web site is a mirror of a conventionally-hosted web site: https://www.lowtechmagazine.com/
I see a lot of links to https://www.lowtechmagazine.com/ on hacker news, and there's always a link in the corner of the screen to the solar server.
(I did try to search but the query is tricky => I keep finding websites targeted at Amiga & C64 & similar stuff, but nothing about a "demo about the website itself"...)
This point has nothing to do with energy use (or very, very little) but is a really great graphic design tip for those looking to make a site more pleasant to browse.
The other weight that's not being used in favor of regular is "bold". Instead of bolding, the font size attribute is changed to establish hierarchy. Faux small caps are also used.
From the CSS:
h1, h2, h3, h4, h5, h6 { font-weight: normal; }
Maybe people enjoy aesthetics other than minimalist? Maybe some people enjoy complex things?
I hope we can agree that adding unnecessary complexity to software is bad, and that simplicity should be something to strive for.
Am not saying graphic design is nearly as (inherently) complex as computer engineering, but neither benefits from complicating things that don't need to be complicated.
You provide a good example with your reference manual. The diagrams will be clear, the fonts readable, they wont have jazzy designs etc etc etc.
The original is 160KB. When I save it in GIMP, the re-encoding (at 90% quality be default) brings me to a baseline value of 164KB. If I turn the quality down to 50%, it appears to be almost identical but is only 72KB, less than half the size. Turning it down further until I can only barely make out more detail than in the dithered image (for example, I can see that the operator on the bottom left is looking at something, whereas in the dithered image I originally thought her face was a headphone and she was facing away from the camera), and at 7% the limit is finally reached. At 6%, the quality is no longer better than the dithered image. So at 7%, what's the size? 20.9KB, much less than the dithered image that is claimed to be 36.5KB.
I'm not sure why I double checked, but I did. You know what? The dithered image is not 36.5KB as the article claims, but a 76KB PNG. Which is impressive because with PNG, I can't get it below 140KB in GIMP. JPG and GIF also can't reduce it beyond 76KB. Their PNG encoder is much better than GIMP's, but I don't know where the 36.5KB claim comes from. What I do know is that JPG can get it to 72KB with virtually no quality loss, or 21KB at a quality still slightly higher than the dithered version. All you have to do is change the quality setting, an option available in almost every editor (no fancy tools or skills needed).
Dithering seems to be just chosen for its 1950s look, not for actual power saving.
And to throw one final nail in the coffin, if they used a modern, but reasonably mature codec like VP8, they could have done even better on resource usage while retaining the same quality.
If you want to build something to demonstrate that using older technology has advantages, that's fine. But you should make sure that you're actually demonstrating what you intended. And I'd pick something other than energy efficiency to target, because the last decade has seen a ton of technological progress improving energy efficiency because of its importance to mobile devices running on tiny batteries.
Incorrect, it is 36.5K:
$ wget https://homebrewserver.club/images/international-switchboard3.png
--2019-03-16 12:41:11-- https://homebrewserver.club/images/international-switchboard3.png
Resolving homebrewserver.club (homebrewserver.club)... 87.214.157.230
Connecting to homebrewserver.club (homebrewserver.club)|87.214.157.230|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 37359 (36K) [image/png]
Saving to: ‘international-switchboard3.png’
international-switc 100%[===================>] 36.48K 26.4KB/s in 1.4s
2019-03-16 12:41:14 (26.4 KB/s) - ‘international-switchboard3.png’ saved [37359/37359]
When you tried reproducing the results using GIMP, were you creating similarly constrained indexed-color/paletted images?You likely won't get the same compression levels with rgb pixels, you can use `pnginfo` to compare the file properties:
$ pnginfo international-switchboard3.png
international-switchboard3.png...
Image Width: 800 Image Length: 655
Bitdepth (Bits/Sample): 2
Channels (Samples/Pixel): 1
Pixel depth (Pixel Depth): 2
Colour Type (Photometric Interpretation): PALETTED COLOUR (4 colours, 0 transparent)
Image filter: Single row per byte filter
Interlacing: No interlacing
Compression Scheme: Deflate method 8, 32k window
Resolution: -547765670, 22093 (Unknown value for unit stored)
FillOrder: msb-to-lsb
Byte Order: Network (Big Endian)
Number of text strings: 0(I'm not at my computer anymore so I can't check what you suggested right now.)
https://ieeexplore.ieee.org/document/7168333
which found JPEG decoding to be much less energy intensive than PNG decoding, mostly because it's faster. Note that that's not just a function of file size, as lower quality JPEGs actually took more energy to decode.
Which all makes a lot of sense when you consider how much work has gone into optimizing frequency domain based compression and decompression.
https://www.lowtechmagazine.com/
And likewise contains some amazing content.
Designers just don't know what to do with the extra space.
Reading any news article at a browser width of greater than 720px is a disaster. We've forgotten how to design for the desktop.
I've been starting to build my own systems based upon the Raspberry Pi 2/3 and the ODROID-C2, and currently use the ODROID as an ultra-low-power server. Most of my documentation and configuration so far has been in a private repo, but with this much interest I made it public[2] in hopes that others would be willing to issue PRs and work on it with me. If you're interested in this type of optimization definitely contact me, I'd love to work on this stuff more with environmentally-interested people.
That's not a complete statement unless you also include the energy use associated with the paper processing that no longer happens, along with controlling for the massive increase in the number of people with access to computation. If all communication that presently happens over the internet was to be redirected to other forms energy use would probably not change that much, after all the telecoms put it all on the same backbone anyways.
I wish. I've yet to see an actual paperless office. And paperless bills have just been replaced by the marketing they send you instead.
Unless you're talking about newspapers, you may have a point there.
As for the marketing, you can refuse that use of your data, at least if you live under the aegis of the GDPR.
> How often will it be off-line?
> When is the best time to visit?
I'd use a Service Worker [1] to go offline-first. Host and serve content that goes offline automatically unless you edit it too often.
Anyway, interesting extreme project.
[1] https://developer.mozilla.org/en-US/docs/Web/API/Service_Wor...
Did they share the article sources too? I didn't see the article markdown/rest file in their lowtechmag github account.
Also, it'd be cool to share a torrent of the sources for when people's access to github goes down. There's so much you can do when you have software like pelican installed, if you have a site's theme, content, and config files.
I personally found the "email to comment" charming.
It's also more readable than whatever this is.
Is there a _cheap_ way to add solar to very low power boards?
Running the Qualsys SSL server test against the site does appear to raise the 15 minute load average several points, though it's hard to say if it's just it being on HN doing that by itself.
I assume it would have to be pretty cloudy to affect the charge level.
Regardless, I must say I love the “offline is ok”, “slow computing” (ala slow food), “get off my lawn”, “sustainable beats schfnacy” attitude. Nice one!
Humanity uses more kWh -equivalent of energy in 1 seconds of an airline flight than everyone who ever has, or ever will use viewing this website. Shit, just takeoff is something like an equivalent 90 MW or so worth of electricity: https://aviation.stackexchange.com/questions/19569/how-many-...
I think society would be better served by engineers learning and working on new technologies to extract and use energy, instead of pushing bits around on a website. Why not get a degree in Nuclear Engineering, or Oil and Gas Engineering? It would certainly benefit society more than this.