A multi-community groups outputs of multiple communities into one entity that you can subscribe to and browse.

Nice.

I’ve been keeping an eye on the multicommunity issue and that getting merged was a nice notification.

Thinking of further use cases, maybe a multicommunity could be used as an “Instance curated” option in addition to All/Local/etc. Because frontpages of topic-specific and regional instances seem to all be dominated by us politics.

Varusteleka much

Next up: the real reason we all stopped breathing oxygen

The bird could have been on a bombing run already.

What kind of magnet doesn’t rappel?

“The simplest way” belongs both to occam and razor?

Prefix the name with what it’s for. For example, I’ve previously got a SoundFontError from opening soundfont file.

“Error” is already used by std::error::Error. It might not be imported by the code that imports your error type, but I think it’s better to give it distinct name.

The other thing is that you might want to use more than one library. Typical imports at the top of the file might look like this:

use bingbong::{BingBong, BingBongError, SomethingElse};
use bogos::binted::crotchidizer::{Crotchidizer, CrotchidizerError};

If both libraries named their error enums just “Error”, the collision could be worked around, but it’s an unnecessary extra step:

// Not sure how renaming affects compiler hints.
use bingbong::{BingBong, Error as BingBongError, SomethingElse};
use bogos::binted::crotchidizer::{Crotchidizer, Error as CrotchidizerError};

or if you want to avoid renaming:

use bingbong::{BingBong, SomethingElse};
use bogos::binted::crotchidizer::{self, Crotchidizer};

/* ... */

    match result {
        Ok(value) => return value,
        Err(bingbong::Error::MissionFailed) => panic!(),
        Err(bingbong::Error::UrMom) => todo!(),
        _ => unreachable!(),
    }
    
    if let Err(crotchidizer::Error::SomethingsWrong) = result2 {
        // ...
    }
    

If the screenshot had followed conventions, the message would say something like this:

could not convert error type `BingBongError` to `MyAppError`

ZBOOBS

I don’t know if this will be attempt, but I helped. Godspeed, OP

You really should avoid naming your type plain “Error”

Thanks, I hate it.

Keith has some issues, but he will still get the job done.

Boo

deleted by creator

I don’t know what app you’re using, but that spoiler tag isn’t part of the spec.

Mate.

Your site says “no confusion”, “no fluff”, “zero BS”, etc. but the entire page is just incoherent fluff bullshit. I read the page and I have no clue what your product does.

Hey! You can’t say that word

Thanks