This has been default experience for "normies" for quite some time now. Same for Google gallery which syncs to gdrive.
Just today we had a guy who got similar messages from one drive as one in the blogpost, and made the mistake of asking chatgpt about it. After renaming, moving, deleting and even doing regedit as llm instructef, some of the files went missing, some we managed to find.
Few weeks ago I had to explain over the phone how to setup windows without ms account, and we had to resort to turning off WiFi in the house lmao
I can't speak for the status quo, but for at least the first ~5 years (so until 3 years ago when I last attempted to use it), the JS implementation of Fluent was a mess. Constant issues with incomplete API, wrong TS typings (which at that point were external) and build/bundling issues to the point where we opted for a homebrew solution.
I imagine that I probably wasn't the only one driven away by that (and I gave it many attempts!).
The standard is, for better or worse, gettext; it's good enough that any attempt to replace it runs into the problem that people can't agree on how much better an alternative needs to be to be worth migrating to; so you get a constant churn that so far hasn't seen any clear winner.
Feels like it's That XKCD page; there were standards like gettext, then web development came along and a load of people (...present company included) rediscovered localization and pluralization through trial, error, half-building one's own localization library, then the JS world reinvented it, etc etc etc.
Wow, the in-browser preview is excellent. I first assumed it was just a demonstration and appreciated it very much, but then I realized it was live-editable and was blown away.
I went into a slight hunt for more knowledge after reading this, and long story short you need to search NFMI (near field magnetic induction)[1]. As far as I can see from my limited reading the main use case of the tech is nfc (near field comm) and true wireless earbuds.
Public transport in London is world class. Most people don’t even drive into London, let alone inside the congestion zone. And this was true even long before the congestion zone was created.
This is some 1960s level of optimism lol. While I applaud the authors enthusiasm, this will break as soon as a warship shows up at your free city, and your society (made up of people who avoid governments as much as possible) turns out to not be willing to fight for yours. This doesn't have to be a warship - I would wager that at first major obstacle many would defect.
The closest historical analog seem to be Jewish communities of medieval europe, perhaps up to 1900s. They could sometimes get different treatment, and had some structures, although never as centralised. Some countries even wanted them for their knowledge/skillset and connections (?) which lines up with digital nomad's attributes.
>I think lots of non-EU and non-technical bloggers would likely see the email I had and think they were in breach of something like you say they are probably not.
Not only that, but the whole section on "Consider these scenarios" simply described the same thing as an API each time, but added words like "smoothly" and "richer" to make it sound different.
I honestly think most of the article was written by an LLM.
The structure seems very LLM-ish. And the details are blurry:
> Two-way communication: MCP supports persistent, real-time two-way communication - similar to WebSockets. The AI model can both retrieve information and trigger actions dynamically".
How do normal paper printers work on such networks? From what I gather there is some standardised solution to that, wherein here bambu requires their own "connect" software, correct?
I think that big enterprises are full of old systems that are put on vans, vpns, conditional access rules etc., so it's weird to me that ftp is such a problem?
There is also a point in their tos: 7.4 - boils down to "your printer will block printing until you accept critical security patches" that directly contradicts the linked blog post
Normal paper printers concentrate print services to a Windows or Linux print server that authenticates users before they submit a job. All the direct ports on the printer are firewalled and restricted to the print server.
The main issue is that paper printers are a terrible legacy technology that didn't evolve much and are grandfathered into corporate security, whereas any new technology or new vendors have a much higher bar to pass before they're let on networks. Yes, there are many workarounds like VLANs, firewalls and black hole routes etc but they're usually treated as exceptions these days.
The TOS is meant to cover worst case scenarios, such as, the x509 certificates on the printer expire, or a major vulnerability is found. The printer is a hybrid cloud connected or LAN connected service and thus it's reasonable to warn users they need to update periodically because Bambu doesn't want to be exposed by for unpatched backdoor attacks etc. This is a similar issue with MacOS or Windows where you cant use your web browser securely after a few years of missing updates, or other connected devices where you must consent to automatic updates to use the device (Google Nest or Amazon Ring devices come to mind). Bambu is actually being better than most device companies in that they are just requiring this for crucial security updates and they don't require an internet connection: you can patch it via SD Card.
WHO wasn't supposed to be a tool of soft power, and the fact it turned to one makes the decision to leave it all more valid. What soft power does a healthcare organisation provide, that couldnt be better served by your own means?
