Sure, that’s covered by my commentary about data exfiltration against the wishes of data or device owners, and about the difficulty of installing the client on the airgapped device.
I believe there are a few legitimate use cases that don’t have a faster/better alternative, but they’re very niche.
LocalSend uses wifi rather than cell but you’re right that a protest could be a good place not to turn on any radios. It’s also a good place not to bring a phone at all, even if you’ve thought in advance to install a visual data transfer program like this. But you have a good point.
I don’t see a lot of use cases where blastQR beats LocalSend. The ones I do see are mostly about surreptitious data exfiltration against the will of device and/or data owners, and those are still complicated by the need to install your client on the sending side.
I’m not sure exactly what you’re saying but you certainly don’t need to drill out rivets to get to it.
I assume you’re talking about the sensor at the start of the tube. Assembly of that one is step 7.19 through 7.21, and attaching the body panel on that side is step 7.40 (maybe look back as early as 7.35 for the prep work).
You might also try talking to Prusa support.
This is a very good point that I neglected. The tube can be pushed in to connect, but must be carefully released from the fitting.
You can look through the assembly manual for the kit version, and find that the black 3d printed elbow that attaches the Bowden tube to the top of the hot end just slides right on. So you might need to undo a tie or two but it should be easy to pop that off and get the filament out.
It sounds like you’re new to consumer products. I have issues with my clothes washer, my dishwasher, my car, and many more expensive and supposedly durable goods that are supposed to Just Work but don’t. And the manufacturer never comes back with an upgrade kit.
Ubiquiti is a great example of a company that sells supposedly prosumer gear with the possibility of firmware updates but actually delivers half-baked garbage and leaves people in the lurch, ignoring longstanding bugs and missing features for years. But their fanboys abound and they continue to sell lots of equipment. It boggles the mind.
I remain thrilled that Prusa is committed to continuous improvement.
Sounds like your advice to OP should be to avoid the bleeding edge Prusa stuff (like INDX), but that it’s reasonable to expect to be pleased with well-baked revisions. Another way to look at that is that they’re more than happy to support hardware for a while after release, with additional improvements. My take is that’s extremely positive, but you’re entitled to your opinion.
I haven’t gotten the Gen 2 upgrade kit yet for my Core One+ but I’m excited about the idea that they’ve reduced bed warping and therefore eliminated the vast majority of the Absorbing Heat step before the flatness check at the start of prints. A gen 2 out of the box sounds delightful.
OP:
My sister wants to get into 3D printing.
Your suggestion: Tell her to order prints from a print farm vendor or makerspace and buy her a nice purse instead.
What?
I’ve been incredibly impressed and pleased with my Prusa Core One+, as a beginner, over the past several months. Assembled myself (I’m a beginner to 3d printing and modeling but not to technical topics) both for cost savings and to have a deeper understanding of how to take it apart if something goes wrong, but it’s been rock solid so far. I was happy to pay the cost premium over Bambu to be on the moral high ground with ethical corporate behavior and production.
YMMV, but I was blown away by how good it was out of the box. I pressed play and it just worked, even with what I thought were ridiculous overhang angles without supports.
That leaves domains. Can’t self host those
You mean DNS? Absolutely can self host those if you have a stable IP address. I ran djbdns for years, although it was on a xen VPS slice in a datacenter, not in my home.
The information you file with your domain registrar includes at least two IP addresses (which can be the same) and names (which must be different) for the primary name resolvers for your domain. The registrar communicates those to the right upstream layer - in the case of .com, that means a query to a.gtld-servers.net asking for an NS record for example.com will get a response with your DNS server’s name (perhaps a.ns.example.com or ns1.example.com) as well as a “glue” answer (in the same response) of an A record that defines the IP address for that name. Any recursive resolver will then ask your server for the subdomain records.
You can update records on your nameserver at any time, but you’re subject to some delays in updating those glue records and it’s not automated, so you really don’t want them to be dynamic addresses.
It gets more complicated with DNSSEC.
If reasonable healthcare was available without employment, the working class would feel substantially more empowered and might even consider such capitalist sacrilege as a general strike. Oligarchs can’t risk it, even if it would appear to increase the profitability of their businesses by removing an enormous part of the cost of labor. They like the chains.
There are many businesses that fabricate one-off parts for individuals through a variety of processes. A lot of them advertise on maker or engineering channels on YouTube. PCBWay is one such business although I’m not endorsing them - I’ve never used any of them.
Oh I see what you mean. Niche but important. Thanks for the explanation.