At that price point, something used and not particularly recent. Even an old laptop will be good performance-wise, but not necessarily storage-wise.

However, buying a laptop to run at home might not be the most reliable or economical way to host Lemmy: you can rent a virtual server for not much, provided that you have access to a computer to remotely access the server with.

I have zero experience with YunoHost, so I don’t know how that may or may not limit the options. Probably the most common way is to use Lemmy-Ansible. It’s easy (well, relatively speaking) and is maintained by the actual lemmy devs themselves. Managed services (ones where you don’t have to deal with the server) should also exist for lemmy, but I’ve never used them.

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

I’ve had that unhelpful error popup blocking os install. In my case it was bad system time. Check the clock.

Because “biological weapons development” sounds a d v a n c e d

Warning: our product can be used for advanced high tech work!!!11

When instances federate, they don’t send old content. Old content will be fetched if a user tries to open it, for example by clicking a link to an old post (on some apps) or pasting its url into the search box.

The data copied to the other instance will stay on the other instance, unless manually deleted for some reason.

Officially:
No.

Unofficially:
Maybe, but the downsides are jank, security, and that you’re relying on Apple not killing access for “unauthorized” software.

Alternative:
Use a cross-platform solution, like Bitwarden

Intentionally blurring the line between ads and user posts. Same stuff as always.

I don’t understand how it ever seemed like a good decision to release an illegal surveillance tape that contains just some mild disrespect.

Headphone jack

Hey, they didn’t fuck everything up!

It’s not copyright infringement if you’re as big as meta.

I think the color had just shown up. It’s been a while, I don’t remember specifics that well. The movie was great though and the encounter was so funny we didn’t mind it.

I watched this in theater. It was very late and there was only one other group of people. During the film one of them loudly said something like “what the fuck is this shit” and they walked out pretty early.

I guess it’s not for everyone.

Classic, but I’m more of a Con Air man myself

You’re god damn right with that opinion

Oh boy, now I can stop missing C++

Not very likely. Translating cpu architectures is completely different from from what wine/proton does. A compatibility layer for arm would be even more difficult and expensive, and have a performance penalty. They might plan that for further into future though, if arm pcs take off. A Mac implementation would probably need a lot of apple-specific work, and there aren’t many mac gamers out there.

I know, but it does let you sled off a cliff if you choose to.

Oh boy, not this bullshit again

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`

You can wrap everything in unsafe and keep living dangerously!