Canadian software engineer living in Europe.

  • 2 Posts
  • 52 Comments
Joined 1 year ago
cake
Cake day: June 7th, 2023

help-circle



  • Yeah I share your issue with their stance on Nuclear as well (though having worked in the industry for a few years now, I’m coming to realise it’s a moot point). I’ll push back a bit on your other points though. I’ve always found their proposals to be well thought out and fully costed.

    The reason I’ve long supported them (even when the leadership was chaotic) was that they were the only party with a platform that shared my priority: a world not on fire. the Conservatives muzzled climate scientists, the Liberals literally bought a pipeline and the NDP keeps cozying up to oil in Alberta and loggers in BC.

    Sure we’ve got crystal-clutching anti-nuclear loonies in the Greens, but at least I can trust they actually believe the IPCC enough to want to do something about it.




  • That’s an interesting thought. There’s a lot of cases you see where people have stripped a comic’s name from the bottom of the image, but that’s not really what this project was designed for. Aletheia will guarantee you that the person/company sharing the media is who they say they are, but critically it won’t prevent infringement.

    The example I give in my talk is that InfoWars could take a BBC news story and say “we made this”, but it wouldn’t let them modify that story and claim that “the BBC made this”. The goal is to be able to re-connect what someone is saying with the reputation of the person saying it, with the hope that we can start delegating our trust to individuals and organisations again.






  • Because post is more than just letters, it’s parcels too. Canada Post is infrastructure that ties the whole country together, not just the denser, more profitable cities. Imagine if there were only for-profit postal services in the country. What would it cost to send a parcel to 100 Mile House, or Baker Lake, or whole swathes of the country that only speak French? Think of all the things that go out by post, like Carbon tax rebate cheques and voting information. It’d introduce a massive disparity in service and access to basic services, and so we socialise that cost across the country.

    There are always ways to improve of course, but you asked specifically about why the system was socialised.


  • That’s a fair point. So long as it’s addressed from a position of “is the community being served well” and not “this should be run like a business”. Canada Post has a difficult (and expensive) mandate: to service all of the country, no matter how remote, and the knee-jerk reaction to such headlines is often to privatise which would change that mandate to “earn as much profit for investors as possible”.

    I’m living in the UK these days, with private post, and private water companies. Things have literally been enshitified, with raw sewage flowing down the river Thames, so I’m concerned when I see such headlines.







  • Daniel Quinn@lemmy.catoLinux@lemmy.mlStopping a badly behaved bot the wrong way.
    link
    fedilink
    English
    arrow-up
    25
    arrow-down
    1
    ·
    edit-2
    3 months ago

    Not throwing any shade, just some advice for the future: try to always consider the problem in the context of the OSI model. Specifically, “Layer 3” (network) is always a better strategy for routing/blocking than “Layer 5” (application) if you can do it.

    Blocking traffic at the application layer means that the traffic has to be routed through (bandwidth consumption) assembled and processed (CPU cost) before a decision can be made. You should always try to limit the stuff that makes it to layer 5 if you’re sure you won’t want it.

    The trouble with layer 3 routing of course is that you don’t have application data there. No host name, no HTTP headers, etc., just packets with a few bits of information:

    • source IP and port
    • destination IP and port
    • A few other firewall-specific bits of information like whether this packet is part of an established connection (syn) etc.

    In your case though, you already knew what you didn’t want: traffic from a particular IP, and you have that at the network layer.

    At that point, you know you can block at layer 3, so the next question is how far up the chain can you block it?

    Most self-hosters will just have their machines on the open internet, so their personal firewall is all they’ve got to work with. It’s still better than letting the packets all the way through to your application, but you still have to suffer the cost of dropping each packet. Still, it’s good enough™ for most.

    In your case though, you had setup the added benefit of Cloudflare standing between you and your server, so you could move that decision making step even further away from you, which is pretty great.