• 2 Posts
  • 93 Comments
Joined 2 years ago
cake
Cake day: July 8th, 2023

help-circle
rss






  • The other reply you already got pretty much sums up how I feel about Merkel, not a fan exactly. But I’d like to add one specific thing she has my respect for.

    During the refugee crisis of 2015 there was a point where her side of the political aisle was approaching hysteria. There were hundreds of thousands of people streaming into the EU from all over the middle east and north Africa, crowds at every major train station and border crossing, normal refugee infrastructure way beyond the point of collapse. So conservatives were starting to seriously argue for the suspension of asylum rights, closing borders, etc. And Merkel was usually one to wait stuff like this out, see what possible consensus forms and then adopt it as if it was her idea all along. But not this time. She saw it starting to gain traction, just came out publicly and said “We will manage this”, and that was that for her. Discussion died immediately.

    I may not respect much of what she did before or after, but taking that stance at that moment as clearly as she did, that I respect her for.



  • You and i read different things.

    Apparently we did.

    I hated how he worded them, but his arguments at greppable and understandable are valid arguments that go beyond rust and if he can read it or not or refuses to.

    I’m failing to see how Rust code is not greppable unless you don’t speak Rust.

    Mixing languages in a part of a project brings complexity and is often a huge ass nono because it makes things unreadable and hard to manage on a large scale.

    An argument which I would acknowledge, but if the decision to do this has been made by the group it still is weird to see it blocked by an individual.

    He also argues that a c interface exists to connect 2 parts of a system. The person that changes the interface should not have to alter the users of that interface, […] So if he changes the interface, the rust team will need to fix it, specially since they are the minority.

    Nobody asked Hellwig to do this, in fact Krummrich said several times they would maintain the interface consuming the C code themselves. They just want one common interface for all Rust drivers, instead of replicating the same code in each driver. Which Hellwig never gives a substantial reply to.

    That also doesnt mean he can change it in whatever way without worry, it is an interface change, that needs discussions and approvals ahead of time ofc.

    Again not how I’m reading that thread. As Krummrich put it:

    Surely you can expect maintainers of the Rust abstraction to help with integrating API changes – this isn’t different compared to driver / component maintainers helping with integrating fundamental API changes for their affected driver / component, like you’ve mentioned videobuf2-dma stuff.


  • How do you figure?

    The only two “technical” arguments I could see were firstly that code should

    [remain] greppable and maintainable

    which unless I’m missing something boils down to “I don’t speak Rust”, and secondly that

    The only reason Linux managed to survive so long is by not having internal boundaries, and adding another language complely breaks this

    which unless I’m missing something boils down to “I don’t speak Rust”, because ain’t nobody trying to add any other languages to the Linux code base.

    Surely this can’t be the “decent technical reasoning” you are referring to? I have to admit I don’t follow kernel development that closely, but I was under the impression that integrating Rust into the code base was a long discussed initiative having the “official” blessing of the higher ups among the maintainers by now, so it seems odd to see it opposed in such harsh terms by a subsystem maintainer here:

    I absolutely support using Rust in new codebase, but I do not at all in Linux.


  • Oh it wasn’t that bad. You just had to understand rules, models, layouts, variants, and options. Oh and then of course key codes, syms, maps, states, and modifiers. Oh and then…

    Kidding aside though, in this particular case it would have been relatively simple:

    If you wanted to enable the Ctrl+Alt+Backspace sequence to kill the X server by default, you could create a configuration snippet /etc/X11/xorg.conf.d/90-zap.conf containing:

    Section "InputClass"
        Identifier "keyboard defaults"
        MatchIsKeyboard "on"
    
        Option "XKbOptions" "terminate:ctrl_alt_bksp"
    EndSection
    

    This would be equivalent to running the shell command:

    setxkbmap -option "terminate:ctrl_alt_bksp"




  • can’t see how this can possibly be a good thing, you know it will mean funding with conditions.

    Well, the things they are funding will get funded? How is that a bad thing?!

    The conditions range from very broad, like “fix bugs” (curl), over somewhat specific like “improve cross-platform compatibility and the Linux RNG” (Wireguard), to very specific like “create a test-suite and drive development on the Fediverse account migration functionality” (ActivityPub).

    You can see more for yourself at https://www.sovereign.tech/tech

    All of these seem to be rather tame conditions that are just there to ensure the funds get used in the way they were intended to be used. And I don’t really see how that gives the STF any sort of direct control over these projects, while it gives those projects resources to achieve more than they might have otherwise. There are no long-term funding models that would enable implicit control over these projects.


  • They could set up an account on one of the larger well established Canadian instances or even better start up their own.

    Both of these options have their pros and cons, and I think it is important to explain these well to the council if you want to have any hope of convincing them.

    A line of argument that has had some success in Europe is what has become known as “Digital Sovereignty”, basically a fancy term for saying government should control its own infrastructure. So you might want to sell it as an easy way to have a permanent archive of public communication and a method for it that is under their direct control, rather than as a way to find more engagement.

    As others have said self hosting has a maintenance and moderation overhead, but this can be lessened by running an instance together with other cities while still retaining most of the benefits of self hosting.

    Seeing from the linked cross-post that this is about Port Alberni, and considering that http://portalberni.ca/ returns an empty reply while https://portalberni.ca/ lets me know I have been geoblocked because I’m outside of Canada and the US, I’d say you have an uphill battle before you though. These people made a website (probably paid for it, too), and then killed much of its use by geoblocking most of the world.

    Good luck.


  • I don’t know if there is any single takeaway here, this story is just fucking ridiculous on every single level.

    1. They bullshited themselves into a search warrant based on typical cannabis “investigation methods”.
    2. In a state where recreational cannabis use is legal.
    3. Persisted in the search even after their main argument for it, high energy usage indicating a grow-op, fell away when it was clear it was indeed a medical facility.
    4. Made the motherfucking “Gun flies to MRI” TV trope a certified reality. This is a thing that verifiably happened now.
    5. Instead of getting help, used a sealed (!) emergency shutdown button…
    6. …which damaged the machine. And released thousands of dollars worth of helium gas.
    7. Forgot their loaded magazine on the ground.

    This can’t be real. I’m fucking dying over here. Please let there be bodycam footage of the cop speaking in a high pitched voice after. (I know the helium was probably not released into the room, but one can hope I guess)


  • android auto

    First I heard of this, but since it seems to be just some software that runs on the hardware of car manufacturers it seems rather unlikely. But very theoretically possible, if the car manufacturer was using default process scheduling in a CPU constrained machine and now switches to real-time scheduling in an update. But that was possible for years before this news, the code has just been mainlined to the default kernel now. If the car manufacturer cared about that they would probably have done it already with a patched kernel.