Ares del Maestrat Spanyol: Desa Pegunungan dan Wisata Sejarah Menarik

Terletak di puncak pegunungan yang menawan, Ares del Maestrat adalah sebuah desa pegunungan di Spanyol yang kaya akan sejarah dan budaya. Kota kecil ini menjadi destinasi menarik bagi para wisatawan yang ingin merasakan pesona alam sekaligus menyelami wisata sejarah yang mendalam. Dengan pemandangan alam yang memesona dan situs-situs bersejarah yang terawat baik, Ares del Maestrat menawarkan pengalaman unik bagi siapa saja yang mengunjunginya.

Lokasi dan Keindahan Alam Ares del Maestrat

Ares del Maestrat berlokasi di wilayah pegunungan Maestrazgo, sebuah kawasan yang dikenal dengan lanskap alamnya yang dramatis dan udara yang segar. Desa kecil ini memiliki ketinggian yang cukup tinggi sehingga memungkinkan pengunjung menikmati pemandangan panorama yang menakjubkan di sekelilingnya.

  • Pegunungan yang luas dan beragam flora.
  • Udara pegunungan yang segar dan menyejukkan.
  • Banyak jalur hiking dan trekking untuk petualangan alam.

Keindahan alam tersebut menjadikan Ares del Maestrat sebagai pilihan tepat bagi para pencinta alam dan aktivitas luar ruangan.

Jejak Peradaban Menawan di Ares del Maestrat

Selain keindahan alamnya, desa pegunungan ini terkenal dengan warisan sejarah yang kaya. Banyak bangunan dan situs peninggalan zaman dahulu yang masih berdiri kokoh, menjadi saksi bisu masa lalu yang gemilang. Wisata sejarah di Ares del Maestrat sangat cocok bagi mereka yang tertarik dengan arsitektur klasik dan Continue reading

Fenomena Kompetisi Automata Mekanis: Seni Kinetik dan Rekayasa Kreatif

Dalam era modern saat ini, perpaduan antara seni dan teknologi semakin menarik perhatian, salah satu contohnya adalah dalam fenomena kompetisi membuat automata mekanis. Automata mekanis merupakan karya seni kinetik yang tidak hanya mengandalkan keindahan visual, tetapi juga membutuhkan pemahaman mendalam tentang rekayasa kreatif untuk menciptakan gerakan yang kompleks dan mengagumkan. Artikel ini akan membahas bagaimana kompetisi inovasi di bidang automata mekanis menjadi wadah menyatukan seni dan teknologi secara harmonis.


Apa Itu Automata Mekanis?

Automata mekanis adalah sebuah objek atau figur yang dapat bergerak secara otomatis menggunakan mekanisme mesin. Biasanya, automata ini terbuat dari berbagai material seperti kayu, logam, atau plastik, dan dioperasikan melalui roda gigi, tuas, dan sistem penggerak mekanis lainnya.

Automata bukan hanya sekadar mainan mekanik; mereka merepresentasikan bentuk seni kinetik yang memukau. Gerakan yang dihasilkan automata bisa berupa animasi sederhana hingga rangkaian gerakan rumit yang menciptakan pengalaman visual dan emosional bagi penontonnya.


Seni Kinetik dan Rekayasa Kreatif dalam Automata Mekanis

Seni Kinetik: Lebih dari Sekadar Estetika

Seni kinetik berfokus pada gerak atau dinamika sebagai bagian esensial dari karya seni. Dalam automata mekanis, seni kinetik tercermin lewat kemampuan objek untuk bergerak dan bertransformasi, sehingga penggerakannya menjadi unsur penting dalam estetika.

Gerakan automata membawa cerita visual yang hidup, mengundang interaksi Continue reading

Notes from NANOG 97

These days you could be excused by suspecting that the world has gone AI-mad, and if you were at the NANOG 97 meeting your suspicions would've only been confirmed! The topics discussed the design of the data centres used to generate the large language models that underpin today's AI tools and the application of AI tools in network operations.

How we built saga rollbacks for Cloudflare Workflows

Cloudflare Workflows allows you to build durable, multi-step applications with built-in retries and state persistence across long-running processes. When a Workflow executes, each step can call external systems, retry failures, and persist state across restarts. But if one step fails, it may leave earlier work from completed steps in an inconsistent or partial state.

Today we’re shipping saga rollbacks for Workflows, allowing you to declare rollback logic within the step itself, in case of failure.

For example, consider a workflow for transferring funds between accounts at two different banks:

  1. Debit from account at Bank A

  2. Credit to account at Bank B

  3. Send email confirmation to both account owners

What happens if Step 2, the credit to account at Bank B, fails? Once the debit succeeds at Bank A, the transaction is committed and the money has left its system. As the orchestrator of the transaction, you cannot simply “undo” the operation in Bank A's system. Instead, the money must be credited back to the account at Bank A through a new operation that semantically reverses the first one.

This pairing of an operation and its compensation logic is called the saga pattern.

Before today, developers had to implement their own Continue reading

Unlocking the Cloudflare app ecosystem with OAuth for all

Cloudflare provides services that help run 20% of the web, but we don’t do it alone. Developers on our platform use a myriad of tools and services from other companies too. Cloudflare provides a rich API for our platform that enables developers to create automations, CI/CD, and integrations that glue together the various parts of their infrastructure. Earlier this month, we announced self-managed OAuth, making it easier for customers to create and manage their own OAuth clients for delegated access to the Cloudflare API.

Cloudflare isn’t new to OAuth. If you’ve used Wrangler, or used integrations from partners like PlanetScale, then you’ve already used it. However, until now, third-party OAuth was only available through a small number of manually onboarded integrations, and was not available to developers more broadly. That meant developers building their own integrations had to rely on API tokens, which are harder to manage and a poor fit for many delegated application flows. 

Over the last year, we onboarded a growing number of early partners while improving the consent, revocation, and security model behind Cloudflare OAuth. But as our Developer Platform grew and agentic tools drove demand for delegated access, it became clear that opening Continue reading

The post-quantum EO is an important milestone. Now it’s time to get to work

On June 22, 2026, President Trump signed Executive Order 14409, "Securing the Nation Against Advanced Cryptographic Attacks." The order sets a December 31, 2030, deadline for federal agencies to transition their most sensitive systems to post-quantum encryption, and a December 31, 2031, deadline for post-quantum authentication. The EO also directs federal contractors to comply with post-quantum Federal Information Processing Standards (FIPS) by the end of 2030.

We welcome this executive order. The U.S. government has a long track record of using federal leadership and procurement to drive adoption of new technologies across the broader industry. We've seen this work with IPv6, with routing security and the Resource Public Key Infrastructure (RPKI), and with DNSSEC, and we’re glad to see this tradition continue with post-quantum cryptography.

The EO is especially important at this moment because the timeline for Q-Day, the day that quantum computers can break the public-key cryptography used across the Internet, has been accelerated. In April 2026, Cloudflare moved our own target for full post-quantum security to 2029, following research breakthroughs from Google and Oratomic. This EO updates guidance from 2024, when the National Institute of Standards Continue reading

Chapter 2: Installing SONiC NOS

 

ONIE-Based SONiC Installation

Many switch vendors have added SONiC NOS support to at least part of their switch portfolio. Depending on the vendor and switch model, customers may be able to order a switch with a vendor-customized SONiC version that is supported at the same level as the vendor's own network operating system. Some vendors also allow customers to run the community-based SONiC distribution.

The support model for Community SONiC depends on the vendor. Some hardware vendors provide full support, while others provide no support at all. Compared with vendor-specific SONiC distributions, Community SONiC provides greater flexibility because it can be customized, rebuilt, and adapted to customer requirements. However, running a Community SONiC deployment without vendor support or in-house expertise is generally not a recommended operating model.

Community SONiC is typically installed by using ONIE (Open Network Install Environment) [1], a small open-source installation environment that provides a standardized method for installing network operating systems on supported switches. Figure 2-1 illustrates a conceptual ONIE-based Community SONiC installation process.

If the switch is delivered with a vendor-specific SONiC distribution already installed, it may boot directly into that operating system without requiring a separate ONIE installation workflow. For Community SONiC deployments, Continue reading

How we found a bug in the hyper HTTP library

The Images service, built in Rust on Workers, runs on every machine in Cloudflare’s edge network. To handle client connections, we use hyper, an open-source HTTP library for Rust.

Last year, we introduced the Images binding to enable custom, programmatic workflows for processing remote images in Workers. At the end of 2025, we rearchitected the binding to provide a more direct, local connection between the Workers runtime and the Images service.

Shortly after rollout, we received reports that transformation requests from the binding were failing — but only intermittently and only for larger images. Even stranger, the responses for these requests returned a 200 status without any errors logged. The image data was simply cut short: A response that should have been two megabytes might arrive with a few hundred kilobytes instead.

We spent six weeks chasing a nearly invisible bug — a race condition that occurred only under specific conditions — in the hyper library that impacted how the Images binding returned processed image data back to the client. In the end, it took four lines of code to fix it.

Hops, handoffs, and hyper

When developers build on Cloudflare, they compose full-stack applications from a set Continue reading

NB580: Project Glasswing on Hold – or Not; Why You Should Hold In-Person Background Checks

Take a Network Break! Our Red Alert covers critical vulnerabilities found in OpenClaw, the open-source AI assistant. On the news front, we discuss the status of Anthropic’s Project Glasswing and examine the Korean Electronics and Telecommunications Research Institute‘s (ETRI) development of an intelligent, service-programmable mobile core network, a key enabling technology for the 6G era.... Read more »

Worth Reading: AI Enthusiasts Against AI Skeptics

Charity Majors wrote an excellent article describing AI enthusiasts in a race against time and AI skeptics in a race against entropy. Fair warning: its very first sentence triggered an acute case of PTSD:

I recently attended a talk where one of the presenters made some pretty…astonishing claims about what they had achieved by the pure, uncut power of vibe coding.

I’ve seen way too many presentations making “astonishing claims” about the unlimited unicorn-driven powers of OpenFlow, SDN, OpenDaylight, or Ansible.

Rebuilding My Proxmox Cluster for the Version 9 Upgrade

Rebuilding My Proxmox Cluster for the Version 9 Upgrade

I've been running Proxmox for maybe two years now, and I'd consider myself somewhat of a beginner. I set it up once using Proxmox version 8.x alongside Proxmox Backup Server and pretty much forgot about it. I can spin up new VMs and CTs, or remove existing ones, and that's about it. Fast forward to mid-2026, Proxmox released version 9, and I'd been meaning to upgrade. I went through a few guides and forum posts, and people tended to recommend backing up the VMs and CTs using PBS, then reinstalling Proxmox with the new version and restoring from backup.

TL;DR

I upgraded my Proxmox setup from version 8.x to 9 without doing an in-place upgrade. Instead, I used a spare node already on version 9 as a temporary home and rebuilt the other two nodes one at a time. The idea was to back up everything with PBS, restore onto the spare, then wipe and fresh install version 9 on each node before joining them into a new three-node cluster. Once the cluster was sorted, I also rebuilt pbs-01 to version 4 and cleaned up the old backups. The whole thing was seamless, I didn't lose anything, and Continue reading

1 2 3 3,883