• 0 Posts
  • 17 Comments
Joined 2 years ago
cake
Cake day: June 17th, 2023

help-circle



  • Hydrogen is troublesome as an energy storage. The roundtrip efficiency (electricity -> hydrogen -> electricity) is just… very not worthwhile compared to batteries. Then beyond efficiency there is still the question of “how do we store hydrogen safely?”

    Storing energy indefinitely is not a problem for electricity storage, since we are pretty much guaranteed to use the stored energy up in a single day.


  • It is all quite complicated.

    1. A renewable producer (e.g. solar panels) cannot produce energy 24/7. And when it produces energy, you are not guaranteed the production is stable.

    2. A consumer cannot consume energy 24/7. And when they consume energy, you are not guaranteed the consumption is stable.

    3. To make the issue worse, a producer may not be producing energy when the consumer wants it, and vice versa.

    4. Currently, energy storage is not widely installed. Hence any produced energy must be consumed at the same time.

    The factors above combined means that there will be a mismatch. If the production is too great, your electricity appliances will probably explode and whatnot. If the consumption is too great, you experience blackouts. Neither are desirable.

    Now consider there is a middleman. The grid. Producers sell energy to the grid. Consumers buy energy from the grid.

    At some point in time, due to the factors above, the grid will need (A) zero to negative prices to encourage consumers to buy & use more energy from it, and to encourage producers to produce & sell less energy to it. Or (B) increased prices to encourage consumers to buy & use less energy and producers to produce & sell more energy. A flat price is not realistic. (Residential users only have a flat rate because our demand patterns are more stable.)

    But due to the production patterns of renewable energy and consumption patterns of our society, there is a not-insignificant risk that renewable producers will consistently face scenario (A) above making it difficult to cover back the costs.













  • IPv4 version: Think of your public IP:Port as the office building, your internal IP:Port as the floor number, and reverse proxy as the reception on that floor.

    (Your public IP:Port is routed to your internal IP:Port by the NAT on your router. The router knows which public port relates to which internal IP:Port due to the port forwarding rules you setup.)

    IPv6 version: Think of your public IP:Port as the office, and the reverse proxy as the reception.

    The following will be common to both IP protocols.

    The port is usually 80 or 443, because reverse proxy is used for HTTP(S) connections, and by default those connections use the aforementioned ports.

    When someone connects to your IP:Port, they ask the reverse proxy “hey, can you bring me to Mr. https://my-awesome-plex.xyz ?” and the reverse proxy will act as a middleman between that someone and the actual server that is serving that domain name.

    The reverse proxy, as a middleman, forwards your requests to the server, and the server’s response is forwarded back to you by the reverse proxy too.

    And just to make things complete… Why do we use reverse proxies?

    1. To hide the identity of the actual server. This is easy to understand - you are only ever talking to the proxy, never the actual server. It’s just that your messages are continually forwarded to the actual server.

    2. To save IP addresses. (One public address can serve multiple websites, if the actual servers are given only private IP addresses.)

    3. To load balance. The reverse proxy can direct one to another server if the first server is overloaded. This requires a website to be served by more than one server though, and selfhosters like us never really need it.

    4. To prevent attacks. If the reverse proxy realises that someone has been making too many connections to https://my-awesome-nas.com, the reverse proxy can reject subsequent connections. This is how Cloudflare works.

    5. Caching. If the middleman remembers that the server responded “what is the answer to everything” with “42”, then the next time someone asks the same question again, the middleman will simply reply with the same response. This takes off the workload on the server.