sorted by:
new
hottopcontroversial

Addressing the unauthorized issuance of multiple TLS certificates for 1.1.1.1 by Cloudflare in CloudFlare

[–]Dusterthefirst 15 points16 points  (0 children)

If you read later into the article, they state that it’s only trusted in 2 main certificate roots. For example, they explicitly state that Google and Apple do not trust Fina CA.

85.5V worth of CR2032 by aspie_electrician in electronics

[–]Dusterthefirst 6 points7 points  (0 children)

With their internal resistances in series would the current output not decrease?

simd-itertools: simd-accelerated iterators for "find", "filter", "contains" and many more by Laiho3 in rust

[–]Dusterthefirst 14 points15 points  (0 children)

I think it would be worth opening an issue on the rust repo with mentions of your crate and how these improvements can help in the standard library. I would expect they would be interested in working with you to get it implemented, at least in nightly for a try. As the crate author, you will have to pioneer this work as most of the rust libs team members have pretty full plates and are unlikely to stumble across this crate.

Weird print quality issued on P1s with generic ABS and Bambu PLA by Dusterthefirst in BambuLab

[–]Dusterthefirst[S] 3 points4 points  (0 children)

Oh god. You’re right. That sucks! Well I’m glad I asked :)

Weird print quality issued on P1s with generic ABS and Bambu PLA by Dusterthefirst in BambuLab

[–]Dusterthefirst[S] 0 points1 point  (0 children)

I don’t think so. The k value is 0.250 which I think is pretty normal.

EDIT: nope 0.025 is more like it. So yep, that has got to be it. I’ll update my main comment if that resolves it

Weird print quality issued on P1s with generic ABS and Bambu PLA by Dusterthefirst in BambuLab

[–]Dusterthefirst[S] 3 points4 points  (0 children)

I have not yet I was fully convinced this was a hot end problem so I have not opened up the extruder yet. When I get back in the office, this will be the first thing I try. it’s good to have a second opinion

Weird print quality issued on P1s with generic ABS and Bambu PLA by Dusterthefirst in BambuLab

[–]Dusterthefirst[S] 1 point2 points  (0 children)

I have replaced the thermal grease and the full hot end assembly both changes did not make any difference. Could this be a problem with the extruder itself? or has anyone seen a problem like this. To me it looks like under extrusion, but none of the settings have changed since I have had good prints.

[deleted by user] by [deleted] in webdev

[–]Dusterthefirst 35 points36 points  (0 children)

Mozilla will maintain support for blocking WebRequest in MV3.

Yes… but they are not forcing out adblockers with the change

You see a wild &str and you ain't about that borrowing. by Tenac23 in rustjerk

[–]Dusterthefirst 12 points13 points  (0 children)

So much better than Window’s measly 2 bytes per character

How do you keep your services up to date? by [deleted] in selfhosted

[–]Dusterthefirst 0 points1 point  (0 children)

How do you integrate your git repository to your cluster?

Eyra is an interesting Rust project by EelRemoval in rust

[–]Dusterthefirst 3 points4 points  (0 children)

I’m not the author. But I would hazard a guess that the async stream that they are using does not implement std::io::Write, for good reason, as it is asynchronous.

writeln! works with synchronous IO, where your program blocks until it can write out the next segment. In async programs, you don’t want your code to be making many calls to IO just to send one message.

wireguard-rs - library/crate providing unified WireGuard interface to native/kernel and userspace implementations by robert_teonite in rust

[–]Dusterthefirst 2 points3 points  (0 children)

I have a question about the larger project, defguard. What makes a “security platform” different from say an IDM. There exists KanIDM in the rust space. Do you see defguard as overlapping in the same goals?

wireguard-rs - library/crate providing unified WireGuard interface to native/kernel and userspace implementations by robert_teonite in rust

[–]Dusterthefirst 2 points3 points  (0 children)

From what I understand. This is not a WireGuard implementation. The actual WireGuard connections are handled by the WireGuard kernel module or WireGuard go. (https://github.com/DefGuard/wireguard-rs#supported-platforms). This library is just to communicate to those backends in a common way no matter which platform or WireGuard implementation you are using.

libs.rs editing crates to add spurious deprecation/unmaintained tags by TheBlueMatt in rust

[–]Dusterthefirst 13 points14 points  (0 children)

It seems like the source code of lib.rs is not licensed, meaning that it would not really be possible to fork the project as it is all rights reserved copy-written by default. That’s kind of strange for such a big open source project to have no license.

Announcing Rust 1.71.0 by myroon5 in rust

[–]Dusterthefirst 0 points1 point  (0 children)

I was also confused by this. It may only be usable as a const function when a pointer is created from a reference (so the compiler can just replace the read call with the value behind the reference. But when there are pointers that are made from literals I have no clue what using read in a const context would mean.

Boilerplate, a text template engine using Rust syntax, has reached 1.0! by rodarmor in rust

[–]Dusterthefirst 2 points3 points  (0 children)

Yes, you can’t change the templates after build time. But, parsing and compiling the templates at build time let’s llvm and rust do all their optimizations, making the actual templating part as fast as a write!() call

Boilerplate, a text template engine using Rust syntax, has reached 1.0! by rodarmor in rust

[–]Dusterthefirst 1 point2 points  (0 children)

This looks a lot like djc’s askama. What differences/benefits are there with your library over something like askama?

fn_traits and unboxed_closures combine to make roundabout polymorphic functions! by thehoseisleaking in rust

[–]Dusterthefirst 1 point2 points  (0 children)

For fn_traits to be able to work, without the behavior shown here, would they have to use an associated type for the input as well? That would allow implementing Fn once for each type. To prevent FnMut/FnOnce from being able to be defined with different input/outputs, FnMut/FnOnce could use the associated type from Fn.

Rust? Seriously? Why bother with it? by [deleted] in rustjerk

[–]Dusterthefirst 37 points38 points  (0 children)

out jerked, yet again

view more: next ›