Tram EM but instead of trams with really good brakes you have to do precision stops with 1800 tons of freight train
@haskal See the pinned posts in the networkmanager channel, duh [the pinned posts do not explain this]
@matt > If it's not signed, it could be any rando impersonating them
if it's signed by a key you can't authenticate, it could just as easily be any rando who can generate a key and puts "Trustworthy Organization" into the name field
@matt it doesn't have to be mutual, they don't need to trust you to sign a public message. If you wanted, you could go talk to someone you know is a trustworthy part of the organization, get them to confirm this is their key, and then you would locally trust the key.
But unless you're actually going to talk to them, this doesn't add any security and it just annoys people because GPG is ancient software
@vertigo Each call to `paint_with` creates a fresh `TextureCreator`, which is dropped at the end of the function
@vertigo That understanding of lifetime annotations is the wrong way around. They indicate that a struct annotated with one contains a reference to something else outside of itself, which naturally implies that the struct itself can only be valid as long as the thing it references is valid.
The types are tied to each other like this: `TextureCreator` is tied to the `Canvas`/the `Window` it contains because the definition of this method: https://docs.rs/sdl2/latest/sdl2/render/struct.Canvas.html#method.texture_creator - notice how it carried along the `'s` lifetime annotation. In turn then the `Texture`s are tied to the `TextureCreator` because of the definition of the definition of this method: https://docs.rs/sdl2/latest/sdl2/render/struct.TextureCreator.html#method.create_texture - The `'_` thing in the return type is a shorthand for reusing the lifetime of a single input reference, i.e. the one of `&self` in this case
@vertigo The 'a lifetime in your struct wants to be the lifetime of the `Canvas`. Do you see why the `TextureCreator` and its `Textures` are tied to each other?
@vertigo The `TextureCreator` is tied to the `Canvas`, and the textures it returns are tied to the `TextureCreator` (https://docs.rs/sdl2/latest/sdl2/render/struct.TextureCreator.html#method.create_texture, notice the `'_` lifetime)
this means that the struct is self-referential (i.e. one field is a reference to another), which don't work in Rust
@matt "building a trust path" means using the archaic system it provides for verifying that a key belongs to the person it claims to belong to. It works by creating signatures that attest that, i.e. Person A says Person B is who they claim to be, and Person B says Person C is who they claim to be, then you manually verify the identity of Person A which gets you trusted keys for B & C
it's a neat idea in theory but really convoluted in practice
@codl there's no need to list every URL for a release (https://musicbrainz.org/doc/Style/Relationships/URLs)
person on the internet, physically located in northern Germany.
Previously known as @email@example.com