281–290 of 344 posts
Earlier quoted context omitted.
[flagged]
> Vibe coding a slop website drastically increases your bounce rate and reduces trust in your project. The masses love this. Really! They love their slop like the good little cattle they are. Source: I work in this field with customers, they love the AI-slop corpo-fied website that looks like an app.
Technical audiences do not love AI slop.
Earlier quoted context omitted.
So the C&D was stupid, and so is how their network works apparently. Fundamentally, what Bambu are saying is that they have a right to restrict what software accesses their network. The C&D was allegedly sent to stop distribution of software that was written to access their network in an unauthorized fashion (Allegedly according to their ToS). AGPL covers source code. It does not cover who can access what network wit…
I think the really important part of this is that Pawel modified OrcaSlicer to look like BambuStudio by looking at the AGPL licensed source code of BambuStudio and copying it over. And the function he copied over just set the UserAgent string to some hard coded values also available in the AGPL source code of BambuStudio. He didn't reverse engineer anything. Just went and looked at public code that's free to use for…
Love it; but just wait, I bet Claude surprises you this year.
Earlier quoted context omitted.
So the C&D was stupid, and so is how their network works apparently. Fundamentally, what Bambu are saying is that they have a right to restrict what software accesses their network. The C&D was allegedly sent to stop distribution of software that was written to access their network in an unauthorized fashion (Allegedly according to their ToS). AGPL covers source code. It does not cover who can access what network wit…
> Thus Bambu - like it or not - have a right to limit what software accesses their cloud. You are still free to do whatever you want with Bambu's AGPL'ed software. But they don't have to let you on their network if they don't want to. Even if we take this at face value, it is irrelevant to their legal threat. They demanded the author to stop distributing software. So no they do not respect your right to be "free to d…
They sent a C&D asking him to take the code down. He was and still is free to ignore that C&D. It's simply the easiest, laziest move on their part to get non-BambuStudio software off their cloud. I am sure they are working on software updates right now; their shitty, dickish C&D was simply the most expedient way to stop it.
I seriously doubt they would've taken him to court over it, and also doubt they'll sue this clout- and click-chasing Rossmann idiot either. But a C&D requires almost no effort.
Sending that lazy childish C&D still in no way violates the AGPL.
Earlier quoted context omitted.
I dont understand what the issue is. Theres not really any benefit in having cloud enabled if local is working fine. I have my bambu printer set to local only, and dont miss the cloud offer one bit.
I imagine some (many?) people just enjoy accessing their printer over the mobile phone without setting up VPN, even if said mobile phone isn't on the home wifi.
There's no reason I couldn't access through the cloud on my phone and from Orca locally without any cloud. The spool management is on the physical printer. I don't need Orca to use their cloud; it just needs to chat to the printer.
Earlier quoted context omitted.
There abusing the AGPL. At this point, it’s on principle.
Please explain how they are abusing the AGPL
I can't think of a scenario in which they aren't going to subject themselves to more Streisand effect visibility every time they file an obviously bogus AGPL claim, so why do it??
It's maddening that quite a few people are jumping to defend Bambu here. Principally if you sell a device with a certain functionality and you later modify that device later to remove that functionality that is called theft. It does not matter the slightest bit whether you break into someone's house to physically alter the device or whether you remotely install a malicious software update to do that. But what's even…
Factually, it is not. Maybe you think it should be prohibited -- as I also do.
But the proper legalese here is likely a consumer protection regulation.
Squashing the git history is not cool.
Presumably the original dev that implemented the changes for this functionality that pulled the repo does not want to be associated so some level of squashing was required but yeah, the whole history was maybe a bit silly.
And it doesn't look good. This has me call into question the caliber of developer who made the fork. No sane open source project would allow this to be upstreamed in this shape
Earlier quoted context omitted.
I always put printers (2d and 3d) behind a firewall so they cannot reach the internet. This prevents auto-updates and surprises like disappearing functionality.
I've been bitten by an HP printer auto updating and my aftermarket ink suddenly not being acceptable. Never buying HP again after that.