ezone
  • Home
  • Blog
    • Cloud ERP
  • Flutter
    • FlutterFlow
  • Joomla
  • About

Multizone | All our technotes

If we've published it, you can find it here.

Why the Internet Has Always Needed Guardrails

Why the Internet Has Always Needed Guardrails

Three Decades of Online Harm Prove That Self-Regulation Was Never Enough

There is a version of the internet regulation debate that treats government oversight as a novel, heavy-handed intrusion into a space that has functioned perfectly well on its own. Advocates of this position argue that platforms are already doing enough, that existing laws are sufficient, and that any legislative intervention risks stifling the innovation that made the internet great. This argument has been made persistently, passionately, and with considerable political effect since the mid-1990s.

It is also demonstrably wrong — and in 2026, the evidence against it is no longer confined to history. Governments are now legislating with a specificity and urgency that would have been unthinkable a decade ago. The United Kingdom has enacted criminal penalties for possessing AI models optimised to generate child sexual abuse material. Prime Minister Keir Starmer used London Tech Week in June 2026 to announce that Britain intends to become the first country where children cannot take, share, or view nude images on their devices — with Apple and Google given three months to comply before legislation kicks in. Apple, for its part, previewed a suite of new child safety features the same month, including mandatory parental controls for under-thirteens that will ship with iOS later in 2026. 

TL:DR – These are not proposals. They are policy in motion. And they are the direct consequence of thirty years of documented harm that the industry declined to prevent on its own.

Details
Last Updated: 29 July 2026

Read more: Why the Internet Has Always Needed Guardrails

Why Chrome couldn't reach my LAN web server on macOS, and why it wasn't DNS

Why Chrome couldn't reach my LAN web server on macOS, and why it wasn't DNS

 

Chrome Local Network Permission on macOS

What It Is and Why It Can Be So Hard to Diagnose

Starting with Chrome 130, Google introduced a new permission prompt that asks users whether a website should be allowed to access devices on their local network. This change aligns Chrome's behavior with the privacy goals outlined in the Private Network Access specification, a W3C proposal designed to prevent malicious websites from reaching routers, printers, smart home devices, and other hardware that sits behind a firewall.

On macOS, this permission works alongside the operating system's own network permission layer, which means users and administrators can find themselves troubleshooting problems that involve two entirely separate permission systems at once. The result is a diagnostic challenge that is easy to underestimate.

TL:DR – If you find this because Google sent you here after a few hours of staring at `ERR_NAME_NOT_RESOLVED`, `ERR_ADDRESS_UNREACHABLE`, or `net::os_error: 65` (ENETUNREACH) when Chrome can't reach a host on your own network, scroll to "The fix" at the bottom. The first 80% of this post is the diagnostic journey, because the journey is the lesson: the obvious suspects were all innocent, and the real cause was a quietly broken state in macOS itself.

Details
Last Updated: 29 July 2026

Read more: Why Chrome couldn't reach my LAN web server on macOS, and why it wasn't DNS

Don't fight macOS (DFMOS)

Don't fight macOS (DFMOS)

Don't Fight macOS (DFMOS)

A nod to DSMOS, the "Don't Steal macOS" message that Apple quietly logs to the console during boot as a gentle reminder that macOS is licensed software tied to Apple hardware. Consider this article a similar quiet reminder: don't take shortcuts when setting up macOS as a CI system. Work with the operating system, not against it.

TL:DR – The temptation to do things the Linux way on macOS is real and best avoided.

Details
Last Updated: 29 July 2026

Read more: Don't fight macOS (DFMOS)

MacBook Neo is the first indicator of the Ternus era

MacBook Neo is the first indicator of the Ternus era

MacBook Neo Is the First Indicator of the Ternus Era

There is a particular kind of moment in Apple's history that only becomes legible in retrospect. The introduction of the original iMac in 1998 looked, to many observers at the time, like a colourful curiosity. The first MacBook Air, unveiled by Steve Jobs from a manila envelope in 2008, seemed to some like a compromised machine for a niche audience. It is only later, when the thread becomes visible, that you understand you were watching the opening statement of something much larger. The MacBook Neo looks to me to be one of those moments.

TL:DR – The MacBook Neo was launched before Ternus became CEO but it is a sign of what his tenure will be about

Details
Last Updated: 29 July 2026

Read more: MacBook Neo is the first indicator of the Ternus era

Joomla custom Fields

Joomla custom Fields

Joomla Custom Fields in 2026: Capabilities, Limitations, and Practical Guidance for Administrators

Joomla's custom fields feature has matured considerably since its introduction in version 3.7. With Joomla now at version 6.1 — the current release as of 2026 — custom fields remain one of the most powerful and most underused tools available to site administrators. They provide a formal mechanism for attaching typed, queryable metadata to articles, contacts, and users without touching a database schema or reaching for a third-party component. Used well, they transform a generic CMS installation into a tightly organised information system. Used carelessly, they create invisible data that editors cannot find and developers cannot maintain.

TL:DR – This article covers what custom fields genuinely do well in the current Joomla release, where they still fall short, how to access them programmatically via the Joomla API, how to build custom field types using the modern namespace-based architecture, and how to resolve the persistently common problem of fields not appearing in the administrator interface.

Details
Last Updated: 29 July 2026

Read more: Joomla custom Fields

5 Reasons to Upgrade from M1 to M5 Max Today

5 Reasons to Upgrade from M1 to M5 Max Today

5 Reasons to Upgrade from M1 to M5 Max Today

Apple's M5 Max chip represents a significant leap in performance and efficiency over the M1, making it an attractive option for users seeking enhanced capabilities. Here are five compelling reasons to consider upgrading from the M1 to the M5 Max MacBook Pro.

1. Unmatched Processing Speed

The M5 Max boasts a substantial increase in processing speed, with benchmarks showing improvements of up to 50% in multi-core tasks compared to the M1. This speed enhancement is particularly beneficial for power users engaged in resource-intensive applications such as video editing, 3D rendering, and software development. The increase in performance translates to faster compile times, smoother playback, and generally improved responsiveness in demanding workflows.

2. Enhanced Graphics Performance

Graphics performance sees a dramatic boost with the M5 Max, featuring a more advanced GPU architecture. This upgrade results in up to 80% improved graphics rendering capabilities compared to the M1. For professionals working in creative fields, such as graphic design, animation, and game development, the enhanced GPU allows for real-time rendering of complex scenes and higher frame rates in graphics-intensive applications. The M5 Max also supports more display outputs and higher resolutions, making it ideal for multi-monitor setups.

3. Extended Battery Life

Despite the significant increase in performance, the M5 Max offers improved energy efficiency, leading to extended battery life. Users can expect up to 20 hours of usage on a single charge, surpassing the M1's already impressive performance. This extended battery duration is crucial for professionals who rely on their devices during long working hours or while travelling, reducing the need for frequent recharging and allowing for uninterrupted productivity.

4. Advanced Machine Learning Capabilities

The M5 Max introduces enhancements in machine learning performance, with a dedicated Neural Engine that is twice as powerful as that of the M1. This upgrade allows for faster processing of machine learning tasks, making it particularly advantageous for developers and data scientists who utilise AI and machine learning algorithms in their work. The increased capabilities facilitate more efficient training of models and quicker execution of AI-driven applications.

5. Superior Thermal Management

The M5 Max features an improved thermal design, allowing for better heat dissipation during extended periods of high performance. This design means that the laptop can maintain peak performance for longer periods without throttling, which is a common issue with previous generations. For users who push their machines to the limits, such as gamers or video editors, this ensures consistent performance without overheating, resulting in a more reliable and enjoyable user experience.

Upgrading from the M1 to the M5 Max MacBook Pro presents numerous benefits that cater to the needs of power users. With significant improvements in processing speed, graphics performance, battery life, machine learning capabilities, and thermal management, the M5 Max is a compelling choice for those looking to enhance their computing experience.

Details
Last Updated: 29 July 2026
GitHub Copilot’s Data Policy Shift: What It Means for Developers and Organisations

GitHub Copilot’s Data Policy Shift: What It Means for Developers and Organisations

A recent communication from GitHub signals a notable shift in how user data may be leveraged to enhance its AI tooling, specifically GitHub Copilot. From 24 April 2026, interactions with Copilot, covering prompts, generated code, snippets, and contextual metadata, may be used to train and refine AI models unless users explicitly opt out.

At first glance, this reads as a standard product improvement notice. In reality, it introduces a set of material risks that warrant closer scrutiny, particularly for developers working within commercial, regulated, or security-sensitive environments.

TL:DR – For organisations, this is not merely a developer preference setting. It is a governance issue.

This update is not unusual. It is, however, consequential.

AI-assisted development is rapidly becoming standard practice. But convenience should not quietly erode control. The default settings of tools rarely align with the risk tolerance of serious organisations.

A small configuration choice left unchecked can have unintended consequences

Act accordingly.

Details
Last Updated: 29 July 2026

Read more: GitHub Copilot’s Data Policy Shift: What It Means for Developers and Organisations

Page 4 of 46

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
Add as a preferred source on Google

Popular articles

  • Use an Apple Magic Mouse on Windows 11 PC
  • Disk Recovery Success Using GNU ddrescue on Ubuntu Linux
  • Working headless RDP with GNOME Remote Desktop on Ubuntu 25.10
  • Amazon Fire Max 11 - best value for the money tablet
  • Airport Time Capsule shared Drive for Mac and Linux

Recent articles

  • What a Joomla developer learned modernising a WordPress site
  • Building for One, Part six: four names for one app
  • Building for One, Part five: everybody reads it before she does
  • Building for One, Part four: the £200 tablet that just worked
  • Building for One, Part three: what a real iPad changed
  • Maintaining Gitea with Let's Encrypt on macOS via Homebrew — and the push failure nobody warns you about
My Blog
  • Terms of use
  • Privacy statement
  • Contact us
  • Sitemap
  • Joomla! — award-winning content management system (CMS)
  • Flutter — An open source framework for building applications from a single codebase