4 ms·

is part of the manifesto "host your own server for static content"?

bawolff 2y ago
To quote: "Solarpunk is about youth maker culture, local solutions, local energy grids, ways of creating autonomous functioning systems. It is about loving the world." So, yes actually, it does seem like that would fit in their manifesto. As an aside, if it was actually static - just apache serving a .html file on a server somewhere, i suspect it would still be up :)
- boopdewoop 2y ago
  Yeah they should probably learn to code.. I mean using a WYSIWYG to make this page is just messy. its using WordPress, Its more than just this page however so I can understand why. but host it on a git repo MD file. easier to allow Pull requests and edits.
- zzo38computer 2y ago
  This file has many JavaScripts and CSS and other stuff more than will be needed (the copy from web.archive.org adds more, but you can add "id_" after the numbers to avoid them). Even just a plain text file would do. HTML and HTTP are probably more complicated than will be needed, too (although you can still use HTTP as an alternative service if you want to do). TLS also adds more complexity and uses up more power, too. There is simpler protocols (probably the "nex:" is simplest kind of "small web" protocols), simpler file formats, simpler ways to use existing file formats, and more efficient server software, available, too. I had also invented "hashed:" URI scheme (which is documented together with the specifiction of Scorpion protocol/file-format, but can also be used independently) to include the hash of the file in the URL (which can sometimes allow detection if the spies or the server operator will alter the contents of the file, and can also allow the hash to be known in case you are able to find the same file from other sources in case one source is unavailable). However, other people can make a copy of Solar Punk Manifesto; it is CC-BY-SA.
  - bawolff 2y ago
    The CSS and JS isn't really that relavent in this context. TLS adds some overhead but probably insignificant in context. HTTP (any version) is a fine protocol. HTML is a very simple format if all you want is a list. All of these things are reasonable choices that are probably more robust than the other random things you mentioned. None of this really matters though, people should use whatever they want. My main point was mostly just that contrary to what the person i was responding to implied, self-hosting static content is a totally reasonable thing to do and a very easy thing to performance optimize (basically just do nothing). An actually self-hosted static site (apache + html, css, js) would have probably stood up to the hn hug of death. > I had also invented "hashed:" URI scheme "Invent" is a strong word given magnet: links have been around forever.
    - zzo38computer 2y ago
      Yes, if you only want a list, you can use the <OL> and <LI> commands of HTML and not much else should be needed. HTTP and HTML will still work, although not the only possibility. I agree that self-hosting static content is a reasonable thing to do, and would be a good idea. However, reducing the number of files and file sizes still makes it more efficient, and so does using simpler server software (which is possible for HTTP, although it can be even more simpler with some other protocols if the server software is also simpler). > magnet: links have been around forever. I know about magnet: URI scheme, although mine is somewhat simpler (it is not intended to do everything that magnet: does), but also allows relative URLs (although supporting this involves things other than the usual URL format), and does not require URL encoding, and has some other differences. (Unlike the magnet: scheme, it is not intended to use with BitTorrent; it is intended for documents like other URI schemes are.) ("Forever" is a strong word; magnet: scheme was invented in 2002, according to Wikipedia.)
bigiain 2y ago
Have you seen: https://solar.lowtechmagazine.com/about/the-solar-website/ https://solar.lowtechmagazine.com/about/the-solar-website/ ?

To quote: "Solarpunk is about youth maker culture, local solutions, local energy grids, ways of creating autonomous functioning systems. It is about loving the world." So, yes actually, it does seem like that would fit in their manifesto. As an aside, if it was actually static - just apache serving a .html file on a server somewhere, i suspect it would still be up :)

boopdewoop 2y ago
Yeah they should probably learn to code.. I mean using a WYSIWYG to make this page is just messy. its using WordPress, Its more than just this page however so I can understand why. but host it on a git repo MD file. easier to allow Pull requests and edits.
zzo38computer 2y ago
This file has many JavaScripts and CSS and other stuff more than will be needed (the copy from web.archive.org adds more, but you can add "id_" after the numbers to avoid them). Even just a plain text file would do. HTML and HTTP are probably more complicated than will be needed, too (although you can still use HTTP as an alternative service if you want to do). TLS also adds more complexity and uses up more power, too. There is simpler protocols (probably the "nex:" is simplest kind of "small web" protocols), simpler file formats, simpler ways to use existing file formats, and more efficient server software, available, too. I had also invented "hashed:" URI scheme (which is documented together with the specifiction of Scorpion protocol/file-format, but can also be used independently) to include the hash of the file in the URL (which can sometimes allow detection if the spies or the server operator will alter the contents of the file, and can also allow the hash to be known in case you are able to find the same file from other sources in case one source is unavailable). However, other people can make a copy of Solar Punk Manifesto; it is CC-BY-SA.
- bawolff 2y ago
  The CSS and JS isn't really that relavent in this context. TLS adds some overhead but probably insignificant in context. HTTP (any version) is a fine protocol. HTML is a very simple format if all you want is a list. All of these things are reasonable choices that are probably more robust than the other random things you mentioned. None of this really matters though, people should use whatever they want. My main point was mostly just that contrary to what the person i was responding to implied, self-hosting static content is a totally reasonable thing to do and a very easy thing to performance optimize (basically just do nothing). An actually self-hosted static site (apache + html, css, js) would have probably stood up to the hn hug of death. > I had also invented "hashed:" URI scheme "Invent" is a strong word given magnet: links have been around forever.
  - zzo38computer 2y ago
    Yes, if you only want a list, you can use the <OL> and <LI> commands of HTML and not much else should be needed. HTTP and HTML will still work, although not the only possibility. I agree that self-hosting static content is a reasonable thing to do, and would be a good idea. However, reducing the number of files and file sizes still makes it more efficient, and so does using simpler server software (which is possible for HTTP, although it can be even more simpler with some other protocols if the server software is also simpler). > magnet: links have been around forever. I know about magnet: URI scheme, although mine is somewhat simpler (it is not intended to do everything that magnet: does), but also allows relative URLs (although supporting this involves things other than the usual URL format), and does not require URL encoding, and has some other differences. (Unlike the magnet: scheme, it is not intended to use with BitTorrent; it is intended for documents like other URI schemes are.) ("Forever" is a strong word; magnet: scheme was invented in 2002, according to Wikipedia.)

bigiain 2y ago

Have you seen: https://solar.lowtechmagazine.com/about/the-solar-website/ https://solar.lowtechmagazine.com/about/the-solar-website/ ?