Re:Porting USB applications to the web. Part 1: libusb
by jandrese on Thursday January 20, 2022 @01:06PM
(#30012395)
It won't be cached on the Internet Archive because the site is hidden behind a signup link and DRMed to your printer. The company will go after third party developers with legal threats like all closed hardware companies.
Re:Porting USB applications to the web. Part 1: libusb
by RReverser on Thursday January 20, 2022 @01:10PM
(#30012428)
Companies that want to do so, already embed "ring home" mechanisms in their apps that periodically connect to the Internet and check that you still hold a valid license or refuse to continue working.
It seems this depends a lot more on the company policy rather than specific technology used for the implementation.
Re:Porting USB applications to the web. Part 1: libusb
by RReverser on Thursday January 20, 2022 @12:58PM
(#30012293)
You can likely visit the old version of the website via Internet Archive or save an offline snapshot yourself if you want, so it would be no different to driver on an offline computer.
Re:Porting USB applications to the web. Part 1: libusb
by folkhack on Thursday January 20, 2022 @01:15PM
(#30012495)
Have to disagree here. Anything remotely complex with JS usually doesn't work as-expected after archived on Internet Archive. Keep in mind we're not talking about a LAMP-driven WordPress blog with some jQuery sprinkled in - we're talking about an actual piece of software running in the browser ie: device driver.
In good faith I would not expect something which uses experimental browser APIs to maintain functionality when archived by Internet Archive's automated crawling solutions. Same applies to offline saving.
Re:Porting USB applications to the web. Part 1: libusb
by RReverser on Thursday January 20, 2022 @01:18PM
(#30012529)
Good point regarding the offline capabilities, I'm not sure how well the Internet Archive will handle Wasm, but for the rest - WebUSB was already stabilized and isn't considered experimental (although I admit that didn't stop some other non-cross-browser APIs from being removed in the past).
Because you can’t force a company to keep a website up and running. But you can keep a driver on an offline computer.