Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Reverse Engineering Bambu Connect

wiki.rossmanngroup.com

Post reply on HN
Print view View original

201–210 of 367 posts

Re: Reverse Engineering Bambu Connect

#201

Post by mft_ »

askariwa wrote: post #105
DrBenCarson wrote: post #78

Earlier quoted context omitted.

AFAIK, Apple has never retroactively removed functionality from devices people already purchased Selling a walled garden is one thing, building walls around a garden you already bought is another thing entirely

Just some of them: - Battery Management (iPhone 6, 6s, and SE): In 2017, Apple introduced a battery management feature in iOS 10.2.1 to prevent unexpected shutdowns by throttling the performance of iPhones with degraded batteries. This led to slower device performance without informing users, which is a removal of expected performance functionality. - 32-bit App Support: With the release of iOS 11 in 2017, Apple drop…

The big difference is that none of these changes were part of a defined strategy to lock the user in to their products and ultimately generate more profit, as with the Bambu example:

- Battery management was to handle an issue that was encountered as batteries aged

- 32 bit support: Apple is well known for being one of the more aggressive companies when it comes to forcing users (and especially people coding apps for their platforms) to adopt required tech changes. But again, not directly profit-driven.

- Pulse oximetry: probably the closest to a profit-driven-decision, as this was driven by a patent issue, and presumably they calculated less of a hit from removing the feature than paying feed to the patent owner? Not great, but still not directly part of a user-unfriendly Apple-derived strategy, as with Bambu.

Re: Reverse Engineering Bambu Connect

#202

Post by piaste »

jumski wrote: post #180
Arch-TK wrote: post #176

Earlier quoted context omitted.

Currently the only thing which won't run on a non-google blessed android build is google wallet, although a lot of applications rely on google's proprietary services exposed through google play. I've not ran into any banking applications which won't run on a non-google build of android (as then they would only run on a pixel). That being said, I refuse to seriously bank with any bank which doesn't offer a functioning…

Revolut stopped working for me on GrapheneOS with an official message "Sorry, Revolut is not supported on devices with custom firmware".

Do you have the sandboxed Play Services installed? It works fine for me on Graphene (just checked).

That said, the recommendation I always give, and personally follow: keep a spare phone in a drawer somewhere, with official Android installed, a Google account, and use it exclusively for business purposes - banking, government services, and the email account you use for those (separate from the one you use for everything else). Nothing else, no messaging, socials, browsing, or games.

Then you're free to keep your personal phone FOSS and as private as you like, without fear of getting locked out of important stuff due to a crappy Google® SafetyNet® upgrade.

Re: Reverse Engineering Bambu Connect

#203

Post by 63stack »

Arch-TK wrote: post #176
ulrikrasmussen wrote: post #91

Earlier quoted context omitted.

This is the Google model then. Base everything on open source, even allow unofficial builds of your operating system (LineageOS, Graphene), but slowly introduce more and more device attestation and DRM so it becomes de facto impossible to actually use anything but the closed builds because everything from banking apps and electronic identification apps to streaming apps will refuse to run on your "unsafe" operating s…

Currently the only thing which won't run on a non-google blessed android build is google wallet, although a lot of applications rely on google's proprietary services exposed through google play. I've not ran into any banking applications which won't run on a non-google build of android (as then they would only run on a pixel). That being said, I refuse to seriously bank with any bank which doesn't offer a functioning…

Anything that depends on the SafetyNet API will not run if your android build does not pass the checks, the list is much much bigger than "just google wallet". Whether a rom passes safetynet or not very much depends on what google considers blessed today, and what they will consider blessed in the future.

Re: Reverse Engineering Bambu Connect

#204

Post by esskay »

kiba wrote: post #199
esskay wrote: post #187

Earlier quoted context omitted.

The problem is even with Prusas recent efforts to catch up with the Core One, it's expensive, and they still dont have a viable answer to the AMS. The MMU is still a hot mess, requires tinkering, isn't stable and overall just doesnt come close to an out of the box experience. They still seem to be thinking the primary audience of 3d printers is people who tinker. It's not been that way for a long time. People just wa…

A Prusa MK4, completely factory built, is a reliable workhorse for me.

I didn't suggest otherwise, nor was that even part of my point.

Re: Reverse Engineering Bambu Connect

#205

Post by ulrikrasmussen »

Arch-TK wrote: post #176
ulrikrasmussen wrote: post #91

Earlier quoted context omitted.

This is the Google model then. Base everything on open source, even allow unofficial builds of your operating system (LineageOS, Graphene), but slowly introduce more and more device attestation and DRM so it becomes de facto impossible to actually use anything but the closed builds because everything from banking apps and electronic identification apps to streaming apps will refuse to run on your "unsafe" operating s…

Currently the only thing which won't run on a non-google blessed android build is google wallet, although a lot of applications rely on google's proprietary services exposed through google play. I've not ran into any banking applications which won't run on a non-google build of android (as then they would only run on a pixel). That being said, I refuse to seriously bank with any bank which doesn't offer a functioning…

This is false. List of apps which refuse to run on my old OnePlus 6 which I revived with LineageOS:

- Danish national identity app (MitID). I had to get a hardware token that generates one-time passwords.

- My banking app (still works in the browser though).

- The de facto payment app used for peer-to-peer payments and as a credit card alternative all over Denmark (MobilePay).

- The app for controlling the heating system in my car.

- Revolut.

- The app for showing a digital version of my government issued health insurance card. It's literally just a barcode and a number, so I can get by using a photo of the card instead. This underlines the ridiculousness of requiring Play Integrity attestion.

- The app for showing a digital version of my driver's license. As a bonus this app also doesn't work if you have set your default browser to Firefox instead of Chrome, even on a non-rooted phone.

On top of this, one app for scanning goods in the supermarket stopped working, but without explicitly saying why. I suppose it just silently depends on some Google service, but I have not way of knowing that.

I also cannot get Chromecast to work, but that is perhaps to be expected when replacing the Google services with microg, and not strictly a result of DRM. It is a major inconvenience though.

Denmark is one of the most digitized countries, and in many ways that is good. However, it also means that you are increasingly coerced into the whole Google/Apple ecosystem and that it is very hard to get out. Luckily there are alternatives to all of the above apps, but it is a major inconvenience to have to use them.

Re: Reverse Engineering Bambu Connect

#206

Post by intothemild »

c0nsumer wrote: post #21
bdcravens wrote: post #9

Earlier quoted context omitted.

They used a plugin to communicate print jobs (and other integrations), so that third party software could be used pretty seamlessly. Now they're moving to a new authentication model, and will be requiring users to send files to a separate print app. (Bambu Connect) It adds friction to the process, especially for those who were looking to run print jobs at scale, using "print farm" software or building their own solut…

I do wonder how much friction it'll really add, since the slicers can send the data to Connect via a protocol handler. It also means that Connect could act as a farm / queueing system as well, more like a print driver vs. individual printer support within the app.

Its pretty much this, nothing seems to be blocking any third party slicer like Orca from working with bambu printers as they are now.. just the print button would now send the file to Bambu Connect, where you would most likely only press an extra button..

Getting info from the printer or AMS? MQTT still works. They specifically said they are not touching that.

Sadly the usual groups of people are screaming, and the open printer people are laughing. But at worst.. this is just friction.

Anyone pointing this out seems to get downvoted. But its all there in the bambu press statement and subsequent pages. Those that are upset seemed to have not read those, and instead just read or watched something inflammatory.

Re: Reverse Engineering Bambu Connect

#208

Post by bayindirh »

Arch-TK wrote: post #176
ulrikrasmussen wrote: post #91

Earlier quoted context omitted.

This is the Google model then. Base everything on open source, even allow unofficial builds of your operating system (LineageOS, Graphene), but slowly introduce more and more device attestation and DRM so it becomes de facto impossible to actually use anything but the closed builds because everything from banking apps and electronic identification apps to streaming apps will refuse to run on your "unsafe" operating s…

Currently the only thing which won't run on a non-google blessed android build is google wallet, although a lot of applications rely on google's proprietary services exposed through google play. I've not ran into any banking applications which won't run on a non-google build of android (as then they would only run on a pixel). That being said, I refuse to seriously bank with any bank which doesn't offer a functioning…

None of the unofficial Android builds allows me to access to the secure element in my SIM card to use my e-signature, which works with SIM menu prompts triggered OTA by the application I'm currently using, mostly governmental services.

If I'm on a custom ROM, the notification never pops up.

Re: Reverse Engineering Bambu Connect

#209

Post by elcapitan »

As a precaution, I've blocked my A1 mini from Internet access on the router, and will not apply any firmware updates anymore. I will also not update Bambu Studio anymore (or completely switch to Orcaslicer). I was already using LAN mode exclusively.

Kind of annoying, but I'm not desperately waiting for Firmware updates, everything works fine so far.

Re: Reverse Engineering Bambu Connect

#210

Post by CarVac »

esskay wrote: post #194
bborud wrote: post #171

Earlier quoted context omitted.

I ThouYS may have a point. It seems to me that Prusa were tempted to go after the prosumer/pro market and invested a lot of time and engineering horsepower into higher spec machines (Prusa XL, HT90) and resin printers (SL1S). A lot of 3D printer companies have tried to go this route. It is not a strategy that tends to succeed. I don't know their sales numbers, but I would be willing to bet that the ROI on those print…

Thing is even with the core one finally releasing...its not a compelling product. It costs more than the P1S - which lets fact it, thats what it should be compared to, not the X1C as the Core one doesn't have the stronger nozzle, nor any features that would make it a 'pro' level product. They also still dont have an answer to the AMS, which is a big selling point for the Bambu's. The MMU3 may be better than the previ…

> not the X1C as the Core one doesn't have the stronger nozzle

Swapping nozzles makes the machine worth double?

Post reply on HN