I’ve been using mega. They have a decent linux client and file manager integrations.

Well, I did read it. Obviously Apple didn’t use those exact words, but the argument is the same: users are incapable of making safe decisions and need to be protected from themselves.

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 really should avoid naming your type plain “Error”

Love David Wise’s soundtracks.

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

The sidebar’s gone because I removed it :)

I’ll try to incorporate that info elsewhere. At this stage, a lot can change on a whim.

Yeah, I’d love to have some kind of full SSR solution that doesn’t require scripts at user’s end, but it’s probably not possible with this.

I wish there were more people building frontends. Since Lemmy is properly decentralized, there’s a lot of potential for interesting instance diversity.

People who make foss apps generally know and care more about programming than secondary things, such as design.

I’ve seen people with weird personal preferences, and some who seemingly perceived design as unnecessary, just getting in the way of “real” work. I think it’s mostly just lack of time and knowledge than an active decision though.

If you have thoughts about my app, I welcome them.

If you want to call it a fault. One instance can’t cover all, just the slice its users interact with.

Blaze screenshot it at lemmy.ml.

The number shown is how many posts or comments your instance is aware of. If your number is smaller than the real one, it means that there’s content that doesn’t exist on your instance.

The missing content is either:

• Old: The account is like 3 or 4 years older tham your instance. Old content doesn’t get federated unless someone deliberately asks for it.
• Posted in communities that no one at your instance has subscribed to them yet. This stuff also doesn’t get auto-federated.

I’ve been using mega synced folders for most stuff. Works fine.

I tried to do this before, but it did not work out.

I couldn’t make the meta key alone open overview. I also tried to add a dock there, but I can only have a panel when not in overview, which is the opposite of that I wanted. I also liked the notification menu and the quick toggles menu in top right corner.

I have been planning to get into plasma extension development to fix some of these issues.

It would help if you got the model right, and an exact one at that. As the others said, “iMac” isn’t a mac laptop, but an AIO desktop.

I run linux on one of these. Everything worked out of the box, except for wireless. See my 2-part adventure for how I solved it.

Mac “bios” isn’t exactly how you’d expect from PCs. Hold down alt key during startup to enter boot menu, and you’re good to go.

If your family member was a mac user before, they might be most comfortable on Gnome, as it has aped many ui features from mac os. It has a similar dock, fluid trackpad-friendly navigation that works the same way, and more.