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

help-circle



  • Yeah, those are both good examples of interdependent supply between us and Canada, where it makes sense to keep markets geographically together.

    I’m more referring to artificial blocks in terms of provincial barriers put in place for political reasons, like my alcohol example. Historically, these were restrictions for tax reasons between Ontario, Quebec and western Canada, but recent (last 20 years) spats and competition for transfer payments have essentially cut off lumber, paint, car parts, raw minerals, etc between provinces as close as sask and Manitoba.

    And that is on top of intangible services gradually being restricted more and more between provinces. As a remote worker and contractor, rules have tightened for me about working in multiple provinces simultaneously.

    These measures aren’t there to balance economics, they exist because provinces compete more than they cooperate.



  • So I went to the demo and I have a few questions:

    • Couldn’t figure out how to use 3d in demo (not critical)
    • developer discord link on github is expired
    • distinction between “public” and “shared” trails isn’t clear
    • “Completion Status” for trails… what does this mean?
    • Couldn’t import a trail in demo:
    haystack-mountain-101522-105940.gpx
    {"message":"TypeError: Cannot read properties of null (reading 'id')"}
    

    I am actually really impressed with what you have so far, and I’d love to start using this!






  • HA… Do you mean failover? It would need some consideration, either a second wan link or accepting that a few TCP sessions might reset after the cutover, even with state sync. But it’s definitely doable.

    I’m currently in a state of ramping down my hardware from a 1u dual Xeon to a more appropriate solution on less power-hungry gear, so I’m not as interested in setting up failover if it means adding to my power consumption simply for the uptime. After 25 years in IT, its become clear to me that the solutions we put in place at work come with some downsides like power consumption, noise, complexity and cost that aren’t offset by any meaningful advantage.

    All that said, i did run that setup for a few years and it does perform very well. The one advantage of having a router virtualized was being able to revert to a snapshot if an upgrade failed, which is a good case for virtualizing a router on its own.