grue

And as part of the “open” part, any data added must be compatible with the odbl license, which means sources must first be verified as compatible, so any imports of government databases are oftentimes simply not legally possible and even if they are it’s something you have to do quasi-manually since it’s probably in a completely different format.

Considering that collections of facts aren't actually copyrightable in the first place (see Feist Publications, Inc. v. Rural Telephone Service Co.), how much does that actually matter?

Like, as a practical matter I can see how the people that run OpenStreetMap might not want you to do it, but I don't think it would actually be copyright infringement if somebody, say, scraped the business directory information from Google Maps and bulk-imported it to OpenStreetMap.

A lot of the people in my neighborhood are actually pretty friendly, in an idealized-small-town sort of way. But I live in one of those "scary" "inner-city" neighborhoods with The Blacks™ and The Gays™ and whatnot, so it's a little different for me.

Meanwhile, my Boomer parents, who live out in the suburbs, complain that their subdivision has gone completely to Hell. Funny, that.

Do you? Or do you remember when they falsely claimed to mind their own goddamn business?

Well, you sure sound upset, and you're downvoting both me and the other guy who replied to you, so...

I buy used/refurbished phones a generation or so out-of-date, and recently upgraded from a Pixel 7 to a Pixel 8. Amazon sells "unlocked" phones, but does not distinguish between carrier-unlocked and OEM (bootloader)-unlocked. Whatever phone you get, you'll want to immediately do the "enabling OEM unlocking" step (enable Developer Options and make sure that "OEM unlocking" exists as an option and isn't grayed out) before the return period expires.

It took me two tries to get an actually-unlockable phone this time around, and I've still got the unsuitable one sitting here on my desk waiting to get packed and shipped back to Amazon.

Also, I've been actually screwed by it a year or so ago, when I got a Pixel 7 for my dad, with the idea of preserving the option to install something like GrapheneOS or LineageOS at a later date. When that later date came (after the return window had closed), we discovered that his "unlocked" phone wasn't actually OEM-unlockable and now he's stuck on the stock ROM.

My Ender 3 required a little bit of assembly (attaching the Z-axis frame and the control panel, along with associated wires), but my Monoprice one came completely assembled. It was literally just plug it in, check the bed for level (which wasn't automatic, but also required little to no adjustment out of the box), feed in some filament, and then print the lucky cat gcode that came on the SD card.

Things like union busting, failure to enforce anti-trust law, and rent-seeking cause wealth transfers. Climate change leading to higher insurance costs is more like wealth destruction, even if people invested in the insurance industry are seeing gains.

I don't mind it being a rule, but I do mind it being a secret. It needs to be mentioned in the sidebar (probably as an addendum to rule #2).

You're the one who's upset about it.

Eh, there were other filaments that worked well enough, I think (carbonized string or something, maybe?). It's the vacuum that's the real trick to keeping it from burning out too quick.

Does this community not allow videos? I tried posting a link to it directly yesterday, but Automod removed it instantly.

One of @FauxLiving@lemmy.world's comments linked to a bug report about it. Turns out the real reason is that Krita uses a plugin architecture that allows additional file types to be supported, so it can't actually know the complete list of MIME types to put in the .desktop file at application install time.

Krita makes it possible for plugins to extend Krita with additional file format support. Those plugins come with a desktop file that tell the desktop that krita can load those file types. Of course Krita's main desktop file cannot have the full list of supported file types, because that's implemented by plugins. Most of those plugins are shipped with Krita, but that is not necessary. People can create extra import/export plugins that still need desktop files so your desktop can know that Krita can load this file format.

I'm not completely convinced that's a good reason (compared to, say, having each plugin installation modify a single krita.desktop file or something), but I think it manages to upgrade it from "indefensible."