Oh, I was using Keepass2Android as a password vault, but was a little frustrated with it because occasionally it’ll forget to synchronize with the file before adding an entry and leave a “conflicted copy” I have to deal with manually. If KeepassDX will also do TOTPs that sounds perfect.

Do you have a replacement you would recommend?

I definitely considered FFmpeg (I mean, it does everything, and pretty much as fast as possible), but the sense I had was that people were mostly posting about tools that were reasonably accessible to novice users, with nice-ish interfaces. FFmpeg is pretty daunting to newcomers.

OpenSCAD (CAD, but with a programming language-style interface) is kind of in a similar category. It’s pretty powerful, and for someone who thinks like a programmer it can be relatively easy to learn, but if you don’t already understand 3d transformations on a pretty intuitive level, the program doesn’t have a lot of features to ease you into that.

Adding on:

Inkscape - vector graphics program

Meshrom - photogrammetry

Handbrake - video transcoding

MakeMKV - rips DVDs and Blu Ray into video files

7zip - file compression and decompression

Droid48 - Truly excellent HP48 emulator for android

LibreOffice - free word processor & office suite (not without some recent drama though, I guess)

I’m sure I’m forgetting plenty, but hey, more for additional commenters to name.

Edit: Removed Audacity, apparently I’d missed privatization drama around that one too

The “idiot” part comes in where I encountered this problem, and didn’t even stop to consider whether this might be specific to this model, or even try something as basic as turn the model on the print bed, which wouldn’t have fixed the slicing, but would have told me my assumption about how the “bridging angle” setting worked was wrong. Instead, I leapt straight from “huh, this model sliced in a weird way” to “this basic slicer feature is designed in a bizarrely poor way and I’m the first one to ever notice,” and posted about it on social media.

So I appreciate the sentiment, and I’ll leave the post up as it I agree it’s a mildly interesting and counterintuitive result, but I still maintain I acted kinda dumb. :)

That wasn’t the issue for me–my bridging angle was set to zero (the default). The issue was that the anchors for these bridges ran into one another, which made the slicer treat them all as one single unified bridge, and choose one angle for the lines across them all, rather than treating them as separate bridges (which is how I was thinking of them, because they crossed different gaps). I put the text below the images on this link before I understood what had gone wrong, but the images are still useful for illustrating the error: https://imgur.com/a/VjUTVaq

I was being an idiot. It does bridge correctly, it just got confused because the bridges were close enough together that it thought it had to make them one single bridge. Thanks!

I was being an idiot. It does bridge correctly, it just got confused because the bridges were close enough together that it thought it had to make them one single bridge. Thanks!

Oh, you’re totally right! I knew I was a little braindead today. Thanks so much! It absolutely already does the thing I’m asking for, it just got confused because the edges of the bridges were close enough that their anchors overlapped.

Bridging working normally: https://imgur.com/a/U7yqZU3

Thanks!

I’m using PrusaSlicer, and in PrusaSlicer there is a specific setting for this, which is called “bridging angle.” But my point is that bridges are already specifically identified by the slicer as a specific category of print area needing specific settings, and in this case it should be possible for the slicer to choose an optimal bridging angle on a bridge-by-bridge basis, rather than requiring the user to choose a single global angle. You’re right that it would be less catastrophic for the bridging to be 45 degrees off than to be 90 degrees off, but it’s not obvious why this should be a global setting at all, rather than tailored to the needs of the local geometry of the bridge. It could even be something fairly simple, like just drawing lines parallel to the perimeters of the bridge, similar to what “concentric infill” does. I haven’t really looked in to what the best way to implement this feature would be, I’m still at the point of trying to work out how to even describe the issue.

Basically this: https://imgur.com/a/VjUTVaq

The blue sections have no support material below them and are printing as bridges, but in the default behavior, PrusaSlicer just uses the single, global “bridging angle” setting to decide which way to print layers on top of these sections. The perimeters on these sections are printed correctly to make the shortest path across the gap, but the rest of the lines making up those bridge layers are printed to match the “bridging angle,” which here means that two of the bridges are printed so they are supported only by those two perimeter bridges themselves.

Please ignore the details of the print itself, as I’m a little braindead today and this is a print that won’t actually fold together correctly as designed. But the issue of bridges orienting poorly is more general than this particular design.

Because they didn’t turn on federation until last year, and at that point it was still limited to fewer than ten users per alternate server, and you had to manually request federation through a Discord server from an actual human. This year they’ve automated the federation process, but you still have to start with a tiny server, and they claim they’re going to raise the user limit gradually as new servers remain federated with the main server.

But yeah, the upshot is bsky.social has 13 million users, and there are no other servers with notable numbers of users. That’s a pretty notable difference from ActivityPub.

I dunno, I think you may be underestimating ARM here. I’ve heard that the overhead from translating the machine code is a lot lower than you might think, because so much X86 code is optimized down to a RISC-like subset of the instruction set already. And if that overhead isn’t too daunting in the common cases, the more robust power management on the ARM side of the chip market might be able to make up the difference in a handheld environment for most users. Obviously it’s a huge amount of work to nail the software, and it would be on top of the work they were already doing on Linux, so I’m not saying it’ll definitely be in the next iteration, but I could definitely imagine it happening eventually.

It’s the “with which we are okay” that sounds a little stilted. Most speakers would probably phrase that part of the sentence as “which we’re okay with.” It’s just because “okay with” is so common that it almost feels like a transitive form of the verb “to be okay,” so splitting apart sounds odd.

Note that there’s already a different transitive verb “okay” which means “approve” or “authorize,” as in “the boss okayed your plan to use the forklift,” implying that the person doing this has authority or control over whether the thing happens. “I’m okay with it” by contrast typically means something like “I have no control over it but it also doesn’t trouble me.” “Unfazed by” (spelled in this way, not related to “phase”) would be a similar expression.

Kinda feels like moving out of America ought to be covered by my health insurance, really

Sound doesn’t travel as far through warm humid air, so the world feels a little more muted and calm. (Contrast this with the dry, dense air of a frigid winter day, when the sound of cars carries for miles as a dull growl.) The light is almost entirely diffuse thanks to clouds, rather than the sharp glare of a sunny day; your skin isn’t dried out and burned in the same way either. Public spaces aren’t as crowded. Indoor rooms are often lighted more gently as well without sharp sunbeams drawing lines. Add the sound of rain itself and the faint smell of petrichor, and the improvement in the air quality as the rain washes particulate and pollen into the gutters, and you get a perfect day to curl up with a book, a cup of tea, and a cat on your lap.

Wasn’t the phrase supposed to be “Primus sucks”? I seem to remember that being a self-identification thing for fans back in the day.

If I’m remembering correctly, this phrase was immortalized in a Primus track at one point. There’s a weird, short track (or maybe an intro to a longer song?) on “Sailing the Seas of Cheese” that’s just one guy singing along with running water, and as I remember them, the lyrics are: “As I stand here in the shower, singing opera and such/pondering the possibility that I pull the pud too much/there’s a scent that fills the air; is it flatus? just a touch/and it makes me think of you.”

Which apparently is still in my brain, even though I didn’t think I’ve listened to that album since the 90’s. My brain is weirdly prone to storing old audio, though.

Oh, cool! I didn’t know about that. I might actually check it out once that’s released.