Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the amp domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_has_paired_endpoint was called incorrectly. Function cannot be called before services are registered. The service ID "paired_routing" is not recognized and cannot be retrieved. Please see Debugging in WordPress for more information. (This message was added in version 2.1.1.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_has_paired_endpoint was called incorrectly. Function cannot be called before services are registered. The service ID "paired_routing" is not recognized and cannot be retrieved. Please see Debugging in WordPress for more information. (This message was added in version 2.1.1.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `plugins_loaded` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `plugins_loaded` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the gotmls domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170
Tiang Monolit Misteri Kini Lesap – Independent

Tiang Monolit Misteri Kini Lesap

Reading Time: 2 minutes

Seperti mana misteri kemunculannya, monolit logam setinggi 12 kaki yang ditemui minggu lalu oleh pekerja keselamatan awam Utah kini telah lenyap, kata pegawai pada hari Sabtu.

Struktur logam tiga sisi itu dikeluarkan pada hari Jumaat malam “oleh pihak yang tidak dikenali” dari tanah awam tempatnya ditemui, kata pejabat Biro Pengurusan Tanah persekutuan Utah dalam satu kenyataan.

Biro itu mengatakan pihaknya tidak mengeluarkan monolit itu, yang dianggapnya sebagai “harta persendirian.”

Jabatan Keselamatan Awam Utah mengatakan pada hari Isnin bahawa ia telah menjumpai objek itu ketika melakukan pengiraan jumlah biri-biri bighorn.

“Ia sudah tiada!” kata Jabatan Keselamatan Awam, yang bertindak balas terhadap berita tersebut dalam catatan Instagram. “Hampir sepantas ia muncul sekarang telah hilang,” kata jabatan itu sambil menambah, “Saya hanya dapat berspekulasi” bahwa makhluk asing mengambilnya kembali,” menggunakan emoji makhluk luar angkasa.

“Mungkin ia akan hampir dan mengunjungi kami di Kanada !!” seseorang memberi komen.

Ini adalah misteri bagaimana monolit dipasang di sana. Leftenan Nick Street, jurucakap Jabatan Keselamatan Awam, mengatakan minggu ini bahawa monolit itu telah tertanam di dalam batu.

“Seseorang meluangkan masa untuk menggunakan beberapa jenis alat pemotong konkrit atau sesuatu untuk benar-benar menggali, hampir sama bentuk objek itu, dan menanamnya dengan sangat baik,” katanya. “Aneh. Terdapat jalan-jalan yang dekat, tetapi untuk mengangkut bahan untuk memotong batu, dan mengangkut logam, yang lebih tinggi daripada 12 kaki – untuk melakukan semua itu di tempat terpencil itu pasti menarik. “

Pegawai mengatakan bahawa struktur itu kemungkinan besar merupakan karya seni dan pemasangannya di tanah awam adalah tidak sah. Tidak jelas siapa yang meletakkannya di sana – dan bila – tetapi dunia seni dengan cepat membuat spekulasi bahawa itu adalah karya John McCracken, seorang pemahat fiksyen. Dia meninggal pada tahun 2011.

Anak lelakinya, Patrick McCracken, mengatakan kepada The New York Times minggu ini bahawa ayahnya telah memberitahunya pada tahun 2002 bahawa “dia ingin meninggalkan karya seninya di tempat-tempat terpencil untuk ditemukan kemudian.”

Walaupun pegawai enggan mendedahkan lokasi monolit itu, beberapa orang berjaya mengesannya. David Surber, yang mengunjungi struktur itu minggu ini dan menyiarkan video di Instagram, mengatakan ia terletak berhampiran Lockhart Basin Road, yang terletak di selatan Moab.

Adakah John McCracken Membuat Monolit Itu di Utah?

Biro Pengurusan Tanah mengatakan tidak akan menyiasat kehilangan tersebut kerana “jenayah yang melibatkan harta persendirian” diuruskan oleh pejabat sheriff tempatan. Pejabat Sheriff San Juan dan Grand County menolak permintaan untuk memberi komen.