They fully expected for it to get "talibanned"

https://twitter.com/edefic/status/1757110857949958429

Also, it made me rotate my phone into landscape view. I guess that's one way to not have to deal with responsive design

I think you mean portrait mode. But yeah that immediately made me not care about whatever this is. If someone is too lazy to make their site responsive, that's fine. But when they go out of their way to make the site unusable, that's another thing entirely.

Finally, they/them RAM

It is: https://proxy.golang.org/. The goal is faster module downloads, and to an extent prevent users from hitting GitHub/etc ratelimits

This talks about concerns with piping curl into bash. It doesn't address any issues with just curling arbitrary data

At my college (Rochester Institute of Technology), every device on ethernet and wifi gets assigned a public IP address from the /16 they own, with no firewall. I host my server in a club's server room. No cost or setup besides registering the MAC address, just a public IP address.

Hey, that's where I went! Guess they've continued not cracking down on unregistered servers.

I wrote this tool[1] to help me create a CA, generate certificates, and automatically renew them

https://github.com/galenguyer/hancock

It sounds like the app always requests the weather in Celsius from the API before converting to Farenheit and rounding up

That'd make perfect sense, actually. 20°C = 68.0°F, 21°C = 69.8°F which rounds up to 70. No anti-niceness conspiracy here, just math.

On Debian they end up under /var/lib/docker/volumes/

Ah ok cool, I guess it isn't hard to find then.

I usually have my docker-compose.yml file in a dir along with the mapped volume directories. Allows me to just rsync that one folder to capture all config & data.

Are names volumes just a way to not have to worry about the files and leave them handled by docker?

Yea a use case would be to to persist application data when updating by pulling a newer container. Mapping to the host introduces the possibility of conflicts between the host and/or other containers.

You can move them as well.

I typically see Rust marketed as a better replacement for C. In what cases isn't it a practical replacement?

Rust is a fine replacement for C++, but not really for C, and the reasons why Rust can't be a replacement for C are very similar to why C++ can't be a replacement for C. Everybody who chooses C today has slightly different reasons to do so, but one important reason is that C is a very small language with a very small standard library, and most parts of the standard library can be ignored without losing any of the "qualities" of the C language. IME a small language feature set makes it easier to evaluate and integrate third party code, it's hard to say exactly why that is, but that's my experience anyway. Of course one could say "nobody forces you to use the whole feature set of Rust", but the same has been said in the C++ world for decades. The problem is that everybody selects their own subset of the language when having the choice.

Core Rust is very small language. It doesn't have memory allocator, so it can be used in embedded, where heap is not available. C++ cannot do that.

https://doc.rust-lang.org/core/index.html

Its a replacement for c++ not c

When you’re targeting platforms that Rust doesn’t, have a lot of legacy code that can’t do for a new toolchain, or cannot handle dependencies.