I love systemd timers! I've slowly moved all of my ansible-deployed cron jobs to timers (now just an ansible copy!). The integration with journalctl, especially in a newer OS like Debian 13 where syslog is gone, is really nice. It's also really nice to be able to start the service manually for debug. Having a cron job that didn't work was an annoying exercise in copy/pasting or writing an extra shell script. Don't even get me started on the black hole of cron job stdout. I can monitor systemd services like I already do and get a notification on failure.
I've noticed more and more open source projects recommending timers as a deployment method and I think that's great!
I wonder if you would get good enough results by just extruding two separate filaments simultaneously. Sure, they won't fully mix, but with thin enough layers, you'd benefit from the same visual processing that makes alternating layers look like a solid color...
Dual color filaments exist, and they do not mix at all... It gives the objects a nice transition when rotated. But indicates that color mixing in the nozzle is probably pretty difficult?
> In further digging, we noticed that the URL the phone opens up is “kira-abboud.com,” a website that references fashion influencer “@kirasfashionfinds.” Notably, this exact URL isn’t listed anywhere on Abboud’s social media, and the affiliate codes don’t match up either. The redirect coming from Motorola phones is using Amazona affiliate code “sramz-kff-008-20” which is completely different from any of the codes we saw from links shared by Abboud’s accounts and linked websites.
Something funny is up; this doesn't seem deliberate.
I agree, but in fairness, I don't know of any brand, tech or otherwise, that can completely wall itself off against insider threats. No matter how vigilant you are, someone who knows exactly how you move will find a way around you.
I can understand it's hard to defend against plausibly deniable errors that create backdoors, etc. But this would show a complete lack of code review, no?
> But this would show a complete lack of code review, no?
You'd be surprised how many websites use Google Tag Manager to allow their marketing department to roll out trackers and other JS snippet directly into the site's root context.
GTM et al's sole reason of existence is to provide marketing people with a way to bypass corporate IT.
And I definitely would not rule out something like this being the cause in the end.
Not even that. Bury it in a sufficiently-large PR and there’s a very good chance it’ll be rubber-stamped because no one wants to take the time to carefully review the entire set of changes.
> The standard defense for something like this is "the plugin is a separate work, so it's not subject to copyleft." That argument falls apart on contact with the actual software. BS cannot do its primary job without the plugin. The plugin cannot do anything without BS.
But that's just not true? You can connect a printer in LAN/dev mode and print directly from slicer to printer. There are apparently some issues with more complex network setups but that seems to be the exception rather than the rule.
I think the concerns he has generally are valid, but I have yet to see something from a legal perspective (e.g. precedent) that convinces me this constitutes a license violation. Would love to see one.
I wish there were a "strict" yaml. Another subset a la json, where you don't have nonsense like no === false, but "no" does not, but you also get the block style which to me is easier to read and write. I don't mind requiring quotes for strings. Modern IDEs make it easy enough and it removes ambiguity.
It's surprising to me that bun is so much faster serving web requests. The article mentions Zig as a factor, but is micromanaging memory really gaining over 2x vs node?
Similarly, it seems, though they didnt exactly say, that they're running bun with a warm package cache... What about the others? Do they have caches?
All the developments are done in a virtual remote file system. From editing to compiling, everything is done remotely. Of course this does not fully stop people from doing manual c&p, but it still makes it hard enough to discourage it.
I have no knowledge of actual enforcement mechanisms, but it is way, way, way easier to do all development on the distributed file system that feels like a local disk than it is to copy things over locally.
If you need to do development locally, you are either doing something very wrong or extremely specialized.
So there is effectively no motivation to copy the sources over. And because everything is on this distributed file system and built from it in a very bespoke environment, I would imagine (with no inside knowledge at all), that it is easy for auditors to detect when someone starts copying things out.
I don't think so. They can already track popularity very effectively because they control makerworld, and they could have Bambu studio, the app, and the printer phone home too. I don't think they care enough about the tiny tiny minority of users running orca with a LAN only printer.
More likely, it's technical incompetence. It's just easier (for their cloud) to send everything through their cloud
I think OP meant designs which are not on MakerWorld.
And I think technical incompetence is not a reason here otherwise they wouldn't gatekeep the access so much.
I don't think they baited and switched? I bought my P1S before the whole LAN mode debacle and even then it was all or nothing on the cloud. I just went with the cloud because they were using some IGMP stuff for the local connection, but I had the printer on a separate VLAN and pfsense IGMP proxying was broken.
A different way of looking at it is that Bambu is saying if you want to use their cloud you have to send everything through their cloud. Stupid? Sure. It's very much a technically solvable problem. But I don't think there was any rug pull (this time; in Jan 2025 they tried...)
I think this is all more out of incompetence than malice. Something bad happens, exposing wildly inadequate programming expertise, they panic and over correct, and the community pushes back. They're great at making 3D printers, terrible at cloud infra.
For me, I want to use orca for slicing there are many more additions to the local code. As both orca and Bambo are from the same open source, the current limitation in the Bambo version is breaking the licensing of the application, and my rights in that software are broken by this addition.
Then, during the print, I'm really happy to use the handy app to monitor the progress. This use case was supported when I got the hardware. Now I have to disable the app to get the slicer. I actually like to use both slicers to compare and see progress.
They are also terrible at software licensing, don't understand what open source is, and they found their main software on that. They probably should embrace the orca community and use their research for their own customers. Better slicing helps everyone.
Technically true, because bait-and-switch refers merely to advertising an attractive product offer in order to lure people into a pitch for a different product.
In this case, they actually sold a product, then decided to maliciously alter the product after it was sold to modify its behavior. That makes this a much more serious offense, equivalent to trespass, vandalism, or possibly even burglary.
It's equivalent to selling someone a house that includes a secret entrance that you retain access to, so you can surreptitiously enter the house to steal the new homeowners' property after they've moved in.
I've noticed more and more open source projects recommending timers as a deployment method and I think that's great!
reply