Max Ammann
Max Ammann
This would be an excellent first try for that!
Oh I just saw that you opened this issue as RFC! Excellent! Should we turn this into a PR right away and create an RFC section in the Rust book...
So RFC would probably not use Github Issues, but only Github PRs: > Fork the RFC repo https://github.com/rust-lang/rfcs Copy 0000-template.md to text/0000-my-feature.md (where 'my-feature' is descriptive. don't assign an RFC...
Possibly duplicate of https://github.com/maplibre/maplibre-rs/issues/91. The two issues can probably be merged. @DerKarlos can you copy all the important things over to https://github.com/maplibre/maplibre-rs/issues/91? Then close this one.
Since I first noticed about this a few years back I just put all my music at "/media/music/library". Its kind of a pain, but I think switching to relative paths...
> I think we need to keep claims somehow (for the Objective Oracle). We definitely want to keep something that fulfills our goal. The issue with the tlspuffin-claims is that...
> Regarding the diagram: shouldn't the Wolfssl/OpenSSL bindings be removed? I think that is to be discussed. Either can keep them or redo the work in plain C and go...
Low prio because it wont block the release.
@michael-markl I created this issue. I think it makes sense, right? related to #695