It’s a major contributor to the fragmentation of the internet into information black holes along with the other “social” media.
It’s the wrong tool to organize an effort to maintain an open access repository of information.
1,523 karma · joined April 1, 2020
It’s a major contributor to the fragmentation of the internet into information black holes along with the other “social” media.
It’s the wrong tool to organize an effort to maintain an open access repository of information.
Instead, he raced to tweet it. This is just dumb.
It's not hard to effect change over time with a few memos (e.g. no more "pregnant people") and reviews. It may not be quick enough for certain items already in motion, but that really doesn't matter if the pipeline quickly empties out as the memos take effect.
The scorched earth policy is intended to sow fear.
I'm still waiting to become magnetic! That and I want to shed spike proteins like a Pokemon.
Similarly, as fast as processors have gotten, people still complain their applications are slow. Because they do so much more.
Generally applicable ML is still in its infancy, and usage is exploding. All those newfound spare cycles will get soaked up fairly quickly.
> Whatever Bambu does is whatever Bambu does, you need to accept it.
And maybe it is time to take your ball and go home.
> What would Bambu's motivation be to do that?
What is Bambu's motivation for being cloud first when it is not technically necessary? Why can't OrcaSlicer be a first class citizen like BambuSlicer? Instead it has to go through Bambu Connect which is inherently clunky and less featureful. It's simple. Control, and vendor lock-in. Possibly, Bambu sees this as a way to curtail print farm automation software from other vendors.
Bambu is forcing its customers to use its cloud offerings when many users want to use the machine on their LAN without the cloud guff. Many for security reasons. Bambu essentially tells its customers to pound sand, they are forced to use cloud. Now Bambu is claiming it has a cloud DDOS problem and therefore it is going to lock down what users can do further. I'm sorry, that's just silly. Let me connect to the printer locally, and your cloud DDOS problems go away.
The DDOS problem itself doesn't sound particularly compelling as a justification for this action, either. If every user action is authenticated, you know which users are abusing the system - throttle them or kick them out. Adding a TLS certificate for mutual authentication is going to reduce the DDOS overhead by a negligible amount.
> forcing a constraint on the approved software clients
Which will do nothing against a determined DDOSer since they will always be able to extract the certificates from Bambu Connect, or BambuSlicer.
Finally, if the issue is airtight security for the on-prem printer and preventing a hacker external or internal to the LAN from exploiting them. Maybe Bambu can take a page from the Matter smart home specs. if they are out of ideas. These are solved problems. Cloud not necessary. Software lockdown not necessary.
Yes. That's where the maintainers need to decide if they are Bambu Lab's lackeys or if they have a say in their beloved project. Part of that is thinking about at what point the project becomes pointless as a meaningful BambuSlicer alternative.
> The alternative is that users have to manually use bambu connect and that seems inferior to what the PR enables.
Everything is going to be inferior to using BambuSlicer. That is Bambu's real intent.
The OrcaSlicer maintainers probably have the most leverage (what little there may be) on Bambu Lab. I think that is why Bambu Lab is keen to offer the PR on GitHub. The maintainers should exercise whatever leverage they have while they still can.
Bambu Lab is introducing something else. Most charitably, it could be described as security through obscurity, which is never secure. More realistically, Bambu Lab is introducing vendor lock-in under the pretext of security. Vendor lock-in is what this change actually achieves.
It's clear you like your Bambu Lab printer/s. But I think you are letting it cloud your judgement. Bambu Lab is being predatory here.
I don't know if the OrcaSlicer maintainers feel this way. But if they feel that Bambu Lab is stabbing them in the back, they don't have to jump when Bambu Lab tells them to (that's pretty much the raison d'être of open source).
This isn't a security fix. As a security protocol, it wouldn't pass any kind of security audit. A security fix would be something based on a per user credential, not on obscurity.
> Personally I don't want any device or application to send any old G-code to my printer.
Username/password over TLS would do that better than what Bambu Lab is proposing, as an extremely simplistic example.
You would never allow your bank account to be secured with something akin to Bambu Lab's "security fix".
The BLM riots were an aimless mob of malcontents.
I do remember being frustrated by the endless papers on SCARA and the importance of the inverse kinematics but no mention of what they actually were. So here they are. (I just checked now, and there seem to be at least a few papers online with the derivation. Times have changed)
I also have this:
def do(self, (x, y), (dx, dy)):
""" Calculate o derivative (do1, do2) given position (x, y) and desired movement derivative (dx, dy)
"""
xy2 = x**2 + y**2
ll2 = self.L1**2 + self.L2**2
lld2 = self.L1**2 - self.L2**2
# do1
N = x*dy - y*dx
M = xy2
P1 = x**4 + 2 * x**2 * (y**2 - ll2) + y**4
P2 = -2 * ll2 * y**2 + lld2**2
P = P1 + P2
Q = xy2
PQ = math.sqrt(-P/Q)
R = (xy2 - lld2) * (x*dx + y*dy)
S1 = math.sqrt(xy2)
S2 = P
S = S1*S2
# do2
T = 2 * (x * dx + y * dy)
U1 = (2*self.L1*self.L2)**2 - (x**2 + y**2 - ll2)**2
U = math.sqrt(U1)
return -(PQ*R)/S + N/M, -T/U
For this I used a symbolic solver but I don’t remember what it was. I also don’t remember if it was a meaningful improvement over a simple interpolation between angles.BTW if memory serves, parsing basic SVG is pretty easy. Though, these days it may be more useful to implement a gcode parser as there are so many freely available gcode generation tools.
o1 = atan(y/x) - acos((x^2 + y^2 + L1^2 - L2^2) / (2 * L1 * sqrt(x^2 + y^2)))
o2 = acos((x^2+y^2-L1^2-L2^2)/(2L1L2))