monotremata

In addition to “format shifting,” which is a well-recognized use case, and game preservation, which is a huge and under-recognized public interest in emulator development, emulators are also used for the development of homebrew software. E.g., there’s a port of Moonlight for the Switch, which lets you play Steam games streamed from a PC using your Switch, letting it serve many of the purposes of a Steam Deck. That’s huge! It would be way less practical to develop this kind of software if you could only test on real hardware. Testing on real hardware is also essential, of course, but testing on an emulator is vastly faster for rapid iteration.

Honestly what the homework is probably looking for is that it’s equivalent to “B or not A.” But yeah.

Doesn’t the “missed step detection” on the Prusa printers already achieve a lot of that? I think it monitors the current to the motor and flags any abnormal behavior, without needing extra hardware on the motor.

That’s not to knock the value of positional feedback, which is clearly superior, but just to say that I don’t think this idea has been entirely neglected.

I had a similar issue on my Pixel 6, where I’m using Nova launcher. (I know they changed hands and are not great now, but it’s still more usable than the Pixel Launcher.) There the solution was to go into the Apps settings, find Pixel Launcher, and choose force stop, then clear cache, then clear settings. Apparently there was some bug in Android 14 causing both launchers to try to intercept the “recent apps” press, and it caused it to hang like that.

Obviously that’s not going to be exactly the same issue on your phone, since presumably Pixel Launcher isn’t on there, but maybe doing the “force stop, clear cache, clear storage” on the default launcher on your phone would help?

It’s also used for sending huge amounts of data long distances. “Never underestimate the bandwidth of a station wagon full of tapes hurtling down the highway.” That’s usually attributed to Andrew S. Tanenbaum, but wikipedia follows that with “other alleged speakers include…” so take that with a grain of salt. They do note that the first problem in his book on computer networks asks students to calculate the throughput of a Saint Bernard carrying floppy disks.

putting the “ad” in “advent calendar”

Oh, I literally misread it as OpenSCAD. Laughing at my stupid brain right now.

I’d say it’s more like Premiere vs ffmpeg.

I dunno, I prefer swipe typing and this doesn’t seem like it would work with that.

To me the biggest barriers to long-form typing on the phone are that so many websites screw up form handling for long-form content, and that the cursor maneuvering is still pretty broken.

Websites do weird things when you’re typing. Sometimes the input field won’t scroll, so you can’t see what you’re typing. Other times it’ll force-scroll to put the current line you’re working on at the very top of the screen, so you can’t see anything you wrote previously. At least they finally fixed the weird behavior where if you deleted more than a few characters it would start jumping around in the text and duplicating huge sections of it–I think it was around Android 9 that they finally fixed that.

As for moving the cursor, the “swipe on the space bar to move the cursor left and right” works, but trying to go back further, like going up a few lines, is very, very difficult. The cursor will scroll the text box if you move to the edge, but there’s no delay in the scrolling, so instead of scrolling a couple of lines and then pausing briefly to give you a chance to stop there, it just immediately scrolls again on the next frame of rendering, so effectively your choices are “scroll within the few lines of text still visible” or “jump all the way to the beginning of your text.” Anything else you need to scrub through character by character using the space bar control, which is very slow.

Basically, I don’t think the issue is the keyboard itself. I think the issue is that Android has never prioritized long-form text entry, and so it’s just very buggy.

The timeline should be at the bottom of the editor window, if you’re in the default design workspace. If you started in the mesh editor workspace then “design history” might be turned off, in which case you wouldn’t have a timeline. It looks like this:

https://help.autodesk.com/cloudhelp/ENU/Fusion-Assemble/images/animation/timeline-groups.gif

If some of the icons are highlighted in yellow, those have errors, so, things like broken projection links, or missing objects for some operations. You can usually fix those and patch things up.

Edit: oh, sorry, just realized you were working from someone else’s file. That might not have design history turned on. The person who told you how to edit the extrusion operation has the right idea.

Did you get any warnings or errors when you changed the parameters? Are any of the elements in your timeline highlighted in yellow?

Fair enough, I only got in to the hobby around 2015. But site issues were another reason that a lot of folks migrated to printables recently, so I do think it’s possible that’s part of what Fogle was referring to.

FWIW though, I suspect that a lot of the folks here in the Fediverse do actually care about open source, open standards, and the value in defending truly public resources.

Well, also just that the site had kind of deteriorated from lack of maintenance–the search didn’t work (you had to use Google with site:thingiverse.com), model pages were incredibly slow to load, etc. They’ve fixed a lot of that recently, but for a year or so it seemed borderline unusable.

Could still be temperature if the thermistors on e printers read differently–that is, the same setting doesn’t necessarily work out to the same physical temperature on two printers, even if they’re the same model, because the thermistors vary. My suspicion would be that you’re printing a little hot, and the filament is contracting after it’s extruded. On the first few layers it can’t shrink much because of all the material in the middle, but on the vase mode layers there’s nothing preventing it.

Another possibility is that your overlap percentage between your infill and perimeters is too high. This leads to something that basically is overextrusion, but it’s usually visible as more of a ripple.

A third possibility is that it’s just the filament.

Honestly, Google killing this will probably be the best outcome for it, because otherwise they’ll try to monetize it, and that could be a nightmare. Just a straight-up conversation partner that tries to wheedle personal information out of you for their advertising profiles. Even their example question about what you like to do for fun is a little uncomfortable in that context.

Attack ships on fire off the shoulder of Orion…

Fakespot used to reveal more about how they detected fakes, but as you say there are obvious issues with that, as it’s a bit of an arms race. They don’t just look at the text of the individual review though. Folks who buy reviews tend to get them from “review farms” that do reviews for a lot of products, and they don’t have an infinite number of Amazon accounts to use for that, so there are network effects that can be powerful indicators, and that aren’t easy for manipulate.

It also doesn’t with with PLA and ABS. Same issue, they won’t stick together well.

And when you say “laser or printer” here, are you referring to a 2d printer, or a 3d printer?

The questions are because, fundamentally, a wireframe image like the one you linked is just a different way of rendering the same file. So if what you want is literally an image like this, then there are tools to do that, which will depend a bit on what operating system you’re using. Blender, as mentioned in another comment, is one such option.

If, on the other hand, what you want is a 3d printable structure that resembles a wireframe rendering of the object, that’s a more complicated task. The STL file just lists the triangles that make up the surface of the object; in order to make a solid structure that resembles this, you’d need to create a solid (e.g. a cylinder, maybe with balls at the ends) for every edge in the file (3n / 2 edges for n triangles, since every edge in a properly printable [“manifold”] STL is shared by two triangles) and then takes a boolean union of all of them. I don’t think a tool to do this exists currently, as it’s a rather specialized need, but it wouldn’t be too hard to throw together a python script that could take an STL file and generate an OpenSCAD script that you could then render with OpenSCAD to get the STL.

Specifically, the 8 pro has a 5x telephoto 48mp sensor that the base model lacks, a 48MP wide angle sensor compared to 12MP on the base model, a thermometer the base model lacks, 12GB of ram vs 8 on the base model, and a slightly larger and brighter display and slightly larger battery (though the gain in battery is probably roughly offset by the increased power draw of the screen). I believe those are the only hardware difference.

Source: https://www.phonearena.com/reviews/Google-Pixel-8-Pro-vs-Pixel-8-Google-is-about-to-reap-the-harvest_id5921