In case you haven't seen it, here's a talk regarding Rust's integration into the Linux filesystem that gets completely derailed at The Linux Storage, Filesystem, Memory Management and BPF Summit.

It seems like the key_value function has been removed from Cursor in 1.78.0-nightly. I've been using this to get the key/value pair from BTreeMap::upper_bound and BTreeMap::lower_bound.

Does anyone know why this was removed and what a good idiomatic alternative would be?

Edit: In case anyone encounters the same problem and is curious what's going on (the documentation hasn't been updated to reflect the change yet), it was referred to in this issue: 107540 changed in this commit: 8ee9693. Essentially, cursors in BTreeMaps previously pointed to specific nodes in the tree whereas now they point to gaps between the nodes. To get the node values, you need to use prev or next on the cursors returned by upper_bound or lower_bound.

The new instance icon looks great!

A while ago we had a post about a new instance icon. Just wondering if there's any news on that?

I'm getting errors such as "Socket: CLOSED" when I try to create comments, however the comment gets created. It then brings me back to the comment editing screen where if I click create again, it keeps duplicating the comment.

Wondering if anyone else is having this issue?

Edit: I get an error when creating posts as well: "stream was reset: CANCEL"

This is a really simple silly thing I just realized, but I noticed I have a lot code that looks something like this:

fn foo() -> Result<(), Error> {
    // do something
}

fn bar() -> Option<()> {
    let Ok(f) = foo() else {
        return None;
    };
}

I hated that if-statement. I realized today that I could simplify to:

fn bar() -> Option<()> {
    let f = foo().ok()?;
}

And that cleaned up my code a lot. It's a tiny thing, but when it's okay to discard the error from the result, makes such a big difference when you have a lot of them!

As per this Github pull request which is removing it from the Lemmy sign up page, we should defederate from this instance as well.

It looks like if a community name is on the longer side, it pushes some of the UI elements to the edge of the screen and makes them look strange. You can see it at this community:

!mildlyinteresting@lemmit.online

Not sure if anyone else is having this problem, but whenever I'm reading a longer comment thread and I click "1 more reply" (or "N more replies"), the app crashes.

I'm curious when the next beta release will be, or how often there will be a release if there's a schedule?