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.

https://en.wikipedia.org/wiki/Near-field_magnetic_induction_...

Thanks, this will be an interesting read.

Those "least well-off" that happen to live in the zone, which is less and less each year due to gentrification

People outside the zone benefit too -- from the tax revenue, the reduced pollution, and every time they visit.

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.

This is true for all laws, all scams, all ads.

The article has the same usb-c photo three times, but doesn't actually explain what it is, or how it works.

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".

This is not what two-way communication means.

unfortunately it is indistinguishable from what a reasonable human high on mcp copium might write

The usb-c metaphor along with most of the text are lifted from the Anthropic documentation without attribution. I'm not impressed with the author.

Author here – fair point! I can def see how it could've used more explanation. I'll update the post - appreciate the heads-up!

How many R's are in "strawberry"? ;)

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?

How do you feel about something like the International Atomic Energy Agency?

I think you're confusing soft power with hard power.

Showing up to do work is how you wield soft power nonetheless, even if it's a side effect.

As for sharing - text fragments could also do for a nice addition: https://developer.mozilla.org/en-US/docs/Web/URI/Fragment/Te...

Yep, Matt (wordpress guy) has a dramatic writing style, but in essence WPE is using plugins, their security research, user system, theming store etc, without contributing back that much.

Worth adding that WPE is owned by private equity, and they allegedly tried to remove the newsfeed from wp-admin to hide his (dramatic) posts about them

My company is also a heavy user of WordPress and never have contributed. We also hide those widgets. Do we need to be blocked as well then?

Does your company offer a competitor to what Automattic is offering, taking revenues from them, and make 500+ millions in revenues a year? If the answer to those is yes then I’d probably keep quiet before Matt notices you :)

That is a really problematic question to ask. Because remember, Automattic is not the Foundation or the open source project...

so then the question becomes "Why is the Foundation/project hamstringing a competitor to their director's for profit company who is, in theory, and legally should be, independent?"

Is your company building a business with half a billion of dollars in revenue out the uncountable amount of man-hours put into Wordpress development?

We probably made a lot more then that in the past 20 years.

We are talking about yearly revenues here, and something tells me that your company is not in the business of selling services that depend on WordPress code being developed

Seems like you should act as if you will be.

I keep seeing people refer to this tweet. Can you share a link to it, please?

I'm afraid not. I look at twitter only in incognito mode and don't have any history, and can't find anything now.

Hiding the widgets isn't the main issue. If you infringe the WordPress trademark in commercial use, and ignore any attempt to make it right, and pursue legal action, W.ORG does not have to provide those free services to you.

I'm guessing you are not size of WP Engine and Silver Lake, honest question, if you were, would you want to contribute back to WordPress?

> Worth adding that WPE is owned by private equity

How do you think Matt got the money to build his empire?

>royalty free implementation

Yeah, but not the spec itself, meaning it's hard to have both secure and conforming implementation.

The spec can be found online, but it only really details specifically how to decode various features. You can take a look at JXL-Oxide and libjxl's codebases and get a good idea, and before some idiot comes out and speaks about "muh loc" the decoder and encoder bits of libjxl really aren't that hard to read. libjxl's codebase is very well formatted, files are segregated really well into different aspects of the code stream etc.

it's not ideal, but I would rather be given libjxl's codebase over the av1 spec page. (not to mention that heif is paywalled anyways which means that avif, which is heif + av1 is paywalled too... https://www.iso.org/standard/83650.html)