If we agree that greater censorship on social media is necessary, and if private companies aren't taking on the role of censor here, I think that suggests governments must become more active in their roles as censor. What would that look like and how would it work?

This is definitely the piece that gives the current versioning policy its sharp edge, so it's great news that the fix will arrive soon.

Thanks for your hard work on Ring!

Ring has a policy[0] of only supporting the latest released version with users being expected to always upgrade to latest Ring. This in itself is not so bad, but coupled with the lack of any guarantees around API stability means that it can be a very tricky dependency to work with. This problem is compounded by it only being possible to link one version of Ring in to the same program.

Even if you don't depend on Ring directly, Ring could appear as a dependency of many of your dependencies. This forces you into upgrading all of your Ring-depending dependencies in lockstep. You cannot upgrade any until all of these dependencies support the same latest version of Ring.

This is a real shame because Ring otherwise looks fantastic. The API is misuse resistant and looks quite pleasant, and the documentation is thorough. Its current versioning and stability policy however is a massive liability for any project that relies on it. I hope this changes eventually.

[0]: https://github.com/briansmith/ring#versioning--stability

Mass surveillance is bad. It is toxic to freedom and democracy. Let's focus on that rather than invoking Red Scare tendencies of old.

https://github.com/dehydrated-io/dehydrated

I've got only good things to say about it. It's a single shell script, making it super easy to install and start using. It's quite configurable, but has sensible defaults and just works without demanding much operator attention.

Comments URL: https://news.ycombinator.com/item?id=23019787

Points: 1

# Comments: 0

It's a brilliant hack and we are on Hacker News after all.

This lets me write code like this:

    #[derive(From, Debug)]
    pub enum SomeSpecificError {
        Io(io::Error),
        SomeAppLevelErrorCondition,
    }

    fn do_something() -> Result<(), SomeSpecificError> {
        do_some_io()?;
        // ...
    }

    fn do_something() -> Result<(), SomeSpecificError> {
        do_some_io().map_err(SomeSpecificError::Io)?;
    }

[0] https://jeltef.github.io/derive_more/derive_more/from.html#e...

Chrome users can install this directly as an unpacked extension.

For Firefox users, there's an xpi hidden in the releases tab.

Comments URL: https://news.ycombinator.com/item?id=22102941

Points: 1

# Comments: 0

If requiring JS to render the homepage is a conscious decision made considering the various tradeoffs, please at least add a message saying so in a noscript tag.

The book is quite information dense, intellectually honest with regard to the likelihood of various outcomes, and offers the clearest and broadest assessment I've yet read of where we are and what lies for us in the future.

Describing the contemporary climate discourse as "alarmist" denies the severity and scale of the problem we face.