# syndication_item

link: https://fedoramagazine.org/4-cool-new-projects-to-try-in-copr-for-june-2023/
encoded_syndication_url: aHR0cDovL2ZlZG9yYW1hZ2F6aW5lLm9yZy9mZWVkLw==
read: False
type: Rss
title: 4 cool new projects to try in COPR for June 2023
categories: Fedora Project community|Copr|free software|software|unsupported
comments_url: https://fedoramagazine.org/4-cool-new-projects-to-try-in-copr-for-june-2023/feed/
description:
Copr&#160;is a build-system for anyone in the Fedora community. It hosts thousands of projects for various purposes and audiences. Some of them should never be installed by anyone, some are already being transitioned to the official Fedora Linux repositories, and the rest is somewhere in between. Copr gives you the opportunity to install 3rd party [&#8230;]

content:
<p><a href="https://copr.fedorainfracloud.org/" target="_blank" rel="noreferrer noopener">Copr</a>&nbsp;is a build-system for anyone in the Fedora community. It hosts thousands of projects for various purposes and audiences. Some of them should never be installed by anyone, some are already being transitioned to the official Fedora Linux repositories, and the rest is somewhere in between. Copr gives you the opportunity to install 3rd party software that is not available in Fedora Linux repositories, try nightly versions of your dependencies, use patched builds of your favorite tools to support some non-standard use-cases, and just experiment freely.</p>



<p>If you don&#8217;t know&nbsp;<a href="https://docs.pagure.org/copr.copr/how_to_enable_repo.html#how-to-enable-repo" target="_blank" rel="noreferrer noopener">how to enable a repository</a>&nbsp;or if you are concerned about whether&nbsp;<a href="https://docs.pagure.org/copr.copr/user_documentation.html#is-it-safe-to-use-copr" target="_blank" rel="noreferrer noopener">is it safe to use Copr</a>, please consult the&nbsp;<a href="https://docs.pagure.org/copr.copr/user_documentation.html" target="_blank" rel="noreferrer noopener">project documentation</a>.</p>



<p>This article takes a closer look at interesting projects that recently landed in Copr.</p>



<span id="more-38402"></span>



<h2 class="wp-block-heading"><a href="https://github.com/frostyx/fedora-magazine/blob/main/2023-june.md#chatgpt-shell-cli"></a>chatGPT-shell-cli</h2>



<p>This year it seems that anywhere you look,&nbsp;<a href="https://openai.com/product/chatgpt" target="_blank" rel="noreferrer noopener">ChatGPT</a>&nbsp;is there. This time we have a lightweight ChatGPT and&nbsp;<a href="https://openai.com/product/dall-e-2" target="_blank" rel="noreferrer noopener">DALL-E</a>&nbsp;client, written in Bash, called&nbsp;<a href="https://github.com/0xacx/chatGPT-shell-cli" target="_blank" rel="noreferrer noopener">chatGPT-shell-cli</a>. Look for the &#8220;Commands&#8221; section at <a href="http://github.com/0xacx/chatGPT-shell-cli" target="_blank" rel="noreferrer noopener">chatGPT-shell-cli </a> for usage. This Bash script can be especially useful for systems without standard dependencies such as Python or Node.js.</p>



<figure class="wp-block-image size-full"><img decoding="async" loading="lazy" width="770" height="339" src="https://fedoramagazine.org/wp-content/uploads/2023/05/chatgpt.png" alt="" class="wp-image-38403" srcset="https://fedoramagazine.org/wp-content/uploads/2023/05/chatgpt.png 770w, https://fedoramagazine.org/wp-content/uploads/2023/05/chatgpt-300x132.png 300w, https://fedoramagazine.org/wp-content/uploads/2023/05/chatgpt-768x338.png 768w" sizes="(max-width: 770px) 100vw, 770px" /></figure>



<h3 class="wp-block-heading"><a href="https://github.com/frostyx/fedora-magazine/blob/main/2023-june.md#installation-instructions"></a>Installation instructions</h3>



<p>The&nbsp;<a href="https://copr.fedorainfracloud.org/coprs/kylegospo/chatGPT-shell-cli/" target="_blank" rel="noreferrer noopener">repo</a>&nbsp;currently provides&nbsp;<em>chatgpt-shell-cli</em>&nbsp;for Fedora 37, 38, Fedora Rawhide, RHEL8, RHEL9, and others. To install it, use these commands:</p>



<pre class="wp-block-preformatted">sudo dnf copr enable kylegospo/chatGPT-shell-cli
sudo dnf install chatgpt-shell-cli</pre>



<p>Note that an OpenAI API key is required to use this script. You may create an account and get a free API Key at <a href="https://beta.openai.com/account/api-keys" target="_blank" rel="noreferrer noopener">OpenAI</a>.</p>



<h2 class="wp-block-heading"><a href="https://github.com/frostyx/fedora-magazine/blob/main/2023-june.md#hyprland"></a>Hyprland</h2>



<p><a href="https://hyprland.org/" target="_blank" rel="noreferrer noopener">Hyprland</a> is a beautiful looking compositor for Wayland. It provides dynamic tiling with multiple layouts, smooth animations, and endless customization options. Similarly to&nbsp;<a href="https://swaywm.org/" target="_blank" rel="noreferrer noopener">Sway</a>&nbsp;or&nbsp;<a href="https://i3wm.org/" target="_blank" rel="noreferrer noopener">i3</a>, it has a simple configuration file that doesn&#8217;t require you to know the programming language it was written in.</p>



<figure class="wp-block-image size-full"><img decoding="async" loading="lazy" width="2515" height="1415" src="https://fedoramagazine.org/wp-content/uploads/2023/05/hyprland.png" alt="" class="wp-image-38404" srcset="https://fedoramagazine.org/wp-content/uploads/2023/05/hyprland.png 2515w, https://fedoramagazine.org/wp-content/uploads/2023/05/hyprland-300x169.png 300w, https://fedoramagazine.org/wp-content/uploads/2023/05/hyprland-1024x576.png 1024w, https://fedoramagazine.org/wp-content/uploads/2023/05/hyprland-768x432.png 768w, https://fedoramagazine.org/wp-content/uploads/2023/05/hyprland-1536x864.png 1536w, https://fedoramagazine.org/wp-content/uploads/2023/05/hyprland-2048x1152.png 2048w, https://fedoramagazine.org/wp-content/uploads/2023/05/hyprland-816x459.png 816w" sizes="(max-width: 2515px) 100vw, 2515px" /></figure>



<h3 class="wp-block-heading"><a href="https://github.com/frostyx/fedora-magazine/blob/main/2023-june.md#installation-instructions-1"></a>Installation instructions</h3>



<p>The&nbsp;<a href="https://copr.fedorainfracloud.org/coprs/carlwgeorge/hyprland/" target="_blank" rel="noreferrer noopener">repo</a>&nbsp;currently provides Hyprland for Fedora 37, 38, and Fedora Rawhide. To install it, use these commands:</p>



<pre class="wp-block-preformatted">sudo dnf copr enable carlwgeorge/hyprland
sudo dnf install hyprland</pre>



<h2 class="wp-block-heading"><a href="https://github.com/frostyx/fedora-magazine/blob/main/2023-june.md#wezterm"></a>Wezterm</h2>



<p><a href="https://wezfurlong.org/wezterm/" target="_blank" rel="noreferrer noopener">Wezterm</a>&nbsp;is a modern terminal emulator that runs on all the major operating systems. It has built-in support for terminal multiplexing, rendering images, emojis, GPU acceleration, and many more features.</p>



<figure class="wp-block-image size-full"><img decoding="async" loading="lazy" width="771" height="344" src="https://fedoramagazine.org/wp-content/uploads/2023/05/wezterm.png" alt="" class="wp-image-38405" srcset="https://fedoramagazine.org/wp-content/uploads/2023/05/wezterm.png 771w, https://fedoramagazine.org/wp-content/uploads/2023/05/wezterm-300x134.png 300w, https://fedoramagazine.org/wp-content/uploads/2023/05/wezterm-768x343.png 768w" sizes="(max-width: 771px) 100vw, 771px" /></figure>



<h3 class="wp-block-heading"><a href="https://github.com/frostyx/fedora-magazine/blob/main/2023-june.md#installation-instructions-2"></a>Installation instructions</h3>



<p>The&nbsp;<a href="https://copr.fedorainfracloud.org/coprs/zjlin/majesty-dubbed-skyline/" target="_blank" rel="noreferrer noopener">repo</a>&nbsp;currently provides Wezterm for Fedora 37, 38, and Fedora Rawhide. To install it, use these commands:</p>



<pre class="wp-block-preformatted">sudo dnf copr enable zjlin/majesty-dubbed-skyline
sudo dnf install wezterm</pre>



<h2 class="wp-block-heading"><a href="https://github.com/frostyx/fedora-magazine/blob/main/2023-june.md#htpdate"></a>htpdate</h2>



<p><a href="http://www.vervest.org/htp/" target="_blank" rel="noreferrer noopener">htpdate</a>&nbsp;is a time synchronization client for the HTTP Time Protocol (HTP). Is it better than Network Time Protocol (NTP) which is used in Fedora by default? It is not!&nbsp;<a href="https://www.vervest.org/htp/?FAQ" target="_blank" rel="noreferrer noopener">You should use NTP if you can</a>. However, NTP sometimes doesn&#8217;t work because of proxy or firewall restrictions. That&#8217;s when HTP and&nbsp;<em>htpdate</em>&nbsp;become very useful.</p>



<figure class="wp-block-image size-full"><img decoding="async" loading="lazy" width="770" height="339" src="https://fedoramagazine.org/wp-content/uploads/2023/05/htpdate.png" alt="" class="wp-image-38406" srcset="https://fedoramagazine.org/wp-content/uploads/2023/05/htpdate.png 770w, https://fedoramagazine.org/wp-content/uploads/2023/05/htpdate-300x132.png 300w, https://fedoramagazine.org/wp-content/uploads/2023/05/htpdate-768x338.png 768w" sizes="(max-width: 770px) 100vw, 770px" /></figure>



<h3 class="wp-block-heading"><a href="https://github.com/frostyx/fedora-magazine/blob/main/2023-june.md#installation-instructions-3"></a>Installation instructions</h3>



<p>The&nbsp;<a href="https://copr.fedorainfracloud.org/coprs/whitehara/htpdate/" target="_blank" rel="noreferrer noopener">repo</a>&nbsp;currently provides&nbsp;<em>htpdate</em>&nbsp;for Fedora 37, 38, Fedora Rawhide, Fedora ELN, RHEL8, RHEL9, and others. To install it, use these commands:</p>



<pre class="wp-block-preformatted">sudo dnf copr enable whitehara/htpdate
sudo dnf install htpdate</pre>


link: https://fedoramagazine.org/youre-invited-to-the-fedora-linux-38-release-party/
encoded_syndication_url: aHR0cDovL2ZlZG9yYW1hZ2F6aW5lLm9yZy9mZWVkLw==
read: False
type: Rss
title: You’re invited to the Fedora Linux 38 Release Party!
categories: Events|Release Party
comments_url: https://fedoramagazine.org/youre-invited-to-the-fedora-linux-38-release-party/feed/
description:
Join the Fedora community this weekend on Friday, June 2nd and Saturday, June 3rd to celebrate the final release of Fedora Linux 38!

content:
<p>Join the Fedora community this weekend on Friday, June 2nd and Saturday, June 3rd to celebrate the final release of Fedora Linux 38 with a virtual <a href="https://communityblog.fedoraproject.org/tag/release-parties/">Release Party</a>. Please&nbsp;<a href="https://hopin.com/events/fedora-linux-38-release-party" target="_blank" rel="noreferrer noopener"><strong>register on Hopin</strong></a>&nbsp;and join us on June 2nd &amp; 3rd for a short program of informational sessions and social activities. Make sure to save the dates, share the registration, and show up to celebrate with Fedora Friends, old and new!</p>



<span id="more-38431"></span>



<p>The <a href="https://fedoraproject.org/wiki/Fedora_Linux_38_Release_Party_Schedule" target="_blank" rel="noreferrer noopener">schedule for the Release Party</a> features informational sessions about the <a href="https://notifications.fedoraproject.org/" target="_blank" rel="noreferrer noopener">rewritten Fedora Notifications service</a>, a <a href="https://creativefreedomsummit.com/" target="_blank" rel="noreferrer noopener">Creative Freedom Summit retrospective</a>, <a href="https://fedoraproject.org/coreos/" target="_blank" rel="noreferrer noopener">Fedora CoreOS</a>, updates from the <a href="https://docs.fedoraproject.org/en-US/epel/" target="_blank" rel="noreferrer noopener">EPEL</a> and <a href="https://docs.fedoraproject.org/en-US/docs/" target="_blank" rel="noreferrer noopener">Fedora Docs</a> teams, and more community activities. Last, but certainly not least, we will be hanging out in the&nbsp;<a href="https://play.workadventu.re/@/mindshare-committee/nestwithfedora/fedoramuseum">Fedora Museum WorkAdventure</a>&nbsp;for our Hallway track. Thanks to our amazing community for all your contributions to the latest release of Fedora Linux. Let’s party!</p>


link: https://fedoramagazine.org/the-community-platform-engineering-f2f-2023-experience-part-ii/
encoded_syndication_url: aHR0cDovL2ZlZG9yYW1hZ2F6aW5lLm9yZy9mZWVkLw==
read: False
type: Rss
title: The Community Platform Engineering F2F 2023 Experience – Part II
categories: Fedora Project community|CPE
comments_url: https://fedoramagazine.org/the-community-platform-engineering-f2f-2023-experience-part-ii/feed/
description:
20 Mar 2023 &#8211; 23 Mar 2023 &#8211; Barcelona, Spain Intro If you have not already &#8211; now is the best time to read through the first part of the event report before getting into the second part here. Day 2Wednesday, 22nd March 2023The team members decided to start a bit late on the second [&#8230;]

content:
<blockquote class="wp-block-quote">
<p>20 Mar 2023 &#8211; 23 Mar 2023</p>
<cite>&#8211; Barcelona, Spain</cite></blockquote>



<span id="more-38357"></span>



<p><strong>Intro</strong></p>



<p>If you have not already &#8211; now is the best time to read through the <a href="https://fedoramagazine.org/the-community-platform-engineering-f2f-2023-experience-part-i/" target="_blank" rel="noreferrer noopener">first part</a> of the event report before getting into the second part here. </p>



<figure class="wp-block-image size-large"><a href="https://fedoramagazine.org/wp-content/uploads/2023/05/20230323_115842-scaled.jpg"><img decoding="async" loading="lazy" width="1024" height="511" src="https://fedoramagazine.org/wp-content/uploads/2023/05/20230323_115842-1024x511.jpg" alt="" class="wp-image-38362" srcset="https://fedoramagazine.org/wp-content/uploads/2023/05/20230323_115842-1024x511.jpg 1024w, https://fedoramagazine.org/wp-content/uploads/2023/05/20230323_115842-300x150.jpg 300w, https://fedoramagazine.org/wp-content/uploads/2023/05/20230323_115842-768x383.jpg 768w, https://fedoramagazine.org/wp-content/uploads/2023/05/20230323_115842-1536x766.jpg 1536w, https://fedoramagazine.org/wp-content/uploads/2023/05/20230323_115842-2048x1021.jpg 2048w, https://fedoramagazine.org/wp-content/uploads/2023/05/20230323_115842-816x407.jpg 816w, https://fedoramagazine.org/wp-content/uploads/2023/05/20230323_115842-400x200.jpg 400w" sizes="(max-width: 1024px) 100vw, 1024px" /></a><figcaption class="wp-element-caption"><strong>From left to right</strong> &#8211; Actually, never mind &#8211; there are too many people there.</figcaption></figure>



<p><strong>Day 2</strong><br /><strong><em>Wednesday, 22nd March 2023<br /></em></strong>The team members decided to start a bit late on the second day to ensure that everyone gets enough rest after the adventurous first day. Once the joint breakfast was completed in the hotel restaurant, the members started heading off to the office by 10 in the morning. They were were gracefully served Catalonian snacks by <a href="https://accounts.fedoraproject.org/user/lenkaseg/" target="_blank" rel="noreferrer noopener">Lenka Segura</a>, Japanese souvenirs by <a href="https://accounts.fedoraproject.org/user/dkirwan/" target="_blank" rel="noreferrer noopener">David Kirwan</a>, and German sweets by <a href="https://accounts.fedoraproject.org/user/jbley/" target="_blank" rel="noreferrer noopener">Julia Bley</a> for the duration of the meeting. <a href="https://accounts.fedoraproject.org/user/mattdm/" target="_blank" rel="noreferrer noopener">Matthew Miller</a> started the second day with his talk about the Fedora Project strategy and how <a href="https://docs.fedoraproject.org/en-US/cpe/" target="_blank" rel="noreferrer noopener">Community Platform Engineering</a> fits into the picture. This talk was followed by the one by <a href="https://accounts.fedoraproject.org/user/humaton/" target="_blank" rel="noreferrer noopener">Tomas Hrcka</a> about how the <a href="https://docs.pagure.org/releng/" target="_blank" rel="noreferrer noopener">Fedora Release Engineering team</a> addresses its responsibilities. The team took a short break after the first couple of sessions, before heading into the next set.</p>



<figure class="wp-block-image size-large"><a href="https://fedoramagazine.org/wp-content/uploads/2023/05/IMG_1723-scaled.jpg"><img decoding="async" loading="lazy" width="1024" height="768" src="https://fedoramagazine.org/wp-content/uploads/2023/05/IMG_1723-1024x768.jpg" alt="" class="wp-image-38359" srcset="https://fedoramagazine.org/wp-content/uploads/2023/05/IMG_1723-1024x768.jpg 1024w, https://fedoramagazine.org/wp-content/uploads/2023/05/IMG_1723-300x225.jpg 300w, https://fedoramagazine.org/wp-content/uploads/2023/05/IMG_1723-768x576.jpg 768w, https://fedoramagazine.org/wp-content/uploads/2023/05/IMG_1723-1536x1152.jpg 1536w, https://fedoramagazine.org/wp-content/uploads/2023/05/IMG_1723-2048x1536.jpg 2048w, https://fedoramagazine.org/wp-content/uploads/2023/05/IMG_1723-816x612.jpg 816w" sizes="(max-width: 1024px) 100vw, 1024px" /></a><figcaption class="wp-element-caption"><strong>From left to right</strong> &#8211; <a href="https://accounts.fedoraproject.org/user/lenkaseg/" target="_blank" rel="noreferrer noopener">Lenka Segura</a>  <a href="https://accounts.fedoraproject.org/user/mattdm/" target="_blank" rel="noreferrer noopener">Matthew Miller</a>  <a href="https://accounts.fedoraproject.org/user/asamalik/" target="_blank" rel="noreferrer noopener">Adam Samalik</a>  <a href="https://accounts.fedoraproject.org/user/tdawson/" target="_blank" rel="noreferrer noopener">Troy Dawson</a></figcaption></figure>



<p>After a short break, the team continued with three lightning talks delivered about <a href="https://www.redhat.com/en/technologies/cloud-computing/openshift" target="_blank" rel="noreferrer noopener">OpenShift</a> operators by <a href="https://accounts.fedoraproject.org/user/dkirwan/" target="_blank" rel="noreferrer noopener">David Kirwan</a>, <a href="https://packit.dev/" target="_blank" rel="noreferrer noopener">Packit</a> by <a href="https://accounts.fedoraproject.org/user/lachmanfrantisek/" target="_blank" rel="noreferrer noopener">Frantisek Lachman</a> and <a href="https://accounts.fedoraproject.org/user/lbarczio/" target="_blank" rel="noreferrer noopener">Laura Barcziova</a>, and <a href="https://pulpproject.org/" target="_blank" rel="noreferrer noopener">Pulp</a> by <a href="https://accounts.fedoraproject.org/user/msuchy/" target="_blank" rel="noreferrer noopener">Miroslav</a><a href="https://accounts.fedoraproject.org/user/msuchy/"> Suchy</a>. Miroslav Suchy delivered a thought-provoking talk about the scope of tooling for the Community Platform Engineering team, and how it contributes to <a href="https://fedoraproject.org/" target="_blank" rel="noreferrer noopener">Fedora Linux</a>. With that, the folks dispersed into small groups for lunch. Once they were back in the office, <a href="https://accounts.fedoraproject.org/user/csomh/" target="_blank" rel="noreferrer noopener">Hunor Csomortáni</a> delivered a talk about revisiting source-git and the plans for unifying package sources in the pipeline. This was followed by a talk by <a href="https://accounts.fedoraproject.org/user/carlwgeorge/" target="_blank" rel="noreferrer noopener">Carl George</a> about the <a href="https://docs.fedoraproject.org/en-US/epel/" target="_blank" rel="noreferrer noopener">EPEL</a> 10 plans for improvements that would be coming very soon. The final interesting talk of the day was delivered by <a href="https://accounts.fedoraproject.org/user/bstinson/" target="_blank" rel="noreferrer noopener">Brian Stinson</a> about the expectations of <a href="https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux" target="_blank" rel="noreferrer noopener">RHEL</a> from Fedora Linux and <a href="http://centosproject.org/" target="_blank" rel="noreferrer noopener">CentOS</a><a href="http://centosproject.org/"> Stream</a>.</p>



<figure class="wp-block-image size-large"><a href="https://fedoramagazine.org/wp-content/uploads/2023/05/IMG20230321190020_01-scaled.jpg"><img decoding="async" loading="lazy" width="1024" height="576" src="https://fedoramagazine.org/wp-content/uploads/2023/05/IMG20230321190020_01-1024x576.jpg" alt="" class="wp-image-38360" srcset="https://fedoramagazine.org/wp-content/uploads/2023/05/IMG20230321190020_01-1024x576.jpg 1024w, https://fedoramagazine.org/wp-content/uploads/2023/05/IMG20230321190020_01-300x169.jpg 300w, https://fedoramagazine.org/wp-content/uploads/2023/05/IMG20230321190020_01-768x432.jpg 768w, https://fedoramagazine.org/wp-content/uploads/2023/05/IMG20230321190020_01-1536x864.jpg 1536w, https://fedoramagazine.org/wp-content/uploads/2023/05/IMG20230321190020_01-2048x1152.jpg 2048w, https://fedoramagazine.org/wp-content/uploads/2023/05/IMG20230321190020_01-816x459.jpg 816w" sizes="(max-width: 1024px) 100vw, 1024px" /></a><figcaption class="wp-element-caption"><strong>From left to right</strong> &#8211; <a href="https://accounts.fedoraproject.org/user/ekidney" target="_blank" rel="noreferrer noopener">Emma Kidney</a>  <a href="https://accounts.fedoraproject.org/user/dfan/" target="_blank" rel="noreferrer noopener">David Fan</a>  <a href="https://accounts.fedoraproject.org/user/zlopez/" target="_blank" rel="noreferrer noopener">Michal Konecny</a>  <a href="https://accounts.fedoraproject.org/user/t0xic0der/" target="_blank" rel="noreferrer noopener">Akashdeep Dhar</a>  <a href="https://accounts.fedoraproject.org/user/jnsamyak/" target="_blank" rel="noreferrer noopener">Samyak Jain</a>  <a href="https://accounts.fedoraproject.org/user/dkirwan/" target="_blank" rel="noreferrer noopener">David Kirwan</a></figcaption></figure>



<p>In the evening, at around 19:00, the team members left for a regional burger restaurant, <a href="https://www.tripadvisor.com/Restaurant_Review-g187497-d7223439-Reviews-Tio_Joe-Barcelona_Catalonia.html" target="_blank" rel="noreferrer noopener">Tio Joe’s</a>. This had been booked in advance and was near the hotel premises . With toasts made to the team members that were now united after a long time, they not only enjoyed the appetizing food that was served but also the company of the friends that they had bonded with over the course of the last couple days. </p>



<p>Once the dinner was over, at around 21:30, some folks headed back to the hotel for a respite. The remainder went to the <a href="https://trompokaraokebar.com/">Trompos </a><a href="https://trompokaraokebar.com/" target="_blank" rel="noreferrer noopener">Karaoke</a><a href="https://trompokaraokebar.com/"> Bar</a> to participate in the fun karaoke night session organized by <a href="https://accounts.fedoraproject.org/user/abompard/" target="_blank" rel="noreferrer noopener">Aurelien Bompard</a>. People queued up their songs and soon began to collaborate in performing their favorite songs in duos and in choirs.  This was a fitting end to the night, as late as 02:00, and a fun look at their singing preferences.</p>



<p><strong>Day 3</strong><strong><br /></strong><strong><em>Thursday, 23rd March 2023</em></strong></p>



<p>This was the day of departure for a lot of people. Since they would miss out on the sessions on this third day, it was incredibly light in terms of the agenda and activities. Many of the team members checked out of their hotel rooms after breakfast at 09:00 and left their luggage with the hotel before leaving for the office.</p>



<p> <a href="https://accounts.fedoraproject.org/user/smattejiet/" target="_blank" rel="noreferrer noopener">Stefan Mattejiet</a> started off the last day with his discussion session about CPE Futurespective, and understanding what direction the team should head in the coming times. The interesting discussion felt a lot inspired by the established logic model planning structure used for <a href="https://docs.fedoraproject.org/en-US/council/" target="_blank" rel="noreferrer noopener">Fedora Council</a> community initiatives. This structure starts off with planning the general objectives first and then going back to the implementation details later.&nbsp;</p>



<figure class="wp-block-image size-large"><a href="https://fedoramagazine.org/wp-content/uploads/2023/05/20230323_104914-scaled.jpg"><img decoding="async" loading="lazy" width="1024" height="768" src="https://fedoramagazine.org/wp-content/uploads/2023/05/20230323_104914-1024x768.jpg" alt="" class="wp-image-38358" srcset="https://fedoramagazine.org/wp-content/uploads/2023/05/20230323_104914-1024x768.jpg 1024w, https://fedoramagazine.org/wp-content/uploads/2023/05/20230323_104914-300x225.jpg 300w, https://fedoramagazine.org/wp-content/uploads/2023/05/20230323_104914-768x576.jpg 768w, https://fedoramagazine.org/wp-content/uploads/2023/05/20230323_104914-1536x1152.jpg 1536w, https://fedoramagazine.org/wp-content/uploads/2023/05/20230323_104914-2048x1536.jpg 2048w, https://fedoramagazine.org/wp-content/uploads/2023/05/20230323_104914-816x612.jpg 816w" sizes="(max-width: 1024px) 100vw, 1024px" /></a><figcaption class="wp-element-caption"><strong>From left to right</strong> &#8211; <a href="https://accounts.fedoraproject.org/user/arrfab" target="_blank" rel="noreferrer noopener">Fabian Arrotin</a>  <a href="https://accounts.fedoraproject.org/user/james/" target="_blank" rel="noreferrer noopener">James Antill</a>  <a href="https://accounts.fedoraproject.org/user/asaleh/" target="_blank" rel="noreferrer noopener">Adam Saleh</a>  <a href="https://accounts.fedoraproject.org/user/carlwgeorge/" target="_blank" rel="noreferrer noopener">Carl George</a>  <a href="https://accounts.fedoraproject.org/user/humaton/" target="_blank" rel="noreferrer noopener">Tomas Hrcka</a></figcaption></figure>



<p>The next session was hosted by <a href="https://accounts.fedoraproject.org/user/amoloney/" target="_blank" rel="noreferrer noopener">Aoife Moloney</a> who kicked off an interesting discussion about the limited-scope projects that the team undertakes and the maintainers for the applications that the team takes care of. The members participated in pointing out the things that currently work great and those that could use some improvements. This was the last planned session for the day and the group assembled to be a part of the “Community Platform Engineering family picture”. After that, they dispersed into small groups to have their lunches in their preferred places. </p>



<p>With no more planned talks after lunchtime, the team members were divided into smaller groups for breakout rooms to participate in more detailed discussions. <a href="https://accounts.fedoraproject.org/user/zlopez" target="_blank" rel="noreferrer noopener">Michal Konecny</a> lead the one for the infrastructure and release engineering team.&nbsp;</p>



<figure class="wp-block-image size-large"><a href="https://fedoramagazine.org/wp-content/uploads/2023/05/Group-Stories.jpeg"><img decoding="async" loading="lazy" width="1024" height="653" src="https://fedoramagazine.org/wp-content/uploads/2023/05/Group-Stories-1024x653.jpeg" alt="" class="wp-image-38361" srcset="https://fedoramagazine.org/wp-content/uploads/2023/05/Group-Stories-1024x653.jpeg 1024w, https://fedoramagazine.org/wp-content/uploads/2023/05/Group-Stories-300x191.jpeg 300w, https://fedoramagazine.org/wp-content/uploads/2023/05/Group-Stories-768x490.jpeg 768w, https://fedoramagazine.org/wp-content/uploads/2023/05/Group-Stories-816x520.jpeg 816w, https://fedoramagazine.org/wp-content/uploads/2023/05/Group-Stories.jpeg 1200w" sizes="(max-width: 1024px) 100vw, 1024px" /></a><figcaption class="wp-element-caption"><strong>From left to right</strong> &#8211; <a href="https://accounts.fedoraproject.org/user/zlopez/" target="_blank" rel="noreferrer noopener">Michal Konecny</a>  <a href="https://accounts.fedoraproject.org/user/carlwgeorge/" target="_blank" rel="noreferrer noopener">Carl George</a>  <a href="https://accounts.fedoraproject.org/user/t0xic0der/" target="_blank" rel="noreferrer noopener">Akashdeep Dhar</a>  <a href="https://accounts.fedoraproject.org/user/dkirwan/" target="_blank" rel="noreferrer noopener">David Kirwan</a>  <a href="https://accounts.fedoraproject.org/user/nphilipp/" target="_blank" rel="noreferrer noopener">Nils Philippsen</a>  <a href="https://accounts.fedoraproject.org/user/arrfab/" target="_blank" rel="noreferrer noopener">Fabian Arrotin</a>  <a href="https://accounts.fedoraproject.org/user/tdawson/" target="_blank" rel="noreferrer noopener">Troy Dawson</a>  <a href="https://accounts.fedoraproject.org/user/dherrera/" target="_blank" rel="noreferrer noopener">Diego Herrera</a></figcaption></figure>



<p>The team started slowly thinning down even more in the late afternoon, with the members bidding farewell to each other in the office and returning to the hotel. Some members decided to stay longer to explore Barcelona a bit more. Others began collecting their luggage from the hotel and leaving for the airport. With “goodbyes” waved to teammates and “resolves” about the next thing, the members departed from the face-to-face meeting with a new zeal and energy to contribute in an even better way to the community. </p>



<p>Even with minor hiccups and some teammates not being able to join the event, the meeting event turned out to be a grand success &#8211; both in uniting the members and in strategizing the team&#8217;s efforts. The members of the team surely look forward to the next time they get together.&nbsp;</p>


link: https://fedoramagazine.org/make-use-of-btrfs-snapshots-to-upgrade-fedora-linux-with-easy-fallback/
encoded_syndication_url: aHR0cDovL2ZlZG9yYW1hZ2F6aW5lLm9yZy9mZWVkLw==
read: False
type: Rss
title: Make use of Btrfs snapshots to upgrade Fedora Linux with easy fallback
categories: FAQs and Guides|btrfs|snapshot|system-upgrade
description:
Use a Btrfs snapshot as a fallback in case of any problems with a system upgrade. Think of it as a "save game" for your computer!

content:
<p>Back in 2018, a <a href="https://fedoramagazine.org/use-lvm-upgrade-fedora/" target="_blank" rel="noreferrer noopener">previous article</a> demonstrated how to use LVM to clone the root filesystem before upgrading Fedora Linux so as to have a fallback in the unlikely event that something goes wrong. Today, the default Fedora Workstation install uses Btrfs. Now you can use a Btrfs snapshot to make creating a bootable fallback much easier. Note that converting or migrating a system to Btrfs from another filesystem is outside the scope of this article.</p>



<span id="more-38259"></span>



<h2 class="wp-block-heading">Check that root filesystem is Btrfs</h2>



<p>This example uses a Pinebook aarch64 laptop. Before proceeding, first make sure that Btrfs is being used for the root (system) filesystem. Not every spin or image uses Btrfs by default.</p>



<pre class="wp-block-preformatted">$ df -T
Filesystem     Type     1K-blocks     Used Available Use% Mounted on
devtmpfs       devtmpfs      4096        0      4096   0% /dev
tmpfs          tmpfs       998992        0    998992   0% /dev/shm
tmpfs          tmpfs       399600     6360    393240   2% /run
/dev/mmcblk2p3 btrfs     56929280 39796116  15058348  73% /
tmpfs          tmpfs       998996       24    998972   1% /tmp
tmpfs          tmpfs      5242880        0   5242880   0% /var/lib/mock
/dev/mmcblk2p3 btrfs     56929280 39796116  15058348  73% /f34
/dev/mmcblk2p3 btrfs     56929280 39796116  15058348  73% /home
/dev/mmcblk2p2 ext4        996780   551888    376080  60% /boot
/dev/mmcblk2p1 vfat        194348    31648    162700  17% /boot/efi
tmpfs          tmpfs       199796      100    199696   1% /run/user/1000
tmpfs          tmpfs       199796       84    199712   1% /run/user/0</pre>



<h2 class="wp-block-heading">List the existing Btrfs subvolumes</h2>



<p>The above example output shows that the file system mounted on &#8220;root&#8221; (&#8220;/&#8221;) is type Btrfs. Notice that three mountpoints show the same backing device and the same <em>Used</em> and <em>Available</em> blocks. This is because they are parts (subvolumes) mounted from a single Btrfs filesystem. The <em>/f34</em> subvolume is my bootable snapshot from last year.</p>



<p>A default Fedora Btrfs install creates one Btrfs filesystem with two subvolumes &#8212; <em>root</em> and <em>home</em> &#8212; mounted on / and /home respectively. Let&#8217;s see what other subvolumes I&#8217;ve added:</p>



<pre class="wp-block-preformatted">$ sudo btrfs subvol list /
ID 272 gen 110428 top level 5 path root
ID 273 gen 110426 top level 5 path home
ID 300 gen 109923 top level 5 path f34
ID 301 gen 95852 top level 5 path home.22Jul26
ID 302 gen 95854 top level 5 path f36.22Jul26</pre>



<p>There is an <em>f34</em> subvol from the last system-upgrade and two readonly snapshots of <em>home</em> and <em>f36</em>. The easiest way to add and delete snapshots is to mount the Btrfs root. I will update the system and create a new snapshot of the current f36 <em>root</em> subvolume. If you have renamed your <em>root</em> subvolume, then you presumably know enough to adjust the following example accordingly for your system.</p>



<h2 class="wp-block-heading">Create the Btrfs fallback snapshot</h2>



<pre class="wp-block-preformatted">$ sudo dnf update --refresh
... lots of stuff updated (reboot if kernel updated)
$ sudo mkdir -p /mnt/root
$ sudo mount /dev/mmcblk2p3 /mnt/root
$ cd /mnt/root
$ ls
f34  f36.22Jul26  home  home.22Jul26  root
$ sudo btrfs subvol snapshot root f36
Create a snapshot of 'root' in './f36'</pre>



<p>Because Btrfs snapshots are filesystem based, it is not necessary to &#8220;sync&#8221; before the snapshot, as I recommended for LVM. To boot from the new subvol as a fallback, you will need to edit /mnt/root/f36/etc/fstab with your favorite editor. If you are a beginner, nano is a dirt simple text editor with minimal features. Here are some lines from my <em>fstab</em> file:</p>



<pre class="wp-block-preformatted">LABEL=PINE		/    btrfs   subvol=root,compress=zstd:1        1 1
UUID=e31667fb-5b6f-48d9-aa90-f2fd6aa5f005 /boot ext4    defaults        1 2
UUID=75DB-5832          /boot/efi               vfat    umask=0077,shortname=winnt 0 2
LABEL=PINE		/home    btrfs   subvol=home,compress=zstd:1    1 1
LABEL=SWAP swap			swap	discard=once	0 0</pre>



<p>Change <em>subvol=root</em> to <em>subvol=f36</em>. This change is to the file in the snapshot, not your production <em>fstab</em>. You can compare them with <kbd>diff /etc/fstab /mnt/root/f36/etc/fstab</kbd>. In my case, I also deleted my <em>f34</em> snapshot from last year with <kbd>sudo btrfs subvol delete f34</kbd>.</p>



<h2 class="wp-block-heading">Test the Btrfs fallback snapshot</h2>



<p>Now you are ready to test the fallback. You could use <a href="https://fedoramagazine.org/setting-kernel-command-line-arguments-with-fedora-30/" target="_blank" rel="noreferrer noopener">grubby</a> or edit an entry in /boot/loader/entries to change <em>subvol=root</em> to <em>subvol=f36</em>. But in the interest of safety for beginners, I will have you edit the GRUB entry at boot time instead. Check out  <a href="https://fedoramagazine.org/boot-earlier-kernel/" target="_blank" rel="noreferrer noopener">this article on GRUB</a> for tips on getting to the GRUB menu.  Once you are there, press the <strong>e</strong> key to edit the default kernel entry. Don&#8217;t worry &#8212; your changes are in volatile memory only. If you mess up, reboot to start over. Just like with fstab, find <em>subvol=root</em> and change it to <em>subvol=f36</em>. Press <strong>F10</strong> or <strong>Ctrl</strong>+<strong>X</strong> to boot your modified entry. With these changes, the system should boot into your new snapshot. Look at /etc/fstab to make sure you are booting from the right subvol, or enter <kbd>mount | grep subvol</kbd> to see what subvolume is mounted on &#8220;/&#8221;. </p>



<h2 class="wp-block-heading">Do the Fedora Linux system upgrade</h2>



<p>If your fallback is working, reboot back to your normal root filesystem (and confirm as above). Then proceed with the standard system-upgrade outlined on the <a href="https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/" target="_blank" rel="noreferrer noopener">wiki page</a>. TIP: Before running <kbd>dnf system-upgrade reboot</kbd>, make another snapshot of root. Call it something like <em>root.dl</em>. That way, you don&#8217;t have to download five gigabytes of packages again should you discover that there wasn&#8217;t enough free space. The snapshot will not take up any additional space because all but the downloaded packages are shared with <em>root</em> and <em>f36</em>. About that sharing of disk blocks … <br /><br /><kbd>dnf system-upgrade</kbd> gets confused about free space as reported by Btrfs because the f36 files in the <em>root</em> subvolume use the same disk locations as the same files in the <em>f36</em> subvolume. So removing them from the <em>root</em> subvolume during the upgrade process doesn&#8217;t actually free up any space. If you run out of space, and you reboot &#8212; the graphical user interface (GUI) won&#8217;t start. Use <strong>Ctrl</strong>+<strong>Alt</strong>+<strong>F2</strong> to login on a text console and practice your command line interface skills. Figuring out what to remove to free up space or how to expand the root filesystem is beyond the scope of this article (mine is often on an LVM volume and can be expanded). Having more than 50% free for the upgrade is a safe bet.</p>



<h2 class="wp-block-heading">Recovery</h2>



<p>Should something go wrong, you can reboot and edit the GRUB entry to boot the fallback. If you are a beginner, you&#8217;ll want some hand holding if you do end up needing to change the GRUB entry on disk (so you don&#8217;t have to edit at each boot). It is straight forward to delete or rename the broken <em>root</em> subvol.  Snapshot the <em>f36</em> subvol (or the <em>root.dl</em> snapshot) to try the system-upgrade process again. Here is an example of starting over after booting into the fallback system on subvol f36:</p>



<pre class="wp-block-preformatted">$ mount | grep subvol
$ sudo mount /dev/mmcblk2p3 /mnt/root
$ cd /mnt/root
$ sudo mv root root.failed
$ sudo btrfs subvol snapshot f36 root
Create a snapshot of 'f36' in './root'

Don't forget to edit /mnt/root/root/etc/fstab to change the subvol mounted on "/" to "root".</pre>



<p>As it turns out, the new kernel-6.2.11 for f38 did not boot on my Pinebook after the system-upgrade!  (Don&#8217;t worry, ARM is an alternative CPU architecture for Fedora Linux &#8212; this is very unlikely to happen to you on a mainstream device.) I was indeed able to boot back to f36 by editing the GRUB entry for kernel-6.2.10 at boot time as described above. I am now using f38 again &#8212; but with kernel-6.2.10 from f36. </p>



<p><strong>Update</strong>: <em>kernel-6.2.12 is out and it works on the Pinebook.</em></p>



<h2 class="wp-block-heading">Expiration</h2>



<p>As you update the f38 system, it will eventually want to delete the last f36 kernel from /boot. That is normally not a problem, as by that time you have settled into f38, and the f36 snapshot is just an archive.  If you want to keep your fork (f36 snapshot) bootable indefinitely, you should preserve a working f36 kernel under /boot. The simplest way to do so is to set <em>installonly_limit=0</em> in /etc/dnf/dnf.conf and manually remove old kernels. It is simple and safe (but annoying).<br /><br />Outline of a more complex solution (not for beginners): Run <kbd>find /boot -name "*fc36*"</kbd> to list all the kernel and GRUB files for your f36 subvolume snapshot that are under /boot (which is not in the snapshot). Copy them to a backup location (I would mount the f36 subvolume and copy to a backup directory there). While booted from f38, for each f36 kernel version, use dnf to remove that specific kernel version (for example, <kbd>dnf remove kernel-core-5.19.11-200.fc36</kbd>).  Do not remove the f38 kernels! Now restore the f36 kernels you saved to /boot. The f38 system doesn&#8217;t know about f36 kernels anymore, and it will not remove them from /boot.<br /><br />The problem with that method is the danger of accidentally removing the running f38 kernel. If anyone has a better method, let me know in the comments.</p>



<h2 class="wp-block-heading">Future directions</h2>



<p>Those comfortable with modifying GRUB entries might consider creating a snapshot subvolume named <em>f38</em>, modifying the current GRUB entry to boot into that, rebooting, and running the system-upgrade in that subvolume. Then always name the subvol for the root filesystem after the Fedora Linux release it contains. I did not do that for this article for two reasons.</p>



<ol>
<li>Naming the current active subvolume <em>root</em> matches the Fedora Linux default.</li>



<li>Sticking with <em>root</em> for the current subvol does not require any permanent changes outside of the normal system-upgrade procedure.</li>
</ol>



<p>As this article has demonstrated, readonly snapsnots are useful as local restore points in case things go wrong when making significant system changes (such as a system release upgrade). These snapshots can also be sent to a remote backup using Btrfs&#8217; <em>send</em> subcommand. (And if the remote backup device already contains previous backups, Btrfs can do an incremental send that only transmits changed files to save time and space.) If you intend to archive these snapshots long term, the key to not getting confused about which ones are which and what order to restore them is to use a consistent naming convention. See the article on <a href="https://fedoramagazine.org/btrfs-snapshots-backup-incremental/" target="_blank" rel="noreferrer noopener">Btrfs snapshots for backup</a> for more information about using Btrfs&#8217; <em>send</em> command to create backups.</p>

comments_url:
https://fedoramagazine.org/make-use-of-btrfs-snapshots-to-upgrade-fedora-linux-with-easy-fallback/feed/


link: https://fedoramagazine.org/use-fido-u2f-security-keys-with-fedora-linux/
encoded_syndication_url: aHR0cDovL2ZlZG9yYW1hZ2F6aW5lLm9yZy9mZWVkLw==
read: False
type: Rss
title: Use FIDO U2F security keys with Fedora Linux
categories: FAQs and Guides|CTAP|CTAP1|FIDO|FIDO2|Security Key|U2F|W3C|WebAuthn|YubiKey
comments_url: https://fedoramagazine.org/use-fido-u2f-security-keys-with-fedora-linux/feed/
description:
A FIDO U2F security key is a small USB and/or NFC based device. It is a hardware security token with modules for many security related use-cases. There are several brands of FIDO compliant keys, including NitroKey, SoloKey v2, and YubiKey. FIDO, in contrast to proprietary protocols like Yubico OTP, is hardware token agnostic and the [&#8230;]

content:
<p>A FIDO U2F security key is a small USB and/or NFC based device. It is a hardware security token with modules for many security related use-cases. There are several brands of FIDO compliant keys, including NitroKey, SoloKey v2, and YubiKey. FIDO, in contrast to proprietary protocols like Yubico OTP, is hardware token agnostic and the tools used are manufacturer independent.</p>



<p>This post introduces the FIDO protocol(s) and shows how to install and enable a FIDO U2F security key as an alternative authentication factor for logging into a terminal, GDM, or authenticating for sudo.</p>



<span id="more-38200"></span>



<p>For YubiKeys, especially older ones <em>without</em> FIDO2/U2F support, see the previous post titled &#8220;<a href="https://fedoramagazine.org/how-to-use-a-yubikey-with-fedora-linux/">How to use a YubiKey with Fedora Linux</a>&#8220;.</p>



<figure class="wp-block-embed is-type-wp-embed is-provider-fedora-magazine wp-block-embed-fedora-magazine"><div class="wp-block-embed__wrapper">
<blockquote class="wp-embedded-content" data-secret="c3WsreIZcz"><a href="https://fedoramagazine.org/how-to-use-a-yubikey-with-fedora-linux/">How to use a YubiKey with Fedora Linux</a></blockquote><iframe class="wp-embedded-content" sandbox="allow-scripts" security="restricted" title="&#8220;How to use a YubiKey with Fedora Linux&#8221; &#8212; Fedora Magazine" src="https://fedoramagazine.org/how-to-use-a-yubikey-with-fedora-linux/embed/#?secret=10dooDXm0Y#?secret=c3WsreIZcz" data-secret="c3WsreIZcz" width="600" height="338" frameborder="0" marginwidth="0" marginheight="0" scrolling="no"></iframe>
</div></figure>



<p>This post will not cover storing OpenPGP keys or X.509 certificates because those features are hardware dependent and not part of the FIDO U2F standard.</p>



<h2 class="wp-block-heading">Keep a backup security key</h2>



<p>As soon as you start working with security tokens you have to account for the potential to lock yourself out of accounts tied to these tokens. As hardware security tokens are unique and designed to be extremely hard to copy you cannot just make a backup of it like you can with software vaults like KeePass or AndOTP. Consequently, all registrations you make with your primary key you should immediately repeat with a second backup key that you will store in a secure location, maybe even a safe.</p>



<p>In practice this means you will need to register both hardware tokens with your Linux and web accounts, generate OpenSSH private keys twice, and upload both OpenSSH public keys to the servers and services you use (for example, GitHub).</p>



<p>Should you lose a key, you&#8217;ll want to use your second key to sign in on every service the keys are registered with, remove the lost key, and register a new one. This is especially true for password-less logins using a FIDO2 protocol.</p>



<h2 class="wp-block-heading">FIDO2, U2F and the FIDO Alliance</h2>



<p>FIDO2 is a collection of standards maintained by the <a href="https://fidoalliance.org" target="_blank" rel="noreferrer noopener">FIDO Alliance</a>. The FIDO Alliance hopes to eventually get rid of passwords altogether and instead provide procedures to authenticate users securely through multiple factors but without the need for passwords.</p>



<p>The standard consists of the World Wide Web Consortium&#8217;s (W3C) Web Authentication (WebAuthn) and the FIDO Alliance&#8217;s Client-to-Authenticator Protocol (CTAP). WebAuthn is a standard API to request and process public key challenges for authentication. With this, browsers send a challenge to a client which then produces a response with a private key that the challenger then verifies using a previously exchanged public key. How the challenge answer is produced is unknown to the service and it is controlled by the CTAP. The user might be prompted for several verification methods like biometrics, PIN, or presence check (or some combination of these methods). These checks are the same for authentication as they are when registering the key with the service.</p>



<p>A access PIN to protect any interaction with the hardware token is optional and it is unset by default. Most keys will self-invalidate after eight sequential failed attempts at entering the access PIN. The only way to recover an invalidated key and set a new PIN is to reset the key. However, when a key is reset, all its service registrations will be lost!</p>



<p>A FIDO2 key also supports the FIDO U2F protocol (now renamed CTAP1). This protocol is designed for second- or multi-factor (but not password-less) authentication. Linux&#8217;s PAM authentication system can also be configured to use the U2F protocol. Although FIDO U2F is not designed for password-less authentication, the U2F PAM module does allow password-less authentication.</p>



<h2 class="wp-block-heading">Security implications</h2>



<p>FIDO2 / U2F works by tying the security key to your user account. Most keys have a basic presence-check which is enabled / used by default. They typically perform a presence-check by lighting up and prompting you to touch the key. A FIDO2 PIN is optional and it will be unset by default. When the key is registered for signing in to your Linux account or for using sudo, it is sufficient to have the device and key physically present. A FIDO2 PIN is an important additional verification step to ensure that only you can use the key for authentication.</p>



<blockquote class="wp-block-quote">
<p>Wait! Now I have to keep track of an additional PIN? Isn&#8217;t this just a shorter password?</p>
<cite>The concerned reader</cite></blockquote>



<p>A FIDO2 PIN is not a password. It is a short, easy-to-remember phrase. This is not a problem because:</p>



<ol>
<li>You need physical access to the key <em>and</em> you need to know the PIN.</li>



<li>Failing to enter the PIN eight times will invalidate the key which makes it hard to brute-force.</li>
</ol>



<p>On the contrary, you can now use a secure password stored in a password manager that you don&#8217;t need to remember.</p>



<p>A 2016 case study by Google, titled &#8220;<em><a href="http://fc16.ifca.ai/preproceedings/25_Lang.pdf" target="_blank" rel="noreferrer noopener">Security Keys: Practical Cryptographic Second Factors for the Modern Web</a></em>&#8220;, shows security keys effectively protect users from password reuse, phishing and man-in-the-middle attacks.</p>



<h2 class="wp-block-heading">User authentication using PAM</h2>



<p>Local system authentication uses <a href="https://www.redhat.com/sysadmin/pluggable-authentication-modules-pam" target="_blank" rel="noreferrer noopener">Pluggable Authentication Modules (PAM)</a>. The PAM module for U2F devices (and hence authentication) is <em>pam_u2f</em>. Whether your key supports FIDO2 or FIDO U2F will depend on its firmware version and hardware model.</p>



<p>The setup is as follows:</p>



<ol>
<li>Install the PAM module.</li>



<li>Register a key with your user account.</li>



<li>Use <em>authselect</em> to activate smart card support in PAM.</li>
</ol>



<p><a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_authentication_and_authorization_in_rhel/configuring-user-authentication-using-authselect_configuring-authentication-and-authorization-in-rhel" target="_blank" rel="noreferrer noopener">Authselect</a> is a tool for configuring PAM with reproducible profiles. By using authselect&#8217;s profiles, manually altering configuration files under the /etc/pam.d directory can be avoided.</p>



<h2 class="wp-block-heading">Dependencies</h2>



<p>The required packages are available in the official repositories.</p>



<pre class="wp-block-preformatted">[…]$ sudo dnf install pam-u2f pamu2fcfg fido2-tools</pre>



<h3 class="wp-block-heading">Set a FIDO2 PIN on your key</h3>



<p>The FIDO2 standard defines an optional PIN for access protection. There is no PUK or other way to restore a lost or invalidated PIN so make sure you have a backup approach for authentication. If the PIN is invalidated through sequential entry of invalid PINs, the only way to recover is to reset the key. However, resetting your key removes all its credentials and disconnects it from all previously registered services.</p>



<p>The <em>fido2-tools</em> package contains a tool to set the FIDO2 PIN of your key: <em>fido2-token</em>. Get a list of currently connected FIDO2 devices with <kbd>fido2-token -L</kbd> and set a new pin with <kbd>fido2-token -C &lt;/path/to/device&gt;</kbd>:</p>



<pre class="wp-block-preformatted">[…]$ fido2-token -L
/dev/hidraw1: vendor=0x1050, product=0x0407 (Yubico YubiKey OTP+FIDO+CCID)
[…]$ fido2-token -C /dev/hidraw1
Enter current PIN for /dev/hidraw1: 
Enter new PIN for /dev/hidraw1:</pre>



<h3 class="wp-block-heading"><strong>Register the security key with your local account(s)</strong></h3>



<p>Use the tool <em>pamu2fcfg</em> to retrieve a configuration line that goes into ~/.config/Yubico/u2f_keys. <em>pam_u2f</em> is a Yubico-provided, generic module for U2F keys, hence the Yubico specific default configuration path. Each configuration line in this file consists of a username and a key-specific credential / config part separated by colons. Be sure to only use one line per user.</p>



<pre class="wp-block-preformatted">fedora-user:owBYtPIH2yzjlSQaRrVcxB...Pg==,es256,+presence+pin[:another key for this user]</pre>



<p>If the key is PIN protected you&#8217;ll be asked to enter the PIN for this operation. Use the following for the initial registration of your first key:</p>



<pre class="wp-block-preformatted">[…]$ mkdir -p ~/.config/Yubico
[…]$ pamu2fcfg --pin-verification &gt; ~/.config/Yubico/u2f_keys</pre>



<p>To add another key (for example, your backup key) to this single-user configuration, use the following command:</p>



<pre class="wp-block-preformatted">[…]$ pamu2fcfg --nouser --pin-verification &gt;&gt; ~/.config/Yubico/u2f_keys</pre>



<p><em>pam_u2f</em> also supports the use of a central authentication file. In that case, be sure to use one line per user and to keep all the keys of a given user on the same line. If two lines reference the same username only the last one will be used! Have a look at the <a href="https://manpages.org/pam_u2f/8" target="_blank" rel="noreferrer noopener">pam_u2f man page</a> for all available options.</p>



<h2 class="wp-block-heading">Configure PAM with authselect</h2>



<p><strong><a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_authentication_and_authorization_in_rhel/configuring-user-authentication-using-authselect_configuring-authentication-and-authorization-in-rhel" target="_blank" rel="noreferrer noopener">authselect</a></strong> is a tool for controling your system&#8217;s PAM configuration. It introduces profiles as an additional layer of abstraction. One authselect profile can change several PAM configuration files. Profiles have parameters that control additional features and behaviors like enabling FIDO U2F security keys. A detailed tour of <em>authselect</em> is planned for a future article.</p>



<p>Display the currently active <em>authselect</em> profile. With the SSSD (System Security Service Daemon) profile selected and U2F support enabled, the output might resemble the following:</p>



<pre class="wp-block-preformatted">[…]$ authselect current
Profile ID: sssd
Enabled features:
- with-pam-u2f</pre>



<p>Activate FIDO U2F support in PAM using <em>authselect</em> with the <em>with-pam-u2f</em> flag:</p>



<pre class="wp-block-preformatted">[…]$ sudo authselect select sssd with-pam-u2f</pre>



<p>If you also want to use your fingerprint reader you have to enable both features:</p>



<pre class="wp-block-preformatted">[…]$ sudo authselect select sssd with-pam-u2f with-fingerprint</pre>



<p>This activates the <em>sssd</em> profile with <em>pam_u2f</em> and fingerprint reader support. For example, when using sudo on a terminal with the above authselect profile configuration, you&#8217;ll first be asked for a fingerprint and if that fails for the U2F key. GDM, however, will use the U2F key first.</p>



<h2 class="wp-block-heading">Unlocking the GNOME keyring daemon</h2>



<p>When using biometrics, a U2F key, or any other method that does not require a passphrase to sign in to GNOME, the <em>Login</em> keyring cannot be unlocked automatically. This is because, by default, the keyring passphrase is set to the same value as your login passphrase. Normally, PAM passes your login passphrase to the keyring daemon. Since you are not entering a passphrase when authenticating via methods such as biometrics or U2F keys, there is no passphrase for PAM to pass to the keyring daemon. There is no straight forward solution to this problem.</p>



<p>If you use LUKS encryption for your home partition and operate a single-user system, you could remove the passphrase from your keyring. This will leave your gnome keyring unencrypted at the file level. But it will still be encrypted at the block level by LUKS. LUKS encryption is equivalent to the default file-based keyring encryption on a single-user system since the keyring&#8217;s encryption is only designed to protect its contents from offline access. The keyring will be decrypted / unlocked after login either way and any runtime application or malware can potentially access the keyring&#8217;s contents after it is unlocked. Since LUKS is also an offline protection mechanism, it can be considered an equivalent alternative to the keyring&#8217;s normal file-based encryption.</p>



<p>LUKS encryption and the keyring&#8217;s normal file-based encryption are not equivalent if your system is used by multiple users. In the case of a multi-user system with the keyrings protected only by LUKS, any user with authorization to decrypt the disk and boot the system will be able to access any other user&#8217;s keyring on that same system.</p>



<p>Removing the GNOME <em>Login</em> keyring passphrase is straight forward. Just set a new empty password and the keyring will be unlocked and it will be stored unencrypted at the file level. The graphical utility <em>seahorse</em> (also called <em>Passwords and Keys</em>) can be used to set a blank password on your GNOME <em>Login</em> keyring.</p>



<h2 class="wp-block-heading">Lookout and other use-cases</h2>



<p>Upcoming articles will explore how to use FIDO2/U2F keys for unlocking LUKS-encrypted disks using the U2F Dracut plugin.</p>



<p>OpenSSH 8.2+ supports the use of <em>ed25519-sk</em> security keys. This topic has already been touched upon in the previous article titled &#8220;<a href="https://fedoramagazine.org/how-to-use-a-yubikey-with-fedora-linux/">How to use a YubiKey with Fedora Linux</a>&#8220;.</p>



<p>Note that FIDO2/U2F is an authentication standard. There are other use-cases for security tokens (primarily established by Yubico) like (T)OTP, PIV (for x509 key management) or OpenPGP which are not covered in general but on a hardware by hardware basis.</p>


link: https://fedoramagazine.org/trying-different-desktop-environments-using-rpm-ostree/
encoded_syndication_url: aHR0cDovL2ZlZG9yYW1hZ2F6aW5lLm9yZy9mZWVkLw==
read: False
type: Rss
title: Trying different desktop environments using “rpm-ostree rebase”
categories: Fedora Project community
comments_url: https://fedoramagazine.org/trying-different-desktop-environments-using-rpm-ostree/feed/
description:
Fedora Linux Workstation features a GNOME desktop environment which is an easy to use, intuitive, and efficient desktop environment. But this is not the only option if you would like to use Fedora Linux. There are other spins that provide alternative desktop environments like KDE, XFCE, Cinnamon, etc. This article describes how you can try [&#8230;]

content:
<p>Fedora Linux Workstation features a GNOME desktop environment which is an easy to use, intuitive, and efficient desktop environment. But this is not the only option if you would like to use Fedora Linux. There are other spins that provide alternative desktop environments like KDE, XFCE, Cinnamon, etc. This article describes how you can try different desktop environments if you are using an OSTree based Fedora Linux spins.</p>



<span id="more-38288"></span>



<h2 class="wp-block-heading">Main version of Fedora Workstation</h2>



<p>If you installed a non-OSTree Fedora Workstation or one of the Spins and would like to try different desktop environment, you have some possibilities:</p>



<ul>
<li>install different desktop environment using <em>dnf</em></li>



<li>dual boot multiple spins of Fedora</li>
</ul>



<p>If you choose the first option, you have to install another desktop environment by using the <em>dnf install </em>command. This technique enables you to select which desktop environment you would like to use on the login screen after system boots. Using this method will pull in a lot of dependencies. This is  especially true when you have a GTK based desktop environment (like GNOME) and install a QT based (like KDE), or vice-versa. It can be difficult to completely uninstall one of the installed desktop environment if you are not satisfied with them.</p>



<p>Another issue with this is that system apps may be doubled in the application menu on each environment. For example, if you have installed GNOME and install KDE, you have Nautilus and Dolphin for browsing files, GNOME Terminal and Konsole for terminal emulation, etc. You have to remember which app to use on which environment, because apps from KDE behave worse on GNOME and vice-versa.</p>



<p>If you choose the second option, you have to make some free unpartitioned space on your hard drive to install another Fedora spin alongside one you are currently using. In this way, the systems are separated from each other and the system apps will not be doubled. You can decide to share the <em>/home</em> partition between them. This technique enables you select the system to use in the bootloader menu before system boots. But if you use this method, you have to maintain these systems separately (for example installing updates) and it consumes a lot of free space on the hard drive.</p>



<h2 class="wp-block-heading">OSTree based version of Fedora Workstation</h2>



<p>Some variants of Fedora Linux are OSTree based. OSTree provides immutability and transactional upgrades with the possibility of rollback in case something goes wrong. You can read more about it in <a href="https://fedoramagazine.org/pieces-of-fedora-silverblue/" target="_blank" rel="noreferrer noopener">this great article.</a> Right now, we have three OSTree based Fedora Workstation variants:</p>



<ul>
<li>Silverblue &#8211; provides GNOME desktop environment</li>



<li>Kinoite &#8211; provides KDE Plasma desktop environment</li>



<li>Sericea &#8211; provides Sway window manager (not recommended for beginners)</li>
</ul>



<p>If you are running one of these variants of Fedora Linux, you can easily switch your system to another OSTree compatible one to try different desktop environment. This process is similar to doing a system upgrade. OSTree guarantees that the operation is transactional (finishes successfully or nothing is changed) and you are able to rollback if you are not satisfied with the change. The operation does not consume much space on the hard drive, and system apps are not doubled.</p>



<h3 class="wp-block-heading">How to use OSTree rebase to switch to a new variant</h3>



<p>To start, I recommend executing the following command to pin the current deployment. This makes certain it will not be deleted automatically in the future and provides the ability to roll back to it. </p>



<pre class="wp-block-preformatted">$ sudo ostree admin pin 0</pre>



<p>If you have a pending update, the command may fail with the message:</p>



<pre class="wp-block-preformatted">error: Cannot pin staged deployment</pre>



<p>In this case, reboot your system to apply pending updates,  and try again.</p>



<p>After pinning the deployment, execute:</p>



<pre class="wp-block-preformatted">$ ostree remote refs fedora</pre>



<p>It outputs a list of all available branches that you can rebase into. Every branch has an architecture, version, and the name of the variant. Select carefully. In the following examples I assume you would like to rebase into the current stable version of Fedora for x86_64 (version 38). </p>



<ul>
<li>for Fedora Silverblue, use fedora:fedora/38/x86_64/silverblue</li>



<li>for Fedora Kinoite, use fedora:fedora/38/x86_64/kinoite</li>



<li>for Fedora Sericea, use fedora:fedora/38/x86_64/sericea</li>
</ul>



<p>Choose the branch you wish to rebase into and execute the following command (change the branch name provided in the example if necessary):</p>



<pre class="wp-block-preformatted">$ rpm-ostree rebase fedora:fedora/38/x86_64/kinoite</pre>



<p>When  this command succeeds, restart the system to begin using the new desktop environment. If it fails, the system should continue to work unmodified thanks to transactional updates provided by OSTree.  </p>



<h3 class="wp-block-heading">Undo the rebase into an OSTree variant</h3>



<p>If you are not satisfied with the new environment the following command will return you to your original variant:</p>



<pre class="wp-block-preformatted">rpm-ostree rollback</pre>



<p>Restart your system once again to switch back to the previous variant of Fedora.</p>


link: https://fedoramagazine.org/new-aws-storage-type-for-fedora-linux/
encoded_syndication_url: aHR0cDovL2ZlZG9yYW1hZ2F6aW5lLm9yZy9mZWVkLw==
read: False
type: Rss
title: New AWS storage type for Fedora Linux
description: Fedora Linux now has a better performing default storage option at a lower cost on AWS.
categories: Fedora Project community|AWS|Cloud
comments_url: https://fedoramagazine.org/new-aws-storage-type-for-fedora-linux/feed/
content:
<p>If you filter Fedora Linux AWS images using a script, you might notice a change in the image names. The Fedora Cloud SIG recently updated the image publishing configuration to use the latest generation storage option and simplify the image listings.</p>



<span id="more-38326"></span>



<p>This involves two changes:</p>



<ul>
<li>Replacing <em>gp2</em> storage with <em>gp3</em> storage by default for new images</li>



<li>Removing <em>standard</em> storage from new images</li>
</ul>



<h2 class="wp-block-heading">What&#8217;s the benefit of these changes?</h2>



<p>The <em>gp3</em> storage type appeared in 2020 and switching to that storage type for Fedora Linux users means more consistent performance for a lower cost. (For more details, read Corey Quinn&#8217;s <a href="https://www.lastweekinaws.com/blog/the-best-release-of-reinvent-2020/" target="_blank" rel="noreferrer noopener">helpful blog post</a>.)</p>



<p>Removing <em>standard</em> storage from new image uploads means we&#8217;re creating half the AMIs we created before and it reduces the number of images you need to review when launching an instance. Finding the right Fedora Linux image for your deployment should be a little easier.</p>



<h2 class="wp-block-heading">What if I really like the other storage types?</h2>



<p>When you launch your instance, you can choose any storage type that is compatible with your instance in your preferred region. Although Fedora Linux images will have <em>gp3</em> set as the default, you can choose from any other storage type at launch time.</p>



<h2 class="wp-block-heading">How should I adjust my scripts that look for Fedora Linux images on AWS?</h2>



<p>The format of the image names remains the same, but you&#8217;ll notice a new string in the storage type portion of the image name. As an example, here&#8217;s what you would see before the change was made:</p>



<pre class="wp-block-preformatted">Fedora-Cloud-Base-Rawhide-20230503.n.0.aarch64-hvm-us-east-1-standard-0
Fedora-Cloud-Base-Rawhide-20230503.n.0.aarch64-hvm-us-east-1-gp2-0
Fedora-Cloud-Base-Rawhide-20230503.n.0.x86_64-hvm-us-east-1-standard-0
Fedora-Cloud-Base-Rawhide-20230503.n.0.x86_64-hvm-us-east-1-gp2-0</pre>



<p>After the change, there is only one image per release and architecture:</p>



<pre class="wp-block-preformatted">Fedora-Cloud-Base-Rawhide-20230504.n.0.aarch64-hvm-us-east-1-gp3-0
Fedora-Cloud-Base-Rawhide-20230504.n.0.x86_64-hvm-us-east-1-gp3-0</pre>



<h2 class="wp-block-heading">Why was this change made?</h2>



<p>The Fedora Cloud SIG wants to make the Fedora Linux cloud experience the best it can possibly be on every public cloud platform. This change gives Fedora Linux a better performing default storage option at a lower cost, reduces the overhead from creating AMIs on AWS, and simplifies the Fedora Linux image listings.</p>



<p>Read the Fedora change proposals for <a href="https://fedoraproject.org/wiki/Changes/CloudEC2ImagesNoStandardStorage">removing standard storage</a> and <a href="https://fedoraproject.org/wiki/Changes/CloudEC2gp3">switching the default to gp3</a> for a lot more detail. As always, you can find members of the Fedora Cloud SIG and join our group on <a href="https://chat.fedoraproject.org/#/room/#cloud:fedoraproject.org">Fedora Matrix</a> or on Libera IRC in <kbd>#fedora-cloud</kbd>.</p>


link: https://arstechnica.com/?p=1951385
encoded_syndication_url: aHR0cHM6Ly9hcnN0ZWNobmljYS5jb20vZmVlZC8=
read: False
type: Rss
title: Mars has liquid guts and strange insides, InSight suggests
description: Wobbles in its rotation are difficult to explain without a liquid core.
categories: Science|astronomy|Insight|Mars|NASA|planetary science
content:
<div id="rss-wrap">
<div>
      <img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/PIA22743-800x200.png">
  
<p class="caption" style="font-size:0.8em">Artist's view of what InSight looked like after landing. (credit: <a rel="nofollow" class="caption-link" href="https://mars.nasa.gov/resources/22116/insight-deploys-its-instruments/?site=insight">NASA/JPL-Caltech</a>)</p>
</div>





<div><a name="page-1"></a></div>
<p><a href="https://arstechnica.com/science/2022/12/marsquakes-recent-volcanism-suggest-mars-still-has-a-mantle-plume/">Mars</a> appears to be a frozen expanse of red dust, gaping craters, and rocky terrain on the outside—but what lies beneath its wind-blasted surface? NASA’s <a href="https://arstechnica.com/science/2022/10/insight-and-mars-orbiter-use-impacts-to-give-new-info-on-mars-interior/">InSight lander</a> might have discovered this before it took its proverbial last breaths in a <a href="https://arstechnica.com/science/2022/12/nasas-insight-lander-has-probably-phoned-home-for-the-last-time/">dust storm</a>.</p>
<p>Whether the core of Mars is solid or liquid has been long debated. While there is no way to observe the Martian <a href="https://arstechnica.com/science/2021/07/marsquakes-illuminate-what-lies-beneath-the-sands-of-mars/">core</a> directly, InSight tried. Its seismometer, SEIS, was the first instrument to find possible evidence of a liquid core. In the meantime, its RISE (Rotation and Interior Structure Experiment) instrument had been measuring minuscule changes in the planet’s rotation as it orbited, “wobbles” in its axis caused by the push and pull of the Sun’s gravity.</p>
<p>“Our analysis of InSight’s radio tracking data argues against the existence of a solid inner core and reveals the shape of the core, indicating that there are internal mass anomalies deep within the mantle,” write the researchers behind the instrument in a <a href="https://astronomycommunity.nature.com/posts/detection-of-tiny-variations-in-the-rotation-of-mars-used-to-characterize-its-liquid-core">study</a> recently published in Nature.</p></div><p><a href="https://arstechnica.com/?p=1951385#p3">Read 11 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1951385&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/science/2023/07/mars-has-liquid-guts-and-strange-insides-insight-suggests/feed/


link: https://arstechnica.com/?p=1951456
encoded_syndication_url: aHR0cHM6Ly9hcnN0ZWNobmljYS5jb20vZmVlZC8=
read: False
type: Rss
title: SpaceX launches groundbreaking European dark energy mission
description: SpaceX is filling in for ESA as European rockets face delays.
categories: Space|astronomy|dark energy|Dark Matter|ESA|euclid
content:
<div id="rss-wrap">
<div>
      <img src="https://cdn.arstechnica.net/wp-content/uploads/2023/07/IMG_0440-800x649.jpg">
  
<p class="caption" style="font-size:0.8em">SpaceX's Falcon 9 rocket soars through the sky over Cape Canaveral with Europe's Euclid space telescope. (credit: Stephen Clark/Ars Technica)</p>
</div>





<div><a name="page-1"></a></div>
<p>A European Space Agency telescope launched Saturday on top of a SpaceX Falcon 9 rocket from Florida to begin a $1.5 billion mission seeking to answer fundamental questions about the unseen forces driving the expansion of the Universe. The Euclid telescope, named for the ancient Greek mathematician, will observe billions of galaxies during its six-year survey of the sky, measuring their shapes and positions going back 10 billion years, more than 70 percent of cosmic history.</p>
<p>Led by the European Space Agency, the Euclid mission has the ambitious goal of helping astronomers and cosmologists learn about the properties and influence of <a href="https://arstechnica.com/science/2022/06/an-astrophysicist-explains-the-often-misunderstood-nature-of-dark-energy/">dark matter and dark energy</a>, which are thought to make up about 95 percent of the Universe. The rest of the cosmos is made of regular atoms and molecules that we can see and touch.</p>
<h2>Stumbling in the dark</h2>
<p>“To highlight the challenge we face, I would like to give the analogy: It’s very difficult to find a black cat in a dark room, especially if there’s no cat,” said Henk Hoekstra, a professor and cosmologist at Leiden Observatory in the Netherlands. “That’s a little bit of the situation we find ourselves in because we have these observations … But we lack a good theory. So far, nobody has come up with a good explanation for dark matter or dark energy.”</p></div><p><a href="https://arstechnica.com/?p=1951456#p3">Read 32 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1951456&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/space/2023/07/europes-euclid-telescope-launched-to-study-the-dark-universe/feed/


link: https://arstechnica.com/?p=1951322
encoded_syndication_url: aHR0cHM6Ly9hcnN0ZWNobmljYS5jb20vZmVlZC8=
read: False
type: Rss
title: Clever DNA tricks
description: As cells divide, they must copy all of their chromosomes only once or chaos will ensue.
categories: Science|DNA|syndication
comments_url: https://arstechnica.com/science/2023/07/clever-dna-tricks/feed/
content:
<div id="rss-wrap">
<div>
      <img src="https://cdn.arstechnica.net/wp-content/uploads/2017/03/DNA-Stock-Image_22532584_SMALL-800x600.jpg">
  
<p class="caption" style="font-size:0.8em">(credit: <a rel="nofollow" class="caption-link" href="https://commonfund.nih.gov/newinnovator/programhighlights">NIH</a>)</p>
</div>





<div><a name="page-1"></a></div>
<div class="article-content">
<p>Every person starts as just one fertilized egg. By adulthood, that single cell has turned into roughly 37 trillion cells, many of which keep dividing to create the same amount of fresh human cells every few months.</p>
<p>But those cells have a formidable challenge. The average dividing cell must copy—perfectly—3.2 <em>billion</em> base pairs of DNA, about once every 24 hours. The cell’s replication machinery does an amazing job of this, copying genetic material at a lickety-split pace of some 50 base pairs per second.</p>
<p>Still, that’s much too slow to duplicate the entirety of the <a href="https://knowablemagazine.org/article/living-world/2020/the-blueprint-life-neatly-folded" target="_blank" rel="noopener">human genome</a>. If the cell’s copying machinery started at the tip of each of the 46 chromosomes at the same time, it would finish the longest chromosome—No. 1, at 249 million base pairs—in about two months.</p>
<p>“The way cells get around this, of course, is that they start replication in multiple spots,” says James Berger, a structural biologist at the Johns Hopkins University School of Medicine in Baltimore, who co-authored <a href="https://www.annualreviews.org/doi/10.1146/annurev-biochem-090120-125407" target="_blank" rel="noopener">an article on DNA replication in eukaryotes</a> in the 2021 Annual Review of Biochemistry. Yeast cells have hundreds of potential replication origins, as they’re called, and animals like mice and people have tens of thousands of them, sprinkled throughout their genomes.</p>
<p>“But that poses its own challenge,” says Berger, “which is, how do you know where to start, and how do you time everything?” Without precision control, some DNA might get copied twice, causing cellular pandemonium.</p>
<p>Keeping tight reins on the kickoff of DNA replication is particularly important to avoid that pandemonium. Today, researchers are making steps toward a full understanding of the molecular checks and balances that have evolved in order to ensure that each origin initiates DNA copying once and only once, to produce precisely one complete new genome.</p>
<h2>Do it right, do it fast</h2>
<p>Bad things can happen if replication doesn’t start correctly. For DNA to be copied, the DNA double helix must open up, and the resulting single strands—each of which serves as a template for building a new, second strand—are vulnerable to breakage. Or the process can get stuck. “You really want to resolve replication quickly,” says John Diffley, a biochemist at the Francis Crick Institute in London. Problems during DNA replication can cause the genome to become disorganized, which is often a key step on the route to cancer.</p>
<p>Some genetic diseases, too, result from <a href="https://www.mdpi.com/1422-0067/22/2/911" target="_blank" rel="noopener">problems with DNA replication</a>. For example, Meier-Gorlin syndrome, which involves short stature, small ears, and small or no kneecaps, is caused by mutations in several genes that help to kick off the DNA replication process.</p>
<p>It takes a tightly coordinated dance involving dozens of proteins for the DNA-copying machinery to start replication at the right point in the cell’s life cycle. Researchers have a pretty good idea of which proteins do what, because they’ve managed to make DNA replication happen in cell-free biological mixtures in the lab. They’ve mimicked the first crucial steps in initiation of replication <a href="https://www.nature.com/articles/nature14285" target="_blank" rel="noopener">using proteins from yeast</a>—the same kind used to make bread and beer—and they’ve mimicked much of the entire replication process <a href="https://www.nature.com/articles/s41586-022-04759-1" target="_blank" rel="noopener">using human versions of replication proteins</a>, too.</p>
<p>The cell controls the start of DNA replication in a two-step process. The whole goal of the process is to control the actions of a crucial enzyme—called a helicase—that unwinds the DNA double helix in preparation for copying it. In the first step, inactive helicases are loaded onto the DNA at the origins, where replication starts. During the second step, the helicases are activated, to unwind the DNA.</p>
<h2>Ready (load the helicase) …</h2>
<p>Kicking off the process is a cluster of six proteins that sit down at the origins. Called ORC, this cluster is <a href="https://www.nature.com/articles/nature14239" target="_blank" rel="noopener">shaped like a double-layer ring</a> with a handy notch that allows it to slide onto the DNA strands, Berger’s team has found.</p>
<p>In baker’s yeast, which is a favorite for scientists studying DNA replication, these start sites are easy to spot: They have a specific, 11- to 17-letter core DNA sequence, rich in adenine and thymine chemical bases. Scientists have watched as ORC grabs onto the DNA and then slides along, <a href="https://www.nature.com/articles/s41467-021-22216-x" target="_blank" rel="noopener">scanning for the origin sequence</a> until it finds the right spot.</p>
<p>But in humans and other complex life forms, the start sites aren’t so clearly demarcated, and it’s not quite clear what makes the ORC settle down and grab on, says Alessandro Costa, a structural biologist at the Crick Institute who, with Diffley, wrote <a href="https://www.annualreviews.org/doi/10.1146/annurev-biochem-072321-110228" target="_blank" rel="noopener">about DNA replication initiation</a> in the 2022 Annual Review of Biochemistry. Replication seems more likely to start in places where the genome—normally tightly spooled around proteins called histones—has loosened up.</p>
<div class="centered-figure-container"><div class="image center full"><img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/Screenshot-2023-06-30-at-09-19-03-Clever-DNA-tricks.png"><p class="caption" style="font-size:0.8em">The initiation of DNA replication starts at the tail end of the previous cell division and continues through the cell cycle phase known as G1. DNA synthesis happens during the S phase. Levels of a protein called CDK are critical to ensuring that DNA is replicated once and only once. When CDK levels are low, helicases can jump onto the DNA and start to unwind it. But repeat binding does not happen because CDK levels rise, and this blocks the helicase from binding again. (credit: <a rel="nofollow" class="caption-link" href="https://knowablemagazine.org/article/living-world/2023/how-dna-is-copied">Knowable Magazine</a>)</p></div></div>
<p>Once ORC has settled onto the DNA, it attracts a second protein complex: one that includes the helicase that will eventually unwind the DNA. Costa and colleagues used electron microscopy to work out how ORC <a href="https://www.nature.com/articles/s41586-019-1768-0" target="_blank" rel="noopener">lures in first one helicase, and then another</a>. The helicases are also ring-shaped, and each one opens up to wrap around the double-stranded DNA. Then the two helicases close up again, facing toward each other on the DNA strands, like two beads on a string.</p>
<p>At first, they just sit there, like cars with no gas in the tank. They haven’t been activated yet, and for now the cell goes about its usual business.</p>
<div><a name="page-2"></a></div>
<h2>Get set (activate the helicase)...</h2>
<p>Things kick into high gear when a crucial molecule called CDK waves the green flag, jump-starting chemical steps that lure in even more proteins. One of them is DNA polymerase—what Costa calls the “typewriter” that will build new DNA strands—which hitches onto each helicase. Others activate the helicases, which can now burn energy to chug along the DNA.</p>
<p>As this occurs, the helicases change shape, pushing on one DNA strand and pulling on the other. This creates strain on the weak hydrogen bonds that normally hold the two strands together by the bases—the As, Cs, Ts and Gs that make up the rungs of the DNA ladder. The two strands get ripped apart. Costa and colleagues have observed how the two helicases <a href="https://www.nature.com/articles/s41586-022-04829-4" target="_blank" rel="noopener">untwist the DNA between them</a>, and they’ve seen how the helicases keep the unbound bases stable and out of the way.</p>
<div class="centered-figure-container"><div class="image center large"><a href="https://cdn.arstechnica.net/wp-content/uploads/2023/06/Screenshot-2023-06-30-at-09-20-12-Clever-DNA-tricks.png"><img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/Screenshot-2023-06-30-at-09-20-12-Clever-DNA-tricks-640x438.png" srcset="https://cdn.arstechnica.net/wp-content/uploads/2023/06/Screenshot-2023-06-30-at-09-20-12-Clever-DNA-tricks.png 2x"></a><p class="caption" style="font-size:0.8em"><a href="https://cdn.arstechnica.net/wp-content/uploads/2023/06/Screenshot-2023-06-30-at-09-20-12-Clever-DNA-tricks.png" class="caption-link" rel="nofollow">Left: Several genes involved in the initiation of DNA replication (horizontal axis) are amplified—that is, mistakenly copied in extra numbers — to varying degrees (vertical axis) in different cancers. Right: On chromosome 8, a cluster of three genes—shown in green text—are frequently amplified together in certain cancers.</a> (credit: <a rel="nofollow" class="caption-link" href="https://knowablemagazine.org/article/living-world/2023/how-dna-is-copied">Knowable Magazine</a>)</p></div></div>
<h2>Go!</h2>
<p>At first, both helicases are wrapped around both strands of DNA, and they can’t get very far like this, because they are facing each other and will just run into each other. But next, they each undergo a change in position, spitting one DNA strand or the other out of the ring. Now separated, they can jostle past each other, and replication proceeds apace.</p>
<p>Each helicase motors along its single strand, in the opposite direction from the other. They leave the origin behind and yank apart those hydrogen-bonded base pairs as they travel. The DNA polymerase is right behind, copying the DNA letters as they’re freed from their partners.</p>
<p>CDK’s second job is to stop any more helicases from hopping on the origins. Thus, there is one start of replication per origin, ensuring proper copying of the genome—although copying doesn’t begin at the same time at each site. The whole process of DNA replication, in human cells, takes about eight hours.</p>
<p>There is still plenty to be worked out. For one thing, the DNA that’s being copied is not a naked double helix. It’s wrapped around histones and attached to lots of other proteins that are busy turning genes on or off or <a href="https://knowablemagazine.org/article/living-world/2020/what-do-genes-do-things-know" target="_blank" rel="noopener">making RNA copies of the genes</a>. How do those jostling proteins affect each other and avoid getting in each other’s way?</p>
<p>Beyond this fascinating, fundamental biology—a remarkable process essential for all life on Earth—there are implications for diseases like cancer. Scientists already know that faulty replication can destabilize DNA, and an unstable genome that’s prone to mutation may be an early hallmark of cancer development. And they are <a href="https://reporter.nih.gov/search/kOCJ2EoIXUyMRjVy9712gA/projects" target="_blank" rel="noopener">further investigating</a> links between replication proteins and cancer.</p>
<p>“I think that there are opportunities for therapeutic interventions for these systems,” says Berger, “once we have enough insights about how they work and what they look like.”</p>
<p><em><b>Amber Dance</b>, a science writer in the Los Angeles area, also likes to break large tasks into smaller segments: It took her five days to complete the steps to draft this article. This article originally appeared in <a href="https://knowablemagazine.org/article/living-world/2023/how-dna-is-copied">Knowable Magazine</a>, an independent journalistic endeavor from Annual Reviews. Sign up for the <a href="https://www.knowablemagazine.org/page/newsletter-signup">newsletter</a>.</em></p>
<p><img style="height: 40px;" src="https://www.knowablemagazine.org/assets/images/logo-k.svg" alt="Knowable Magazine | Annual Reviews"></p>
</div>

</div><p><a href="https://arstechnica.com/?p=1951322">Read on Ars Technica</a> | <a href="https://arstechnica.com/?p=1951322&comments=1">Comments</a></p>


link: https://arstechnica.com/?p=1951436
encoded_syndication_url: aHR0cHM6Ly9hcnN0ZWNobmljYS5jb20vZmVlZC8=
read: False
type: Rss
title: Saturn’s rings steal the show in new image from Webb telescope
description: Webb turned its gold-coated mirror toward Saturn this week.
categories: Space|astronomy|James Webb Space Telescope|NIRCam|Saturn|solar system
content:
<div id="rss-wrap">
<div>
      <img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/webbsaturn-800x450.jpg">
  
<p class="caption" style="font-size:0.8em">Saturn stars in this near-infrared image taken June 25 by the James Webb Space Telescope. (credit: <a rel="nofollow" class="caption-link" href="https://stsci-opo.org/STScI-01H41MRMD902WV0QQQ4B4PF18K.jpg">NASA/ESA/CSA/STSci</a>)</p>
</div>





<div><a name="page-1"></a></div>
<p>The James Webb Space Telescope has observed Saturn for the first time, completing a family portrait of the Solar System’s ringed planets nearly a year after the mission’s <a href="https://arstechnica.com/science/2022/07/the-other-firsts-the-rest-of-the-first-five-webb-telescope-images/">first jaw-dropping image release.</a></p>
<p>Webb’s near-infrared camera took the picture of Saturn on June 25. Scientists added orange color to the monochrome picture to produce the image released Friday.</p>
<p>The picture shows Saturn’s iconic icy rings shining around the disk of the gas giant, which appears much darker in near-infrared due to the absorption of sunlight by methane particles suspended high in the planet’s atmosphere.</p></div><p><a href="https://arstechnica.com/?p=1951436#p3">Read 11 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1951436&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/space/2023/06/saturns-rings-steal-the-show-in-new-image-from-webb-telescope/feed/


link: https://arstechnica.com/?p=1951425
encoded_syndication_url: aHR0cHM6Ly9hcnN0ZWNobmljYS5jb20vZmVlZC8=
read: False
type: Rss
title: Death toll rises to 7 in fungal meningitis outbreak; cases at 34, 161 at risk
description: Anyone exposed should get medical care and testing immediately, even without symptoms.
categories: Health|Science|cosmetic surgery|epidural|fungal meningitis|Matamoros|mexico|outbreak|surgery
content:
<div id="rss-wrap">
<div>
      <img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/GettyImages-1256207119-800x519.jpeg">
  
<p class="caption" style="font-size:0.8em">One of the medical clinics suspended by Mexican health authorities in Matamoros, Tamaulipas, Mexico, on May 19, 2023.  (credit: <a rel="nofollow" class="caption-link" href="https://www.gettyimages.com/detail/news-photo/general-view-of-one-of-the-medical-clinics-suspended-by-news-photo/1256207119?adppopup=true">Getty | AFP</a>)</p>
</div>





<div><a name="page-1"></a></div>
<p>Three more people in the US have died from <a href="https://arstechnica.com/health/2023/06/deadly-fungal-meningitis-cases-nearly-double-as-cdc-rushes-to-find-exposed/">fungal meningitis in an outbreak</a> linked to tainted surgeries in Mexico, bringing the total deaths to seven, <a href="https://www.cdc.gov/hai/outbreaks/meningitis-epidural-anesthesia.html">the Centers for Disease Control and Prevention reported Thursday</a>.</p>
<p>The total case count remains unchanged from an update earlier this month, with 34 cases in the US: nine confirmed, 10 probable, and 15 suspected. Health officials are investigating 161 others who may have been exposed.</p>
<p>The outbreak is linked to cosmetic surgeries involving epidural anesthesia at two clinics in Matamoros, Mexico, just across the border from Brownsville, Texas. Mexican and US officials suspect that a component of the anesthetic was contaminated, resulting in the pathogenic fungus <em>Fusarium solani</em> being injected directly into people's spinal cords. The tainted surgeries are thought to have occurred between January 1, 2023, to May 13, 2023, around when the clinics were shut down by local health officials.</p></div><p><a href="https://arstechnica.com/?p=1951425#p3">Read 5 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1951425&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/health/2023/06/three-more-dead-in-fungal-meningitis-outbreak-linked-to-tainted-surgeries/feed/


link: https://arstechnica.com/?p=1951389
encoded_syndication_url: aHR0cHM6Ly9hcnN0ZWNobmljYS5jb20vZmVlZC8=
read: False
type: Rss
title: FBI finally tracks “swatting” incidents as attacks increase nationwide
description: Experts aren't sure the database will reverse troubling swatting trend.
categories: Policy|fbi|Federal Bureau of Investigation|online harassment|SWAT|SWATting
content:
<div id="rss-wrap">
<div>
      <img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/GettyImages-1136245690-800x534.jpg">
  
<p class="caption" style="font-size:0.8em">(credit: <a rel="nofollow" class="caption-link" href="https://www.gettyimages.com/detail/news-photo/close-up-of-the-fbi-logo-on-a-black-cap-the-text-stands-for-news-photo/1136245690">Roberto Machado Noa / Contributor | LightRocket</a>)</p>
</div>





<div><a name="page-1"></a></div>
<p>Last month, the FBI created a national online database to finally start coordinating law enforcement reports about "swatting" attacks nationwide, <a href="https://www.nbcnews.com/news/us-news/fbi-formed-national-database-track-prevent-swatting-rcna91722">NBC News reported</a> yesterday.</p>
<p>Swatting is a form of domestic terrorism that is <a href="https://arstechnica.com/tech-policy/2019/03/man-gets-20-years-for-deadly-swatting-hoax/">sometimes deadly</a> and has become more widespread in the US, according to a <a href="https://www.computer.org/csdl/magazine/co/2023/03/10058781/1Ldkevf1sJy">March report</a> from Hal Berghel, a computer science professor at University of Nevada, Las Vegas. Berghel's report defined swatting as:</p>
<blockquote><p>A malicious act that involves making fraudulent 911 calls to cause emergency response teams, such as law enforcement special weapons and tactics teams, or SWAT teams (that’s where the gerund’s root comes from), to react forcefully to a nonexistent public threat.</p></blockquote>
<p>Scott Schubert, of the FBI's Criminal Justice Information Services, told NBC News that the database will help combat the growing swatting problem by facilitating "information sharing between hundreds of police departments and law enforcement agencies across the country pertaining to swatting incidents."</p></div><p><a href="https://arstechnica.com/?p=1951389#p3">Read 26 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1951389&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/tech-policy/2023/06/fbi-finally-tracks-swatting-incidents-as-attacks-increase-nationwide/feed/


link: https://arstechnica.com/?p=1951352
encoded_syndication_url: aHR0cHM6Ly9hcnN0ZWNobmljYS5jb20vZmVlZC8=
read: False
type: Rss
title: Google tells Canada it won’t pay “link tax,” will pull news links from search
description: Canada requiring payments from tech to news orgs; similar bills pending in US.
categories: Google|Policy|google
content:
<div id="rss-wrap">
<div>
      <img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/getty-google-logo-800x533.jpg">
  
<p class="caption" style="font-size:0.8em">A Google sign at the Viva Tech fair in Paris on June 15, 2023. (credit: Getty Images | Bloomberg)</p>
</div>





<div><a name="page-1"></a></div>
<p>In response to a new Canadian law requiring payments to news organizations, Google said it will remove links to Canadian news sources from Google Search and Google News for users who access the services in Canada. <a href="https://blog.google/intl/en-ca/company-news/outreach-initiatives/an-update-on-canadas-bill-c-18-and-our-search-and-news-products/">Google's announcement</a> yesterday followed a <a href="https://arstechnica.com/tech-policy/2023/06/facebook-cutting-off-news-in-canada-to-avoid-paying-publishers-for-content/">similar announcement</a> by Meta that it will end news access on Facebook and Instagram.</p>
<p>The <a href="https://www.parl.ca/DocumentViewer/en/44-1/bill/C-18/royal-assent">new law's</a> "duty to bargain" requires large search engines and social media services to negotiate payments with news businesses or groups of news businesses. The law requires mediation and then arbitration if negotiations don't result in a deal. The law is <a href="https://www.cbc.ca/news/politics/online-news-act-meta-facebook-1.6885634">expected</a> to take effect in six months.</p>
<p>"We have now informed the Government that when the law takes effect, we unfortunately will have to remove links to Canadian news from our Search, News and Discover products in Canada, and that [bill] C-18 will also make it untenable for us to continue offering our Google News Showcase product in Canada," Google President of Global Affairs Kent Walker wrote yesterday.</p></div><p><a href="https://arstechnica.com/?p=1951352#p3">Read 12 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1951352&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/tech-policy/2023/06/google-tells-canada-it-wont-pay-link-tax-will-pull-news-links-from-search/feed/


link: https://arstechnica.com/?p=1951350
encoded_syndication_url: aHR0cHM6Ly9hcnN0ZWNobmljYS5jb20vZmVlZC8=
read: False
type: Rss
title: Florida mosquitoes test positive for malaria as officials spray area
description: Officials have ramped up ground and aerial spraying.
categories: Health|anopheles|cases|CDC|cluster|Florida|malaria|mosquitoes|outbreak|parasite
content:
<div id="rss-wrap">
<div>
      <img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/GettyImages-1504347371-800x533.jpeg">
  
<p class="caption" style="font-size:0.8em">A Miami-Dade mosquito control inspector sprays a pesticide to kill adult mosquitos on June 29, 2023, in Miami. The Miami-Dade mosquito control department continues its regular spraying and inspection of neighborhoods and is ready to react if malaria-carrying mosquitos are found, as they were in the Sarasota area. (credit: <a rel="nofollow" class="caption-link" href="https://www.gettyimages.com/detail/news-photo/barrington-sanders-a-miami-dade-mosquito-control-inspector-news-photo/1504347371?adppopup=true">Getty | Joe Raedle</a>)</p>
</div>





<div><a name="page-1"></a></div>
<p>Three mosquitoes collected near Sarasota, Florida, have tested positive for malaria amid an unusual <a href="https://arstechnica.com/health/2023/06/malaria-spreading-in-texas-and-florida-first-us-based-cases-in-two-decades/">cluster of locally acquired cases</a>. It is the first time in two decades that US mosquitoes have tested positive for malaria in connection to US-based cases.</p>
<p>Four cases have so far been confirmed in Florida, all in close geographic proximity, <a href="https://www.floridahealth.gov/newsroom/2023/06/20230626-mosquito-borne-illnesses.pr.html">health officials reported</a> on Monday. The Sarasota Herald-Tribune reported Wednesday that officials are <a href="https://www.heraldtribune.com/story/news/local/sarasota/2023/06/28/the-four-malaria-cases-confirmed-in-sarasota-county-by-the-florida-department-of-health-were-contrac/70362251007/">investigating a possible fifth case</a>.</p>
<p>With outbreak response efforts ongoing, officials have been trapping and testing local mosquitoes. In a statement to CBS News, Sarasota County Mosquito Management Services manager said the <a href="https://www.cbsnews.com/news/malaria-florida-mosquitoes-human-cases/">three positive insects were among more than a hundred</a> sent to the Centers for Disease Control and Prevention for testing.</p></div><p><a href="https://arstechnica.com/?p=1951350#p3">Read 6 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1951350&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/health/2023/06/malaria-found-in-florida-mosquitoes-amid-cluster-of-local-cases/feed/


link: https://arstechnica.com/?p=1951336
encoded_syndication_url: aHR0cHM6Ly9hcnN0ZWNobmljYS5jb20vZmVlZC8=
read: False
type: Rss
title: TSMC says some of its data was swept up in a hack on a hardware supplier
description: The pernicious LockBit ransomware syndicate claims responsibility and demands $70 million.
categories: Biz & IT|Security|lockbit|ransomware|TSMC
content:
<div id="rss-wrap">
<div>
      <img src="https://cdn.arstechnica.net/wp-content/uploads/2022/03/ransom-note-800x609.jpeg">
  
<p class="caption" style="font-size:0.8em">(credit: <a rel="nofollow" class="caption-link" href="https://www.gettyimages.com/">Getty Images</a>)</p>
</div>





<div><a name="page-1"></a></div>
<p>Chipmaker TSMC said on Friday that one of its hardware suppliers experienced a “security incident” that allowed the attackers to obtain configurations and settings for some of the servers the company uses in its corporate network. The disclosure came a day after the LockBit ransomware crime syndicate listed TSMC on its extortion site and threatened to publish the data unless it received a payment of $70 million.</p>
<p>The hardware supplier, Kinmax Technology, confirmed that one of its test environments had been attacked by an external group, which was then able to retrieve configuration files and other parameter information. The company said it learned of the breach on Thursday and immediately shut down the compromised systems and notified the affected customer.</p>
<p>“Since the above information has nothing to do with the actual application of the customer, it is only the basic setting at the time of shipment,” Kinmax officials <a href="https://www-kx-com-tw.translate.goog/KX_News_Letter_20230629-1/?_x_tr_sl=auto&amp;_x_tr_tl=en&amp;_x_tr_hl=en-US">wrote</a>. “At present, no damage has been caused to the customer, and the customer has not been hacked by it.”</p></div><p><a href="https://arstechnica.com/?p=1951336#p3">Read 9 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1951336&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/security/2023/06/tsmc-says-some-of-its-data-was-swept-up-in-a-hack-on-a-hardware-supplier/feed/


link: https://arstechnica.com/?p=1951176
encoded_syndication_url: aHR0cHM6Ly9hcnN0ZWNobmljYS5jb20vZmVlZC8=
read: False
type: Rss
title: The huge power and potential danger of AI-generated code
description: Programming can be faster with algorithms, but AI can make bugs more common.
categories: AI|generative ai|GitHub|GitHub Copilot|syndication
comments_url: https://arstechnica.com/ai/2023/06/the-huge-power-and-potential-danger-of-ai-generated-code/feed/
content:
<div id="rss-wrap">
<div>
      <img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/GettyImages-932736250-800x842.jpg">
  
<p class="caption" style="font-size:0.8em">(credit: <a rel="nofollow" class="caption-link" href="https://www.gettyimages.com/detail/illustration/artificial-intelligence-conceptual-royalty-free-illustration/932736250">Mark Garlick/Science Photo Library/Getty</a>)</p>
</div>





<div><a name="page-1"></a></div>
<p>In June 2021, <a href="https://github.blog/2021-06-29-introducing-github-copilot-ai-pair-programmer/" target="_blank" rel="nofollow noopener" data-offer-url="https://github.blog/2021-06-29-introducing-github-copilot-ai-pair-programmer/" data-event-click='{"element":"ExternalLink","outgoingURL":"https://github.blog/2021-06-29-introducing-github-copilot-ai-pair-programmer/"}' data-uri="7e7f39f3a432d19b71e71af3880657a6">GitHub announced</a> Copilot, a kind of auto-complete for computer code powered by OpenAI’s text-generation technology. It provided an early glimpse of the impressive potential of generative <a href="https://www.wired.com/tag/artificial-intelligence/" data-uri="f1dea372e2522e69f7f578b75bdaa4d4">artificial intelligence</a> to automate valuable work. Two years on, Copilot is one of the most mature examples of how the technology can take on tasks that previously had to be done by hand.</p>
<p>This week <a href="https://github.blog/2023-06-27-the-economic-impact-of-the-ai-powered-developer-lifecycle-and-lessons-from-github-copilot" target="_blank" rel="nofollow noopener" data-offer-url="https://github.blog/2023-06-27-the-economic-impact-of-the-ai-powered-developer-lifecycle-and-lessons-from-github-copilot" data-event-click='{"element":"ExternalLink","outgoingURL":"https://github.blog/2023-06-27-the-economic-impact-of-the-ai-powered-developer-lifecycle-and-lessons-from-github-copilot"}' data-uri="91d918c2ab9dd87e2083e03dda083898">GitHub released a report</a>, based on data from almost a million programmers paying to use Copilot, that shows how transformational generative AI coding has become. On average, they accepted the AI assistant’s suggestions about 30 percent of the time, suggesting that the system is remarkably good at predicting useful code.</p>
<div class="centered-figure-container"><div class="image center large"><a href="https://cdn.arstechnica.net/wp-content/uploads/2023/06/Screenshot-2023-06-29-at-14-19-27-The-Huge-Power-and-Potential-Danger-of-AI-Generated-Code.png"><img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/Screenshot-2023-06-29-at-14-19-27-The-Huge-Power-and-Potential-Danger-of-AI-Generated-Code-640x311.png" srcset="https://cdn.arstechnica.net/wp-content/uploads/2023/06/Screenshot-2023-06-29-at-14-19-27-The-Huge-Power-and-Potential-Danger-of-AI-Generated-Code.png 2x"></a><p class="caption" style="font-size:0.8em"><a href="https://cdn.arstechnica.net/wp-content/uploads/2023/06/Screenshot-2023-06-29-at-14-19-27-The-Huge-Power-and-Potential-Danger-of-AI-Generated-Code.png" class="caption-link" rel="nofollow"></a> (credit: GitHub)</p></div></div>
<figure data-testid="IframeEmbed" data-event-boundary="click" data-event-click='{"pattern":"IframeEmbed"}' data-in-view='{"pattern":"IframeEmbed"}' data-include-experiments="true"></figure>
<p>The striking chart above shows how users tend to accept more of Copilot’s suggestions as they spend more months using the tool. The report also concludes that AI-enhanced coders see their productivity increase over time, based on the fact that <a href="https://arxiv.org/abs/2302.06590" target="_blank" rel="nofollow noopener" data-offer-url="https://arxiv.org/abs/2302.06590" data-event-click='{"element":"ExternalLink","outgoingURL":"https://arxiv.org/abs/2302.06590"}' data-uri="c3882fbc7e7adbe9243458b0bf9e05bd">a previous Copilot study</a> reported a link between the number of suggestions accepted and a programmer’s productivity. GitHub’s new report says that the greatest productivity gains were seen among less experienced developers. </p></div><p><a href="https://arstechnica.com/?p=1951176#p3">Read 10 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1951176&comments=1">Comments</a></p>


link: https://arstechnica.com/?p=1951208
encoded_syndication_url: aHR0cHM6Ly9hcnN0ZWNobmljYS5jb20vZmVlZC8=
read: False
type: Rss
title: Torrent of image-based phishing emails are harder to detect and more convincing
description: The arms race between scammers and defenders continues.
categories: Biz & IT|Security|image|phishing|qr code
content:
<div id="rss-wrap">
<div>
      <img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/qr-code-800x534.jpg">
  
<p class="caption" style="font-size:0.8em">Man hand holding a mobile phone with QR code. (credit: Getty Images)</p>
</div>





<div><a name="page-1"></a></div>
<p>Phishing mongers have released a torrent of image-based junk emails that embed QR codes into their bodies to successfully bypass security protections and provide a level of customization to more easily fool recipients, <a href="https://www.inky.com/en/blog/fresh-phish-malicious-qr-codes-are-quickly-retrieving-employee-credentials">researchers said.</a></p>
<p>In many cases, the emails come from a compromised email address inside the organization the recipient works in, a tactic that provides a false sense of authenticity, researchers from security firm Inky said. The emails Inky detected instruct the employee to resolve security issues such as a missing two-factor authentication enrollment or to change a password and warn of repercussions that may occur if the recipient fails to follow through. Those who take the bait and click on the QR code are led to a site masquerading as a legitimate one used by the company but it captures passwords and sends them to the attackers.</p>
<p>Inky described the campaign's approach as “spray and pray” because the threat actors behind it send the emails to as many people as possible to generate results.</p></div><p><a href="https://arstechnica.com/?p=1951208#p3">Read 7 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1951208&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/security/2023/06/torrent-of-image-based-phishing-emails-are-harder-to-detect-and-more-convincing/feed/


link: https://arstechnica.com/?p=1943379
encoded_syndication_url: aHR0cHM6Ly9hcnN0ZWNobmljYS5jb20vZmVlZC8=
read: False
type: Rss
title: Into the rivers and through the woods: Specialized’s e-mountain bike
description: Specialized's electric mountain bike was more than good enough to hook our reviewer.
categories: Cars|Features|e-bikes|mountain bikes|Specialized
content:
<div id="rss-wrap">
<div>
      <img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/IMG_1199-800x600.jpeg">
  
<p class="caption" style="font-size:0.8em">Behold, the Turbo Levo. (credit: John Timmer)</p>
</div>





<div><a name="page-1"></a></div>
<p>I consider myself a bit of a bicycle fanatic. I've ridden tens of thousands of miles, stripped bikes down to their frames and rebuilt them, and completed a 130-mile ride from New York City to the tip of Long Island. But I have intentionally cut myself off from one of the most exciting, rapidly developing parts of the cycling world. I've never ridden a mountain bike.</p>
<p>This is partly because I know my weaknesses. I expected I'd like it, and being an inveterate gear hound, I would end up wanting to buy one. A lack of money in grad school followed by lack of space for two bikes in New York City meant that wasn't an option. So I stuck to the road and avoided even exposing myself to temptation.</p>
<p>I now have a bit more money and a bit more space, and my resistance started to crack a bit when I <a href="https://arstechnica.com/cars/2023/01/doing-it-all-a-foldable-mountain-e-bike-with-extra-fat-tires/">tested a dual-suspension frame bike</a> late last year. But that foldable, ultra-fat-tire frame didn't give me the confidence I needed to try trails that would challenge both the bike and my lack of skill. It was, however, enough to get me to say yes when Specialized offered some review time with its Levo series of e-mountain bikes. After hitting a few parks with the <a href="https://fave.co/42T1wY4" target="_blank" rel="noopener">Turbo Levo Comp Alloy</a>, I'm here to report that I was right in avoiding trail riding for as long as I did.</p></div><p><a href="https://arstechnica.com/?p=1943379#p3">Read 30 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1943379&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/cars/2023/06/into-the-rivers-and-through-the-woods-specializeds-e-mountain-bike/feed/


link: https://arstechnica.com/?p=1951178
encoded_syndication_url: aHR0cHM6Ly9hcnN0ZWNobmljYS5jb20vZmVlZC8=
read: False
type: Rss
title: Here’s what happens when a swim team competes with an intestinal pathogen
description: Outbreak among Mass. swim teams spread to a Rhode Island team after a meet.
categories:
Health|Science|CDC|college|crypto exchange|Cryptosporidium|diarrhea|intestinal|massachusetts|parasite|pathogen|pool|swimmers|swimming|waterborne disease

content:
<div id="rss-wrap">
<div>
      <img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/GettyImages-120540973-800x533.jpeg">
  
<p class="caption" style="font-size:0.8em">A swimmer in the men's 200 meter breaststroke finals during a national championship competition on August 6, 2011, in Palo Alto, California.  (credit: <a rel="nofollow" class="caption-link" href="https://www.gettyimages.com/detail/news-photo/brendan-hansen-turns-at-the-wall-mid-lap-in-the-mens-200-news-photo/120540973?adppopup=true">Getty | Brian Bahr</a>)</p>
</div>





<div><a name="page-1"></a></div>
<p>Several college swim teams learned a stomach-churning lesson the hard way during a recent series of meets: regardless of skill or speed, the real winner of the meet will always be <a href="https://arstechnica.com/health/2023/06/its-summer-and-that-means-disturbing-swim-advisories-heres-our-top-5/">the gastrointestinal pathogen that enters the pool.</a></p>
<p>In an outbreak investigation that is destined to become a nauseating cautionary tale, health officials traced the spread of the water-based intestinal parasite <em>Cryptosporidium</em> (aka crypto) through several pools of competitive swimmers with the squirts. The case involved a lucky break: Health officials fished out the crypto rather quickly. But, it wasn't fast enough to keep the parasite from butterflying its way to members of another college's team, showing how quickly and easily it could have spread without intervention</p>
<p>It also highlighted "an ongoing need to promote healthy swimming, including recommendations for persons not to swim if they have diarrhea and to avoid swallowing swimming pool water to prevent waterborne disease," the authors of <a href="https://www.cdc.gov/mmwr/volumes/72/wr/mm7226a7.htm?s_cid=mm7226a7_w">a case report on the investigation</a> wrote. The report, led by health officials in Massachusetts, was published Thursday in the Centers for Disease Control and Prevention's Morbidity and Mortality Weekly Report.</p></div><p><a href="https://arstechnica.com/?p=1951178#p3">Read 8 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1951178&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/health/2023/06/heres-what-happens-when-a-swim-team-competes-with-an-intestinal-pathogen/feed/


link: https://arstechnica.com/?p=1951121
encoded_syndication_url: aHR0cHM6Ly9hcnN0ZWNobmljYS5jb20vZmVlZC8=
read: False
type: Rss
title: Christopher Walken is an evil emperor in latest trailer for Dune: Part 2
description: "He who can destroy a thing has the real control of it."
categories: Culture|Dune: part 2|entertainment|film|film trailers|Frank Herbert|Trailers|Warner Bros.
content:
<div id="rss-wrap">




<div><a name="page-1"></a></div>
<figure class="video center"><div class="ars-video-container" style="padding-bottom:56%"><iframe style="display:block" type="text/html" width="980" height="550" src="https://www.youtube.com/embed/_YUzQa_1RCE?start=0&amp;wmode=transparent" frameborder="0" allowfullscreen></iframe></div><p class="caption" style="font-size:0.8em"> Timothée Chalamet's Paul Atreides is ready to fight in the new trailer for <em>Dune: Part 2</em>. </p></figure>
<p>Warner Bros. has dropped a second eye-popping trailer for <a href="https://en.wikipedia.org/wiki/Dune:_Part_Two" data-uri="1cba4a8666f680b8c0ccba79d01cdeb1"><em>Dune: Part 2</em></a>, the second part of Denis Villeneuve's visually stunning, ambitious adaptation of Frank Herbert's seminal sci-fi novel. <em>Part 1,</em> released in 2021, grossed over $400 million globally against a $165 million budget, earned critical acclaim (you can read the largely positive Ars review <a href="https://arstechnica.com/gaming/2021/10/dune-2021-film-review-the-spice-must-flow-but-then-it-stops-abruptly/" data-uri="d96fb28fbb5da71635951e4c6130fd73">here</a>), and snagged six Oscars. If this new trailer is any indication, <em>Part 2</em> promises to be just as powerful.</p>
<p>As <a href="https://arstechnica.com/gaming/2021/07/latest-dune-trailer-gives-us-our-best-look-yet-at-denis-villeneuves-epic-film/" data-uri="81f98a747de3b177992c746d3f83b803">reported previously</a> (also <a href="https://arstechnica.com/gaming/2020/04/needs-more-zendaya-we-have-our-first-look-at-the-new-dune-film/" data-uri="5f2acbec1c7f6b12a9067683af893058">here</a> and <a href="https://arstechnica.com/gaming/2020/09/destiny-awaits-timothee-chalamet-is-the-chosen-one-in-first-dune-trailer/" data-uri="4c38bbf70fa61b156ed19bc8e3584dc4">here</a>), Herbert's novel <a href="https://arstechnica.com/gaming/2019/02/aquaman-khal-drogo-actor-may-play-duncan-idaho-in-new-dune-film/" data-uri="2670945f8a81b0fff10c8813b85a0018"><em>Dune</em> is set in the distant future</a> and follows the fortunes of various noble houses in what amounts to a feudal interstellar society. Much of the action takes place on the planet Arrakis, where the economy is driven largely by a rare, life-extending drug called melange ("the spice"). Melange also conveys a kind of prescience and makes faster-than-light travel practical. There's betrayal, a prophecy concerning a messianic figure, giant sandworms, and battle upon battle as protagonist Paul Atreides (Timothée Chalamet) contends with rival House Harkonnen and strives to defeat the forces of Shaddam IV, Emperor of the Known Universe.</p>
<p><em>Part 1</em>'s finale left Paul and his mother, Lady Jessica (Rebecca Ferguson), presumed dead in the harsh desert of Arrakis, having fled their home when Baron Vladimir Harkonnen (Stellan Skarsgård) betrayed the Atreides family and killed Paul's father, Leto (Oscar Isaac). They were taken in by the Fremen, the planet's native inhabitants, who include Chani (Zendaya), a girl who had been appearing in Paul's dreams/visions.</p></div><p><a href="https://arstechnica.com/?p=1951121#p3">Read 5 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1951121&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/culture/2023/06/paul-atreides-swears-to-do-what-must-be-done-in-new-dune-part-2-trailer/feed/


link: https://arstechnica.com/?p=1951351
encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5hcnN0ZWNobmljYS5jb20vYXJzdGVjaG5pY2EvZ2FkZ2V0cw==
read: False
type: Rss
title: The Asus Zenfone 10 is a tiny 5.9-inch phone with flagship specs
description: Asus invites small phone lovers to put their money where their mouth is.
categories: Tech|android phone|ASUS|Zenfone
content:
<div id="rss-wrap">





<div><a name="page-1"></a></div>
  <ul class="gallery shortcode-gallery gallery-wide">
          <li>
        <div class="gallery-item-content">
          <div class="gallery-image"><img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/73-980x668.jpg" alt=""></div>
          <p>
            The Asus Zenfone 10 in a variety of colors.                          [credit:
                              Asus                            ]
                      </p>
        </div>
      </li>
      </ul>

<p> </p>
<p>Lovers of small phones: Meet the<a href="https://www.asus.com/event/zenfone/"> Asus Zenfone 10</a>, a tiny little device headlined by a 144 Hz, 5.9-inch, 2400×1080 OLED display. For those asking for a one-hand device, this 146.5 mm×68.1mm×9.4 mm phone is one of the smallest on the market, and it has flagship specs. It's not quite the size of the iPhone SE (138.4 mm×67.3 mm×7.3 mm) or the microscopic iPhone 13 Mini (131.5 mm×64.2mm×7.7 mm) but on Android, this is as small as you're going to get.</p>
<p>With those<a href="https://www.asus.com/mobile-handhelds/phones/zenfone/zenfone-10/techspec/"> flagship specs</a>, you get a Qualcomm Snapdragon 8 gen 2 SoC, a baseline of 8GB of RAM with an option for 16GB, and UFS 4.0 storage options of 128GB, 256GB, or 512GB. The big downside to a small phone is the battery, which here is only 4300 mAh. Asus somehow found room to pack in a 3.5-mm headphone jack, along with 15 W wireless charging (wired is 30 W), stereo speakers, NFC, IP68 dust and water resistance, Wi-Fi 7, and Bluetooth 5.3.</p></div><p><a href="https://arstechnica.com/?p=1951351#p3">Read 3 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1951351&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/gadgets/2023/06/the-asus-zenfone-10-is-a-tiny-5-9-inch-phone-with-flagship-specs/feed/


link: https://arstechnica.com/?p=1951212
encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5hcnN0ZWNobmljYS5jb20vYXJzdGVjaG5pY2EvZ2FkZ2V0cw==
read: False
type: Rss
title: Reddit API changes are imminent. Here’s what’s happening to your favorite apps
description: Ars spoke to devs about their apps' future &#038; what they learned from this ordeal.
categories: Features|Policy|Tech|API|reddit|social media
content:
<div id="rss-wrap">
<figure class="intro-image intro-left">
  <img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/GettyImages-1258545135-800x533.jpg" alt="Apollo for Reddit on AppStore displayed on a phone screen and Reddit logo on the website displayed on a screen">
      <p class="caption" style="font-size:0.8em"><a href="https://cdn.arstechnica.net/wp-content/uploads/2023/06/GettyImages-1258545135-scaled.jpg" class="enlarge-link" data-height="1707" data-width="2560">Enlarge</a> (credit: <a rel="nofollow" class="caption-link" href="https://www.gettyimages.com/detail/news-photo/apollo-for-reddit-on-appstore-displayed-on-a-phone-screen-news-photo/1258545135">Getty</a>)</p>  </figure>






<div><a name="page-1"></a></div>
<p>It's been a contentious journey, but Reddit's new API pricing will take effect on July 1. What started as a fight over creating an affordable option for valued third-party Reddit apps has evolved into a bitter battle pitting Reddit against indignant developers, mods, and users. Protests remain, but some users are now preparing to exit the platform, including some of Reddit's most seasoned moderators.</p>
<p>Where does that leave third-party developers, some of which said they would have to pay Reddit $20 million annually to continue? Ars Technica spoke with developers to learn where their apps stand, how some will manage to stay afloat, and what Reddit's changes mean for the future.</p>
<h2>Surviving apps</h2>
<p>When Reddit announced that, starting on July 1, it would no longer permit free API access except for certain non-commercial apps, many Reddit app developers responded by telling users that they were unsure if they could keep the apps running. Now that the new API pricing ($12,000 per 50 million API requests) is set to be reality, here's a look at the most popular apps that will still be available.</p></div><p><a href="https://arstechnica.com/?p=1951212#p3">Read 63 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1951212&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/gadgets/2023/06/reddit-api-changes-are-imminent-heres-whats-happening-to-your-favorite-apps/feed/


link: https://arstechnica.com/?p=1951278
encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5hcnN0ZWNobmljYS5jb20vYXJzdGVjaG5pY2EvZ2FkZ2V0cw==
read: False
type: Rss
title: AMD announces limited-run Ryzen 5600X3D CPU, an ideal upgrade for an aging Ryzen PC
description: Micro Center will be the only seller of this $229, while-supplies-last chip.
categories:
Tech|5800x3d|AM4|AMD Ryzen|amd ryzen 5|amd ryzen 5800x3d|ryzen 5000|ryzen 5000x3d|ryzen 5600x3d|ryzen 5800x3d|socket AM4|Zen 3

content:
<div id="rss-wrap">
<figure class="intro-image intro-left">
  <img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/ryzen-5600x3d-800x450.jpeg" alt="AMD's Ryzen 5 5600X3D.">
      <p class="caption" style="font-size:0.8em"><a href="https://cdn.arstechnica.net/wp-content/uploads/2023/06/ryzen-5600x3d.jpeg" class="enlarge-link" data-height="1080" data-width="1920">Enlarge</a> <span class="sep">/</span> AMD's Ryzen 5 5600X3D. (credit: AMD)</p>  </figure>






<div><a name="page-1"></a></div>
<p>A surprise twist for owners of older AMD PCs using socket AM4: AMD is announcing one last (?) processor for the aging socket, a six-core Ryzen 5 5600X3D that brings the company's 3D V-Cache chip stacking technology to a $229 chip.</p>
<p>The catch? The new CPU will only be available through Micro Center, a brick-and-mortar tech retailer that doesn't ship most of what it sells to online buyers. The chip will only be sold for as long as Micro Center's supply holds out, though Tom's Hardware <a href="https://www.tomshardware.com/news/amd-ryzen-5-5600x3d-to-launch-july-7th-for-dollar229-at-micro-center-only">reports</a> that the company will have "several months'" worth of stock.</p>
<table border="" width="100%">
<tbody>
<tr>
<th>AMD Zen 3 CPUs</th>
<th>Street price</th>
<th>Cores/threads</th>
<th>Clocks (Base/Boost)</th>
<th>L3 cache</th>
<th>TDP</th>
</tr>
<tr>
<td><strong>Ryzen 5 5600</strong></td>
<td><a rel="nofollow" href="http://www.amazon.com/dp/B09VCHR1VH/?tag=arstech20-20">$129</a></td>
<td>6/12</td>
<td>3.5/4.4GHz</td>
<td>32MB</td>
<td>65W</td>
</tr>
<tr>
<td><strong>Ryzen 5 5600X</strong></td>
<td><a rel="nofollow" href="http://www.amazon.com/dp/B08166SLDF/?tag=arstech20-20">$149</a></td>
<td>6/12</td>
<td>3.7/4.6GHz</td>
<td>32MB</td>
<td>65W</td>
</tr>
<tr>
<td><strong>Ryzen 5 5600X3D</strong></td>
<td>$229 (MSRP)</td>
<td>6/12</td>
<td>3.3/4.4GHz</td>
<td>96MB</td>
<td>105W</td>
</tr>
<tr>
<td><strong>Ryzen 7 5800X3D</strong></td>
<td><a rel="nofollow" href="http://www.amazon.com/dp/B09VCJ2SHD/?tag=arstech20-20">$289</a></td>
<td>8/16</td>
<td>3.4/4.5GHz</td>
<td>96MB</td>
<td>120W</td>
</tr>
</tbody>
</table>
<p>Like the <a href="https://arstechnica.com/gadgets/2022/04/review-ryzen-7-5800x3d-is-an-interesting-tech-demo-thats-hard-to-recommend/">Ryzen 5800X3D</a>, the 5600X3D combines a regular Zen 3 processor die with an extra 64MB chunk of L3 cache stacked on top. Relative to its regular Zen 3 counterparts—in this case, the Ryzen 5 5600 and 5600X—the chip will consume slightly more power and run at somewhat lower clock speeds, which can make it slower than the non-X3D chips in tasks that don't benefit from the extra cache. They also have limited support for overclocking and undervolting. However, games tend to like the extra cache a lot, benefitting people who want to pair a high-end GPU with the cheapest CPU that won't hold it back.</p></div><p><a href="https://arstechnica.com/?p=1951278#p3">Read 5 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1951278&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/gadgets/2023/06/amd-ryzen-5600x3d-a-micro-center-exclusive-is-one-last-hurrah-for-socket-am4/feed/


link: https://arstechnica.com/?p=1951251
encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5hcnN0ZWNobmljYS5jb20vYXJzdGVjaG5pY2EvZ2FkZ2V0cw==
read: False
type: Rss
title: Red Hat’s new source code policy and the intense pushback, explained
description: A (reasonably) condensed version of two weeks' worth of heated GPL argument.
categories:
Biz & IT|Tech|CentOS|centos linux|centos stream|Linux|red hat|Red Hat Enterprise Linux|rocky linux|source code

content:
<div id="rss-wrap">
<figure class="intro-image intro-left">
  <img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/GettyImages-1212755749-800x533.jpg" alt="Man wearing fedora in red light">
      <p class="caption" style="font-size:0.8em"><a href="https://cdn.arstechnica.net/wp-content/uploads/2023/06/GettyImages-1212755749-scaled.jpg" class="enlarge-link" data-height="1707" data-width="2560">Enlarge</a> <span class="sep">/</span> A be-hatted person, tipping his brim to the endless amount of text generated by the conflict of corporate versus enthusiast understandings of the GPL.  (credit: Getty Images)</p>  </figure>






<div><a name="page-1"></a></div>
<p>When CentOS <a href="https://blog.centos.org/2020/12/future-is-centos-stream/">announced</a> in 2020 that it was <a href="https://arstechnica.com/gadgets/2020/12/centos-shifts-from-red-hat-unbranded-to-red-hat-beta/">shutting down its traditional "rebuild" of Red Hat Enterprise Linux</a> (RHEL) to focus on its development build, Stream, CentOS suggested the strategy "removes confusion." Red Hat, which largely controlled CentOS by then, <a href="https://www.redhat.com/en/blog/centos-stream-building-innovative-future-enterprise-linux">considered it</a> "a natural, inevitable next step."</p>
<p>Last week, the IBM-owned Red Hat continued "<a href="https://www.redhat.com/en/blog/furthering-evolution-centos-stream">furthering the evolution of CentOS Stream</a>" by announcing that CentOS Stream would be "the sole repository for public RHEL-related source code releases," with RHEL's core code otherwise restricted to a customer portal. (RHEL access is <a href="https://developers.redhat.com/articles/faqs-no-cost-red-hat-enterprise-linux">free for individual developers</a> and <a href="https://arstechnica.com/gadgets/2021/01/centos-is-gone-but-rhel-is-now-free-for-up-to-16-production-servers/">up to 16 servers</a>, but that's largely not the issue here).</p>
<p>Red Hat's post was a rich example of burying the lede and a decisive moment for many who follow the tricky balance of Red Hat's open source commitments and service contract business. Here's what followed.</p></div><p><a href="https://arstechnica.com/?p=1951251#p3">Read 11 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1951251&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/information-technology/2023/06/red-hats-new-source-code-policy-and-the-intense-pushback-explained/feed/


link: https://arstechnica.com/?p=1951133
encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5hcnN0ZWNobmljYS5jb20vYXJzdGVjaG5pY2EvZ2FkZ2V0cw==
read: False
type: Rss
title: Motorola’s “Satellite Link” hotspot lets you send messages via outer space
description: Following the announcement in February, the $150 device is available today.
categories: Tech|Ars Shopping|motorola|satellite phone
content:
<div id="rss-wrap">





<div><a name="page-1"></a></div>
  <ul class="gallery shortcode-gallery gallery-wide">
          <li>
        <div class="gallery-item-content">
          <div class="gallery-image"><img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/vb2209004_29-Motorola-Defy-Satellite-Link_Jordan_Hi-Res-1165-1-980x653.jpg" alt=""></div>
          <p>
            The Motorola Hotspot. It connects to the satellite network and has Bluetooth. That's it.                       </p>
        </div>
      </li>
      </ul>

<p>If you're still jealous of the iPhone 14's ability to do satellite messaging, Motorola has a Bluetooth accessory that will help you feel less left out. The<a href="https://fave.co/3NRov1C" target="_blank" rel="noopener"> Motorola Defy Satellite Link</a> is officially for sale today, following its <a href="https://arstechnica.com/gadgets/2023/02/motorola-brings-5-a-month-satellite-messaging-to-any-phone-with-new-hotspot/">announcement</a> in February. This is basically a satellite messaging hotspot—it's a box with Bluetooth, a battery, and a chip that will give you a satellite connection. You pair your phone to it, run the app, and you can start firing text messages into outer space. The hotspot is <a href="https://fave.co/3NRov1C" target="_blank" rel="noopener">$150</a> and will work today on Android and iOS devices in the US.</p>
<p>The iPhone 14 made satellite messaging the hot new thing when it was announced last year, and competitors are just starting to appear. The big difference between Motorola's hotspot and an iPhone (and the reason why you might want Motorola's option even if you have an iPhone 14) is that the iPhone 14 only sends a specially crafted SOS message to emergency services—a keyboard is not involved in the process at all, it's just for emergency usage. The Motorola hotspot is not just for emergencies. It does full-blown messaging, where you can type whatever message you want to whoever you want, but via a satellite instead of the usual cellular network.</p>
<p>Motorola's messaging service works just like SMS, but it can only be delivered to other people running the special <a href="https://play.google.com/store/apps/details?id=com.bullitt.wave">Bullitt Satellite Messenger app</a>. The service will do SMS forwarding, though, so if you punch in a random number, that person will receive a message prompting them to download the Bullitt app so they can talk to you. It's probably best to set this up with someone beforehand, but it sounds like a great way to communicate when you're off the grid.</p></div><p><a href="https://arstechnica.com/?p=1951133#p3">Read 5 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1951133&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/gadgets/2023/06/motorolas-satellite-link-hotspot-lets-you-send-messages-via-outer-space/feed/


link: https://arstechnica.com/?p=1950582
encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5hcnN0ZWNobmljYS5jb20vYXJzdGVjaG5pY2EvZ2FkZ2V0cw==
read: False
type: Rss
title: 30 years later, Myst demake for Atari 2600 reminds us how far we’ve come
description: Unofficial <em>Myst</em> port for 8-bit Atari 2600 gives the '90s adventure a '70s makeover.
categories: Gaming|Tech|1977|1993|Atari|Atari 2600|Cyan|Cyan Worlds|demake|Myst|retrotech
content:
<div id="rss-wrap">
<figure class="intro-image intro-left">
  <img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/myst_hero_3-800x450.jpg" alt="An enhanced screenshot of a Myst demo for the Atari 2600 game console.">
      <p class="caption" style="font-size:0.8em"><a href="https://cdn.arstechnica.net/wp-content/uploads/2023/06/myst_hero_3.jpg" class="enlarge-link" data-height="675" data-width="1200">Enlarge</a> <span class="sep">/</span> Blocks ahoy! (credit: Vince Weaver)</p>  </figure>






<div><a name="page-1"></a></div>
<p>Nearly 30 years after its release on the Mac in 1993, Cyan's <a href="https://arstechnica.com/gaming/2020/01/video-how-mysts-designers-stuffed-an-entire-universe-onto-a-single-cd-rom/"><em>Myst</em></a> is still as unstoppable as ever. As one of the most successful (yet sometimes <a href="https://www.fastcompany.com/90240345/myst-at-25-how-it-changed-gaming-created-addicts-and-made-enemies">divisive</a>) computer games of all time, it sold <a href="https://www.filfre.net/2020/02/myst-or-the-drawbacks-to-success/">6 million</a> boxed copies in the 1990s and later ended up on over <a href="https://www.mobygames.com/game/1223/myst/">a dozen platforms</a>, with remakes counting for <a href="https://cyan.com/games/myst/">even more</a> appearances, including a VR version. Now, thanks to an unofficial <a href="http://deater.net/weave/vmwprod/myst_vcs/">hobby project</a> by Vince Weaver, <em>Myst</em> can add one more platform to the list: Atari 2600.</p>

<p>Vince Weaver is an associate professor at the University of Maine in Computer Engineering. Since last year, he has been working on a partial "demake" of the famous point-and-click adventure game that runs on Atari's 8-bit game system, and he just returned to the project to make updates <a href="https://twitter.com/deater78/status/1672071594372476929?s=20">last week</a>.</p>
<p>For those not in the gaming community, the term "demake" might need some unpacking. A demake is essentially the opposite of a remake: instead of upgrading a game to fit modern standards, a demake takes a modern or classic game and adapts it for older, less powerful hardware.</p></div><p><a href="https://arstechnica.com/?p=1950582#p3">Read 12 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1950582&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/gaming/2023/06/30-years-later-myst-demake-for-atari-2600-reminds-us-how-far-weve-come/feed/


link: https://arstechnica.com/?p=1950992
encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5hcnN0ZWNobmljYS5jb20vYXJzdGVjaG5pY2EvZ2FkZ2V0cw==
read: False
type: Rss
title: Windows 11’s AI-powered Copilot (and its Bing-powered ads) enters public preview
description: Also includes Settings app changes, wider support for compressed file formats.
categories:
AI|Tech|Bing Chat|bing chat gpt|chatbot gpt|ChatGPT|chatgtp|copilot|openai|win11|windows 11|windows 11 22h2

content:
<div id="rss-wrap">
<figure class="intro-image intro-left">
  <img src="https://cdn.arstechnica.net/wp-content/uploads/2023/05/windows-copilot-800x450.jpg" alt="Windows Copilot is an AI-assisted feature coming to Windows 11 preview builds.">
      <p class="caption" style="font-size:0.8em"><a href="https://cdn.arstechnica.net/wp-content/uploads/2023/05/windows-copilot.jpg" class="enlarge-link" data-height="1080" data-width="1920">Enlarge</a> <span class="sep">/</span> Windows Copilot is an AI-assisted feature coming to Windows 11 preview builds. (credit: Microsoft)</p>  </figure>






<div><a name="page-1"></a></div>

<p>Last month, Microsoft announced that it would continue its put-ChatGPT-in-everything adventure with a new Windows 11 feature called <a href="https://arstechnica.com/gadgets/2023/05/built-in-chatgpt-driven-copilot-will-transform-windows-11-starting-in-june/">Copilot</a>. The company added generative AI to Edge and to the Bing-powered taskbar Search field months ago, but Copilot promises to be the most visible and hard-to-ignore version of Microsoft's big AI push in its most visible and hard-to-ignore product.</p>
<p>This week's Windows Insider Preview build for Dev channel users, build 23493, will be <a href="https://blogs.windows.com/windows-insider/2023/06/29/announcing-windows-11-insider-preview-build-23493">the first to enable Copilot for public testers</a>. After installing the update, preview users can press Windows + C to open a Copilot column on the right side of the screen. It will use the same Microsoft account you use for the rest of the OS (it's unclear whether it will work without a Microsoft account, though, to date, the preview has required sign-up and sign-in). And like the other Bing Chat implementations, it has three different "conversation style" settings that either try to rein the chatbot in and keep its answers straightforward and factual or allow it to get "more creative" but <a href="https://arstechnica.com/information-technology/2023/04/why-ai-chatbots-are-the-ultimate-bs-machines-and-how-people-hope-to-fix-them/">more prone to confabulations</a>.</p>
<p>In addition to chatting, Copilot will also support creating AI images using OpenAI's DALL-E 2 model, the same technology used for the <a href="https://www.bing.com/create">Bing Image Creator</a>. Some features announced last month, including third-party plugin support, aren't included in this initial preview, and later versions will also be able to adjust a wider range of Windows settings.</p></div><p><a href="https://arstechnica.com/?p=1950992#p3">Read 6 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1950992&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/gadgets/2023/06/windows-11s-copilot-brings-ai-chat-to-desktops-in-first-public-preview/feed/


link: https://arstechnica.com/?p=1950755
encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5hcnN0ZWNobmljYS5jb20vYXJzdGVjaG5pY2EvZ2FkZ2V0cw==
read: False
type: Rss
title: Speed matters: How Ethernet went from 3Mbps to 100Gbps… and beyond
description: One of the biggest computing inventions of all time, courtesy of Xerox PARC.
categories: Tech|10 Gigabit Ethernet|ethernet|gigabit ethernet|seoexplainer
content:
<div id="rss-wrap">
<figure class="intro-image intro-left">
  <img src="https://cdn.arstechnica.net/wp-content/uploads/2020/10/broadband-ethernet-cables-800x533.jpg" alt="Extreme close-up photo of cables.">
      <p class="caption" style="font-size:0.8em"><a href="https://cdn.arstechnica.net/wp-content/uploads/2020/10/broadband-ethernet-cables.jpg" class="enlarge-link" data-height="1414" data-width="2121">Enlarge</a> (credit: <a rel="nofollow" class="caption-link" href="https://www.gettyimages.com/search/photographer?assettype=image&amp;family=creative&amp;license=rf&amp;photographer=Adrienne%20Bresnahan&amp;sort=best#license"> Adrienne Bresnahan | Getty Images</a>)</p>  </figure>




      <p><em>With Ethernet turning 50 this year, Ars is resurfacing this feature on the development and evolution of Ethernet that was originally published in 2011.</em></p>
    

<div><a name="page-1"></a></div>
<p>Although watching TV shows from the 1970s suggests otherwise, the era wasn't completely devoid of all things resembling modern communication systems. Sure, the 50Kbps modems that the ARPANET ran on were the size of refrigerators, and the widely used Bell 103 modems only transferred 300 bits per second. But long-distance digital communication was common enough, relative to the number of computers deployed. Terminals could also be hooked up to mainframe and minicomputers over relatively short distances with simple serial lines or with more complex <a href="http://www.pulsewan.com/data101/multidrop_polling_basics.htm">multidrop</a> systems. This was all well known; what was new in the '70s was the local area network (LAN). But how to connect all these machines?</p>
<p>The point of a LAN is to connect many more than just two systems, so a simple cable back and forth doesn't get the job done. Connecting several thousands of computers to a LAN can in theory be done using a star, a ring, or a bus topology. A star is obvious enough: every computer is connected to some central point. A bus consists of a single, long cable that computers connect to along its run. With a ring, a cable runs from the first computer to the second, from there to the third and so on until all participating systems are connected, and then the last is connected to the first, completing the ring.</p></div><p><a href="https://arstechnica.com/?p=1950755#p3">Read 55 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1950755&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/gadgets/2023/06/speed-matters-how-ethernet-went-from-3mbps-to-100gbps-and-beyond/feed/


link: https://arstechnica.com/?p=1950705
encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5hcnN0ZWNobmljYS5jb20vYXJzdGVjaG5pY2EvZ2FkZ2V0cw==
read: False
type: Rss
title: Google reportedly gives up on making AR glasses—for the third time
description: Project Iris said to be scrapped as Google focuses on AR software.
categories: Google|Tech|ar|augmented reality|google
content:
<div id="rss-wrap">
<figure class="intro-image intro-left">
  <img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/Screenshot-2023-06-28-154157-800x419.jpg" alt="woman wearing AR glasses with graphic displaying what the user is seeing">
      <p class="caption" style="font-size:0.8em"><a href="https://cdn.arstechnica.net/wp-content/uploads/2023/06/Screenshot-2023-06-28-154157-scaled.jpg" class="enlarge-link" data-height="1341" data-width="2560">Enlarge</a> <span class="sep">/</span> A Google video promoted AR's translation potential with these normal-looking consumer AR glasses a year ago, but Google's reportedly quit developing AR specs. (credit: <a rel="nofollow" class="caption-link" href="https://www.youtube.com/watch?v=lj0bFX9HXeE">Google/YouTube</a>)</p>  </figure>






<div><a name="page-1"></a></div>
<p>Google has reportedly scrapped plans to release a pair of augmented reality (AR) glasses. The cancellation of the gadget, reportedly codenamed Project Iris, marks the third time the company's supposedly thrown in the towel on AR glasses. The most recent specs were expected to become Google's second foray into consumer tech and feature a more mainstream-friendly appearance than Google Glass.</p>
<p>In January 2022, the rumor mill churned out its <a href="https://arstechnica.com/gadgets/2022/01/first-details-leak-on-project-iris-googles-next-ar-headset/">first details on Project Iris</a>, thanks to a report from The Verge citing anonymous sources "familiar with the project." Iris was reportedly wireless with external cameras and left heavy graphical processing duties to the cloud.</p>
<p>Last year's report also described prototypes in development as being ski goggle-like, but <a href="https://www.businessinsider.com/google-ar-iris-augmented-reality-smart-glasses-2023-6">Business Insider's</a> report Monday claimed that those prototypes were actually for Google's AR partnership with Samsung and Qualcomm to make a mixed reality (MR) platform. Google announced the project alongside minimal details <a href="https://www.cnet.com/tech/mobile/samsung-google-and-qualcomm-team-up-on-a-new-mixed-reality-platform/">in February</a> 2023.</p></div><p><a href="https://arstechnica.com/?p=1950705#p3">Read 12 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1950705&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/gadgets/2023/06/google-reportedly-gives-up-on-making-ar-glasses-for-the-third-time/feed/


link: https://arstechnica.com/?p=1950753
encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5hcnN0ZWNobmljYS5jb20vYXJzdGVjaG5pY2EvZ2FkZ2V0cw==
read: False
type: Rss
title: Sharpie scanning goof reveals major PlayStation budgets and revenues
description: It's not a good week for gaming companies trying to submit sensitive data.
categories: Gaming|Tech|Call of Duty|FTC|microsoft|PlayStation|redaction|sharpie|Sony
content:
<div id="rss-wrap">
<figure class="intro-image intro-left">
  <img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/sony-sharpie-redact-800x450.jpg" alt="Sharpie with magic sparks shooting out, on top of redacted Sony documents">
      <p class="caption" style="font-size:0.8em"><a href="https://cdn.arstechnica.net/wp-content/uploads/2023/06/sony-sharpie-redact.jpg" class="enlarge-link" data-height="1049" data-width="1864">Enlarge</a> <span class="sep">/</span> Sharpies are great for many things—labeling leftovers, writing "bedroom" on packing boxes, ruining dry erase boards. They're not the best tool for sensitive documents submitted in a federal hearing. (credit: Aurich Lawson)</p>  </figure>






<div><a name="page-1"></a></div>
<p>Most people know AAA games cost a lot to make, but they can also be cash cows if they're hits. Now, because Sharpies can fail to fully redact paper documents if you scan them, we can quantify some of Sony's PlayStation game budgets, earnings, headcounts, and other figures.</p>
<p><a href="https://www.theverge.com/2023/6/28/23777298/sony-ftc-microsoft-confidential-documents-marker-pen-scanner-oops">As reported by The Verge</a>, the documents were supplied by Sony's CEO of PlayStation Jim Ryan. Ryan's submission is part of <a href="https://arstechnica.com/gaming/2023/06/worries-over-starfield-skipping-xbox-helped-push-microsoft-to-buy-bethesda/">the ongoing <em>FTC v. Microsoft</em> hearing</a> resulting from <a href="https://arstechnica.com/gaming/2023/06/report-ftc-will-file-to-block-microsofts-69b-activision-blizzard-acquisition/">the Federal Trade Commission's attempt to block Microsoft's purchase of Activision Blizzard</a> on antitrust grounds. By giving the FTC confidential numbers on AAA game performance, Sony aimed to show how Microsoft having Call of Duty as an exclusive franchise could hurt Sony (despite <a href="https://arstechnica.com/gaming/2023/06/playstation-chief-privately-dismissed-concerns-of-xbox-exclusive-call-of-duty/">emails to the contrary)</a>.</p>
<p>But because of the interplay of paper, printer ink, Sharpie ink, and optical scanners, a lot more people, including journalists, can see those numbers. Some of the big ones are:</p></div><p><a href="https://arstechnica.com/?p=1950753#p3">Read 2 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1950753&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/gaming/2023/06/major-sony-playstation-budget-figures-leaked-because-of-poor-sharpie-redactions/feed/


link: https://arstechnica.com/?p=1950684
encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5hcnN0ZWNobmljYS5jb20vYXJzdGVjaG5pY2EvZ2FkZ2V0cw==
read: False
type: Rss
title: After merger with Google Maps division, Waze gets hit with layoffs
description: Waze, no longer independent at Google, continues its merger with the Geo division.
categories: Google|Tech|google maps|layoffs|Waze
comments_url: https://arstechnica.com/google/2023/06/waze-googles-other-mapping-app-gets-hit-with-layoffs/feed/
content:
<div id="rss-wrap">
<figure class="intro-image intro-left">
  <img src="https://cdn.arstechnica.net/wp-content/uploads/2023/03/GettyImages-1235613908-800x537.jpg" alt="In this photo illustration a Waze logo of a GPS navigation software app is seen on a smartphone and a pc screen.">
      <p class="caption" style="font-size:0.8em"><a href="https://cdn.arstechnica.net/wp-content/uploads/2023/03/GettyImages-1235613908-scaled.jpg" class="enlarge-link" data-height="1720" data-width="2560">Enlarge</a> (credit: Pavlo Gonchar/SOPA Images/LightRocket via Getty Images)</p>  </figure>






<div><a name="page-1"></a></div>
<p>Late last year, Waze faced serious questions about its future at Google when, as part of Google's company-wide efforts at cost-cutting, Waze <a href="https://arstechnica.com/gadgets/2022/12/googles-cost-cutters-come-for-waze-will-lose-status-as-independent-company/">lost its status</a> as an independent company. The mapping app was forced to merge with Google Geo (aka the Google Maps division) even though the two apps supposedly remain mostly independent. Six months later, CNBC's <a href="https://www.cnbc.com/2023/06/27/google-cuts-jobs-at-waze-as-it-continues-to-merge-mapping-products.html">Jennifer Elias</a> reports the job cuts have arrived, and Waze will be losing some employees.</p>
<p>Google Geo's VP and general manager, Chris Phillips, announced that Waze's ad platform would be shut down in favor of Google ads and reportedly told employees that the move "will result in a reduction of Waze Ads monetization-focused roles in sales, marketing, operations, and analytics." It's not clear how many of Waze's 500 employees will be affected. Google has been doing all sorts of layoffs lately, with the biggest batch—12,000 jobs—announced <a href="https://arstechnica.com/gadgets/2023/01/google-cuts-12000-jobs-the-largest-layoff-in-the-companys-history/">in January</a>.</p>
<p>If there's anything Google is good at, it's advertising, so it certainly makes sense for Waze to adopt Google's ad platform. Waze has a lot of redundancy compared to Google Maps, and it's unclear how far Google wants to take this logic. Right now, the company maintains two separate mapping apps with similar features and similar layouts. Waze has 140 million monthly active users, but that's not much compared to the billion-plus users of Google Maps. You could certainly argue for a full-blown merger, but Google told CNBC it "remains deeply committed to growing Waze’s unique brand, its beloved app and its thriving community of volunteers and users," which should calm the fears of Waze users a bit. Remember, though, mergers and shutdowns come at you fast at Google, like when the company most recently said Stadia "<a href="https://twitter.com/GoogleStadia/status/1552989433590214656?s=20&amp;t=xVzXMW9DJZI57ZMwnGDF7w">is not shutting down</a>" two months before announcing Stadia <a href="https://arstechnica.com/gadgets/2022/09/google-stadia-officially-shuts-down-january-2023-will-refund-game-purchases/">would be shut down</a>.</p></div><p><a href="https://arstechnica.com/?p=1950684#p3">Read 2 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1950684&comments=1">Comments</a></p>


link: https://arstechnica.com/?p=1950134
encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5hcnN0ZWNobmljYS5jb20vYXJzdGVjaG5pY2EvZ2FkZ2V0cw==
read: False
type: Rss
title: Guidemaster: Track your health without ditching your mechanical watch
description: There are options for tracking your health without removing your stylish watch.
categories: Shopping|Tech|EDC|everyday carry|fitness tracker|Health|health tracker|Oura|wearable|whoop|Withings
content:
<div id="rss-wrap">
<figure class="intro-image intro-left">
  <img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/Watches-and-smartwatches-800x600.jpeg" alt="Watches and smartwatches">
      <p class="caption" style="font-size:0.8em"><a href="https://cdn.arstechnica.net/wp-content/uploads/2023/06/Watches-and-smartwatches-scaled.jpeg" class="enlarge-link" data-height="1920" data-width="2560">Enlarge</a> <span class="sep">/</span> From left to right: Apple Watch Ultra, Shinola Bronze Monster, Oura Ring, Withings Scanwatch Horizon, a traditional ring, and Garmin Epix Gen 2.  (credit: Chuong Nguyen)</p>  </figure>






<div><a name="page-1"></a></div>
<p>Everyday carry enthusiasts typically face a conundrum when it comes to choosing between a smartwatch with all the benefits of modern wrist-worn tech or giving up tracking their health metrics in exchange for classic, mechanical watches. There are a few people who wear a regular timepiece on one wrist and a smartwatch on the other, but those drawbacks are obvious.</p>
<p>Fortunately, there's a growing selection of wearables that offer the tracking power of an Apple watch without taking up space on your wrist. These allow you to wear a mechanical watch for timekeeping while a health-tracking device feeds data to your phone. If you care about sleep metrics, step counts, heart and respiration rates, blood oxygen levels and still want to wear your mechanical watch, we’ve found three great wearable solutions for you.</p>
<p><em>Ars Technica may earn compensation for sales from links on this post through <a href="https://arstechnica.com/affiliate-link-policy/" target="_blank" rel="noopener" data-uri="4c776bd3d2b303f3138d656b48f6862b">affiliate programs</a>.</em></p></div><p><a href="https://arstechnica.com/?p=1950134#p3">Read 16 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1950134&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/shopping/2023/06/guidemaster-track-your-health-without-ditching-your-mechanical-watch/feed/


link: https://arstechnica.com/?p=1950366
encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5hcnN0ZWNobmljYS5jb20vYXJzdGVjaG5pY2EvZ2FkZ2V0cw==
read: False
type: Rss
title: Devs find that Vision Pro can’t do true room-scale VR, but that’s no surprise
description: Opinion: Safety features limit Vision Pro for VR—but VR isn't its purpose.
categories:
Apple|Tech|apple|Apple Vision|Apple Vision Pro|ar|augmented reality|hmd|mixed reality|virtual reality|visionOS|VR|XR

content:
<div id="rss-wrap">





<div><a name="page-1"></a></div>
  <ul class="gallery shortcode-gallery gallery-wide">
          <li>
        <div class="gallery-item-content">
          <div class="gallery-image"><img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/IMG_4028-980x735.jpeg" alt=""></div>
          <p>
            This is Apple’s Vision Pro headset. It looks a bit like a particularly bulky pair of ski goggles, with the materials and design language of Apple’s AirPods Max headphones.                          [credit:
                              Samuel Axon                            ]
                      </p>
        </div>
      </li>
      </ul>

<p>Recent discoveries by developers working with Apple's visionOS software development kit have revealed that Apple isn't going for room-scale VR with Vision Pro—something that will potentially frustrate users hoping for a high-end VR headset to compete with offerings from Meta and others.</p>
<p>As reported by <a href="https://9to5mac.com/2023/06/27/vision-pro-safe-area/">9to5Mac</a>, Hans Karlsson of creative marketing agency Mimir <a href="https://twitter.com/VRmaninJapan/status/1671702526851432448?ref_src=twsrc%5Etfw%7Ctwcamp%5Etweetembed%7Ctwterm%5E1672002859397976064%7Ctwgr%5E75a948230ce68d1674e1290ee9f62ea7e4677629%7Ctwcon%5Es2_&amp;ref_url=https%3A%2F%2F9to5mac.com%2F2023%2F06%2F27%2Fvision-pro-safe-area%2F">lamented</a> last week on Twitter that visionOS pulls users out of immersive VR when they move more than 1.5 meters away from the virtual environment's origin point, saying that Apple has thus "crippled VR" and made it so the platform is only for "couch potatoes." This wasn't new information, though; Apple's documentation for visionOS developers revealed this was the case during WWDC. The <a href="https://developer.apple.com/documentation/visionos/creating-fully-immersive-experiences">documentation</a> reads:</p>
<blockquote><p>When you start a fully immersive experience, visionOS defines a system boundary that extends 1.5 meters from the initial position of the person’s head. If their head moves outside of that zone, the system automatically stops the immersive experience and turns on the external video again. This feature is an assistant to help prevent someone from colliding with objects.</p></blockquote>
<p>Around the same time, people discovered that Apple also <a href="https://9to5mac.com/2023/06/22/apple-vision-pro-high-speeds/">yanks you out</a> of any immersive environment if you start moving too quickly in any direction. visionOS will show users a message stating that they are "moving at an unsafe speed" and that "virtual content has been temporarily hidden until you return to a safe speed."</p></div><p><a href="https://arstechnica.com/?p=1950366#p3">Read 16 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1950366&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/gadgets/2023/06/devs-find-that-vision-pro-cant-do-true-room-scale-vr-but-thats-no-surprise/feed/


link: https://arstechnica.com/?p=1948838
encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5hcnN0ZWNobmljYS5jb20vYXJzdGVjaG5pY2EvZ2FkZ2V0cw==
read: False
type: Rss
title: Lenovo ThinkPad X1 Carbon Gen 11 review: Two steps forward, one step back
description: New Gen 11 model fixes the worst of Gen 10's flaws, but not without compromises.
categories:
Tech|Ars Shopping|Gadgetology|laptop|Lenovo|lenovo laptop|Lenovo ThinkPad|lenovo thinkpad x1 carbon|ThinkPad|thinkpad x1 carbon|ultrabook|x1 carbon

content:
<div id="rss-wrap">
<figure class="intro-image intro-left">
  <img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/IMG_1204-800x533.jpeg" alt="Lenovo's ThinkPad X1 Carbon Gen 11, which not-confusingly-at-all feature 13th-generation Intel Core processors.">
      <p class="caption" style="font-size:0.8em"><a href="https://cdn.arstechnica.net/wp-content/uploads/2023/06/IMG_1204.jpeg" class="enlarge-link" data-height="1707" data-width="2560">Enlarge</a> <span class="sep">/</span> Lenovo's ThinkPad X1 Carbon Gen 11, which not-confusingly-at-all feature 13th-generation Intel Core processors. (credit: Andrew Cunningham)</p>  </figure>






<div><a name="page-1"></a></div>
<table class="specifications right" width="300">
<tbody>
<tr>
<th style="text-align: left;" colspan="2">Specs at a glance: Lenovo ThinkPad X1 Carbon Gen 11 (As reviewed)</th>
</tr>
<tr>
<th>Display</th>
<td>14.0-inch 1920×1200 touchscreen (162 PPI)</td>
</tr>
<tr>
<th>OS</th>
<td>Windows 11 Pro</td>
</tr>
<tr>
<th>CPU</th>
<td>Intel Core i7-1355U (2 P-cores, 8 E-cores)</td>
</tr>
<tr>
<th>RAM</th>
<td>16GB LPDDR5 5200 MHz (soldered)</td>
</tr>
<tr>
<th>GPU</th>
<td>Intel Iris Xe (integrated)</td>
</tr>
<tr>
<th>Storage</th>
<td>512GB NVMe SSD</td>
</tr>
<tr>
<th>Networking</th>
<td>Wi-Fi 6E (802.11ax), Bluetooth 5.3</td>
</tr>
<tr>
<th>Battery</th>
<td>57 Wh</td>
</tr>
<tr>
<th>Ports</th>
<td>Two Thunderbolt 4, two 5Gbps USB-A, HDMI 2.0b, headphones</td>
</tr>
<tr>
<th>Size</th>
<td>8.76×12.43×0.6 inches (222.5×315.6×15.36 mm)</td>
</tr>
<tr>
<th>Weight</th>
<td>2.48 lbs (1.12 kg)</td>
</tr>
<tr>
<th>Warranty</th>
<td>1-year</td>
</tr>
<tr>
<th>Price as reviewed</th>
<td><a href="https://howl.me/cj2M8A2AVDu" target="_blank" rel="noopener">$1,733</a></td>
</tr>
</tbody>
</table>
<p>Lenovo's ThinkPad X1 Carbon has long been one of our favorite ultrabook designs, combining a generous array of ports, a nice keyboard and trackpad, and a larger-than-typical 14-inch screen into a thin-and-light package.</p>
<p><a href="https://howl.me/cj2Ncll7q5m" target="_blank" rel="noopener">Last year's Gen 10 iteration</a> had a major flaw, though—a big step down in battery life, at least partially attributable to a more power-hungry 12th-generation Intel processor. (Yes, before we get any further, Lenovo's ThinkPad generational designations don't align with Intel's processor designation, so a Gen 10 ThinkPad uses a 12th-gen Intel CPU, and the Gen 11 ThinkPad uses a 13th-gen CPU.)</p>
<p><a href="https://howl.me/cj2M8A2AVDu" target="_blank" rel="noopener">This year's Gen 11 X1 Carbon refresh</a> mainly has one job: retain all the good stuff about last year's refresh and the X1 Carbon lineup generally but get the battery life closer to where it was before. The Gen 11 partially does that job. That means the performance gains from last year are negligible (and sometimes even a small step backward). It's an acceptable sacrifice for improved battery life, and the X1 Carbon is still one of the best all-around portable laptops you can buy. It's just that the Gen 11 model still can't quite manage to feel like an across-the-board upgrade from the Gen 9 X1 Carbon from two years ago.</p></div><p><a href="https://arstechnica.com/?p=1948838#p3">Read 22 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1948838&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/gadgets/2023/06/lenovo-thinkpad-x1-carbon-gen-11-review-two-steps-forward-one-step-back/feed/


link: https://arstechnica.com/?p=1950229
encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5hcnN0ZWNobmljYS5jb20vYXJzdGVjaG5pY2EvZ2FkZ2V0cw==
read: False
type: Rss
title: GeForce RTX 4060 review: Not thrilling, but a super-efficient $299 workhorse
description: 60-class GPUs are Nvidia's most popular; the 4060 don't fix what ain't broke.
categories:
Features|Gaming|Tech|Ars Shopping|Gadgetology|GeForce|geforce experience|GPU|Graphics Card|NVIDIA|PC gaming|rtx 3060|rtx 4060|rtx 4060 ti

content:
<div id="rss-wrap">
<figure class="intro-image intro-left">
  <img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/IMG_1328-800x533.jpeg" alt="PNY's take on the basic $299 version of the Nvidia GeForce RTX 4060. ">
      <p class="caption" style="font-size:0.8em"><a href="https://cdn.arstechnica.net/wp-content/uploads/2023/06/IMG_1328.jpeg" class="enlarge-link" data-height="1707" data-width="2560">Enlarge</a> <span class="sep">/</span> PNY's take on the basic $299 version of the Nvidia GeForce RTX 4060.  (credit: Andrew Cunningham)</p>  </figure>






<div><a name="page-1"></a></div>
<span class="ars-approved-logo right"></span>
<p>Nvidia's GeForce 1060, 2060, and 3060 graphics cards are some of <a href="https://store.steampowered.com/hwsurvey/Steam-Hardware-Software-Survey-Welcome-to-Steam">the most widely used GPUs</a> in all of PC gaming. Four of Steam's top five GPUs are 60-series cards, and the only one that isn't is an even lower-end GTX 1650.</p>
<p>All of this is to say that, despite all the fanfare for high-end products like the RTX 4090, the new <a href="https://amzn.to/46mKZyC" target="_blank" rel="noopener">GeForce RTX 4060</a> is Nvidia's most important Ada Lovelace-based GPU. History suggests that it will become a baseline for game developers to aim for and the go-to recommendation for most entry-level-to-mainstream PC gaming builds.</p>
<p>The RTX 4060, which launches this week starting at <a href="https://amzn.to/46mKZyC" target="_blank" rel="noopener">$299</a>, is mostly up to the task. It's faster and considerably more power efficient than the 3060 it replaces, and it doesn't come with the same generation-over-generation price hike as the higher-end Lovelace GPUs. It's also a solid value compared to the <a href="https://howl.me/cj28R4MTR6w" target="_blank" rel="noopener">4060 Ti</a>, typically delivering between 80 and 90 percent of the 4060 Ti's performance for 75 percent of the money.</p></div><p><a href="https://arstechnica.com/?p=1950229#p3">Read 22 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1950229&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/gadgets/2023/06/geforce-rtx-4060-review-not-thrilling-but-a-super-efficient-299-workhorse/feed/


link: https://arstechnica.com/?p=1950376
encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5hcnN0ZWNobmljYS5jb20vYXJzdGVjaG5pY2EvZ2FkZ2V0cw==
read: False
type: Rss
title: YouTube “Playables” could bring Facebook-style casual games to YouTube
description: YouTube's demands for eternal growth could mean branching out into casual games.
categories: Google|Tech|YouTube|youtube gaming
content:
<div id="rss-wrap">
<figure class="intro-image intro-left">
  <img src="https://cdn.arstechnica.net/wp-content/uploads/2022/06/youtube-800x520.jpeg" alt="YouTube “Playables” could bring Facebook-style casual games to YouTube">
      <p class="caption" style="font-size:0.8em"><a href="https://cdn.arstechnica.net/wp-content/uploads/2022/06/youtube.jpeg" class="enlarge-link" data-height="650" data-width="1000">Enlarge</a> (credit: Getty Images)</p>  </figure>






<div><a name="page-1"></a></div>
<p><a href="https://www.wsj.com/articles/googles-youtube-is-testing-an-online-games-offering-16d1e772">The Wall Street Journal</a> has an interesting report on a new "YouTube Playables" feature that it says is currently in testing. Google recently killed off one YouTube-adjacent gaming service, <a href="https://arstechnica.com/gadgets/2022/09/google-stadia-officially-shuts-down-january-2023-will-refund-game-purchases/">Stadia</a>, but that was AAA games streamed frame by frame over the Internet. "Playables" would take more of a Facebook approach, offering more casual, simple games that run in a browser. Think <em>Farmville</em> or <em>Angry Birds</em>, but on YouTube.</p>
<p>One example game from the report is <a href="https://www.jagranplay.com/casual/stack-bounce-1670420982574"><em>Stack Bounce</em></a>, a brick-breaking game that has a smartphone app but can also run in a browser. I know the Flash platform has been dead for years, but in my mind, these are still "Flash games"—simple, 2D, addictive games on a browser.</p>
<p>Why exactly would anyone want casual games on YouTube? It says YouTube "is already a popular destination for gamers and competes with Amazon’s Twitch for viewers of livestreamed footage. By hosting a selection of online games, the product would give YouTube a larger footprint in the sector." Do people play Flash-style games on Twitch? If you look at a "<a href="https://twitchtracker.com/games/time-watched">time watched</a>" game tracker for Twitch, what you get are almost exclusively the AAA games that Google opted out of when it shut down Stadia. Aside from gambling games, everything in the top 50 is a AAA title.</p></div><p><a href="https://arstechnica.com/?p=1950376#p3">Read 3 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1950376&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/google/2023/06/youtube-playables-could-bring-facebook-style-casual-games-to-youtube/feed/


link: https://arstechnica.com/?p=1950232
encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5hcnN0ZWNobmljYS5jb20vYXJzdGVjaG5pY2EvZ2FkZ2V0cw==
read: False
type: Rss
title: Protests broke Reddit hack for useful Google search results—and Google knows it
description: Search term + Reddit = John Oliver?
categories: Google|Policy|Tech|API|google|reddit
content:
<div id="rss-wrap">
<figure class="intro-image intro-left">
  <img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/GettyImages-1243641630-800x533.jpg" alt="Protests broke Reddit hack for useful Google search results—and Google knows it">
      <p class="caption" style="font-size:0.8em"><a href="https://cdn.arstechnica.net/wp-content/uploads/2023/06/GettyImages-1243641630-scaled.jpg" class="enlarge-link" data-height="1707" data-width="2560">Enlarge</a> (credit: <a rel="nofollow" class="caption-link" href="https://www.gettyimages.com/detail/news-photo/in-this-photo-illustration-a-reddit-logo-seen-displayed-on-news-photo/1243641630?adppopup=true">Getty</a>)</p>  </figure>






<div><a name="page-1"></a></div>
<p><a href="https://arstechnica.com/gadgets/2023/06/reddit-mods-allowed-porn-as-protest-the-company-nuked-their-mod-badges/">Ongoing protests</a> regarding Reddit's upcoming API price change on July 1 are rattling the Reddit community, but they're not the only ones impacted. Those who navigate Google's ad-littered, search-engine-optimized (SEO) results by adding "Reddit" to their query have seen their experience hampered, too. According to <a href="https://www.cnbc.com/2023/06/26/google-execs-hope-new-search-feature-will-help-amid-reddit-blackouts.html">CNBC</a>, Google's aware that its search results need fine-tuning through appendages like "site:reddit.com." However, Google's response to this problem fails to address the core reasons people modify their search queries like this: There's demand for results delivering human (not necessarily influencer) voices and that aren't listed due to people manipulating Google's algorithm.</p>
<p>People rely on the Reddit hack for Google search results to avoid things that often float to the top of results pages—websites built on SEO but lack reliable or relevant content. But since the Reddit blackout started June 12 and was followed by other forms of user protest, that trick is less effective. As of this writing, over 2,400 subreddits are still private in protest, according to the <a href="https://www.twitch.tv/reddark_247">Reddark_247</a> counter on Twitch, while others are read-only, suddenly labeled as not safe for work (NSFW), or dedicated to images of <a href="https://www.cnn.com/2023/06/23/tech/reddit-john-oliver-protest/index.html">John Oliver</a>.</p>
<p>On Monday, CNBC, citing an audio recording of a company-wide meeting from earlier this month, reported that Prabhakar Raghavan, a Google SVP who heads Google Search, "admitted users are unhappy when employees asked about the Reddit blackouts and their impact on results."</p></div><p><a href="https://arstechnica.com/?p=1950232#p3">Read 12 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1950232&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/gadgets/2023/06/google-admits-reddit-protests-make-it-harder-to-find-helpful-search-results/feed/


link: https://arstechnica.com/?p=1950008
encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5hcnN0ZWNobmljYS5jb20vYXJzdGVjaG5pY2EvZ2FkZ2V0cw==
read: False
type: Rss
title: The Linux coders turning the ROG Ally and other handhelds into Steam Deck clones
description: It's not an easy process, but it's getting close to a nearly full SteamOS feel.
categories: Gaming|Tech|Ars Shopping|asus rog ally|steam deck
content:
<div id="rss-wrap">
<figure class="intro-image intro-left">
  <img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/IMG_3016-EDIT-800x382.jpg" alt="ROG Ally unit running Steam">
      <p class="caption" style="font-size:0.8em"><a href="https://cdn.arstechnica.net/wp-content/uploads/2023/06/IMG_3016-EDIT-scaled.jpg" class="enlarge-link" data-height="1223" data-width="2560">Enlarge</a> <span class="sep">/</span> SteamOS on the Asus ROG Ally, the hard (but kinda fun) way. (credit: Kevin Purdy)</p>  </figure>






<div><a name="page-1"></a></div>
<p>As soon as I was done with my <a href="https://arstechnica.com/gadgets/2023/05/the-asus-rog-ally-runs-windows-eats-battery-and-needs-time-to-cook/">review of the Asus ROG Ally</a>, I grabbed my best USB stick and started looking for ISOs to download.</p>
<p>Windows is, of course, the main highway to most PC gaming, but it's also (as detailed in the review) not yet built to work well on a 7-inch gaming handheld. The <a href="https://howl.me/cj2O7JSo6OD" target="_blank" rel="noopener">ROG Ally</a> ships with Windows (Home) installed and a bunch of Asus software, but it is still, at heart, a PC. With effort, you can get into the BIOS, disable Secure Boot, plug in a USB stick, and boot a USB stick with a live Linux distribution on it.</p>
<p>It's a weird feeling, ignoring almost everything Asus has done to set up this device with gaming and power management software and starting over at the storage level. But, like the many Linux developers who see the Ally as the <a href="https://arstechnica.com/gaming/2022/02/steam-deck-the-comprehensive-ars-technica-review/">Steam Deck</a>'s potentially beefier cousin, I wanted to leave the comforts of the Start menu for wilder lands.</p></div><p><a href="https://arstechnica.com/?p=1950008#p3">Read 22 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1950008&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/gadgets/2023/06/the-linux-coders-turning-the-rog-ally-and-other-handhelds-into-steam-deck-clones/feed/


link: https://arstechnica.com/?p=1949948
encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5hcnN0ZWNobmljYS5jb20vYXJzdGVjaG5pY2EvZ2FkZ2V0cw==
read: False
type: Rss
title: Person who made the Windows 3.1 port of Wordle is back with a ChatGPT client
description: Developer has ported modern SSL/TLS libraries to Windows 3.1 to get it working.
categories: AI|Tech|chat openai|ChatGPT|chatgtp|Nostalgia|Retro computing|ssl|tls|vintage computer|windows 3.1
content:
<div id="rss-wrap">
<figure class="intro-image intro-left">
  <img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/wingpt_computer.png" alt="WinGPT answering many pressing and cutting-edge questions.">
      <p class="caption" style="font-size:0.8em"><a href="https://cdn.arstechnica.net/wp-content/uploads/2023/06/wingpt_computer.png" class="enlarge-link" data-height="600" data-width="800">Enlarge</a> <span class="sep">/</span> WinGPT answering many pressing and cutting-edge questions. (credit: <a rel="nofollow" class="caption-link" href="https://www.dialup.net/wingpt/">Dialup.net</a>)</p>  </figure>






<div><a name="page-1"></a></div>

<p>Microsoft is working to integrate ChatGPT-based technology into <a href="https://arstechnica.com/gadgets/2023/05/built-in-chatgpt-driven-copilot-will-transform-windows-11-starting-in-june/">more and more places in Windows 11</a>, but it isn't doing the same for older versions of Windows. Those of you with an old Windows 3.1 or Windows 95 PC can breathe easy, though, because the same developer who created the Windows 3.1 version of <em>Wordle</em> has returned with a Windows 3.1 ChatGPT client called <a href="https://www.dialup.net/wingpt/">WinGPT</a>.</p>
<p>WinGPT supports any 16- or 32-bit version of Windows 3.1 or newer but won't run natively on 64-bit versions of Windows. You can download it from the bottom of <a href="https://www.dialup.net/wingpt/">this Dialup.net page</a>, which also doubles as a development blog detailing how it was built and how its icon was designed. You'll need to provide your own OpenAI API key.</p>
<p>Running ChatGPT on ancient systems is possible mostly because most processing happens on OpenAI's servers rather than locally, so you don't need a modern 16-core battle station to make it work. The main limitation on old hardware is memory rather than processing power. Windows 3.1 generally won't boot with more than 256MB, and a period-appropriate 386 or 486 PC would be more likely to use between 4MB and 8MB (for reference, here's <a href="http://www.1000bit.it/ad/bro/compaq/CompaqDeskPro-M-WindowsEdition.pdf">a 1992 Compaq Deskpro ad</a> for 386 and 486 PCs). The OS would install and run on systems with as little as 1MB.</p></div><p><a href="https://arstechnica.com/?p=1949948#p3">Read 5 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1949948&comments=1">Comments</a></p>

comments_url:
https://arstechnica.com/gadgets/2023/06/wingpt-is-a-windows-3-1-ai-chatbot-for-your-old-ibm-compatible-desktop/feed/


link: https://arstechnica.com/?p=1949814
encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5hcnN0ZWNobmljYS5jb20vYXJzdGVjaG5pY2EvZ2FkZ2V0cw==
read: False
type: Rss
title: RIP to my Pixel Fold: Dead after four days
description: The closed display halves almost touch, and that can smash debris into the screen.
categories: Features|Google|Tech|Google Pixel|pixel fold
comments_url: https://arstechnica.com/google/2023/06/rip-to-my-pixel-fold-dead-after-four-days/feed/
content:
<div id="rss-wrap">
<figure class="intro-image intro-left">
  <img src="https://cdn.arstechnica.net/wp-content/uploads/2023/06/27-800x545.jpg" alt="My dead Pixel Fold display. That huge white gradient should not be there. ">
      <p class="caption" style="font-size:0.8em"><a href="https://cdn.arstechnica.net/wp-content/uploads/2023/06/27-scaled.jpg" class="enlarge-link" data-height="1746" data-width="2560">Enlarge</a> <span class="sep">/</span> My dead Pixel Fold display. That huge white gradient should not be there.  (credit: Ron Amadeo)</p>  </figure>






<div><a name="page-1"></a></div>
<p>A flame that burns twice as bright burns half as long. That was my brief experience with the Pixel Fold, which was a wonderful little device until the display died, along with my hopes and dreams. I barely used it, but it was beautiful.</p>
<p>I didn't do anything to deserve this. The phone sat on my desk while I wrote about it, and I would occasionally stop to poke the screen, take a screenshot, or open and close it. It was never dropped or exposed to a significant amount of grit, nor had it gone through the years of normal wear and tear that phones are expected to survive. This was the lightest possible usage of a phone, and it still broke.</p>
<p>The flexible OLED screen died after four days. The bottom 10 pixels of the Pixel Fold went dead first, forming a white line of 100 percent brightness pixels that blazed across the bottom of the screen. The entire left half of the foldable display stopped responding to touch, too, and an hour later, a white gradient started growing upward across the display.</p></div><p><a href="https://arstechnica.com/?p=1949814#p3">Read 9 remaining paragraphs</a> | <a href="https://arstechnica.com/?p=1949814&comments=1">Comments</a></p>


link: https://www.digitaleoverheid.nl/nieuws/wet-digitale-overheid-op-1-juli-2023-van-kracht/
encoded_syndication_url: aHR0cDovL3d3dy5kaWdpdGFsZW92ZXJoZWlkLm5sL2ZlZWQv
read: False
type: Rss
title: Wet digitale overheid op 1 juli van kracht
categories: Nieuws
description:
<p>Iedereen moet de digitale wereld kunnen vertrouwen. De Wet digitale overheid (Wdo) regelt een veilige toegang van de digitale overheid en gaat per 1 juli gefaseerd in.</p>
<p>Het bericht <a rel="nofollow" href="https://www.digitaleoverheid.nl/nieuws/wet-digitale-overheid-op-1-juli-2023-van-kracht/">Wet digitale overheid op 1 juli van kracht</a> verscheen eerst op <a rel="nofollow" href="https://www.digitaleoverheid.nl">Digitale Overheid</a>.</p>

content:
<p><img decoding="async" class="alignnone wp-image-55404 size-full" src="https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2022/03/6_network_1000x600.png" alt="een man en vrouw die een laptop bestuderen" width="1000" height="600" srcset="https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2022/03/6_network_1000x600.png 1000w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2022/03/6_network_1000x600-300x180.png 300w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2022/03/6_network_1000x600-768x461.png 768w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2022/03/6_network_1000x600-667x400.png 667w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2022/03/6_network_1000x600-400x240.png 400w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2022/03/6_network_1000x600-88x53.png 88w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2022/03/6_network_1000x600-900x540.png 900w" sizes="(max-width: 1000px) 100vw, 1000px" /></p>
<p><span class="intro">Het kabinet werkt aan een waardengedreven digitale samenleving waarin iedereen mee kan doen, de digitale wereld kan vertrouwen en grip heeft op het digitale leven. Om dat te bereiken moet de toegang tot de digitale overheid op een veilige en betrouwbare manier geregeld worden. Dit regelt het kabinet met de Wet digitale overheid (Wdo) die per 1 juli 2023 gefaseerd in werking gaat.</span></p>
<p>De wet stelt eisen aan de toegang tot de digitale overheid en regelt het toezicht daarop. Daarnaast stelt de wet (open) standaarden verplicht. Hiermee wordt bijvoorbeeld een standaard voor veilige overheidswebsites en webapplicaties ingevoerd, en wordt de tijdelijke regelgeving rondom digitale toegankelijkheid omgezet naar de Wdo.</p>
<h2>Inloggen bij de overheid</h2>
<p>De Wet digitale overheid wordt gefaseerd ingevoerd. Zo worden op 1 juli de nieuwe regels om digitale dienstverlening op het juiste betrouwbaarheidsniveau te classificeren van kracht. De regels sluiten aan bij de verantwoordelijkheid die organisaties hebben om dienstverlening betrouwbaar aan te bieden. Deze regels helpen organisaties daarbij.</p>
<p>De komende jaren wordt de Wet digitale overheid dus gefaseerd en beheerst ingevoerd. Zo komen er naast DigiD &#8211; voor burgers die dat willen &#8211; ook private inlogmiddelen beschikbaar om in te loggen bij de overheid. Deze middelen moeten aan strenge eisen voldoen. Ook voor bedrijven zullen private inlogmiddelen worden toegelaten.</p>
<p>Daarnaast zullen de komende jaren alle (semi-) publieke dienstverleners gefaseerd gebruik gaan maken van de inlogmiddelen die worden toegelaten. De Wdo houdt rekening met de uitvoeringsgevolgen voor dienstverleners. De invoering zal dus stap voor stap gaan. Dienstverleners sluiten in hun eigen tempo en in overleg met het ministerie van Binnenlandse Zaken en Koninkrijksrelaties (BZK) aan. Zij geven zelf de aansluitdatum op. Dit kan gefaseerd per organisatie en per dienst. Vanaf dat moment kunnen burgers met alle toegelaten inlogmiddelen bij de betreffende organisatie terecht.</p>
<h2>Veilige websites en webapplicaties</h2>
<p>De verplichtingen rondom standaarden voor veiligheid gaan direct per 1 juli in. Zo wordt de HTTPS-standaard verplicht voor alle publiek toegankelijke overheidswebsites en webapplicaties. Deze standaard &#8211; ook wel bekend als ‘het slotje’ in de adresbalk van de url &#8211; zorgt ervoor dat de verbinding tussen de browser van de bezoeker en de website van de overheidsorganisatie goed beveiligd is. Dit voorkomt dat criminelen privégegevens van de bezoeker kunnen afluisteren of opgevraagde informatie kunnen manipuleren. In aanvulling op HTTPS moeten overheidsorganisaties ook de HSTS-standaard gebruiken. Dat zorgt ervoor dat browsers na een eerste websitebezoek direct via HTTPS met de website verbinden. Daarnaast moet de HTTPS-configuratie voldoen aan de TLS-richtlijnen en Webapplicatie-richtlijnen van het Nationaal Cyber Security Centrum (NCSC).</p>
<h2>Digitale toegankelijkheid</h2>
<p>Dienstverlening van de overheid moet voor iedereen toegankelijk zijn. Ook wanneer je bijvoorbeeld een visuele beperking hebt. Om dat te regelen is het Tijdelijk Besluit Digitale Toegankelijkheid Overheid omgezet naar de Wet digitale overheid. Daardoor is de Wdo vanaf 1 juli de wettelijke grondslag voor het Besluit geworden en is het woord &#8216;Tijdelijk&#8217; bij het Besluit geschrapt. Met de inwerkingtreding van de Wdo op 1 juli verandert er niets aan de wettelijke verplichting en blijft het Besluit Digitale Toegankelijkheid Overheid van kracht.</p>
<h2>Meer weten?</h2>
<p>Lees meer over de <a href="https://www.digitaleoverheid.nl/overzicht-van-alle-onderwerpen/wetgeving/wet-digitale-overheid/">Wet digitale overheid</a>.</p>
<p>Het bericht <a rel="nofollow" href="https://www.digitaleoverheid.nl/nieuws/wet-digitale-overheid-op-1-juli-2023-van-kracht/">Wet digitale overheid op 1 juli van kracht</a> verscheen eerst op <a rel="nofollow" href="https://www.digitaleoverheid.nl">Digitale Overheid</a>.</p>


link: https://www.digitaleoverheid.nl/nieuws/winnaars-innovatiebudget-bekend/
encoded_syndication_url: aHR0cDovL3d3dy5kaWdpdGFsZW92ZXJoZWlkLm5sL2ZlZWQv
read: False
type: Rss
title: Winnaars innovatiebudget bekend!
categories: Nieuws|Innovatie|Innovatie digitale overheid|innovatiebudget
description:
<p>BZK geeft 14 projecten subsidie vanuit het Innovatiebudget Digitale Overheid. Met dit budget krijgen projecten de financiële mogelijkheid om hun innovatieve ideeën te realiseren.</p>
<p>Het bericht <a rel="nofollow" href="https://www.digitaleoverheid.nl/nieuws/winnaars-innovatiebudget-bekend/">Winnaars innovatiebudget bekend!</a> verscheen eerst op <a rel="nofollow" href="https://www.digitaleoverheid.nl">Digitale Overheid</a>.</p>

content:
<p><img decoding="async" loading="lazy" class="alignnone size-large wp-image-62318" src="https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/DSC_0730-1024x683.jpg" alt="" width="1024" height="683" />Het ministerie van BZK geeft <a href="https://www.digitaleoverheid.nl/overzicht-van-alle-onderwerpen/innovatie/innovatiebudget/toekenning-innovatiebudget-2023/">14 projecten een subsidie</a> vanuit het Innovatiebudget Digitale Overheid. Met dit budget krijgen projecten de financiële mogelijkheid om hun innovatieve ideeën te realiseren. Het innovatiebudget is een bedrag van 3 miljoen euro bedoeld om projecten op te starten, op te schalen of te borgen. Zo kan de digitale dienstverlening van de overheid verbeterd worden.</p>
<h3>Verschillende projecten</h3>
<p>De ingediende projecten bieden een oplossing voor verschillende uitdagingen. 1 van de projecten zorgt ervoor dat participatietools inpasbaar worden gemaakt voor iedere overheidswebsite. Een ander project biedt een integrale aanpak voor digitale inclusie. Maar ook de politie heeft een creatieve oplossing bedacht om de juiste persoon, met de juiste kennis, op het juiste moment bij een incident te betrekken. <a href="https://www.digitaleoverheid.nl/overzicht-van-alle-onderwerpen/innovatie/innovatiebudget/toekenning-innovatiebudget-2023/">Bekijk alle projecten die subsidie kregen.</a></p>
<h3>Gebruikers betrokken</h3>
<p>Tijdens de jurybeenkomst op 7 juni konden de initiatiefnemers hun project pitchen voor een deskundige jury. Zij keken vooral naar uitvoerbaarheid, schaalbaarheid en onderscheidend vermogen. Maar ook zaken als (her)bruikbaarheid en de betrokkenheid van gebruikers wogen mee in het jury-oordeel. <a href="https://www.digitaleoverheid.nl/overzicht-van-alle-onderwerpen/innovatie/innovatiebudget/criteria/">Bekijk alle criteria</a>.</p>
<h3>Werkagenda</h3>
<p>Het ministerie van BZK vindt innovatieve dienstverlening van groot belang. In de <a href="https://www.digitaleoverheid.nl/kabinetsbeleid-digitalisering/werkagenda/">Werkagenda Waardengedreven Digitaliseren</a> speelt innovatie een belangrijke rol. Uiteraard zijn er <a href="https://www.digitaleoverheid.nl/overzicht-van-alle-onderwerpen/innovatie/innovatiebudget/criteria/">criteria</a> verbonden aan het innovatiebudget. Deze staan in lijn met de prioriteiten die zijn beschreven in de Werkagenda. Zo moeten indieners samenwerken met andere (overheids)organisaties om te komen tot integrale dienstverlening. De projecten moeten <a href="https://www.digitaleoverheid.nl/overzicht-van-alle-onderwerpen/standaardisatie-en-architectuur/open-source-software-kennisnetwerk/">open source</a> worden opgeleverd en de jury kijkt naar de mate waarin de gebruiker centraal staat.</p>
<h3>Meewerken aan een vraagstuk</h3>
<p>Herkent jouw organisatie zich in een vraagstuk in de lijst met winnende projecten en wil je bijdragen of samenwerken? Het team rond het Innovatiebudget brengt je graag in contact met de initiatiefnemers. Neem daarvoor contact op met <a href="mailto:innovatie@minbzk.nl">innovatie@minbzk.nl</a>.</p>
<p>Het bericht <a rel="nofollow" href="https://www.digitaleoverheid.nl/nieuws/winnaars-innovatiebudget-bekend/">Winnaars innovatiebudget bekend!</a> verscheen eerst op <a rel="nofollow" href="https://www.digitaleoverheid.nl">Digitale Overheid</a>.</p>


link: https://www.digitaleoverheid.nl/nieuws/nieuwe-kennisbank-digitale-toegankelijkheid/
encoded_syndication_url: aHR0cDovL3d3dy5kaWdpdGFsZW92ZXJoZWlkLm5sL2ZlZWQv
read: False
type: Rss
title: Nieuwe kennisbank digitale toegankelijkheid
categories: Nieuws|digitale toegankelijkheid|Kennisbank
description:
<p>In de nieuwe Kennisbank DigiToegankelijk staan antwoorden op veelgestelde vragen en praktische tips over digitale toegankelijkheid. Zoals wetgeving en toegankelijkheidsnormen. </p>
<p>Het bericht <a rel="nofollow" href="https://www.digitaleoverheid.nl/nieuws/nieuwe-kennisbank-digitale-toegankelijkheid/">Nieuwe kennisbank digitale toegankelijkheid</a> verscheen eerst op <a rel="nofollow" href="https://www.digitaleoverheid.nl">Digitale Overheid</a>.</p>

content:
<p><img decoding="async" loading="lazy" class="alignnone size-full wp-image-62301" src="https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/Kennisbank-DigiToegankelijk.png" alt="Printscreen van de Kennisbank. Je ziet hoe de kennisbank is opgebouwd en hoe de zoekfunctie werkt" width="915" height="786" srcset="https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/Kennisbank-DigiToegankelijk.png 915w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/Kennisbank-DigiToegankelijk-300x258.png 300w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/Kennisbank-DigiToegankelijk-768x660.png 768w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/Kennisbank-DigiToegankelijk-466x400.png 466w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/Kennisbank-DigiToegankelijk-291x250.png 291w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/Kennisbank-DigiToegankelijk-400x344.png 400w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/Kennisbank-DigiToegankelijk-88x76.png 88w" sizes="(max-width: 915px) 100vw, 915px" /></p>
<p><span class="intro">In de nieuwe <a href="https://kennisbank.digitoegankelijk.nl/">Kennisbank DigiToegankelijkheid</a> kunnen bezoekers informatie vinden om digitaal toegankelijk te worden én te blijven. Bijvoorbeeld over de toegankelijkheidsnorm (WCAG) en de wet voor digitale toegankelijkheid. Alle informatie is overzichtelijk ingedeeld per functieprofiel. </span></p>
<h2>Juiste informatie</h2>
<p>Els Aarts, projectleider Ondersteuning bij DigiToegankelijk onderstreept het belang van deze kennisbank: “Het internet staat vol met informatie over digitale toegankelijkheid. Maar hoe weet je of het actueel is en klopt? Ik hoorde laatst dat iemand een halve middag had gegoogeld naar het juiste antwoord. Dat is met deze kennisbank niet meer nodig.” Op dit moment is 50 procent van de geplande content op te vragen. De komende weken wordt de kennisbank aangevuld en deze blijft vervolgens groeien op basis van vragen uit de praktijk. Het team achter de kennisbank bestaat uit toegankelijkheidsexperts en redacteuren.</p>
<h2>Verbeteringen</h2>
<p>Overheidsorganisaties hebben nog veel werk te verzetten. Uit het <a href="https://dashboard.digitoegankelijk.nl/">Dashboard DigiToegankelijk</a> blijkt dat een groot deel van de overheidswebsites en -apps ontoegankelijk zijn. Voor meer dan 10.000 overheidswebsites en -apps is nog geen toegankelijkheidsverklaring opgesteld schat DigiToegankelijk. De kennisbank geeft overheidsmedewerkers en leveranciers van digitale producten handvatten om hiermee aan de slag te gaan.</p>
<h2>Over DigiToegankelijk</h2>
<p><a href="https://www.digitoegankelijk.nl/">DigiToegankelijk</a> werkt in opdracht van het ministerie van Binnenlandse Zaken en Koninkrijksrelaties. Het ondersteunt overheidsorganisaties bij het verbeteren van de digitale toegankelijkheid van hun websites en apps.</p>
<p>Het bericht <a rel="nofollow" href="https://www.digitaleoverheid.nl/nieuws/nieuwe-kennisbank-digitale-toegankelijkheid/">Nieuwe kennisbank digitale toegankelijkheid</a> verscheen eerst op <a rel="nofollow" href="https://www.digitaleoverheid.nl">Digitale Overheid</a>.</p>


encoded_syndication_url: aHR0cDovL3d3dy5kaWdpdGFsZW92ZXJoZWlkLm5sL2ZlZWQv
read: False
type: Rss
title: Inspirerende sessies ‘Securing Public Values Online’ terugzien
categories: Nieuws
link:
https://www.digitaleoverheid.nl/nieuws/inspirerende-sessies-securing-public-values-online-terugzien/

description:
<p>De conferentie ‘Securing Public Values Online’ gemist? Je kan de bijdragen van de inspirerende sprekers terugzien. Zoals de speech van staatssecretaris Van Huffelen.</p>
<p>Het bericht <a rel="nofollow" href="https://www.digitaleoverheid.nl/nieuws/inspirerende-sessies-securing-public-values-online-terugzien/">Inspirerende sessies ‘Securing Public Values Online’ terugzien</a> verscheen eerst op <a rel="nofollow" href="https://www.digitaleoverheid.nl">Digitale Overheid</a>.</p>

content:
<p><span class="intro"><img decoding="async" loading="lazy" class="alignnone size-full wp-image-62332" src="https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/van-huffelen-1-e1688055373378.jpg" alt="" width="755" height="618" srcset="https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/van-huffelen-1-e1688055373378.jpg 755w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/van-huffelen-1-e1688055373378-300x246.jpg 300w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/van-huffelen-1-e1688055373378-489x400.jpg 489w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/van-huffelen-1-e1688055373378-305x250.jpg 305w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/van-huffelen-1-e1688055373378-400x327.jpg 400w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/van-huffelen-1-e1688055373378-88x72.jpg 88w" sizes="(max-width: 755px) 100vw, 755px" />Heb je de conferentie ‘Securing Public Values Online’ gemist? Vanaf nu kun je de bijdragen van inspirerende, internationale sprekers terugkijken.</span></p>
<p>Tijdens de bijeenkomst afgelopen 15 mei in Brussel bespraken staatssecretaris Van Huffelen en deskundigen de rol van de overheid, toezichthouders en online platforms bij het beschermen van publieke waarden op grote platforms. Wat zijn ethische en juridische risico’s? En hoe zit het met de impact op mensenrechten? Experts betrokken bij bijvoorbeeld de European Data Protection Supervisor (EDPS), de European Group on Ethics in Science en de Europese Commissie deelden hun inzichten.</p>
<h2>Video&#8217;s</h2>
<p><a href="https://www.digitaleoverheid.nl/overzicht-van-alle-onderwerpen/nieuwe-technologieen-data-en-ethiek/publieke-waarden/videos-sprekers-conferentie-securing-public-values-online/">Bekijk op deze pagina alle video’s</a>  zoals de keynotes en paneldiscussies. Hieronder bekijk je de opening speech door staatssecretaris Alexandra van Huffelen:</p>



<div class="block-audio-video" id="block-movie-62279"><video id="movie-62279" width="500" height="412" poster="https://www.rovid.nl/bzk/doo/2023/bzk-doo-20230627-id2dwv3c4-still-middel.jpg" data-noplugintxt="Helaas kan deze video niet worden afgespeeld. Een mogelijk oplossing is de meest recente versie van uw browser te installeren."><source type="video/mp4" src="https://www.rovid.nl/bzk/doo/2023/bzk-doo-20230627-id2dwv3c4-web-hd.mp4"><track kind="subtitles" src="https://www.rovid.nl/bzk/doo/2023/bzk-doo-20230627-id2dwv3c4-ondertiteling.srt" label="Ondertitels" srclang="nl"></video>
<div class="downloads">

			<h2 id="videoplayer_download_label_video62279_post62219" class="collapsetoggle"><button aria-expanded="false">Downloads <span class="visuallyhidden"> bij Conferentie ‘Securing Public Values Online&#8217; &#8211; Opening speech Van Huffelen </span></button></h2>
			<div class="collapsible"  hidden>
			<ul aria-labelledby="videoplayer_download_label_video62279_post62219"><li class="download"><a href="https://www.rovid.nl/bzk/doo/2023/bzk-doo-20230627-id2dwv3c4-web-hd.mp4">MP4-bestand<span class="meta mp4">Video, 27 juni 2023, 00:20:04 mp4, </span></a></li><li class="download"><a href="https://www.rovid.nl/bzk/doo/2023/bzk-doo-20230627-id2dwv3c4-ondertiteling.srt">Ondertitelingsbestand<span class="meta srt">Video, 27 juni 2023, 00:20:04 srt </span></a></li>
			</ul>
			</div><!-- div class="collapsible"  hidden> --></div><!-- .downloads -->

				<h2 id="videoplayer_captions_video62279_post62219" class="collapsetoggle">
				<button aria-expanded="false">Uitgeschreven tekst <span class="visuallyhidden"> bij Conferentie ‘Securing Public Values Online&#8217; &#8211; Opening speech Van Huffelen </span></button>
				</h2>
				<div class="collapsible"  hidden>
					<div aria-labelledby="videoplayer_captions_video62279_post62219"><p>Location: Solvay Library, Brussels.</p>
<p>Logo Dutch government.</p>
<p>On-screen text: Ministry of the Interior and Kingdom Relations. Conference Securing Public Values Online. Opening speech Alexandra van Huffelen, Dutch Minister of Digitalisation. Organised by the Dutch Ministry of the Interior and Kingdom Relations ©2023.</p>
<p>Opening speech by Alexandra van Huffelen.</p>
</div>
				</div>
</div><!-- .block-audio-video -->

<p>&nbsp;</p>
<p>Het bericht <a rel="nofollow" href="https://www.digitaleoverheid.nl/nieuws/inspirerende-sessies-securing-public-values-online-terugzien/">Inspirerende sessies ‘Securing Public Values Online’ terugzien</a> verscheen eerst op <a rel="nofollow" href="https://www.digitaleoverheid.nl">Digitale Overheid</a>.</p>


link: https://www.digitaleoverheid.nl/nieuws/monitor-open-standaarden-2022-gepubliceerd/
encoded_syndication_url: aHR0cDovL3d3dy5kaWdpdGFsZW92ZXJoZWlkLm5sL2ZlZWQv
read: False
type: Rss
title: Monitor Open Standaarden 2022 gepubliceerd
categories: Nieuws|cybersecurity|GDI|open standaarden
description:
<p>Monitor Open Standaarden 2022: Open Standaarden te weinig toegepast bij aanbestedingen en jaarverslagen. Er is een positief beeld bij overheidsbrede voorzieningen. </p>
<p>Het bericht <a rel="nofollow" href="https://www.digitaleoverheid.nl/nieuws/monitor-open-standaarden-2022-gepubliceerd/">Monitor Open Standaarden 2022 gepubliceerd</a> verscheen eerst op <a rel="nofollow" href="https://www.digitaleoverheid.nl">Digitale Overheid</a>.</p>

content:
<p><img decoding="async" loading="lazy" class="alignnone wp-image-42916 size-full" src="https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2019/12/observe-monitoring-spy-search-job-security-1441879-pxhere.com_.jpg" alt="illustratie van een man met een stropdas en een verrekijker" width="800" height="474" srcset="https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2019/12/observe-monitoring-spy-search-job-security-1441879-pxhere.com_.jpg 800w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2019/12/observe-monitoring-spy-search-job-security-1441879-pxhere.com_-300x178.jpg 300w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2019/12/observe-monitoring-spy-search-job-security-1441879-pxhere.com_-768x455.jpg 768w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2019/12/observe-monitoring-spy-search-job-security-1441879-pxhere.com_-338x200.jpg 338w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2019/12/observe-monitoring-spy-search-job-security-1441879-pxhere.com_-675x400.jpg 675w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2019/12/observe-monitoring-spy-search-job-security-1441879-pxhere.com_-400x237.jpg 400w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2019/12/observe-monitoring-spy-search-job-security-1441879-pxhere.com_-100x59.jpg 100w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2019/12/observe-monitoring-spy-search-job-security-1441879-pxhere.com_-88x52.jpg 88w" sizes="(max-width: 800px) 100vw, 800px" /></p>
<p><span class="intro">Forum Standaardisatie heeft de Monitor Open Standaarden 2022 gepubliceerd. Uit de resultaten van het onderzoek blijkt dat overheden open standaarden nog steeds te weinig toepassen in openbare aanbestedingen. Ook staat er geen goede uitleg over de toepassing van de standaarden in de jaarverslagen. In overheidsbrede voorzieningen gaat het wél goed.</span></p>
<p>Ieder jaar doet Forum Standaardisatie onderzoek naar het ‘pas toe of leg uit’-beleid voor open standaarden en hoe overheden hiermee omgaan.  De onderzoekers legden de focus voor 2022 op:</p>
<ul>
<li>de vraag naar open standaarden in aanbestedingen;</li>
<li>de uitleg in jaarverslagen;</li>
<li>het gebruik in overheidsbrede voorzieningen (Generieke Digitale Infrastructuur);</li>
<li>wat verder bekend is per standaard, waaronder de halfjaarlijkse IV-meting van de standaarden.</li>
</ul>
<p>De <a href="https://forumstandaardisatie.nl/metingen/monitor">Monitor Open Standaarden 2022</a> is inmiddels gepubliceerd op de website van Forum Standaardisatie en gaat in de loop van 2023 naar de Tweede Kamer.</p>
<h2>Goed nieuws uit de Monitor</h2>
<p>Forum Standaardisatie ziet een goede toepassing van de open standaarden bij overheidsbrede voorzieningen (GDI voorzieningen). Er zijn 17 voorzieningen onderzocht in 2022. Als een standaard relevant is voor die voorziening, wordt deze in 81% van de gevallen ook daadwerkelijk toegepast. Voor de nog ontbrekende standaarden bestaan bovendien vaak plannen ze alsnog toe te passen.</p>
<h2>Verbetering mogelijk</h2>
<p>Het resultaat van de Monitor Open Standaarden 2022 laat zien dat bij openbare aanbestedingen nog steeds te weinig open standaarden worden gevraagd. Vaak betreft dit een veiligheidsstandaard. Hier is dus ruimte voor verbetering, vooral gezien de heersende veiligheidsrisico’s.</p>
<p>Ook bij jaarverslagen is een verbeterslag mogelijk. Uit het onderzoek blijkt dat organisaties zich vaak niet in het jaarverslag verantwoorden als zij standaarden niet toepassen, terwijl dat wel had gemoeten.</p>
<h2>Meer informatie</h2>
<p><a href="https://forumstandaardisatie.nl/nieuws/monitor-open-standaarden-2022-nu-online">Monitor Open Standaarden 2022 nu online</a> (nieuwsbericht Forum Standaardisatie)</p>
<p>Het bericht <a rel="nofollow" href="https://www.digitaleoverheid.nl/nieuws/monitor-open-standaarden-2022-gepubliceerd/">Monitor Open Standaarden 2022 gepubliceerd</a> verscheen eerst op <a rel="nofollow" href="https://www.digitaleoverheid.nl">Digitale Overheid</a>.</p>


link: https://www.digitaleoverheid.nl/nieuws/wetsvoorstel-invoering-bsn-caribisch-nederland/
encoded_syndication_url: aHR0cDovL3d3dy5kaWdpdGFsZW92ZXJoZWlkLm5sL2ZlZWQv
read: False
type: Rss
title: Wetsvoorstel invoering BSN Caribisch Nederland
categories: Nieuws|nieuwsbrief-12-2023
description:
<p>Er is een wetsvoorstel in consulatie gegaan voor invoering van het BSN en voorzieningen rondom de digitale overheid voor inwoners van Bonaire, Sint Eustatius en Saba.</p>
<p>Het bericht <a rel="nofollow" href="https://www.digitaleoverheid.nl/nieuws/wetsvoorstel-invoering-bsn-caribisch-nederland/">Wetsvoorstel invoering BSN Caribisch Nederland</a> verscheen eerst op <a rel="nofollow" href="https://www.digitaleoverheid.nl">Digitale Overheid</a>.</p>

content:
<p><img decoding="async" loading="lazy" class="alignnone wp-image-60466 size-full" src="https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/02/11_beleidsbrief_1000x600.png" alt="" width="1000" height="600" srcset="https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/02/11_beleidsbrief_1000x600.png 1000w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/02/11_beleidsbrief_1000x600-300x180.png 300w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/02/11_beleidsbrief_1000x600-768x461.png 768w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/02/11_beleidsbrief_1000x600-667x400.png 667w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/02/11_beleidsbrief_1000x600-400x240.png 400w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/02/11_beleidsbrief_1000x600-88x53.png 88w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/02/11_beleidsbrief_1000x600-900x540.png 900w" sizes="(max-width: 1000px) 100vw, 1000px" /></p>
<p><span class="intro">Met 5 wetswijzigingen krijgen de Openbare Lichamen van Bonaire, Sint Eustatius en Saba de mogelijkheid om het BSN voor inwoners te gaan registreren en verwerken. Daardoor is het wettelijk mogelijk om voorzieningen van de digitale overheid in te voeren. Zoals het inlogmiddel DigiD.</span></p>
<p>Met een DigiD kunnen inwoners bij overheidsorganisaties in Europees en Caribisch Nederland online inloggen en zaken regelen. Een belangrijke stap binnen de ambitie van het kabinet om de dienstverlening van de overheid te digitaliseren, en gelijkwaardig te maken aan die van Europees Nederland. Vandaag start de internetconsultatie van het wetsvoorstel. Tegelijkertijd wordt het voorstel aan de Autoriteit Persoonsgegevens en de Commissie Bescherming Persoonsgegevens BES voorgelegd. Het streven is dat de wetswijzigingen in 2025 ingaan.</p>
<h2>Online zaken regelen</h2>
<p>Het BSN geeft inwoners van Caribisch Nederland een uniek en persoonsgebonden nummer. Eenzelfde nummer dat overheden in Europees Nederland gebruiken om gegevens van personen online vast te stellen. Zo&#8217;n nummer is nodig om overheidsdienstverlening te kunnen digitaliseren. Zoals de invoering van een DigiD, waarmee mensen online aantonen wie ze zijn om zaken met de overheid te regelen. Het wetsvoorstel regelt ook het online doorgeven van een verhuizing binnen een Openbaar Lichaam. Je bent dan niet meer verplicht om aan een balie te verschijnen.</p>
<h2>Eén nummer en inlogmiddel voor de hele overheid</h2>
<p>Met het BSN hebben Caribische Nederlanders nog maar één nummer voor de hele overheid. Op termijn vervangt het BSN het ID- en CRIB-nummer. Deze worden nu nog gebruikt om personen te identificeren. Ook voor &#8216;MijnCN&#8217; (het online platform van overheidsdiensten in Caribisch Nederland) wordt de inlogfunctie vervangen door DigiD. Zo kunnen inwoners met één middel bij de digitale overheid inloggen.</p>
<h2>Meer weten?</h2>
<p><a href="https://www.nieuwsbzk.nl/2496705.aspx?t=Wetsvoorstel-invoering-Burgerservicenummer-en-voorzieningen-digitale-overheid">Bekijk het persbericht op de nieuwssite van BZK.</a></p>
<p>Het bericht <a rel="nofollow" href="https://www.digitaleoverheid.nl/nieuws/wetsvoorstel-invoering-bsn-caribisch-nederland/">Wetsvoorstel invoering BSN Caribisch Nederland</a> verscheen eerst op <a rel="nofollow" href="https://www.digitaleoverheid.nl">Digitale Overheid</a>.</p>


link: https://www.digitaleoverheid.nl/nieuws/62133/
encoded_syndication_url: aHR0cDovL3d3dy5kaWdpdGFsZW92ZXJoZWlkLm5sL2ZlZWQv
read: False
type: Rss
title: Waarstaatjegemeente.nl is vernieuwd
categories: Nieuws|nieuwsbrief-12-2023|VNG
description:
<p>De website richt zich op de domeinen sociaal, fysiek en lokaal bestuur en veiligheid. Je vindt er relevante dashboards, rapporten en andere (externe) datatoepassingen.</p>
<p>Het bericht <a rel="nofollow" href="https://www.digitaleoverheid.nl/nieuws/62133/">Waarstaatjegemeente.nl is vernieuwd</a> verscheen eerst op <a rel="nofollow" href="https://www.digitaleoverheid.nl">Digitale Overheid</a>.</p>

content:
<p><img decoding="async" loading="lazy" class="alignnone size-full wp-image-62134" src="https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/development-icon-g6139e12d7_1920.jpg" alt="Persoon met laptop met tandwielen. Hij is online aan het ontwikkelen." width="1920" height="1459" srcset="https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/development-icon-g6139e12d7_1920.jpg 1920w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/development-icon-g6139e12d7_1920-300x228.jpg 300w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/development-icon-g6139e12d7_1920-1024x778.jpg 1024w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/development-icon-g6139e12d7_1920-768x584.jpg 768w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/development-icon-g6139e12d7_1920-1536x1167.jpg 1536w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/development-icon-g6139e12d7_1920-526x400.jpg 526w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/development-icon-g6139e12d7_1920-1500x1140.jpg 1500w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/development-icon-g6139e12d7_1920-329x250.jpg 329w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/development-icon-g6139e12d7_1920-400x304.jpg 400w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/development-icon-g6139e12d7_1920-88x67.jpg 88w" sizes="(max-width: 1920px) 100vw, 1920px" /></p>
<p><span class="intro">De vernieuwde website <a href="https://www.waarstaatjegemeente.nl/">Waarstaatjegemeente.nl</a> richt zich op drie domeinen: sociaal, fysiek en lokaal bestuur en veiligheid. Van daaruit is het eenvoudig om naar relevante dashboards, rapporten en andere (externe) datatoepassingen te navigeren.</span></p>
<h2>Gebruiksmogelijkheden</h2>
<p>In de verschillende dashboards staan indicatoren die gebruikt kunnen worden om beleid en benchmarking te monitoren en te testen. Ook is het mogelijk om data van verschillende gemeenten naast elkaar te zetten. Daarnaast kunnen gebruikers zelf presentaties, grafieken, kaarten en tabellen maken. Voor eigen gebruik of om te delen met anderen. De gegevens komen uit verschillende bronnen en onderzoeken, zoals de politie, UWV, KvK en CBS.<br />
Het dataplatform is ontwikkeld door de Vereniging van Nederlandse Gemeenten (VNG) en is bedoeld voor gemeentebestuurders en ambtenaren. Maar ook geïnteresseerde burgers kunnen hier informatie verkrijgen.</p>
<h2>Webinar 26 juni</h2>
<p>Om inzicht te geven in de navigatie en alle gebruiksmogelijkheden van Waarstaatjegemeente.nl wordt op 26 juni om 14:00 een webinar georganiseerd. De deelname is gratis en inschrijven kan <a href="https://vng.webinargeek.com/wegwijs-in-waarstaatjegemeente-nl">via deze link</a>. Deelnemers ontvangen na afloop een terugkijklink.</p>
<p>&nbsp;</p>
<p>Het bericht <a rel="nofollow" href="https://www.digitaleoverheid.nl/nieuws/62133/">Waarstaatjegemeente.nl is vernieuwd</a> verscheen eerst op <a rel="nofollow" href="https://www.digitaleoverheid.nl">Digitale Overheid</a>.</p>


encoded_syndication_url: aHR0cDovL3d3dy5kaWdpdGFsZW92ZXJoZWlkLm5sL2ZlZWQv
read: False
type: Rss
title: Peppol is de keuze van het Rijk voor digitaal zakendoen
categories: Achtergrond|open standaarden
link:
https://www.digitaleoverheid.nl/achtergrondartikelen/rijksoverheid-kiest-peppol-voor-digitaal-zakendoen/

description:
<p>Met Peppol kunnen overheden en organisaties wereldwijd digitaal zakendoen. Justin de Jager vertelt waarom het Rijk deze standaard kiest bij de digitalisering van inkoop.</p>
<p>Het bericht <a rel="nofollow" href="https://www.digitaleoverheid.nl/achtergrondartikelen/rijksoverheid-kiest-peppol-voor-digitaal-zakendoen/">Peppol is de keuze van het Rijk voor digitaal zakendoen</a> verscheen eerst op <a rel="nofollow" href="https://www.digitaleoverheid.nl">Digitale Overheid</a>.</p>

content:
<p><img decoding="async" loading="lazy" class="alignnone wp-image-62109 size-large" src="https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/Justin-de-Jager-1024x782.png" alt="" width="1024" height="782" srcset="https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/Justin-de-Jager-1024x782.png 1024w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/Justin-de-Jager-300x229.png 300w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/Justin-de-Jager-768x587.png 768w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/Justin-de-Jager-1536x1173.png 1536w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/Justin-de-Jager-524x400.png 524w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/Justin-de-Jager-1500x1146.png 1500w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/Justin-de-Jager-327x250.png 327w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/Justin-de-Jager-400x306.png 400w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/Justin-de-Jager-88x67.png 88w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/Justin-de-Jager.png 1656w" sizes="(max-width: 1024px) 100vw, 1024px" /></p>
<p><span class="intro">Met Peppol kunnen overheden en organisaties wereldwijd digitaal zakendoen. Ook het Rijk kiest bij het digitaliseren van de eigen inkoop voor deze standaard. Justin de Jager is portfoliomanager digitalisering Rijksinkoop bij het ministerie van Binnenlandse Zaken en Koninkrijksrelaties (BZK). Hij vertelt over de toepassingsmogelijkheden en vele voordelen van Peppol.</span></p>
<p>Peppol is een internationale open standaard voor de digitale uitwisseling van inkoopgegevens, zoals facturen en orders. Je kunt het vergelijken met de standaarden waarmee je mobiele telefoon werkt. Het maakt niet uit welk merk of type telefoon je gebruikt, je kunt met iedereen bellen en appen. Peppol doet iets vergelijkbaars voor inkoopgegevens. Het zorgt ervoor dat informatie probleemloos wordt uitgewisseld tussen verschillende administratieve en financiële systemen.</p>
<h2>Inkoopgegevens automatisch uitwisselen</h2>
<p>&#8220;Peppol maakt de uitwisseling van inkoopgegevens sneller, nauwkeuriger en efficiënter&#8221;, vertelt Justin de Jager enthousiast. &#8220;Als facturen, orders en andere gegevens rechtstreeks als data tussen administratieve en financiële systemen worden uitgewisseld, scheelt dat handmatig werk en de onvermijdelijke fouten die hiermee gepaard gaan. Nu worden veel stappen in het inkoopproces nog gedaan met behulp van pdf&#8217;s, maar het is beter om die gegevens automatisch en foutloos uit te wisselen en direct in je financiële software te verwerken.”</p>
<blockquote><p><span class="intro">                                   &#8220;Peppol maakt de uitwisseling van inkoopgegevens sneller, nauwkeuriger en efficiënter&#8221;</span></p></blockquote>
<h2>Beter sturen en verantwoorden</h2>
<p>Behalve efficiency biedt een volledig digitaal inkoopproces ook andere voordelen. Door eenduidige digitalisering is het mogelijk de kwaliteit van de inkoopdata van het Rijk te verbeteren. Inkoopdigitalisering schept de mogelijkheid op elk moment precies te weten hoeveel is uitgegeven en waaraan. Het is de ambitie van het Rijk om op deze manier beter en sneller te kunnen verantwoorden waar geld naartoe gaat in het inkoopproces en sneller bij te kunnen sturen. Dat is belangrijk omdat inkoop voor het Rijk ook een beleidsinstrument is om maatschappelijke doelen te bereiken, zoals <a href="https://www.maatwerkvoormensen.nl/sroi-uitgelegd/dit-is-sroi">social return</a> of <a href="https://www.denkdoeduurzaam.nl/doelen">duurzaamheid</a>. Die doelen worden dankzij digitalisering beter meetbaar.</p>
<h2><strong>Medeoverheden en bedrijven stimuleren</strong></h2>
<p>&#8220;We willen met de invoering van de Peppol-standaard bij het Rijk medeoverheden en de markt inspireren&#8221;, aldus De Jager. &#8220;We laten gemeenten, provincies, waterschappen, administratiekantoren, accountants en bedrijven zien dat het de moeite waard is om over te stappen. Veel organisaties gebruiken Peppol al, maar het kan sneller. Het ministerie van BZK wil als coördinerend ministerie voor de Rijksinkoop het inkoopproces van het Rijk met Peppol eenvoudig maken. Daarbij zijn de dienstverlening aan leveranciers en de gebruiksvriendelijkheid speerpunten. Daarin volgen we nadrukkelijk de <a href="https://www.digitaleoverheid.nl/kabinetsbeleid-digitalisering/werkagenda/waardengedreven-en-open-digitale-overheid/">Werkagenda waardengedreven digitaliseren</a> van het Rijk. We breiden de toepassingsmogelijkheden van Peppol voor de Rijksoverheid en haar leveranciers voortdurend uit. Voor Rijksdiensten hebben we al uitgaande e-facturen en <a href="https://www.logius.nl/domeinen/gegevensuitwisseling/e-factureren/e-orders-via-peppol-zijn-nieuwe-stap-in-digitalisering-rijksinkoop">e-orders via Peppol</a> mogelijk gemaakt. Op dit moment werken we aan e-timecards. Daarmee kunnen de uren van tijdelijk personeel veel efficiënter worden goedgekeurd en gefactureerd.&#8221;</p>
<h2><strong>Peppol bereikbaarder maken</strong></h2>
<p>De Jager wil laten zien dat Peppol uitstekend gereedschap is, dat vaak relatief eenvoudig is in te passen in inkoopprocessen. Peppol is gebaseerd op open standaarden en heeft voor de gehele overheid al de <a href="https://forumstandaardisatie.nl/open-standaarden/peppol-bis">status &#8216;aanbevolen&#8217;</a> gekregen van Forum Standaardisatie. &#8216;Aanbevolen&#8217; betekent dat Peppol een veelbelovende techniek is, die voor alle overheden interessant is om uit te vragen bij het aanbesteden van software voor inkoop en financiële administratie. De Nederlandse Peppolautoriteit (NPa) zorgt dat het gebruik van Peppol veilig en betrouwbaar is. Ook spreekt de Nederlandse Peppolautoriteit (NPa) met de makers van <a href="https://peppolautoriteit.nl/cms/view/d1689276-f130-4231-a423-30bf199a1aee/stap-over-op-peppol-als-softwareleverancier">administratieve en financiële software</a> die Peppol nog niet standaard hebben ingebouwd in alle software.</p>
<h2><strong>Meer informatie</strong></h2>
<p>Ben je geïnteresseerd in de voordelen van digitaal inkopen en zakendoen via Peppol? <a href="https://peppolautoriteit.nl/cms/view/11833f70-8653-41f6-804c-7265982fe174/contact">Stel je vragen over het gebruik van Peppol aan de NPa</a>. Stuur je als leverancier e-facturen aan de Rijksoverheid of ga je dit doen? Met deze vragen kun je terecht bij de <a href="https://www.helpdesk-efactureren.nl/contact">Helpdesk e-factureren</a>.</p>
<p>Het bericht <a rel="nofollow" href="https://www.digitaleoverheid.nl/achtergrondartikelen/rijksoverheid-kiest-peppol-voor-digitaal-zakendoen/">Peppol is de keuze van het Rijk voor digitaal zakendoen</a> verscheen eerst op <a rel="nofollow" href="https://www.digitaleoverheid.nl">Digitale Overheid</a>.</p>


link: https://www.digitaleoverheid.nl/nieuws/sluit-aan-op-de-woo-index-voor-actieve-openbaarmaking/
encoded_syndication_url: aHR0cDovL3d3dy5kaWdpdGFsZW92ZXJoZWlkLm5sL2ZlZWQv
read: False
type: Rss
title: Sluit aan op de Woo-index voor actieve openbaarmaking
categories: Nieuws|actieve openbaarheid|nieuwsbrief-12-2023|open overheid|wet open overheid
description:
<p>Publiceert jouw overheidsorganisatie al verplichte informatie? Sluit dan vanaf 19 juni aan op de Woo-index. Hiermee is deze informatie centraal vindbaar en doorzoekbaar.</p>
<p>Het bericht <a rel="nofollow" href="https://www.digitaleoverheid.nl/nieuws/sluit-aan-op-de-woo-index-voor-actieve-openbaarmaking/">Sluit aan op de Woo-index voor actieve openbaarmaking</a> verscheen eerst op <a rel="nofollow" href="https://www.digitaleoverheid.nl">Digitale Overheid</a>.</p>

content:
<p><img decoding="async" loading="lazy" class="alignnone wp-image-49636 size-full" src="https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2021/02/Open-overheid-e1623924812209.png" alt="Vrouw die het rolgordijn opent" width="900" height="691" /></p>
<p><span class="intro">Vanaf 19 juni kunnen centrale en decentrale overheidsorganisaties aansluiten op de Woo-index. Hiermee kunnen zij verwijzen naar door henzelf gepubliceerde documenten. Zo kunnen zij voldoen aan een van de doelstellingen van de Wet open overheid: één centrale plek waar informatie van alle bestuursorganen vindbaar en doorzoekbaar is.</span></p>
<p>Op 1 mei 2022 is de Wet open overheid in werking getreden. Deze verplicht overheden om zoveel mogelijk informatie openbaar te maken. Deze openbaarmaking gaat stap voor stap.</p>
<h2>Aansluiten op de Woo-index</h2>
<p>Overheden die al informatie openbaar maken op hun website kunnen vanaf 19 juni aansluiten op de Woo-index. Hier kunnen burgers, onderzoekers, journalisten, wetenschappers en overige geïnteresseerden alle informatie op één plek vinden. Zo hoeven zij niet langer op zoek naar de informatie die zij nodig hebben op de vele websites in overheidsland.</p>
<p>De Woo-index is geen centrale opslagplaats, maar verwijst naar informatie die overheden al hebben gepubliceerd op hun websites. Een bestuursorgaan kan de URL&#8217;s van deze informatie invoeren in het Register van Overheidsorganisaties (ROO). De URL&#8217;s van documenten die al centraal worden gepubliceerd in bijvoorbeeld Staatscourant, Staatsblad, provinciaal blad, gemeenteblad en waterschapsblad vult KOOP (Kennis- en Exploitatiecentrum Officiële Overheidspublicaties; ontwikkelaar van de Woo-index) al in en hoeven alleen te worden gecontroleerd.</p>
<p>Later dit jaar introduceert KOOP een zoekfunctie waarmee het mogelijk is binnen de documenten te zoeken.</p>
<h2>Wat kan ik vast doen?</h2>
<ul>
<li>Maak een start met de actieve openbaarmaking van je informatie.</li>
<li>Sluit vanaf 19 juni aan op de Woo-index.</li>
<li><a href="https://kia.pleio.nl/cms/view/43df44af-d6af-4fd0-8306-551cb98613a2/informatie-categorien-woo">Denk mee</a> met de verdere uitwerking van de verschillende informatiecategorieën.</li>
</ul>
<h2>Meer weten?</h2>
<p>Wil je meer weten over de ontwikkelingen rond de actieve openbaarmaking? Kijk dan op <a href="https://www.open-overheid.nl/">open-overheid.nl</a> (informatie over beleid en aanpak) of <a href="https://www.koopoverheid.nl/">koopoverheid.nl</a> (informatie over de technische aspecten).</p>
<p>Het bericht <a rel="nofollow" href="https://www.digitaleoverheid.nl/nieuws/sluit-aan-op-de-woo-index-voor-actieve-openbaarmaking/">Sluit aan op de Woo-index voor actieve openbaarmaking</a> verscheen eerst op <a rel="nofollow" href="https://www.digitaleoverheid.nl">Digitale Overheid</a>.</p>


link: https://www.digitaleoverheid.nl/nieuws/internationale-cyberstrategie-gepresenteerd/
encoded_syndication_url: aHR0cDovL3d3dy5kaWdpdGFsZW92ZXJoZWlkLm5sL2ZlZWQv
read: False
type: Rss
title: Internationale Cyberstrategie gepresenteerd
categories: Nieuws|cyberveiligheid|Internationale cyberstrategie|nieuwsbrief-12-2023
description:
<p>Het kabinet presenteert een nieuwe internationale cyberstrategie voor de periode 2023-2028. De 3 kerndoelen binnen de strategie moeten digitale dreiging tegengaan.</p>
<p>Het bericht <a rel="nofollow" href="https://www.digitaleoverheid.nl/nieuws/internationale-cyberstrategie-gepresenteerd/">Internationale Cyberstrategie gepresenteerd</a> verscheen eerst op <a rel="nofollow" href="https://www.digitaleoverheid.nl">Digitale Overheid</a>.</p>

content:
<p><span class="intro"><img decoding="async" loading="lazy" class="alignnone size-full wp-image-62080" src="https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/EU-wetgeving.jpg" alt="" width="767" height="767" srcset="https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/EU-wetgeving.jpg 767w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/EU-wetgeving-300x300.jpg 300w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/EU-wetgeving-150x150.jpg 150w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/EU-wetgeving-400x400.jpg 400w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/EU-wetgeving-250x250.jpg 250w, https://www.digitaleoverheid.nl/wp-content/uploads/sites/8/2023/06/EU-wetgeving-88x88.jpg 88w" sizes="(max-width: 767px) 100vw, 767px" />Nederland moet weerbaar blijven in de digitale wereld. Om voor een open, vrij en veilig digitaal domein te zorgen is de nieuwe Internationale cyberstrategie voor 2023-2028 gepresenteerd. Hierin staan 3 doelen waar Nederland  zich de komende jaren sterk voor gaat maken.</span></p>
<h2>3 doelen</h2>
<p>Nederland wil duidelijke afspraken maken over gedragsregels, het beheer van het cyberdomein en de ontwikkeling van standaarden voor nieuwe technologieën. Ook moeten digitale dreigingen zoals cybercriminaliteit en desinformatie tegen worden gegaan. Hiervoor heeft Nederland voor de periode 2023-2028 3 doelen gesteld:</p>
<ul>
<li>Tegengaan van cyberdreigingen van staten en criminelen. Nederland zal de beschikbare instrumenten proactiever, meer geïntegreerd en strategischer inzetten. Waar mogelijk met EU-partners en NAVO-bondgenoten.</li>
<li>Versterken van democratische en mensenrechtelijke principes online. Een open, vrij en veilig internet is een cruciaal uitgangspunt bij het bevorderen van online mensenrechten. Hiervoor bekijkt Nederland samen met andere landen, hoe ze internationaal erkende principes in de digitale ruimte kan toepassen om wereldwijd de cyberveiligheid te vergroten.</li>
<li>Behoud van een wereldwijd verbonden, open, vrij en veilig internet. Nederland beschermt de publieke kern &#8211; oftewel de technische laag &#8211; van het internet, onder andere om fragmentatie tegen te gaan. Daarbij zal Nederland de betrokkenheid van opkomende landen bij vraagstukken over het beheer van het internet bevorderen en expertise delen om de cybercapaciteiten van andere landen verder te versterken.</li>
</ul>
<p><a href="https://www.rijksoverheid.nl/documenten/publicaties/2023/06/09/internationale-cyberstrategie-2023-2028">Lees de volledig Internationale Cyberstrategie 2023 – 2028</a></p>
<h2>Samenwerking</h2>
<p>De Internationale Cyberstrategie is opgesteld door samenwerking tussen de ministeries van Buitenlandse Zaken, Justitie en Veiligheid, Economische Zaken en Klimaat, Defensie en Binnenlandse Zaken en Koninkrijksrelaties en tussen verschillende overheidsorganisaties (AIVD, MIVD, NCSC, NCTV, OM en de Politie).</p>
<p>Het bericht <a rel="nofollow" href="https://www.digitaleoverheid.nl/nieuws/internationale-cyberstrategie-gepresenteerd/">Internationale Cyberstrategie gepresenteerd</a> verscheen eerst op <a rel="nofollow" href="https://www.digitaleoverheid.nl">Digitale Overheid</a>.</p>


link: https://www.digitaleoverheid.nl/evenementen/conferentie-waardengedreven-dialogen/
encoded_syndication_url: aHR0cDovL3d3dy5kaWdpdGFsZW92ZXJoZWlkLm5sL2FnZW5kYS9mZWVkLw==
read: False
type: Rss
title: Conferentie Waardengedreven Dialogen
description:
3 juli 2023 - 13:30 - 18:00 <br>De conferentie staat in het teken van de Waardengedreven Dialogen omtrent sociale media monitoring in het openbaar bestuur. Er zijn drie dialogen gehouden aan de hand van de Aanpak Begeleidingsethiek (ECP) bij de gemeentes Breda en Eindhoven en bij de veiligheidsregio Noord-Oost Gelderland.

Tijdens deze conferentie worden de resultaten van de dialogen gepresenteerd en gaan we in breder verband de dialoog aan hierover.
<h2>Het programma</h2>
13.30 uur - Inloop
14.00 uur - Opening en welkom
14.05 uur - Introductie: Waardengedreven digitaliseren
14.40 uur - De casussen: Inzet sociale media monitoring in het openbaar bestuur 15.10 uur - Koffiepauze
15.25 uur - Resultaten: Van effecten en waarden naar handelingsopties
16.00 uur - Panelgesprek
16.45 uur - Afsluiting
17.00 uur - Netwerkborrel
18.00 uur - Einde bijeenkomst

Aanmelden en meer informatie vinden kan <a href="https://ecp.nl/agenda/conferentie-waardengedreven-dialogen-sociale-media-monitoring/">via de website van het ECP</a>.

De dialogen zijn onderdeel van de Werkagenda Waardengedreven Digitaliseren van het Ministerie van Binnenlandse Zaken en Koninkrijksrelaties.

&#160;<br>Social Impact Factory <br>Vredenburg 40 <br>Utrecht


link: https://www.digitaleoverheid.nl/evenementen/masterclass-it/
encoded_syndication_url: aHR0cDovL3d3dy5kaWdpdGFsZW92ZXJoZWlkLm5sL2FnZW5kYS9mZWVkLw==
read: False
type: Rss
title: Masterclass IT
description:
4 juli 2023 - Hele dag <br>Voor wie meer over de wereld van IT’ers wil weten kan op 4 en 5 juli 2023 een masterclass in Den Haag volgen. Deelnemers gaan de slag met alle terminologie, het jargon en de rollen van een IT-afdeling.

Deze training bestaat uit zowel theorie en demo’s als praktijkopdrachten en discussies met medecursisten. De terminologie van IT wordt uitgelegd door verschillende cases te behandelen onder begeleiding van een ervaren docent. Na afloop van deze training hebben cursisten een duidelijk beeld van wat zich afspeelt op een IT-afdeling en kunnen meepraten over actuele technologische vraagstukken.
<h2>Aanmelden</h2>
De training wordt gratis aangeboden door de RijksAcademie voor Digitalisering en Informatisering Overheid (<a href="https://www.it-academieoverheid.nl/">RADIO</a>), in samenwerking met <a href="https://www.computrain.nl/">Computrain</a>. Na afloop van de training ontvangen deelnemers het deelnamecertificaat 'Introductie in IT Rollen en Terminologie'. Ga naar deze website <a href="https://www.it-academieoverheid.nl/actueel/agenda/2023/07/masterclassit/masterclassit">voor meer informatie of voor aanmeldingen</a>.<br>ZZIIN Centraal Station <br>Kon. Julianaplein 10 <br>Den Haag


link: https://www.digitaleoverheid.nl/evenementen/congres-metadata-matters/
encoded_syndication_url: aHR0cDovL3d3dy5kaWdpdGFsZW92ZXJoZWlkLm5sL2FnZW5kYS9mZWVkLw==
read: False
type: Rss
title: Congres Metadata Matters
description:
6 september 2023 - 09:30 - 17:00 <br>Het volledig Engelstalige congres  "Metadata Matters: what role does Linked (Meta)Data play in the Geospatial World?" wordt gehouden in Mediamuseum Beeld en Geluid, Hilversum.

Het wordt georganiseerd door EuroSDR (European Spatial Data Research), GeoE3 (Geospatially Enabled Ecosystem for Europe) en PLDN (Platform Linked Data Nederland).

Het evenement dient als een gelegenheid voor de organisatoren om zowel de resultaten van lopende projecten te delen, nieuwe initiatieven te inspireren en leden van alle communities actief te betrekken bij het werken aan innovatieve oplossingen om de linkability en vindbaarheid van datasets in Europa te verbeteren.
<h2>Programma</h2>
Het programma omvat drie sporen en een plenaire sessie ter afsluiting van de dag.
<ul>
 	<li>Een algemeen spoor: hier worden de resultaten en use cases gepresenteerd uit het twee jaar durende onderzoeksproject van GeoE3. Daarnaast is er een sessie over lopende innovatieprojecten en ontwikkelingen in de geospatiale wereld.</li>
 	<li>Het technische spoor biedt EuroSDR de gelegenheid om de lopende activiteiten rond de ontwikkeling van de Metadata Knowledge Graph te bespreken. Daarnaast zijn er presentaties van nationale kadasters en nationale cartografische instanties over hun activiteiten op het gebied van gekoppelde (meta)gegevens.</li>
 	<li>Het derde spoor biedt de deelnemers de gelegenheid een workshop over gekoppelde gegevens te volgen.</li>
</ul>
<h2>Meer informatie en aanmelden</h2>
Meer informatie over dit evenement, het volledige programma en een link om je aan te melden, kun je vinden op de <a href="https://www.pldn.nl/wiki/Metadata_Matters,_What_Role_Does_Linked_(Meta)Data_Play_in_the_Geospatial_World%3F_%E2%80%93_6_September_2023,_Sound_and_Vision,_Hilversum,_the_Netherlands">website van Platform Linked Data Nederland</a>.<br>Beeld en Geluid <br>Media Parkboulevard 1  <br>Hilversum


link: https://www.digitaleoverheid.nl/evenementen/ibestuur-congres-2/
encoded_syndication_url: aHR0cDovL3d3dy5kaWdpdGFsZW92ZXJoZWlkLm5sL2FnZW5kYS9mZWVkLw==
read: False
type: Rss
title: IBestuur congres
description:
13 september 2023 - Hele dag <br>De voorbereidingen voor het iBestuur Congres 2023 zijn weer van start gegaan. De komende maanden maakt IBestuur het programma bekend. Wil je op  de hoogte blijven? Check dan <a href="https://ibestuur.nl/ibestuurcongres/ibestuur-congres-2023-13-september-in-den-haag?tid=TIDP3424239X1590B05B3BA845B58860D98284A2865DYI5&#38;utm_campaign=IB_NB_Wekelijks&#38;utm_medium=email&#38;utm_source=ibestuur">de website</a> of schrijf je in voor de <a href="https://ibestuur.nl/nieuwsbrief">nieuwsbrief.</a>
<h3>iBestuur Congres 2022 terugkijken?</h3>
Alle keynotes, debatten en presentaties van het congres van afgelopen september zijn nog te bekijken via <a href="https://www.ibestuurcongres.nl/2022/replay%3Cbr%20/%3E" target="_blank" rel="noopener">www.ibestuurcongres.nl</a><br>Fokkerterminal <br>Binckhorstlaan 249 <br>Den Haag


link: https://www.digitaleoverheid.nl/evenementen/samen-digitaal-veilig-gemeenten-aan-de-slag/
encoded_syndication_url: aHR0cDovL3d3dy5kaWdpdGFsZW92ZXJoZWlkLm5sL2FnZW5kYS9mZWVkLw==
read: False
type: Rss
title: Samen digitaal veilig: Gemeenten aan de slag!
description:
28 september 2023 - 09:30 - 16:00 <br><p data-pm-slice="1 1 []">Het programma Digitale Veiligheid van de VNG organiseert <a class="mark-link mark-link mark-link Hyperlink SCXW251745502 BCX0" href="https://samendigitaalveilig.vngconnect.nl/" target="_blank" rel="noopener">het congres Samen digitaal veilig: Gemeenten aan de slag!</a> Deze dag vindt plaats in Amersfoort en is bedoeld voor lokale bestuurders, ambtenaren, raadsleden en landelijke partners van de VNG. <a href="https://app.azavista.com/w/event/645cbd43acbb03f64377c3f4/?page_id=645cbd484b3e540883a0defa">Meld je direct aan.</a></p>

<h3 data-pm-slice="1 1 []">Programma</h3>
<p data-pm-slice="1 1 []">Dagvoorzitter is burgemeester Iris Meerts. Tijdens de plenaire opening is er een bijzondere sessie met journalist en programmamaker Sinan Can. Daarnaast geeft Bas Dunnebier, Head of Unit Resilience bij de AIVD, zijn visie op de toekomst. Uiteraard is er ruimte voor interactieve workshops en ontmoetingen met andere gemeenten. Al met al gaan deelnemers vol inspiratie en mét de juiste middelen naar huis om digitale veiligheid in hun eigen gemeente aan te pakken.</p><br> <br> <br>


link: https://www.digitaleoverheid.nl/evenementen/de-week-van-de-toegankelijkheid/
encoded_syndication_url: aHR0cDovL3d3dy5kaWdpdGFsZW92ZXJoZWlkLm5sL2FnZW5kYS9mZWVkLw==
read: False
type: Rss
title: De Week van de Toegankelijkheid
description:
2 oktober 2023 - Hele dag <br>De Week van de Toegankelijkheid is van 2 t/m 7 oktober 2023 en vraagt aandacht voor een toegankelijke samenleving voor mensen met een beperking.

Het is een initiatief van Ieder(in), landelijk netwerk van mensen met een beperking of chronische ziekte. Tijdens de Week van Toegankelijkheid wordt duidelijk gemaakt hoe belangrijk het is dat mensen met een beperking mee kunnen doen. Met een toegankelijke website bereik je meer mensen en in een toegankelijke school groeien kinderen met en zonder beperking met elkaar op. En zo zijn er meer voorbeelden te geven waarom toegankelijkheid loont.
<h2>Doe mee</h2>
Wil je als gemeente of organisatie meedoen? Kijk voor meer informatie, activiteiten, tips en de mogelijkheid om aan te melden op <a href="https://weekvandetoegankelijkheid.nl/doe-mee/">weekvandetoegankelijkheid.nl</a>.

&#160;<br> <br> <br>


link: https://www.digitaleoverheid.nl/evenementen/one-conference/
encoded_syndication_url: aHR0cDovL3d3dy5kaWdpdGFsZW92ZXJoZWlkLm5sL2FnZW5kYS9mZWVkLw==
read: False
type: Rss
title: ONE Conference
description:
3 oktober 2023 - 4 oktober 2023 - Hele dag <br>Cybersecurity is belangrijker dan ooit. De ONE Conference stimuleert internationale samenwerking tussen cybersecurity-professionals uit het bedrijfsleven, de wetenschap en overheidsorganisaties. De ONE Conference is een exclusief jaarlijks evenement.

In 2023 vindt het evenement plaats op 3 &#38; 4 oktober. Beide dagen is er een plenair programma en keuze uit verschillende breakout-sessies.

Een breed scala aan onderwerpen staat centraal: van zeer technische onderwerpen zoals malwaredetectie, incidentrespons en rechtshandhavingszaken tot minder technische onderwerpen, zoals partnerschappen tussen het publieke en private domein, governance en recent cybersecurity-onderzoek.

Voor meer informatie en aanmelden <a href="https://one-conference.nl/">bezoek je de website.</a><br>World Forum The Hague <br>Churchillplein 10  <br>Den Haag


link: https://www.digitaleoverheid.nl/evenementen/conferentie-gebruiker-centraal-uit-het-doolhof/
encoded_syndication_url: aHR0cDovL3d3dy5kaWdpdGFsZW92ZXJoZWlkLm5sL2FnZW5kYS9mZWVkLw==
read: False
type: Rss
title: Conferentie Gebruiker Centraal: Uit het doolhof
description:
6 oktober 2023 - Hele dag <br>De 2023 conferentie van Gebruiker Centraal is voor iedereen die werkt aan de (digitale) dienstverlening van de overheid. Het thema is dit jaar: Uit het doolhof.  Niet nieuwe technologie, maar menselijke waarden moeten de basis zijn voor dienstverlening. Anders raken we steeds meer verdwaald in het (digitale) doolhof van de overheid. Er rest dus maar 1 vraag: hoe komen we hieruit?
<h2>Het programma</h2>
Werk jij graag mee aan betere, inclusieve dienstverlening van de overheid? Maak jij je sterk voor diensten en communicatie die duidelijk, toegankelijk en bruikbaar zijn? Laat je dan inspireren door vakcollega’s en experts tijdens de jaarlijkse conferentie van Gebruiker Centraal op vrijdag 6 oktober 2023. Op <a href="https://www.gebruikercentraal.nl/conferentie-gebruiker-centraal-2023-uit-het-doolhof/">de website van Gebruiker Centraal</a> lees je het complete programma en op deze site kun je je gratis inschrijven.<br>De Arendshoeve <br>Aalsmeerderdijk 438 <br>Aalsmeerderbrug


link: https://www.digitaleoverheid.nl/evenementen/netwerkcongres-leren-in-uitvoering/
encoded_syndication_url: aHR0cDovL3d3dy5kaWdpdGFsZW92ZXJoZWlkLm5sL2FnZW5kYS9mZWVkLw==
read: False
type: Rss
title: Netwerkcongres Leren in uitvoering
description:
9 oktober 2023 - 10:00 - 17:00 <br>Op maandag 9 oktober organiseert het Netwerk van Publieke Dienstverleners het jaarlijkse netwerkcongres Leren in Uitvoering 2023 in Burgers’ Zoo Arnhem.

Het congres staat in het teken van anders denken, anders leren, anders doen. Hoe kunnen we de dienstverlening verbeteren en het vertrouwen van de burger weer terugwinnen? En tegelijkertijd de nodige uitdagingen het hoofd bieden zoals arbeidsmarktkrapte, complexe wetgeving, gedateerd ICT-landschap, gegevensuitwisselingen en verantwoord ondernemen?

Voor meer informatie en de registratie <a href="https://liu2023.belastingdienst-events.nl/">kijk op deze website</a>.<br>Burgers&#039; Zoo <br>Antoon van Hooffplein 1 <br>Arnhem


link: https://www.digitaleoverheid.nl/evenementen/event-algoritmeregister/
encoded_syndication_url: aHR0cDovL3d3dy5kaWdpdGFsZW92ZXJoZWlkLm5sL2FnZW5kYS9mZWVkLw==
read: False
type: Rss
title: Event Algoritmeregister
description:
9 oktober 2023 - 13:00 - 17:00 <br><p data-pm-slice="1 1 []">Wil jij aan de slag met algoritmes binnen je eigen organisatie? Kom dan naar het event van het Algoritmeregister.</p>
<p data-pm-slice="1 1 []">Leer wat je moet weten om te publiceren, wat je nu al kunt doen en hoe het register werkt. Zet 9 oktober alvast in je agenda. Meer informatie volgt binnenkort. Je kunt wel alvast laten weten dat je er bij wilt zijn <a href="https://algoritmes.pleio.nl/events/view/b5285e93-c337-41b5-a504-ee7c11dec188/event-algoritmeregister">via de Pleio Community.</a></p>
Wil je altijd op de hoogte zijn van het laatste nieuws? <a class="mark-link mark-link" href="https://algoritmeregister.email-provider.eu/memberforms/subscribe/standalone/form/?a=1pjwwoyxrs&#38;l=vdfr1sbovb">Meld je dan aan voor de nieuwsbrief. </a><br>Observant <br>Stadhuisplein 7 <br>Amersfoort


link: https://www.digitaleoverheid.nl/evenementen/overheidsbrede-cyberoefening/
encoded_syndication_url: aHR0cDovL3d3dy5kaWdpdGFsZW92ZXJoZWlkLm5sL2FnZW5kYS9mZWVkLw==
read: False
type: Rss
title: Overheidsbrede Cyberoefening
description:
30 oktober 2023 - Hele dag <br>Digitale systemen bieden onze samenleving veel kansen, maar ze brengen ook risico’s met zich mee. De veiligheid in de digitale wereld is nog niet op hetzelfde niveau als in de fysieke wereld.

Oefenen met cyberincidenten is een goede manier om uw organisatie voor te bereiden op een digitale crisis. Daarom organiseert het ministerie van BZK ook dit jaar weer het Overheidsbreed Cyberprogramma. U kunt in oktober en november verschillende cyberwebinars volgen. Op maandag 30 oktober vindt de Overheidsbrede Cyberoefening plaats en in december een interessante masterclass. Vorig jaar oefenden meer dan 100 organisaties simultaan mee. En ook dit jaar bieden we u deze mogelijkheid.

Alle informatie is te vinden <a href="http://www.weerbaredigitaleoverheid.nl">via de website.</a> Wilt u alle activiteiten op de voet volgen? Dat kan, <a href="https://www.weerbaredigitaleoverheid.nl/registreren/">registreer</a> uw gegevens op onze website of houd de <a href="https://www.linkedin.com/company/overheidsbreed-cyberprogramma/?viewAsMember=true">LinkedIn pagina </a>in de gaten.<br> <br> <br>


link: https://www.digitaleoverheid.nl/evenementen/interbestuurlijke-datastrategiedag/
encoded_syndication_url: aHR0cDovL3d3dy5kaWdpdGFsZW92ZXJoZWlkLm5sL2FnZW5kYS9mZWVkLw==
read: False
type: Rss
title: Interbestuurlijke datastrategiedag
description:
23 november 2023 - Hele dag <br><p data-pm-slice="1 1 []">Vanuit de Interbestuurlijke Datastrategie (IBDS) wordt jaarlijks een evenement georganiseerd samen met overheidspartners. Tijdens het evenement vinden verschillende interessante sessies en workshops plaats. Reserveert u de datum alvast in uw agenda? Meer informatie volgt binnenkort.</p>
<p data-pm-slice="1 1 []">Benieuwd naar de vorige editie? Bekijk de<a href="https://realisatieibds.pleio.nl/cms/view/f3f46793-63a3-4a48-a358-e89d13e1e018/stelseldag-hoe-komen-we-tot-een-federatief-datastelsel"> aftermovie,</a> download de <a href="https://realisatieibds.pleio.nl/cms/view/f3f46793-63a3-4a48-a358-e89d13e1e018/stelseldag-hoe-komen-we-tot-een-federatief-datastelsel">presentaties of lees de interviews</a>. Heb je vragen over de dag of het programma? Stuur een bericht aan <a href="mailto:TeamIBDS@ICTU.nl">TeamIBDS@ICTU.nl</a></p><br>Prodentfabriek <br>Oude Fabriekstraat 20 <br>Amersfoort


link: https://www.digitaleoverheid.nl/evenementen/dag-van-digitale-inclusie-2/
encoded_syndication_url: aHR0cDovL3d3dy5kaWdpdGFsZW92ZXJoZWlkLm5sL2FnZW5kYS9mZWVkLw==
read: False
type: Rss
title: Dag van Digitale Inclusie
description:
27 november 2023 - 10:00 - 17:00 <br>Alvast voor in de agenda’s. Op 27 november 2023 organiseert de Alliantie Digitaal Samenleven de tweede editie van de Dag van Digitale Inclusie.  Meer informatie volgt snel <a href="https://digitaalsamenleven.nl/agenda/dag-van-digitale-inclusie-2/">via deze website</a>.<br> <br> <br>


link: https://www.digitaleoverheid.nl/evenementen/masterclass-het-menselijke-aspect-van-cybersecurity/
encoded_syndication_url: aHR0cDovL3d3dy5kaWdpdGFsZW92ZXJoZWlkLm5sL2FnZW5kYS9mZWVkLw==
read: False
type: Rss
title: Masterclass: Het menselijke aspect van cybersecurity
description:
4 december 2023 - Hele dag <br>Durven collega's het te melden als hun laptop uit hun auto is gestolen? En weten ze bij wie ze terecht kunnen als ze per ongeluk op een phishinglink hebben geklikt?

Mensen vormen een belangrijke verdedigingslinie tegen cyberdreigingen. Uit onderzoek blijkt dat 95% van de cyberaanvallen voorkomen had kunnen worden door mensen. Maar hoe creëer je een cultuur waarin informatieveilig gedrag de norm is?

In deze Masterclass gaat Northwave Security in op het menselijke aspect van cybersecurity. Hoe creëer je bewustzijn voor cyberdreigingen? En hoe neem je belemmeringen weg die informatieveilig gedrag in de weg staan?

<a href="https://www.weerbaredigitaleoverheid.nl/programma-onderdelen/sessie/9da8ace4/">Meld je aan voor deze masterclass</a> waarin verschillende experts ingaan op dit onderwerp.<br> <br> <br>


link: https://www.rijksoverheid.nl/actueel/nieuws/2023/07/01/wet-toekomst-pensioenen-in-werking
encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5yaWprc292ZXJoZWlkLm5sL25pZXV3cy5yc3M=
read: False
type: Rss
title: Wet toekomst pensioenen in werking
description:
Vandaag treedt de Wet toekomst pensioenen in werking. Daarmee begint een overgangsfase van enkele jaren waarin werkgevers en werknemers met elkaar afspraken gaan maken en pensioenuitvoerders deze afspraken gaan uitvoeren.


encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5yaWprc292ZXJoZWlkLm5sL25pZXV3cy5yc3M=
read: False
type: Rss
title: Nieuwe toekenning uit Nationaal Groeifonds: 635 miljoen voor OCW-sectoren
link:
https://www.rijksoverheid.nl/actueel/nieuws/2023/06/30/nieuwe-toekenning-uit-nationaal-groeifonds-635-miljoen-voor-ocw-sectoren

description:
Het kabinet stelt vanuit het Nationaal Groeifonds € 635 miljoen beschikbaar voor projecten op het terrein van onderwijs, cultuur en wetenschap. Ook is er hiervoor nog eens bijna € 1 miljard geserveerd. Dit geld is bedoeld voor 5 voorstellen, onder meer gericht op de professionele ontwikkeling van leraren, betere onderwijshuisvesting en verdere digitale transitie in de creatieve industrie. Dat maakten minister Micky Adriaansens (Economische Zaken en Klimaat) en Rianne Letschert (voorzitter van de adviescommissie Nationaal Groeifonds) vandaag bekend.


encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5yaWprc292ZXJoZWlkLm5sL25pZXV3cy5yc3M=
read: False
type: Rss
title: Roos Vermeij voorzitter van de transitiecommissie pensioenen
link:
https://www.rijksoverheid.nl/actueel/nieuws/2023/06/30/roos-vermeij-voorzitter-van-de-transitiecommissie-pensioenen

description:
Oud-Kamerlid en oud-pensioenfondsbestuurder Roos Vermeij wordt voorzitter van de transitiecommissie pensioenen. Deze onafhankelijke commissie gaat ondersteuning bieden aan vakbonden en werkgevers bij de gesprekken over de nieuwe pensioenregelingen. De minister voor Armoedebeleid, Participatie en Pensioenen Carola Schouten heeft haar samen met de overige leden benoemd.


encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5yaWprc292ZXJoZWlkLm5sL25pZXV3cy5yc3M=
read: False
type: Rss
title: Reactie minister Carola Schouten op eerste rapport Commissie sociaal minimum
link:
https://www.rijksoverheid.nl/actueel/nieuws/2023/06/30/reactie-minister-carola-schouten-op-eerste-rapport-commissie-sociaal-minimum

description:
Voor het eerst is er onderzoek gedaan naar de hoogte van het bedrag dat ten minste nodig is om van te leven en mee te doen, het zogenaamde sociaal minimum. Vandaag overhandigde de voorzitter van de commissie - hoogleraar Godfried Engbersen – het eerste rapport aan minister Carola Schouten (Armoedebeleid, Participatie en Pensioenen).


encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5yaWprc292ZXJoZWlkLm5sL25pZXV3cy5yc3M=
read: False
type: Rss
title: Forse verhoging van het sociaal minimum is nodig
description: Dit is een persbericht van de Commissie Sociaal Minimum
link:
https://www.rijksoverheid.nl/actueel/nieuws/2023/06/30/forse-verhoging-van-het-sociaal-minimum-is-nodig


encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5yaWprc292ZXJoZWlkLm5sL25pZXV3cy5yc3M=
read: False
type: Rss
title: Forse financiële impuls voor meer en efficiënter opleiden zorgprofessionals
link:
https://www.rijksoverheid.nl/actueel/nieuws/2023/06/30/forse-financiele-impuls-voor-meer-en-efficienter-opleiden-zorgprofessionals

description:
Minister Helder (Langdurige Zorg en Sport) zet zich ervoor in ook in de toekomst genoeg mensen te hebben voor al het werk in de zorg en ondersteuning. Dat lukt alleen als de opleidingen goed en efficiënt zijn en er minder begeleidingscapaciteit nodig is. Met de investering van het Nationaal Groeifonds (NGF) in het programma Digital United Training Concepts for Healthcare (DUTCH) kunnen opleidingen worden gemoderniseerd met digitale trainingen en simulaties. In totaal wordt er 132 miljoen beschikbaar gesteld waarvan 48 miljoen onvoorwaardelijk.


encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5yaWprc292ZXJoZWlkLm5sL25pZXV3cy5yc3M=
read: False
type: Rss
title: Innovatieve technologie krijgt opnieuw extra steun uit Nationaal Groeifonds
link:
https://www.rijksoverheid.nl/actueel/nieuws/2023/06/30/innovatieve-technologie-krijgt-opnieuw-extra-steun-uit-nationaal-groeifonds

description:
Circulaire batterijen en -zonnepanelen, 6G, radiofrequentie technologie en klimaatneutrale schepen. Deze en andere innovatieve projecten van bedrijven, kennisinstellingen en overheden vormen de basis om als Nederland voorop te kunnen blijven lopen met technologische (maak)industrie en verduurzaming. Als onderdeel van de vandaag door minister Micky Adriaansens (Economische Zaken en Klimaat) bekend gemaakte investeringen (4 miljard euro) uit de derde ronde van het Nationaal Groeifonds gaat er 2,6 miljard euro specifiek naar onderzoek, ontwikkeling en innovatie op het gebied van klimaat, energie, high tech, digitalisering en gezondheidszorg.


encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5yaWprc292ZXJoZWlkLm5sL25pZXV3cy5yc3M=
read: False
type: Rss
title: Toekomst Nederlandse economie: innovatief, duurzaam, sterk en welvarend
link:
https://www.rijksoverheid.nl/actueel/nieuws/2023/06/30/toekomst-nederlandse-economie-innovatief-duurzaam-sterk-en-welvarend

description:
Meedoen en meeprofiteren van brede welvaart   Brede welvaart staat centraal in de toekomstige economie van Nederland. Dat heeft het kabinet vandaag bepaald op voorstel van minister Adriaansens van Economische Zaken en Klimaat. Onze toekomstige economie is innovatief en duurzaam en kenmerkt zich door een sterke positie van Nederland in een weerbaar Europa. Het kabinet wil dat mensen in voldoende mate kunnen meedoen en profiteren van economische groei, zo schrijft minister Adriaansens in het Perspectief op de Nederlandse economie.


encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5yaWprc292ZXJoZWlkLm5sL25pZXV3cy5yc3M=
read: False
type: Rss
link:
https://www.rijksoverheid.nl/actueel/nieuws/2023/06/30/nationaal-groeifonds-4-miljard-naar-18-projecten-voor-duurzame-economische-groei-en-toekomstige-welvaart

title:
Nationaal Groeifonds: 4 miljard naar 18 projecten voor duurzame economische groei en toekomstige welvaart

description:
Het kabinet investeert 4 miljard euro uit het Nationaal Groeifonds in 18 projecten die moeten zorgen voor langdurige economische groei en toekomstige welvaart. Dat heeft de ministerraad besloten op voorstel van minister Adriaansens van Economische Zaken en Klimaat en minister Kaag van Financiën. Het kabinet neemt hiermee het advies over van de commissie onder leiding van Rianne Letschert, bestuursvoorzitter van de Universiteit Maastricht. Economische groei stelt ons in staat om te blijven investeren in bijvoorbeeld gezondheidszorg, onderwijs en maatregelen tegen klimaatverandering. Ook zorgt groei voor meer inkomen, zodat we ook in de toekomst onze welvaart behouden.


link: https://www.rijksoverheid.nl/actueel/nieuws/2023/06/30/benoeming-secretaris-generaal-defensie
encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5yaWprc292ZXJoZWlkLm5sL25pZXV3cy5yc3M=
read: False
type: Rss
title: Benoeming secretaris-generaal Defensie
description:
Drs. M.R. (Maarten) Schurink wordt secretaris-generaal bij het ministerie van Defensie. De ministerraad heeft ingestemd met het voorstel van minister Bruins Slot van Binnenlandse Zaken en Koninkrijksrelaties. De benoeming gaat in per 21 augustus 2023.


encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5yaWprc292ZXJoZWlkLm5sL25pZXV3cy5yc3M=
read: False
type: Rss
title: Benoeming Toetsingscommissie experimenten rechtspleging
link:
https://www.rijksoverheid.nl/actueel/nieuws/2023/06/30/benoeming-toetsingscommissie-experimenten-rechtspleging

description:
De ministerraad heeft op voordracht van minister Weerwind voor Rechtsbescherming besloten tot de benoeming van de voorzitter en zes leden van de Toetsingscommissie experimenten rechtspleging. Deze commissie wordt ingesteld in het kader van de Tijdelijke Experimentenwet rechtspleging.


link: https://www.rijksoverheid.nl/actueel/nieuws/2023/06/30/wettelijke-regeling-voor-draagmoederschap
encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5yaWprc292ZXJoZWlkLm5sL25pZXV3cy5yc3M=
read: False
type: Rss
title: Wettelijke regeling voor draagmoederschap
description:
Draagmoederschap wordt bij wet geregeld in Nederland. Tot op heden is er geen specifieke regeling voor ouderschap na draagmoederschap. De ministerraad heeft op voorstel van minister Weerwind voor Rechtsbescherming ingestemd met een wetsvoorstel dat daar verandering in gaat brengen.


encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5yaWprc292ZXJoZWlkLm5sL25pZXV3cy5yc3M=
read: False
type: Rss
title: Kabinet werkt aan opties afschaffen toeslagenstelsel
link:
https://www.rijksoverheid.nl/actueel/nieuws/2023/06/30/kabinet-werkt-aan-opties-afschaffen-toeslagenstelsel

description:
In het coalitieakkoord is de ambitie opgenomen om het toeslagenstelsel af te schaffen. Het huidige toeslagenstelsel biedt mensen gericht en actueel inkomensondersteuning. Tegelijkertijd bevat het stelsel tekortkomingen, waardoor fundamentele aanpassingen nodig zijn. Om een volgend kabinet in de gelegenheid te stellen om weloverwogen keuzes te maken over aanpassingen, werkt het kabinet concrete opties voor alternatieven uit. Dat staat in de Tussenrapportage toekomst toeslagenstelsel, die het kabinet naar de Tweede Kamer heeft gestuurd. Met de tussenrapportage informeert staatssecretaris De Vries van Financiën (Toeslagen en Douane) de Tweede Kamer, samen met minister Van Gennip van Sociale Zaken en Werkgelegenheid, minister Kuipers van Volksgezondheid, Welzijn en Sport en minister De Jonge voor Volkshuisvesting en Ruimtelijke Ordening.


link: https://www.rijksoverheid.nl/actueel/nieuws/2023/06/30/benoeming-vicepresident-hoge-raad
encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5yaWprc292ZXJoZWlkLm5sL25pZXV3cy5yc3M=
read: False
type: Rss
title: Benoeming vicepresident Hoge Raad
description:
Mr. J.A.R. van Eijsden (1973) wordt per 1 september 2023 benoemd tot vicepresident van de belastingkamer van de Hoge Raad der Nederlanden. Dit is besloten door de ministerraad op voordracht van minister Weerwind voor Rechtsbescherming.


encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5yaWprc292ZXJoZWlkLm5sL25pZXV3cy5yc3M=
read: False
type: Rss
title: Benoeming bij Adviescollege Openbaarheid en Informatiehuishouding
link:
https://www.rijksoverheid.nl/actueel/nieuws/2023/06/30/benoeming-bij-adviescollege-openbaarheid-en-informatiehuishouding

description:
De ministerraad heeft op voorstel van minister Bruins Slot van Binnenlandse Zaken en Koninkrijkrelaties (BZK), mede namens staatssecretaris Uslu voor Cultuur en Media, ingestemd met de benoeming van Jamila Aanzi tot lid van het Adviescollege Openbaarheid en Informatiehuishouding.


encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5yaWprc292ZXJoZWlkLm5sL25pZXV3cy5yc3M=
read: False
type: Rss
title: Crisisregeling Personeelsbehoud helpt bedrijven en voorkomt baanverlies in crisistijd
link:
https://www.rijksoverheid.nl/actueel/nieuws/2023/06/30/crisisregeling-personeelsbehoud-helpt-bedrijven-en-voorkomt-baanverlies-in-crisistijd

description:
In geval van een crisis zoals een overstroming, oorlog of pandemie is het belangrijk dat ondernemingen snel kunnen schakelen en zekerheid hebben over behoud van personeel. Om deze zekerheid te bieden ontwikkelt minister Van Gennip van Sociale Zaken en Werkgelegenheid de Crisisregeling Personeelsbehoud. De maatregel werd in april gepresenteerd als onderdeel van het pakket arbeidsmarkt. In een brief aan de Tweede Kamer beschrijft minister Van Gennip hoe de regeling eruit ziet.


encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5yaWprc292ZXJoZWlkLm5sL25pZXV3cy5yc3M=
read: False
type: Rss
title: Ministerie van Economische Zaken en Klimaat: belangrijkste veranderingen per 1 juli 2023
link:
https://www.rijksoverheid.nl/actueel/nieuws/2023/06/30/ministerie-van-economische-zaken-en-klimaat-belangrijkste-veranderingen-per-1-juli-2023

description:
Meer bedrijven krijgen te maken met de plicht om energie te besparen en te verduurzamen, wettelijk wordt vastgelegd dat de overheid de versterkingsoperatie in Groningen leidt en er komen nieuwe regels voor het winnen van aardwarmte. Dit zijn enkele veranderingen van regels en wetten op het terrein van Economische Zaken en Klimaat die 1 juli 2023 ingaan.


link: https://www.rijksoverheid.nl/actueel/nieuws/2023/06/30/specifieke-wetgeving-voor-aardwarmte
encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5yaWprc292ZXJoZWlkLm5sL25pZXV3cy5yc3M=
read: False
type: Rss
title: Specifieke wetgeving voor aardwarmte
description:
Vanaf zaterdag 1 juli 2023 geldt er wet- en regelgeving specifiek voor aardwarmte. Tot en met vandaag is er voor aardwarmte hetzelfde stelsel als voor bijvoorbeeld gaswinning. Omdat aardwarmte anders werkt dan andere mijnbouwactiviteiten is er nu specifieke wetgeving met bijvoorbeeld een afzonderlijke vergunningsstructuur. Staatstoezicht op de Mijnen houdt toezicht en handhaaft op de veiligheid voor mens en milieu.


encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5yaWprc292ZXJoZWlkLm5sL25pZXV3cy5yc3M=
read: False
type: Rss
title: Woondeal zorgt voor meer betaalbare woningen op Bonaire
link:
https://www.rijksoverheid.nl/actueel/nieuws/2023/06/30/woondeal-zorgt-voor-meer-betaalbare-woningen-op-bonaire

description:
Het bestuurscollege op Bonaire en Hugo de Jonge, minister voor Volkshuisvesting en Ruimtelijke Ordening, zetten vandaag hun handtekening onder de woondeal voor Bonaire. Het doel is om 2124 betaalbare woningen te realiseren tot en met 2030. Minister De Jonge maakt € 10 miljoen beschikbaar voor de eerste tranche van de woondeal, waarmee vanaf 2025 de bouw van de eerste 600 woningen mogelijk wordt inclusief infrastructuur.


encoded_syndication_url: aHR0cHM6Ly9mZWVkcy5yaWprc292ZXJoZWlkLm5sL25pZXV3cy5yc3M=
read: False
type: Rss
title: 200 jaar KNRM en 750 jaar Amsterdam thema’s nieuwe munten 2024
link:
https://www.rijksoverheid.nl/actueel/nieuws/2023/06/30/200-jaar-knrm-en-750-jaar-amsterdam-themas-nieuwe-munten-2024

description:
Het 200-jarig bestaan van de Koninklijke Nederlandse Redding Maatschappij (KNRM) en het 750-jarig bestaan van Amsterdam worden de muntthema’s voor 2024.


link: https://nl.wikipedia.org/w/index.php?title=Myanmar&diff=64618206&oldid=64580030
read: False
type: Atom
title: Myanmar
authors: 2A02:A46E:D78C:1:446:A205:F759:D671
description:
&lt;p&gt;&lt;span dir="auto"&gt;&lt;span class="autocomment"&gt;Rivaliserende koninkrijken&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;table style="background-color: #fff; color: #202122;" data-mw="interface"&gt;
				&lt;col class="diff-marker" /&gt;
				&lt;col class="diff-content" /&gt;
				&lt;col class="diff-marker" /&gt;
				&lt;col class="diff-content" /&gt;
				&lt;tr class="diff-title" lang="nl"&gt;
				&lt;td colspan="2" style="background-color: #fff; color: #202122; text-align: center;"&gt;← Oudere versie&lt;/td&gt;
				&lt;td colspan="2" style="background-color: #fff; color: #202122; text-align: center;"&gt;Versie van 2 jul 2023 20:20&lt;/td&gt;
				&lt;/tr&gt;&lt;tr&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 170:&lt;/td&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 170:&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;Het rijk viel uiteen en een aantal eeuwen was Birma verdeeld in diverse staatjes. In het noorden van het land heersten de Shan. De hoofdstad was eerst [[Sagaing (stad)|Sagaing]], daarna in 1364 [[Ava (Myanmar)|Ava]] (of Inwa), beide in de nabijheid van het huidige [[Mandalay (stad)|Mandalay]]. Aan de Irrawaddy herrees het Mon-koninkrijk van [[Pegu (stad)|Pegu]] (of Bago), dat langdurige oorlogen voerde tegen de Thai en de Shan.&amp;lt;br /&amp;gt;&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;Het rijk viel uiteen en een aantal eeuwen was Birma verdeeld in diverse staatjes. In het noorden van het land heersten de Shan. De hoofdstad was eerst [[Sagaing (stad)|Sagaing]], daarna in 1364 [[Ava (Myanmar)|Ava]] (of Inwa), beide in de nabijheid van het huidige [[Mandalay (stad)|Mandalay]]. Aan de Irrawaddy herrees het Mon-koninkrijk van [[Pegu (stad)|Pegu]] (of Bago), dat langdurige oorlogen voerde tegen de Thai en de Shan.&amp;lt;br /&amp;gt;&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;In [[Toungoo]], tussen Ava en Pegu, bevond zich een kleine Birmaanse staat, &lt;del style="font-weight: bold; text-decoration: none;"&gt;dat&lt;/del&gt; profiteerde van de oorlogen tussen de Shan en de Mon en beide staten aan zich onderwierp: in 1539 veroverde het Pegu en in 1555 Ava. Daarmee stichtte koning [[Bayinnaung]] het '''''Tweede Birmaanse koninkrijk (1539-1752)''''' met als hoofdstad [[Pegu (stad)|Pegu]]. Hij voerde ook oorlogen tegen [[Thailand|Siam]] (Thailand) en veroverde in 1569 de hoofdstad [[Ayutthaya (oud)|Ayutthaya]]. De veroveringen hielden overigens niet lang stand. In 1635 werd de hoofdstad overgebracht van Pegu naar Ava. In 1740 kwamen de Mon in opstand en verjoegen de Birmanen uit de rivierdelta en daarna, in 1752, uit Ava en maakten daarmee een einde aan het Tweede Birmaanse koninkrijk.&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;In [[Toungoo]], tussen Ava en Pegu, bevond zich een kleine Birmaanse staat, &lt;ins style="font-weight: bold; text-decoration: none;"&gt;die&lt;/ins&gt; profiteerde van de oorlogen tussen de Shan en de Mon en beide staten aan zich onderwierp: in 1539 veroverde het Pegu en in 1555 Ava. Daarmee stichtte koning [[Bayinnaung]] het '''''Tweede Birmaanse koninkrijk (1539-1752)''''' met als hoofdstad [[Pegu (stad)|Pegu]]. Hij voerde ook oorlogen tegen [[Thailand|Siam]] (Thailand) en veroverde in 1569 de hoofdstad [[Ayutthaya (oud)|Ayutthaya]]. De veroveringen hielden overigens niet lang stand. In 1635 werd de hoofdstad overgebracht van Pegu naar Ava. In 1740 kwamen de Mon in opstand en verjoegen de Birmanen uit de rivierdelta en daarna, in 1752, uit Ava en maakten daarmee een einde aan het Tweede Birmaanse koninkrijk.&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;Maar de Mon werden al gauw teruggeslagen door de Birmanen onder een nieuwe leider [[Alaungpaya]], die &lt;del style="font-weight: bold; text-decoration: none;"&gt;zich&lt;/del&gt; tot koning uitriep en daarmee het '''''Derde Birmaanse koninkrijk (1752-1885)''''' stichtte. Hij verenigde met harde hand de Birmese volken onder één rijk. Koning [[Hsinbyushin]] stuitte een Chinese invasie en veroverde in 1767 opnieuw kortstondig Siam, waarbij [[Ayutthaya (oud)|Ayutthaya]] volledig werd verwoest. Onder koning [[Bodawpaya]] werden ook [[Assam]] en [[Koninkrijk Arakan|Arakan]] onderworpen. Dit leidde tot spanningen met het [[Britse Rijk]] in India. Gedurende het Derde Birmaanse koninkrijk werd de hoofdstad regelmatig verplaatst: in 1783 van [[Ava (Myanmar)|Ava]] naar [[Amarapura (stad)|Amarapura]], in 1813 terug naar Ava, in 1841 (na een verwoestende aardbeving in 1838) weer naar Amarapura en in 1861 naar [[Mandalay (stad)|Mandalay]].&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;Maar de Mon werden al gauw teruggeslagen door de Birmanen onder een nieuwe leider [[Alaungpaya]], die &lt;ins style="font-weight: bold; text-decoration: none;"&gt;zichzelf&lt;/ins&gt; tot koning uitriep en daarmee het '''''Derde Birmaanse koninkrijk (1752-1885)''''' stichtte. Hij verenigde met harde hand de Birmese volken onder één rijk. Koning [[Hsinbyushin]] stuitte een Chinese invasie en veroverde in 1767 opnieuw kortstondig Siam, waarbij [[Ayutthaya (oud)|Ayutthaya]] volledig werd verwoest. Onder koning [[Bodawpaya]] werden ook [[Assam]] en [[Koninkrijk Arakan|Arakan]] onderworpen. Dit leidde tot spanningen met het [[Britse Rijk]] in India. Gedurende het Derde Birmaanse koninkrijk werd de hoofdstad regelmatig verplaatst: in 1783 van [[Ava (Myanmar)|Ava]] naar [[Amarapura (stad)|Amarapura]], in 1813 terug naar Ava, in 1841 (na een verwoestende aardbeving in 1838) weer naar Amarapura en in 1861 naar [[Mandalay (stad)|Mandalay]].&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;[[File:Innwa monastery.jpg|thumb|Innwa-klooster&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;[[File:Innwa monastery.jpg|thumb|Innwa-klooster&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;]]&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;]]&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;

&lt;!-- diff cache key nlwiki:diff:wikidiff2:1.12:old-64580030:rev-64618206:1.13.0 --&gt;
&lt;/table&gt;


link: https://nl.wikipedia.org/w/index.php?title=Charles_Aznavour&diff=64618205&oldid=64618150
read: False
type: Atom
title: Charles Aznavour
authors: Toth
description:
&lt;p&gt;&lt;/p&gt;
&lt;table style="background-color: #fff; color: #202122;" data-mw="interface"&gt;
				&lt;col class="diff-marker" /&gt;
				&lt;col class="diff-content" /&gt;
				&lt;col class="diff-marker" /&gt;
				&lt;col class="diff-content" /&gt;
				&lt;tr class="diff-title" lang="nl"&gt;
				&lt;td colspan="2" style="background-color: #fff; color: #202122; text-align: center;"&gt;← Oudere versie&lt;/td&gt;
				&lt;td colspan="2" style="background-color: #fff; color: #202122; text-align: center;"&gt;Versie van 2 jul 2023 20:20&lt;/td&gt;
				&lt;/tr&gt;&lt;tr&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 16:&lt;/td&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 16:&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| website        = https://www.charlesaznavour-lesite.fr/&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| website        = https://www.charlesaznavour-lesite.fr/&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;}}&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;}}&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;'''Charles &lt;del style="font-weight: bold; text-decoration: none;"&gt;Aznavourian&lt;/del&gt;''', [[pseudoniem]] van ''Chahnour Varinag Aznavourian'' ([[Armeens]]: Շահնուր Վաղինակ Ազնավուրյան), ([[Parijs (hoofdbetekenis)|Parijs]], [[22 mei]] [[1924]] – [[Mouriès]], [[1 oktober]] [[2018]]) was een &lt;del style="font-weight: bold; text-decoration: none;"&gt;Armeense&lt;/del&gt; zanger, liedjesschrijver en acteur van &lt;del style="font-weight: bold; text-decoration: none;"&gt;die&lt;/del&gt; &lt;del style="font-weight: bold; text-decoration: none;"&gt;een Franse nationaliteit had&lt;/del&gt;, die vanaf 2008 ook de Armeense nationaliteit had.&lt;del style="font-weight: bold; text-decoration: none;"&gt; Hij wordt door veel Armenen omarmd en beschouwt als de beste Armeense zanger. &lt;/del&gt;&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;'''Charles &lt;ins style="font-weight: bold; text-decoration: none;"&gt;Aznavour&lt;/ins&gt;''', [[pseudoniem]] van ''Chahnour Varinag Aznavourian'' ([[Armeens]]: Շահնուր Վաղինակ Ազնավուրյան), ([[Parijs (hoofdbetekenis)|Parijs]], [[22 mei]] [[1924]] – [[Mouriès]], [[1 oktober]] [[2018]]) was een &lt;ins style="font-weight: bold; text-decoration: none;"&gt;[[Frankrijk (hoofdbetekenis)|Franse]]&lt;/ins&gt; zanger, liedjesschrijver en acteur van &lt;ins style="font-weight: bold; text-decoration: none;"&gt;[[Armenië|Armeense]]&lt;/ins&gt; &lt;ins style="font-weight: bold; text-decoration: none;"&gt;afkomst&lt;/ins&gt;, die vanaf 2008 ook de Armeense nationaliteit had.&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;== Leven ==&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;== Leven ==&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;

&lt;!-- diff cache key nlwiki:diff:wikidiff2:1.12:old-64618150:rev-64618205:1.13.0 --&gt;
&lt;/table&gt;


read: False
type: Atom
title: Wikipedia:Verzoekpagina voor moderatoren/RegBlok
authors: Bestrijd giftige witheid
link:
https://nl.wikipedia.org/w/index.php?title=Wikipedia:Verzoekpagina_voor_moderatoren/RegBlok&diff=64618204&oldid=64618165

description:
&lt;p&gt;&lt;span dir="auto"&gt;&lt;span class="autocomment"&gt;Nieuwe verzoeken ter beoordeling door meerdere moderatoren: &lt;/span&gt; Typo&lt;/span&gt;&lt;/p&gt;
&lt;table style="background-color: #fff; color: #202122;" data-mw="interface"&gt;
				&lt;col class="diff-marker" /&gt;
				&lt;col class="diff-content" /&gt;
				&lt;col class="diff-marker" /&gt;
				&lt;col class="diff-content" /&gt;
				&lt;tr class="diff-title" lang="nl"&gt;
				&lt;td colspan="2" style="background-color: #fff; color: #202122; text-align: center;"&gt;← Oudere versie&lt;/td&gt;
				&lt;td colspan="2" style="background-color: #fff; color: #202122; text-align: center;"&gt;Versie van 2 jul 2023 20:20&lt;/td&gt;
				&lt;/tr&gt;&lt;tr&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 20:&lt;/td&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 20:&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;:::"Anti-blank" racisme bestaat niet, want racisme is macht + vooroordelen, zoals ik ook al uitgebreider op onze overlegpagina heb uitgelegd. Daarnaast was de uitspraak "dode witte mannen" geen viering van de dood van witte mannen of anderzijds minachtend naar witte mannen in het algemeen bedoeld, maar bedoeld om te benadrukken dat het om witte mannen gaat die in de 17de, 18de, 19de en begin 20ste eeuw leefden, er voor 21ste eeuwse standaarden achterhaalde, pseudowetenschappelijke, problematische ideeën op nahielden, en dus geen relevantie meer hebben op onze huidige samenleving en cultuur. [[Gebruiker:Bestrijd giftige witheid|Bestrijd giftige witheid]] ([[Overleg gebruiker:Bestrijd giftige witheid|overleg]]) 2 jul 2023 19:41 (CEST)&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;:::"Anti-blank" racisme bestaat niet, want racisme is macht + vooroordelen, zoals ik ook al uitgebreider op onze overlegpagina heb uitgelegd. Daarnaast was de uitspraak "dode witte mannen" geen viering van de dood van witte mannen of anderzijds minachtend naar witte mannen in het algemeen bedoeld, maar bedoeld om te benadrukken dat het om witte mannen gaat die in de 17de, 18de, 19de en begin 20ste eeuw leefden, er voor 21ste eeuwse standaarden achterhaalde, pseudowetenschappelijke, problematische ideeën op nahielden, en dus geen relevantie meer hebben op onze huidige samenleving en cultuur. [[Gebruiker:Bestrijd giftige witheid|Bestrijd giftige witheid]] ([[Overleg gebruiker:Bestrijd giftige witheid|overleg]]) 2 jul 2023 19:41 (CEST)&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;::::Tegen zoveel ultraradicale flauwekul ('racisme is macht + vooroordelen') is geen kruid gewassen. Mede daarom denk ik ook dat Wikipedia beter af is zonder jullie. [[Gebruiker:Marrakech|Marrakech]] ([[Overleg gebruiker:Marrakech|overleg]]) 2 jul 2023 20:05 (CEST)&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;::::Tegen zoveel ultraradicale flauwekul ('racisme is macht + vooroordelen') is geen kruid gewassen. Mede daarom denk ik ook dat Wikipedia beter af is zonder jullie. [[Gebruiker:Marrakech|Marrakech]] ([[Overleg gebruiker:Marrakech|overleg]]) 2 jul 2023 20:05 (CEST)&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;:::::Het idee dat racimse macht + &lt;del style="font-weight: bold; text-decoration: none;"&gt;voordelen&lt;/del&gt; betekent is gewoon al jaren algemeen geaccepteerd in activistische kringen, maar ook in academische kringen, zoals op hoogwaardige universiteiten, en begint ook steeds meer draagvlak te vergaren binnen de grote, betrouwbare, hoogwaardige Amerikaanse nieuwsmedia. Als (Zwarte) Civil Rights-activisten als Martin Luther King Jr. nog hadden geleefd, zouden ze dit idee ook hebben onderschreven. Als jullie in de tijd van de Civil Rights hadden geleefd, waren jullie waarschijnlijk ook tegen de Civil Rights Movement, Martin Luther King Jr. en desegregatie geweest. [[Gebruiker:Bestrijd giftige witheid|Bestrijd giftige witheid]] ([[Overleg gebruiker:Bestrijd giftige witheid|overleg]]) 2 jul 2023 20:13 (CEST)&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;:::::Het idee dat racimse macht + &lt;ins style="font-weight: bold; text-decoration: none;"&gt;vooroordelen&lt;/ins&gt; betekent is gewoon al jaren algemeen geaccepteerd in activistische kringen, maar ook in academische kringen, zoals op hoogwaardige universiteiten, en begint ook steeds meer draagvlak te vergaren binnen de grote, betrouwbare, hoogwaardige Amerikaanse nieuwsmedia. Als (Zwarte) Civil Rights-activisten als Martin Luther King Jr. nog hadden geleefd, zouden ze dit idee ook hebben onderschreven. Als jullie in de tijd van de Civil Rights hadden geleefd, waren jullie waarschijnlijk ook tegen de Civil Rights Movement, Martin Luther King Jr. en desegregatie geweest. [[Gebruiker:Bestrijd giftige witheid|Bestrijd giftige witheid]] ([[Overleg gebruiker:Bestrijd giftige witheid|overleg]]) 2 jul 2023 20:13 (CEST)&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;::De eerste uitspraak van ons die u citeert impliceert niet dat wij hierom van plan zijn de Wikipedia-regels maar onze laars te lappen, het is een persoonlijke opvatting van ons over het beleid van Wikipedia. Sinds wannneer is het hebben van eigen meningen die verschillen van de meningen van Wikipedia-moderatoren verboden op Wikipedia? Onze tweede uitspraak die u heeft geciteerd is overigens ook een persoonlijke mening (eigenlijk is het de waarheid, maar daar zullen jullie het nooit mee eens worden), dus dat zou geen betrekking moeten hebben op hoe onze bijdragen aan Wikipedia worden beoordeeld, zolang we ons aan de regels van Wikipedia houden. [[Gebruiker:Bestrijd giftige witheid|Bestrijd giftige witheid]] ([[Overleg gebruiker:Bestrijd giftige witheid|overleg]]) 2 jul 2023 19:48 (CEST)&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;::De eerste uitspraak van ons die u citeert impliceert niet dat wij hierom van plan zijn de Wikipedia-regels maar onze laars te lappen, het is een persoonlijke opvatting van ons over het beleid van Wikipedia. Sinds wannneer is het hebben van eigen meningen die verschillen van de meningen van Wikipedia-moderatoren verboden op Wikipedia? Onze tweede uitspraak die u heeft geciteerd is overigens ook een persoonlijke mening (eigenlijk is het de waarheid, maar daar zullen jullie het nooit mee eens worden), dus dat zou geen betrekking moeten hebben op hoe onze bijdragen aan Wikipedia worden beoordeeld, zolang we ons aan de regels van Wikipedia houden. [[Gebruiker:Bestrijd giftige witheid|Bestrijd giftige witheid]] ([[Overleg gebruiker:Bestrijd giftige witheid|overleg]]) 2 jul 2023 19:48 (CEST)&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;:Onze pagina wordt vooral door één persoon gerund, maar we verwijzen naar onszelf in meervoud om namens de hele commune van onze AFA-afdeling te spreken, alsmede als onderdeel van ons streven om zo genderneutraal mogelijk taalgebruik te gebruiken. Alleen maar omdat wij linkse activisten zijn, betekent niet dat wij hier puur zijn om actie te voeren en niet om oprecht bij te dragen aan Wikipedia. Wij streven er naar om de Nederlandstalige Wikipedia voor iedereen een fijnere plek te maken, door de rechtse bias in artikelen te verminderen en achterhaald taalgebruik te vervangen door inclusiever taalgebruik, binnen de regels en richtlijnen van Wikipedia uiteraard. [[Gebruiker:Bestrijd giftige witheid|Bestrijd giftige witheid]] ([[Overleg gebruiker:Bestrijd giftige witheid|overleg]]) 2 jul 2023 19:54 (CEST)&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;:Onze pagina wordt vooral door één persoon gerund, maar we verwijzen naar onszelf in meervoud om namens de hele commune van onze AFA-afdeling te spreken, alsmede als onderdeel van ons streven om zo genderneutraal mogelijk taalgebruik te gebruiken. Alleen maar omdat wij linkse activisten zijn, betekent niet dat wij hier puur zijn om actie te voeren en niet om oprecht bij te dragen aan Wikipedia. Wij streven er naar om de Nederlandstalige Wikipedia voor iedereen een fijnere plek te maken, door de rechtse bias in artikelen te verminderen en achterhaald taalgebruik te vervangen door inclusiever taalgebruik, binnen de regels en richtlijnen van Wikipedia uiteraard. [[Gebruiker:Bestrijd giftige witheid|Bestrijd giftige witheid]] ([[Overleg gebruiker:Bestrijd giftige witheid|overleg]]) 2 jul 2023 19:54 (CEST)&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 35:&lt;/td&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 35:&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;#...&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;#...&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;*'''Conclusie:'''&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;*'''Conclusie:'''&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-empty diff-side-deleted"&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;== Afgehandelde verzoeken ==&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;== Afgehandelde verzoeken ==&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
&lt;/tr&gt;

&lt;!-- diff cache key nlwiki:diff:wikidiff2:1.12:old-64618165:rev-64618204:1.13.0 --&gt;
&lt;/table&gt;


link: https://nl.wikipedia.org/w/index.php?title=Lijst_van_kattenrassen&diff=64618203&oldid=64556654
read: False
type: Atom
title: Lijst van kattenrassen
authors: StuivertjeWisselen
description:
&lt;p&gt;Behouden bij &lt;a href="/wiki/Wikipedia:Te_beoordelen_pagina%27s/Toegevoegd_20230618#Lijst_van_kattenrassen" title="Wikipedia:Te beoordelen pagina&amp;#039;s/Toegevoegd 20230618"&gt;sessie 2 juli 2023&lt;/a&gt;.&lt;/p&gt;
&lt;table style="background-color: #fff; color: #202122;" data-mw="interface"&gt;
				&lt;col class="diff-marker" /&gt;
				&lt;col class="diff-content" /&gt;
				&lt;col class="diff-marker" /&gt;
				&lt;col class="diff-content" /&gt;
				&lt;tr class="diff-title" lang="nl"&gt;
				&lt;td colspan="2" style="background-color: #fff; color: #202122; text-align: center;"&gt;← Oudere versie&lt;/td&gt;
				&lt;td colspan="2" style="background-color: #fff; color: #202122; text-align: center;"&gt;Versie van 2 jul 2023 20:20&lt;/td&gt;
				&lt;/tr&gt;&lt;tr&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 1:&lt;/td&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 1:&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;{{weg|geen enkele meerwaarde ten opzichte van de al bestaande categorie kattenras|2023|06|18}}&lt;/div&gt;&lt;/td&gt;
  &lt;td colspan="2" class="diff-empty diff-side-added"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;Dit is een '''lijst van erkende [[Kat (dier)|kattenrassen]]'''. Het gaat hier om rassen voortkomend uit de gedomesticeerde kat die erkend zijn door een van de erkende overkoepelende [[Kattenstamboekvereniging|organisaties]], zoals CFA, FIFe, GCCF en TICA:&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;Dit is een '''lijst van erkende [[Kat (dier)|kattenrassen]]'''. Het gaat hier om rassen voortkomend uit de gedomesticeerde kat die erkend zijn door een van de erkende overkoepelende [[Kattenstamboekvereniging|organisaties]], zoals CFA, FIFe, GCCF en TICA:&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;== Lijst ==&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;== Lijst ==&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 627:&lt;/td&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 626:&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|[[Bestand:Turc Du Lac De Van.jpg|129x129px]]&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|[[Bestand:Turc Du Lac De Van.jpg|129x129px]]&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|}&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|}&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-empty diff-side-deleted"&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;{{appendix}}&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
  &lt;td colspan="2" class="diff-empty diff-side-added"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;[[Categorie:Lijsten van zoogdieren|Kattenrassen]]&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;[[Categorie:Lijsten van zoogdieren|Kattenrassen]]&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;[[Categorie:Kattenras&lt;del style="font-weight: bold; text-decoration: none;"&gt;| &lt;/del&gt;]]&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;[[Categorie:Kattenras]]&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;

&lt;!-- diff cache key nlwiki:diff:wikidiff2:1.12:old-64556654:rev-64618203:1.13.0 --&gt;
&lt;/table&gt;


link: https://nl.wikipedia.org/w/index.php?title=Wikipedia:De_kroeg&diff=64618202&oldid=64618155
read: False
type: Atom
title: Wikipedia:De kroeg
authors: Mondo
description:
&lt;p&gt;&lt;span dir="auto"&gt;&lt;span class="autocomment"&gt;Onbetrouwbare bronnen: &lt;/span&gt; Reactie&lt;/span&gt;&lt;/p&gt;
&lt;table style="background-color: #fff; color: #202122;" data-mw="interface"&gt;
				&lt;col class="diff-marker" /&gt;
				&lt;col class="diff-content" /&gt;
				&lt;col class="diff-marker" /&gt;
				&lt;col class="diff-content" /&gt;
				&lt;tr class="diff-title" lang="nl"&gt;
				&lt;td colspan="2" style="background-color: #fff; color: #202122; text-align: center;"&gt;← Oudere versie&lt;/td&gt;
				&lt;td colspan="2" style="background-color: #fff; color: #202122; text-align: center;"&gt;Versie van 2 jul 2023 20:20&lt;/td&gt;
				&lt;/tr&gt;&lt;tr&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 401:&lt;/td&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 401:&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;::::::Dat kun je niet zeggen. Marketeers bijvoorbeeld hebben belang bij positieve informatie en het schrappen van zwarte bladzijden. En wat te denken van klimaatsceptici, coronasceptici, ... Dit geldt wederom voor elke wiki. [[Gebruiker:Wikiwerner|Wikiwerner]] ([[Overleg gebruiker:Wikiwerner|overleg]]) 2 jul 2023 12:00 (CEST)&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;::::::Dat kun je niet zeggen. Marketeers bijvoorbeeld hebben belang bij positieve informatie en het schrappen van zwarte bladzijden. En wat te denken van klimaatsceptici, coronasceptici, ... Dit geldt wederom voor elke wiki. [[Gebruiker:Wikiwerner|Wikiwerner]] ([[Overleg gebruiker:Wikiwerner|overleg]]) 2 jul 2023 12:00 (CEST)&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;:::::::@Mondo, de beoordeling of een bron al dan niet betrouwbaar is berust zeker niet op de mening van een individuele gebruiker van Wikipedia. Bij de beoordeling van de betrouwbaarheid van bronnen gaan we uit van de consensus daarover binnen het/de desbetreffende vakgebied(en). Zie o.a. [http://www.biografischportaal.nl/about/collecties het oordeel van het biografisch portaal] over biografische naslagwerken, een beoordeling in het kader van een samenwerkingsproject van tien wetenschappelijke en culturele instellingen. [[Gebruiker:Wikiwerner|Wikiwerner]] wijst zeer terecht al op het algemeen voorbehoud dat voor Wikipedia en soortgelijke projecten geldt. En zo zijn er nog wel meer kapstokken die gebruikt kunnen worden bij de beoordeling van de betrouwbaarheid van bronnen, zonder daarbij af te gaan op het eigen oordeel van de gebruiker. Ik vermoed dat [[Gebruiker:Ecritures|Ecritures]] zeker niet bedoeld zal hebben dat de beoordeling van de betrouwbaarheid van bronnen slechts 'een mening' zou zijn. [[Gebruiker:Gouwenaar|Gouwenaar]] ([[Overleg gebruiker:Gouwenaar|overleg]]) 2 jul 2023 20:12 (CEST)&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;:::::::@Mondo, de beoordeling of een bron al dan niet betrouwbaar is berust zeker niet op de mening van een individuele gebruiker van Wikipedia. Bij de beoordeling van de betrouwbaarheid van bronnen gaan we uit van de consensus daarover binnen het/de desbetreffende vakgebied(en). Zie o.a. [http://www.biografischportaal.nl/about/collecties het oordeel van het biografisch portaal] over biografische naslagwerken, een beoordeling in het kader van een samenwerkingsproject van tien wetenschappelijke en culturele instellingen. [[Gebruiker:Wikiwerner|Wikiwerner]] wijst zeer terecht al op het algemeen voorbehoud dat voor Wikipedia en soortgelijke projecten geldt. En zo zijn er nog wel meer kapstokken die gebruikt kunnen worden bij de beoordeling van de betrouwbaarheid van bronnen, zonder daarbij af te gaan op het eigen oordeel van de gebruiker. Ik vermoed dat [[Gebruiker:Ecritures|Ecritures]] zeker niet bedoeld zal hebben dat de beoordeling van de betrouwbaarheid van bronnen slechts 'een mening' zou zijn. [[Gebruiker:Gouwenaar|Gouwenaar]] ([[Overleg gebruiker:Gouwenaar|overleg]]) 2 jul 2023 20:12 (CEST)&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-empty diff-side-deleted"&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;::::::::Het ging Ecritures niet om bronnen, maar om uitspraken in zijn algemeenheid. Een uitspraak als “deze bron is onbetrouwbaar” omdat een aantal wikipedianen dat heeft gezegd is een mening, want er zijn ook wikipedianen die bronnen als Reliwiki wél betrouwbaar vinden, dus kun je niet zeggen dat er consensus is. [[Gebruiker:Mondo|Mondo]] ([[Overleg gebruiker:Mondo|overleg]]) 2 jul 2023 20:20 (CEST)&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;

&lt;!-- diff cache key nlwiki:diff:wikidiff2:1.12:old-64618155:rev-64618202:1.13.0 --&gt;
&lt;/table&gt;


read: False
type: Atom
title: Lijst van Formule 1 Grand Prix-overwinningen door Max Verstappen
authors: Stragier t
link:
https://nl.wikipedia.org/w/index.php?title=Lijst_van_Formule_1_Grand_Prix-overwinningen_door_Max_Verstappen&diff=64618201&oldid=64618199

description:
&lt;p&gt;&lt;span dir="auto"&gt;&lt;span class="autocomment"&gt;Aantal overwinningen per circuit&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;table style="background-color: #fff; color: #202122;" data-mw="interface"&gt;
				&lt;col class="diff-marker" /&gt;
				&lt;col class="diff-content" /&gt;
				&lt;col class="diff-marker" /&gt;
				&lt;col class="diff-content" /&gt;
				&lt;tr class="diff-title" lang="nl"&gt;
				&lt;td colspan="2" style="background-color: #fff; color: #202122; text-align: center;"&gt;← Oudere versie&lt;/td&gt;
				&lt;td colspan="2" style="background-color: #fff; color: #202122; text-align: center;"&gt;Versie van 2 jul 2023 20:20&lt;/td&gt;
				&lt;/tr&gt;&lt;tr&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 609:&lt;/td&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 609:&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|-&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|-&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| colspan=4 scope=row bgcolor=dfdfdf align=right|'''Totaal aantal Grand Prix-overwinningen:'''&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| colspan=4 scope=row bgcolor=dfdfdf align=right|'''Totaal aantal Grand Prix-overwinningen:'''&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| bgcolor=dfdfdf align=center|'''&lt;del style="font-weight: bold; text-decoration: none;"&gt;41&lt;/del&gt;'''&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| bgcolor=dfdfdf align=center|'''&lt;ins style="font-weight: bold; text-decoration: none;"&gt;42&lt;/ins&gt;'''&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|}&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|}&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
&lt;/tr&gt;

&lt;!-- diff cache key nlwiki:diff:wikidiff2:1.12:old-64618199:rev-64618201:1.13.0 --&gt;
&lt;/table&gt;


link: https://nl.wikipedia.org/w/index.php?title=McLaren_MCL60&diff=64618200&oldid=64522052
read: False
type: Atom
title: McLaren MCL60
authors: Balenda
description:
&lt;p&gt;OOS&lt;/p&gt;
&lt;table style="background-color: #fff; color: #202122;" data-mw="interface"&gt;
				&lt;col class="diff-marker" /&gt;
				&lt;col class="diff-content" /&gt;
				&lt;col class="diff-marker" /&gt;
				&lt;col class="diff-content" /&gt;
				&lt;tr class="diff-title" lang="nl"&gt;
				&lt;td colspan="2" style="background-color: #fff; color: #202122; text-align: center;"&gt;← Oudere versie&lt;/td&gt;
				&lt;td colspan="2" style="background-color: #fff; color: #202122; text-align: center;"&gt;Versie van 2 jul 2023 20:20&lt;/td&gt;
				&lt;/tr&gt;&lt;tr&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 24:&lt;/td&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 24:&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| huidig_coureurs             = {{0}}4. {{GB-VLAG}} [[Lando Norris]]&amp;lt;br&amp;gt;81. {{AU-VLAG}} [[Oscar Piastri]]&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| huidig_coureurs             = {{0}}4. {{GB-VLAG}} [[Lando Norris]]&amp;lt;br&amp;gt;81. {{AU-VLAG}} [[Oscar Piastri]]&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| debuut                      = [[Grand Prix Formule 1 van Bahrein 2023|GP van Bahrein 2023]]&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| debuut                      = [[Grand Prix Formule 1 van Bahrein 2023|GP van Bahrein 2023]]&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| races                       = &lt;del style="font-weight: bold; text-decoration: none;"&gt;8&lt;/del&gt;&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| races                       = &lt;ins style="font-weight: bold; text-decoration: none;"&gt;9&lt;/ins&gt;&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| overwinningen               = 0&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| overwinningen               = 0&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| poles                       = 0&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| poles                       = 0&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 107:&lt;/td&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 107:&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=cfcfff|17&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=cfcfff|17&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=cfcfff|13&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=cfcfff|13&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-empty diff-side-deleted"&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=dfffdf|5&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=|&amp;lt;!--|bgcolor=dfdfdf|&amp;lt;sup&amp;gt;'''4'''&amp;lt;/sup&amp;gt;2{{Pictogram poleposition|p=1|f=1}} TEST voor sprintrace uitslag 4de, race uitslag 2de met pole en snelste ronde--&amp;gt;&lt;/div&gt;&lt;/td&gt;
  &lt;td colspan="2" class="diff-empty diff-side-added"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=|&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=|&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=|&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=|&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 131:&lt;/td&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 131:&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=cfcfff|13&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=cfcfff|13&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=cfcfff|11&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=cfcfff|11&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-empty diff-side-deleted"&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=cfcfff|17&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=|&amp;lt;!--|bgcolor=dfdfdf|&amp;lt;sup&amp;gt;'''4'''&amp;lt;/sup&amp;gt;2{{Pictogram poleposition|p=1|f=1}} TEST voor sprintrace uitslag 4de, race uitslag 2de met pole en snelste ronde--&amp;gt;&lt;/div&gt;&lt;/td&gt;
  &lt;td colspan="2" class="diff-empty diff-side-added"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=|&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=|&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=|&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=|&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;

&lt;!-- diff cache key nlwiki:diff:wikidiff2:1.12:old-64522052:rev-64618200:1.13.0 --&gt;
&lt;/table&gt;


read: False
type: Atom
title: Lijst van Formule 1 Grand Prix-overwinningen door Max Verstappen
authors: Stragier t
link:
https://nl.wikipedia.org/w/index.php?title=Lijst_van_Formule_1_Grand_Prix-overwinningen_door_Max_Verstappen&diff=64618199&oldid=64618194

description:
&lt;p&gt;&lt;span dir="auto"&gt;&lt;span class="autocomment"&gt;Aantal overwinningen per Grand Prix&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;table style="background-color: #fff; color: #202122;" data-mw="interface"&gt;
				&lt;col class="diff-marker" /&gt;
				&lt;col class="diff-content" /&gt;
				&lt;col class="diff-marker" /&gt;
				&lt;col class="diff-content" /&gt;
				&lt;tr class="diff-title" lang="nl"&gt;
				&lt;td colspan="2" style="background-color: #fff; color: #202122; text-align: center;"&gt;← Oudere versie&lt;/td&gt;
				&lt;td colspan="2" style="background-color: #fff; color: #202122; text-align: center;"&gt;Versie van 2 jul 2023 20:20&lt;/td&gt;
				&lt;/tr&gt;&lt;tr&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 494:&lt;/td&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 494:&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|-&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|-&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| colspan=3 scope=row bgcolor=dfdfdf align=right|'''Totaal aantal Grand Prix-overwinningen:'''&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| colspan=3 scope=row bgcolor=dfdfdf align=right|'''Totaal aantal Grand Prix-overwinningen:'''&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| bgcolor=dfdfdf  align=center|'''&lt;del style="font-weight: bold; text-decoration: none;"&gt;41&lt;/del&gt;'''&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| bgcolor=dfdfdf  align=center|'''&lt;ins style="font-weight: bold; text-decoration: none;"&gt;42&lt;/ins&gt;'''&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|}&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|}&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
&lt;/tr&gt;

&lt;!-- diff cache key nlwiki:diff:wikidiff2:1.12:old-64618194:rev-64618199:1.13.0 --&gt;
&lt;/table&gt;


read: False
type: Atom
title: Wikipedia:Te beoordelen pagina's/Toegevoegd 20230618
authors: StuivertjeWisselen
link:
https://nl.wikipedia.org/w/index.php?title=Wikipedia:Te_beoordelen_pagina%27s/Toegevoegd_20230618&diff=64618198&oldid=64613406

description:
&lt;p&gt;&lt;span dir="auto"&gt;&lt;span class="autocomment"&gt;Toegevoegd 18/06; af te handelen vanaf 02/07&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;table style="background-color: #fff; color: #202122;" data-mw="interface"&gt;
				&lt;col class="diff-marker" /&gt;
				&lt;col class="diff-content" /&gt;
				&lt;col class="diff-marker" /&gt;
				&lt;col class="diff-content" /&gt;
				&lt;tr class="diff-title" lang="nl"&gt;
				&lt;td colspan="2" style="background-color: #fff; color: #202122; text-align: center;"&gt;← Oudere versie&lt;/td&gt;
				&lt;td colspan="2" style="background-color: #fff; color: #202122; text-align: center;"&gt;Versie van 2 jul 2023 20:20&lt;/td&gt;
				&lt;/tr&gt;&lt;tr&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 45:&lt;/td&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 45:&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;{{tbp-links|Terra ultima}}&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;{{tbp-links|Terra ultima}}&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;'''[[Wikipedia:Neutraal standpunt|POV]]''' &amp;amp;ndash; Het boek zelf lijkt E-waardig te zijn, echter niet de manier waarop het nu geschreven is. Ik wil het graag een kans geven. Daarom leg ik het aan de gemeenschap ter beoordeling voor. &amp;amp;ndash; {{Gebruiker:Drummingman/Handtekening}}[[Gebruiker:Drummingman|&amp;amp;zwj;]] 18 jun 2023 19:37 (CEST)&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;'''[[Wikipedia:Neutraal standpunt|POV]]''' &amp;amp;ndash; Het boek zelf lijkt E-waardig te zijn, echter niet de manier waarop het nu geschreven is. Ik wil het graag een kans geven. Daarom leg ik het aan de gemeenschap ter beoordeling voor. &amp;amp;ndash; {{Gebruiker:Drummingman/Handtekening}}[[Gebruiker:Drummingman|&amp;amp;zwj;]] 18 jun 2023 19:37 (CEST)&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
  &lt;td colspan="2" class="diff-empty diff-side-added"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;:Inmiddels heb ik flink gesnoeid en het van een intro voorzien. {{Gebruiker:Drummingman/Handtekening}}[[Gebruiker:Drummingman|&amp;amp;zwj;]] 18 jun 2023 20:16 (CEST)&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;:Inmiddels heb ik flink gesnoeid en het van een intro voorzien. {{Gebruiker:Drummingman/Handtekening}}[[Gebruiker:Drummingman|&amp;amp;zwj;]] 18 jun 2023 20:16 (CEST)&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;::Ziet er prima uit zo. Mooi opgeknapt, @[[Gebruiker:Drummingman|Drummingman]]!  Op zich is het nu wel een [[WP:BEG|beginnetje]], toch? [[Gebruiker:Mondo|Mondo]] ([[Overleg gebruiker:Mondo|overleg]]) 18 jun 2023 23:01 (CEST)&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;::Ziet er prima uit zo. Mooi opgeknapt, @[[Gebruiker:Drummingman|Drummingman]]!  Op zich is het nu wel een [[WP:BEG|beginnetje]], toch? [[Gebruiker:Mondo|Mondo]] ([[Overleg gebruiker:Mondo|overleg]]) 18 jun 2023 23:01 (CEST)&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;:::Dankjewel, ik trek de nominatie in. {{Gebruiker:Drummingman/Handtekening}}[[Gebruiker:Drummingman|&amp;amp;zwj;]] 19 jun 2023 18:14 (CEST)&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;:::Dankjewel, ik trek de nominatie in. {{Gebruiker:Drummingman/Handtekening}}[[Gebruiker:Drummingman|&amp;amp;zwj;]] 19 jun 2023 18:14 (CEST)&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-empty diff-side-deleted"&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;a class="mw-diff-movedpara-left" title="Deze alinea is verplaatst. Klik om naar de nieuwe locatie te springen." href="#movedpara_8_0_rhs"&gt;&amp;#x26AB;&lt;/a&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;&lt;a name="movedpara_4_0_lhs"&gt;&lt;/a&gt;{{einde}}&lt;/div&gt;&lt;/td&gt;
  &lt;td colspan="2" class="diff-empty diff-side-added"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;== [[Lijst van kattenrassen]] ==&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;== [[Lijst van kattenrassen]] ==&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;{{tbp-links|Lijst van kattenrassen}}&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;{{tbp-links|Lijst van kattenrassen}}&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 58:&lt;/td&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 57:&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;::Ik heb al enkele foto's toegevoegd nu... [[Gebruiker:Riki|Riki]] ([[Overleg gebruiker:Riki|overleg]]) 20 jun 2023 09:08 (CEST)&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;::Ik heb al enkele foto's toegevoegd nu... [[Gebruiker:Riki|Riki]] ([[Overleg gebruiker:Riki|overleg]]) 20 jun 2023 09:08 (CEST)&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;:Inmiddels al heel veel foto's (60+?) en van sommige rassen twee verschillende plus een beschrijving. Ook bronnen zijn toegevoegd. Hier wordt duidelijk hard aan gewerkt. Waardevol! [[Speciaal:Bijdragen/2A02:A468:3711:1:6966:7153:F632:6EA1|2A02:A468:3711:1:6966:7153:F632:6EA1]] 25 jun 2023 07:27 (CEST)&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;:Inmiddels al heel veel foto's (60+?) en van sommige rassen twee verschillende plus een beschrijving. Ook bronnen zijn toegevoegd. Hier wordt duidelijk hard aan gewerkt. Waardevol! [[Speciaal:Bijdragen/2A02:A468:3711:1:6966:7153:F632:6EA1|2A02:A468:3711:1:6966:7153:F632:6EA1]] 25 jun 2023 07:27 (CEST)&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-empty diff-side-deleted"&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;{{afh}}''Ik zie geen reden om deze lijst te verwijderen. [[Gebruiker:StuivertjeWisselen|StuivertjeWisselen]] ([[Overleg gebruiker:StuivertjeWisselen|overleg]]) 2 jul 2023 20:20 (CEST)''&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
  &lt;td colspan="2" class="diff-empty diff-side-added"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-empty diff-side-deleted"&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;a class="mw-diff-movedpara-right" title="Deze alinea is verplaatst. Klik om naar de oude locatie te springen." href="#movedpara_4_0_lhs"&gt;&amp;#x26AB;&lt;/a&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;&lt;a name="movedpara_8_0_rhs"&gt;&lt;/a&gt;{{einde}}&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;== [[Auditeren (Scientology)]] ==&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;== [[Auditeren (Scientology)]] ==&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;{{tbp-links|Auditeren (Scientology)}}&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;{{tbp-links|Auditeren (Scientology)}}&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;

&lt;!-- diff cache key nlwiki:diff:wikidiff2:1.12:old-64613406:rev-64618198:1.13.0 --&gt;
&lt;/table&gt;


link: https://nl.wikipedia.org/w/index.php?title=Ferrari_SF-23&diff=64618197&oldid=64522076
read: False
type: Atom
title: Ferrari SF-23
authors: Balenda
description:
&lt;p&gt;OOS&lt;/p&gt;
&lt;table style="background-color: #fff; color: #202122;" data-mw="interface"&gt;
				&lt;col class="diff-marker" /&gt;
				&lt;col class="diff-content" /&gt;
				&lt;col class="diff-marker" /&gt;
				&lt;col class="diff-content" /&gt;
				&lt;tr class="diff-title" lang="nl"&gt;
				&lt;td colspan="2" style="background-color: #fff; color: #202122; text-align: center;"&gt;← Oudere versie&lt;/td&gt;
				&lt;td colspan="2" style="background-color: #fff; color: #202122; text-align: center;"&gt;Versie van 2 jul 2023 20:19&lt;/td&gt;
				&lt;/tr&gt;&lt;tr&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 28:&lt;/td&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 28:&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| huidig_coureurs             = 16. {{MC-VLAG}} [[Charles Leclerc (autocoureur)|Charles Leclerc]]&amp;lt;br&amp;gt;55. {{ES-VLAG}} [[Carlos Sainz jr.]]&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| huidig_coureurs             = 16. {{MC-VLAG}} [[Charles Leclerc (autocoureur)|Charles Leclerc]]&amp;lt;br&amp;gt;55. {{ES-VLAG}} [[Carlos Sainz jr.]]&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| debuut                      = [[Grand Prix Formule 1 van Bahrein 2023|GP van Bahrein 2023]]&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| debuut                      = [[Grand Prix Formule 1 van Bahrein 2023|GP van Bahrein 2023]]&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| races                       = &lt;del style="font-weight: bold; text-decoration: none;"&gt;8&lt;/del&gt;&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| races                       = &lt;ins style="font-weight: bold; text-decoration: none;"&gt;9&lt;/ins&gt;&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| overwinningen               = 0&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| overwinningen               = 0&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| poles                       = 1&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| poles                       = 1&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 110:&lt;/td&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 110:&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=cfcfff|11&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=cfcfff|11&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=dfffdf|4&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=dfffdf|4&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-empty diff-side-deleted"&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=dfdfdf|2&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=|&amp;lt;!--|bgcolor=dfdfdf|&amp;lt;sup&amp;gt;'''4'''&amp;lt;/sup&amp;gt;2{{Pictogram poleposition|p=1|f=1}} TEST voor sprintrace uitslag 4de, race uitslag 2de met pole en snelste ronde--&amp;gt;&lt;/div&gt;&lt;/td&gt;
  &lt;td colspan="2" class="diff-empty diff-side-added"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=|&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=|&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=|&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=|&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 134:&lt;/td&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 134:&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=dfffdf|5&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=dfffdf|5&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=dfffdf|5&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=dfffdf|5&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-empty diff-side-deleted"&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=dfffdf|&amp;lt;sup&amp;gt;'''3'''&amp;lt;/sup&amp;gt;4&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=|&amp;lt;!--|bgcolor=dfdfdf|&amp;lt;sup&amp;gt;'''4'''&amp;lt;/sup&amp;gt;2{{Pictogram poleposition|p=1|f=1}} TEST voor sprintrace uitslag 4de, race uitslag 2de met pole en snelste ronde--&amp;gt;&lt;/div&gt;&lt;/td&gt;
  &lt;td colspan="2" class="diff-empty diff-side-added"&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=|&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=|&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=|&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|bgcolor=|&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;

&lt;!-- diff cache key nlwiki:diff:wikidiff2:1.12:old-64522076:rev-64618197:1.13.0 --&gt;
&lt;/table&gt;


read: False
type: Atom
title: Oekraïens tegenoffensief 2023
authors: Sidebart
link:
https://nl.wikipedia.org/w/index.php?title=Oekraïens_tegenoffensief_2023&diff=64618196&oldid=64618102

description:
&lt;p&gt;&lt;/p&gt;
&lt;table style="background-color: #fff; color: #202122;" data-mw="interface"&gt;
				&lt;col class="diff-marker" /&gt;
				&lt;col class="diff-content" /&gt;
				&lt;col class="diff-marker" /&gt;
				&lt;col class="diff-content" /&gt;
				&lt;tr class="diff-title" lang="nl"&gt;
				&lt;td colspan="2" style="background-color: #fff; color: #202122; text-align: center;"&gt;← Oudere versie&lt;/td&gt;
				&lt;td colspan="2" style="background-color: #fff; color: #202122; text-align: center;"&gt;Versie van 2 jul 2023 20:19&lt;/td&gt;
				&lt;/tr&gt;&lt;tr&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 69:&lt;/td&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 69:&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;Volgens Oekraïense functionarissen rukten Oekraïense troepen, in een dag tijd, tot 1 kilometer op richting [[Berdjansk]].&amp;lt;ref name=":7"&amp;gt;{{Citeer web |url=https://www.telegraph.co.uk/world-news/2023/06/13/ukraine-russia-war-latest-news-counter-offensive-donetsk/ |titel=Ukraine-Russia war latest: Ukrainian forces advance in Zaporizhzhia |datum=2023-06-13 |bezochtdatum=2023-06-13 |werk=Telegraph |taal=en}}&amp;lt;/ref&amp;gt;&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;Volgens Oekraïense functionarissen rukten Oekraïense troepen, in een dag tijd, tot 1 kilometer op richting [[Berdjansk]].&amp;lt;ref name=":7"&amp;gt;{{Citeer web |url=https://www.telegraph.co.uk/world-news/2023/06/13/ukraine-russia-war-latest-news-counter-offensive-donetsk/ |titel=Ukraine-Russia war latest: Ukrainian forces advance in Zaporizhzhia |datum=2023-06-13 |bezochtdatum=2023-06-13 |werk=Telegraph |taal=en}}&amp;lt;/ref&amp;gt;&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-empty diff-side-deleted"&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-empty diff-side-deleted"&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;Eind juni staken Oekraiense troepen bij de stad Cherson de Dnepr over en wisten een klein bruggenhoofd bij de in 2022 zwaar beschadigde Antonivsky-verkeersbrug te slaan aan de rand van [[Olesjky]].&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;== Bronnen/referenties ==&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;== Bronnen/referenties ==&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;

&lt;!-- diff cache key nlwiki:diff:wikidiff2:1.12:old-64618102:rev-64618196:1.13.0 --&gt;
&lt;/table&gt;


link: https://nl.wikipedia.org/w/index.php?title=Adrián_Marín_Gómez&diff=64618195&oldid=61369015
read: False
type: Atom
title: Adrián Marín Gómez
authors: G SBPW
description:
&lt;p&gt;&lt;/p&gt;
&lt;table style="background-color: #fff; color: #202122;" data-mw="interface"&gt;
				&lt;col class="diff-marker" /&gt;
				&lt;col class="diff-content" /&gt;
				&lt;col class="diff-marker" /&gt;
				&lt;col class="diff-content" /&gt;
				&lt;tr class="diff-title" lang="nl"&gt;
				&lt;td colspan="2" style="background-color: #fff; color: #202122; text-align: center;"&gt;← Oudere versie&lt;/td&gt;
				&lt;td colspan="2" style="background-color: #fff; color: #202122; text-align: center;"&gt;Versie van 2 jul 2023 20:19&lt;/td&gt;
				&lt;/tr&gt;&lt;tr&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 1:&lt;/td&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 1:&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;{{Infobox voetballer&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;{{Infobox voetballer&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| spelernaam                  = Adrián Marín &lt;del style="font-weight: bold; text-decoration: none;"&gt;Gómez&lt;/del&gt;&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| spelernaam                  = Adrián Marín &lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| volledigenaam               = Adrián Marín Gómez&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| volledigenaam               = Adrián Marín Gómez&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| afbeelding                  = &lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| afbeelding                  = &lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 11:&lt;/td&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 11:&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| stadvanoverlijden           = &lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| stadvanoverlijden           = &lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| landvanoverlijden           = &lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| landvanoverlijden           = &lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| lengte                      = &lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| lengte                      = &lt;ins style="font-weight: bold; text-decoration: none;"&gt;181&lt;/ins&gt;&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| been                        = Links&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| been                        = Links&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| huidigeclub                 = {{&lt;del style="font-weight: bold; text-decoration: none;"&gt;ES&lt;/del&gt;-VLAG}} [[&lt;del style="font-weight: bold; text-decoration: none;"&gt;Deportivo&lt;/del&gt; &lt;del style="font-weight: bold; text-decoration: none;"&gt;Alavés&lt;/del&gt;]]&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| huidigeclub                 = {{&lt;ins style="font-weight: bold; text-decoration: none;"&gt;PT&lt;/ins&gt;-VLAG}} [[&lt;ins style="font-weight: bold; text-decoration: none;"&gt;SC&lt;/ins&gt; &lt;ins style="font-weight: bold; text-decoration: none;"&gt;Braga&lt;/ins&gt;]]&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| rugnummer                   = &lt;del style="font-weight: bold; text-decoration: none;"&gt;17&lt;/del&gt;&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| rugnummer                   = &lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| positie                     = [[Vleugelverdediger|Linksback]]&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| positie                     = [[Vleugelverdediger|Linksback]]&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| contracttot                 = 30 juni &lt;del style="font-weight: bold; text-decoration: none;"&gt;2021&lt;/del&gt;&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| contracttot                 = 30 juni &lt;ins style="font-weight: bold; text-decoration: none;"&gt;2026&lt;/ins&gt;&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| jeugdjaren                  = –2009 &amp;lt;br /&amp;gt; 2009–2014&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| jeugdjaren                  = –2009 &amp;lt;br /&amp;gt; 2009–2014&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| jeugdteams                  = {{ES-VLAG}} San Ginés &amp;lt;br /&amp;gt; {{ES-VLAG}} [[Villarreal CF]]&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| jeugdteams                  = {{ES-VLAG}} San Ginés &amp;lt;br /&amp;gt; {{ES-VLAG}} [[Villarreal CF]]&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| seizoen                     = 2013–2014 &amp;lt;br /&amp;gt; 2013–2016 &amp;lt;br /&amp;gt; 2014–2018&amp;lt;br /&amp;gt; 2016–2017&amp;lt;br /&amp;gt; &lt;del style="font-weight: bold; text-decoration: none;"&gt;2018–&lt;/del&gt;&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| seizoen                     = 2013–2014 &amp;lt;br /&amp;gt; 2013–2016 &amp;lt;br /&amp;gt; 2014–2018&amp;lt;br /&amp;gt; 2016–2017&amp;lt;br /&amp;gt; &lt;ins style="font-weight: bold; text-decoration: none;"&gt;2018–2021 &amp;lt;br/&amp;gt;2021-2022 &amp;lt;br/&amp;gt;2021-2022 &amp;lt;br/&amp;gt;2022-2023 &amp;lt;br/&amp;gt;2023-&lt;/ins&gt;&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| club                        = {{ES-VLAG}} [[Villarreal CF]] C &amp;lt;br /&amp;gt; {{ES-VLAG}} [[Villarreal CF]] B &amp;lt;br /&amp;gt; {{ES-VLAG}} [[Villarreal CF]]&amp;lt;br /&amp;gt;→ {{ES-VLAG}} [[CD Leganés]]&amp;lt;br /&amp;gt; {{ES-VLAG}} [[Deportivo Alavés]]&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| club                        = {{ES-VLAG}} [[Villarreal CF]] C &amp;lt;br /&amp;gt; {{ES-VLAG}} [[Villarreal CF]] B &amp;lt;br /&amp;gt; {{ES-VLAG}} [[Villarreal CF]]&amp;lt;br /&amp;gt;→ {{ES-VLAG}} [[CD Leganés]]&amp;lt;br /&amp;gt; {{ES-VLAG}} [[Deportivo Alavés&lt;ins style="font-weight: bold; text-decoration: none;"&gt;]]&amp;lt;br /&amp;gt;{{ES-VLAG}} [[Granada CF]]&amp;lt;br /&amp;gt;→ {{PT-VLAG}} [[FC Famalicão]]&amp;lt;br /&amp;gt;{{PT-VLAG}} [[Gil Vicente FC]]&amp;lt;br /&amp;gt;{{PT-VLAG}} [[SC Braga&lt;/ins&gt;]]&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| wedstr(goals)               = 15{{0|00}}(0)&amp;lt;br /&amp;gt; 21{{0|00}}(1)&amp;lt;br /&amp;gt; 18{{0|00}}(0)&amp;lt;br /&amp;gt;13{{0|00}}(0)&amp;lt;br /&amp;gt;&lt;del style="font-weight: bold; text-decoration: none;"&gt;20&lt;/del&gt;{{0|00}}(0)&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| wedstr(goals)               = 15{{0|00}}(0)&amp;lt;br /&amp;gt; 21{{0|00}}(1)&amp;lt;br /&amp;gt; 18{{0|00}}(0)&amp;lt;br /&amp;gt;13{{0|00}}(0)&amp;lt;br /&amp;gt;&lt;ins style="font-weight: bold; text-decoration: none;"&gt;23{{0|00}}(0)&amp;lt;br /&amp;gt;9{{0|00}}(0)&amp;lt;br /&amp;gt;29{{0|00}}(4)&amp;lt;br /&amp;gt;31{{0|00}}(0)&amp;lt;br /&amp;gt;0&lt;/ins&gt;{{0|00}}(0)&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| interlandjaren              = 2014&amp;lt;br /&amp;gt;2014&amp;lt;br /&amp;gt;2014–2016&amp;lt;br /&amp;gt;&lt;del style="font-weight: bold; text-decoration: none;"&gt;2016–&lt;/del&gt;&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| interlandjaren              = 2014&amp;lt;br /&amp;gt;2014&amp;lt;br /&amp;gt;2014–2016&amp;lt;br /&amp;gt;&lt;ins style="font-weight: bold; text-decoration: none;"&gt;2016&lt;/ins&gt;&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| interlandteam               = {{ES-VLAG}} Spanje –17&amp;lt;br /&amp;gt;{{ES-VLAG}} Spanje –18&amp;lt;br /&amp;gt;{{ES-VLAG}} [[Spaans voetbalelftal onder 19 (mannen)|Spanje –19]]&amp;lt;br /&amp;gt;{{ES-VLAG}} [[Spaans voetbalelftal onder 21 (mannen)|Spanje –21]]&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| interlandteam               = {{ES-VLAG}} Spanje –17&amp;lt;br /&amp;gt;{{ES-VLAG}} Spanje –18&amp;lt;br /&amp;gt;{{ES-VLAG}} [[Spaans voetbalelftal onder 19 (mannen)|Spanje –19]]&amp;lt;br /&amp;gt;{{ES-VLAG}} [[Spaans voetbalelftal onder 21 (mannen)|Spanje –21]]&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| interlandwedstrijden(goals) = 4{{0|00}}(0)&amp;lt;br /&amp;gt;3{{0|00}}(0)&amp;lt;br /&amp;gt;3{{0|00}}(3)&amp;lt;br /&amp;gt;1{{0|00}}(0)&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| interlandwedstrijden(goals) = 4{{0|00}}(0)&amp;lt;br /&amp;gt;3{{0|00}}(0)&amp;lt;br /&amp;gt;3{{0|00}}(3)&amp;lt;br /&amp;gt;1{{0|00}}(0)&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| trainersjaren               = &lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| trainersjaren               = &lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| getraindeclubs              = &lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| getraindeclubs              = &lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| clubupdate                  = &lt;del style="font-weight: bold; text-decoration: none;"&gt;4&lt;/del&gt; &lt;del style="font-weight: bold; text-decoration: none;"&gt;september&lt;/del&gt; &lt;del style="font-weight: bold; text-decoration: none;"&gt;2020&lt;/del&gt;&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| clubupdate                  = &lt;ins style="font-weight: bold; text-decoration: none;"&gt;2&lt;/ins&gt; &lt;ins style="font-weight: bold; text-decoration: none;"&gt;juli&lt;/ins&gt; &lt;ins style="font-weight: bold; text-decoration: none;"&gt;2023&lt;/ins&gt;&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| landupdate                  = &lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| landupdate                  = &lt;ins style="font-weight: bold; text-decoration: none;"&gt;2 juli 2023&lt;/ins&gt;&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;}}&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;}}&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;'''Adrián Marín Gómez''' ([[Torre-Pacheco]], [[9 januari]] [[1997]]) is een [[Spanje|Spaans]] [[betaald voetbal|voetballer]] die doorgaans als [[Vleugelverdediger|linksback]] speelt. &lt;del style="font-weight: bold; text-decoration: none;"&gt;Hij&lt;/del&gt; &lt;del style="font-weight: bold; text-decoration: none;"&gt;verruilde&lt;/del&gt; &lt;del style="font-weight: bold; text-decoration: none;"&gt;[[Villarreal&lt;/del&gt; &lt;del style="font-weight: bold; text-decoration: none;"&gt;CF]]&lt;/del&gt; &lt;del style="font-weight: bold; text-decoration: none;"&gt;in&lt;/del&gt; &lt;del style="font-weight: bold; text-decoration: none;"&gt;augustus&lt;/del&gt; &lt;del style="font-weight: bold; text-decoration: none;"&gt;2018&lt;/del&gt; &lt;del style="font-weight: bold; text-decoration: none;"&gt;transfervrij&lt;/del&gt; &lt;del style="font-weight: bold; text-decoration: none;"&gt;voor&lt;/del&gt; [[&lt;del style="font-weight: bold; text-decoration: none;"&gt;Deportivo&lt;/del&gt; &lt;del style="font-weight: bold; text-decoration: none;"&gt;Alavés&lt;/del&gt;]].&amp;lt;ref&amp;gt;[https://www.transfermarkt.de/adrian-marin/profil/spieler/295414 Spelersprofiel op Transfermarkt]&lt;del style="font-weight: bold; text-decoration: none;"&gt;. [https://web.archive.org/web/20211028220607/https://www.transfermarkt.de/adrian-marin/profil/spieler/295414 Gearchiveerd] op 28 oktober 2021&lt;/del&gt;.&amp;lt;/ref&amp;gt;&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;'''Adrián Marín Gómez''' ([[Torre-Pacheco]], [[9 januari]] [[1997]]) is een [[Spanje|Spaans]] [[betaald voetbal|voetballer]] die doorgaans als [[Vleugelverdediger|linksback]] speelt. &lt;ins style="font-weight: bold; text-decoration: none;"&gt;Sinds&lt;/ins&gt; &lt;ins style="font-weight: bold; text-decoration: none;"&gt;1&lt;/ins&gt; &lt;ins style="font-weight: bold; text-decoration: none;"&gt;juli&lt;/ins&gt; &lt;ins style="font-weight: bold; text-decoration: none;"&gt;2023&lt;/ins&gt; &lt;ins style="font-weight: bold; text-decoration: none;"&gt;speelt&lt;/ins&gt; &lt;ins style="font-weight: bold; text-decoration: none;"&gt;hij&lt;/ins&gt; &lt;ins style="font-weight: bold; text-decoration: none;"&gt;bij&lt;/ins&gt; &lt;ins style="font-weight: bold; text-decoration: none;"&gt;de&lt;/ins&gt; &lt;ins style="font-weight: bold; text-decoration: none;"&gt;Portugese subtopper&lt;/ins&gt; [[&lt;ins style="font-weight: bold; text-decoration: none;"&gt;SC&lt;/ins&gt; &lt;ins style="font-weight: bold; text-decoration: none;"&gt;Braga&lt;/ins&gt;]].&amp;lt;ref&amp;gt;[https://www.transfermarkt.de/adrian-marin/profil/spieler/295414 Spelersprofiel op Transfermarkt].&amp;lt;/ref&amp;gt;&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;== Clubcarrière ==&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;== Clubcarrière ==&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;

&lt;!-- diff cache key nlwiki:diff:wikidiff2:1.12:old-61369015:rev-64618195:1.13.0 --&gt;
&lt;/table&gt;


read: False
type: Atom
title: Lijst van Formule 1 Grand Prix-overwinningen door Max Verstappen
authors: Stragier t
link:
https://nl.wikipedia.org/w/index.php?title=Lijst_van_Formule_1_Grand_Prix-overwinningen_door_Max_Verstappen&diff=64618194&oldid=64618189

description:
&lt;p&gt;&lt;span dir="auto"&gt;&lt;span class="autocomment"&gt;Aantal overwinningen per circuit&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;table style="background-color: #fff; color: #202122;" data-mw="interface"&gt;
				&lt;col class="diff-marker" /&gt;
				&lt;col class="diff-content" /&gt;
				&lt;col class="diff-marker" /&gt;
				&lt;col class="diff-content" /&gt;
				&lt;tr class="diff-title" lang="nl"&gt;
				&lt;td colspan="2" style="background-color: #fff; color: #202122; text-align: center;"&gt;← Oudere versie&lt;/td&gt;
				&lt;td colspan="2" style="background-color: #fff; color: #202122; text-align: center;"&gt;Versie van 2 jul 2023 20:18&lt;/td&gt;
				&lt;/tr&gt;&lt;tr&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 506:&lt;/td&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 506:&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;!scope=col|Overwinningen&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;!scope=col|Overwinningen&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|-&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|-&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;!rowspan=&lt;del style="font-weight: bold; text-decoration: none;"&gt;2&lt;/del&gt;|1&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;!rowspan=&lt;ins style="font-weight: bold; text-decoration: none;"&gt;1&lt;/ins&gt;|1&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| {{AT-VLAG}} [[Red Bull Ring]]&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| {{AT-VLAG}} [[Red Bull Ring]]&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| [[Spielberg (Stiermarken)|Spielberg]]&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| [[Spielberg (Stiermarken)|Spielberg]]&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| [[Grand Prix Formule 1 van Oostenrijk 2018|2018]], [[Grand Prix Formule 1 van Oostenrijk 2019|2019]], [[Grand Prix Formule 1 van Stiermarken 2021|2021]], [[Grand Prix Formule 1 van Oostenrijk 2021|2021]]&amp;lt;ref&amp;gt;Op de Red Bull Ring werden in 2021 twee Grands Prix gehouden. Verstappen won deze allebei.&amp;lt;/ref&amp;gt;&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| [[Grand Prix Formule 1 van Oostenrijk 2018|2018]], [[Grand Prix Formule 1 van Oostenrijk 2019|2019]], [[Grand Prix Formule 1 van Stiermarken 2021|2021]], [[Grand Prix Formule 1 van Oostenrijk 2021|2021]]&amp;lt;ref&amp;gt;Op de Red Bull Ring werden in 2021 twee Grands Prix gehouden. Verstappen won deze allebei.&amp;lt;/ref&amp;gt;&lt;ins style="font-weight: bold; text-decoration: none;"&gt;, [[Grand Prix Formule 1 van Oostenrijk 2023|2023]]&lt;/ins&gt;&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|rowspan=&lt;del style="font-weight: bold; text-decoration: none;"&gt;2&lt;/del&gt; align=center|&lt;del style="font-weight: bold; text-decoration: none;"&gt;4&lt;/del&gt;&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|rowspan=&lt;ins style="font-weight: bold; text-decoration: none;"&gt;1&lt;/ins&gt; align=center|&lt;ins style="font-weight: bold; text-decoration: none;"&gt;5&lt;/ins&gt;&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|-&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|-&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-empty diff-side-deleted"&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;!rowspan=1|2&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| {{MX-VLAG}} [[Autódromo Hermanos Rodríguez]]&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| {{MX-VLAG}} [[Autódromo Hermanos Rodríguez]]&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| [[Mexico-Stad]]&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| [[Mexico-Stad]]&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| [[Grand Prix Formule 1 van Mexico 2017|2017]], [[Grand Prix Formule 1 van Mexico 2018|2018]], [[Grand Prix Formule 1 van Mexico-Stad 2021|2021]], [[Grand Prix Formule 1 van Mexico-Stad 2022|2022]]&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;| [[Grand Prix Formule 1 van Mexico 2017|2017]], [[Grand Prix Formule 1 van Mexico 2018|2018]], [[Grand Prix Formule 1 van Mexico-Stad 2021|2021]], [[Grand Prix Formule 1 van Mexico-Stad 2022|2022]]&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-empty diff-side-deleted"&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|rowspan=1 align=center|4&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|-&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;|-&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;! rowspan=2 scope=row|3&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;! rowspan=2 scope=row|3&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;

&lt;!-- diff cache key nlwiki:diff:wikidiff2:1.12:old-64618189:rev-64618194:1.13.0 --&gt;
&lt;/table&gt;


link: https://nl.wikipedia.org/w/index.php?title=Hart_en_vaatstelsel&diff=64618193&oldid=64618060
read: False
type: Atom
title: Hart en vaatstelsel
authors: ChristiaanPR
description:
&lt;p&gt;&lt;span dir="auto"&gt;&lt;span class="autocomment"&gt;Evolutie van het hart&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;table style="background-color: #fff; color: #202122;" data-mw="interface"&gt;
				&lt;col class="diff-marker" /&gt;
				&lt;col class="diff-content" /&gt;
				&lt;col class="diff-marker" /&gt;
				&lt;col class="diff-content" /&gt;
				&lt;tr class="diff-title" lang="nl"&gt;
				&lt;td colspan="2" style="background-color: #fff; color: #202122; text-align: center;"&gt;← Oudere versie&lt;/td&gt;
				&lt;td colspan="2" style="background-color: #fff; color: #202122; text-align: center;"&gt;Versie van 2 jul 2023 20:18&lt;/td&gt;
				&lt;/tr&gt;&lt;tr&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 115:&lt;/td&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 115:&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt; | onderschrift3 = Hart&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt; | onderschrift3 = Hart&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;}}&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;}}&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-empty diff-side-deleted"&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;{{Clearall}}&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;{{Clearall}}&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-empty diff-side-deleted"&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;Hierin zijn&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-empty diff-side-deleted"&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;* BL basale laminae&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-empty diff-side-deleted"&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;* CE coelomisch epitheel&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-empty diff-side-deleted"&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;* [[Coeloom|CO coelomische holte]]&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-empty diff-side-deleted"&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;* [[Maag-darmstelsel|DT spijsverteringskanaal]]&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-empty diff-side-deleted"&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;* HS hemaal systeem&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-empty diff-side-deleted"&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;* MES mesenterisch coelomisch epitheel&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-empty diff-side-deleted"&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;* [[Orgaan|V organen]]&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-empty diff-side-deleted"&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;Vanuit organismen zonder circulatie ontstonden organismen met coelomische circulatie, vervolgens het hemaal systeem en vanuit daar het hart.&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;Vanuit organismen zonder circulatie ontstonden organismen met coelomische circulatie, vervolgens het hemaal systeem en vanuit daar het hart.&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 129:&lt;/td&gt;
  &lt;td colspan="2" class="diff-lineno"&gt;Regel 139:&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;Zo'n 700-600 miljoen jaar geleden ontwikkelde zich het mesoderm bij de voorouder van de [[Bilateria]]. In het mesoderm ontstond het coeloom doordat openingen in het mesoderm bedekt werden met [[mesotheel]]. Dit doorlatende [[epitheel]] vormde zich uit mesoderme cellen die zich met hun apicale zijde richtten naar het coeloom en met hun basale zijde richting de opening. Met deze bekleding kon het coeloom gevuld worden met een coelomische vloeistof.&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;Zo'n 700-600 miljoen jaar geleden ontwikkelde zich het mesoderm bij de voorouder van de [[Bilateria]]. In het mesoderm ontstond het coeloom doordat openingen in het mesoderm bedekt werden met [[mesotheel]]. Dit doorlatende [[epitheel]] vormde zich uit mesoderme cellen die zich met hun apicale zijde richtten naar het coeloom en met hun basale zijde richting de opening. Met deze bekleding kon het coeloom gevuld worden met een coelomische vloeistof.&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker" data-marker="−"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;Mogelijk betrof het in eerste instantie een [[hydroskelet]] voor het weke lichaam van de vroege Bilateria, maar het kan ook dienen voor transport. Dit vindt plaats met [[Trilhaar|trilharen]] (''cilia''), [[spiercontractie]] van de lichaamswand of contractie van myo-epitheliale cellen. Myo-epitheliale cellen zijn mesotheelcellen die een [[Spier (anatomie)|spierfunctie]] &lt;del style="font-weight: bold; text-decoration: none;"&gt;(&lt;/del&gt;''myo-'' voor spier&lt;del style="font-weight: bold; text-decoration: none;"&gt;)&lt;/del&gt; hebben verworven en vaten met deze cellen vormden de eerste specifieke [[pomp (machine)|pomp]] en daarmee het eerste hart.&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker" data-marker="+"&gt;&lt;/td&gt;
  &lt;td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;Mogelijk betrof het in eerste instantie een [[hydroskelet]] voor het weke lichaam van de vroege Bilateria, maar het kan ook dienen voor transport. Dit vindt plaats met [[Trilhaar|trilharen]] (''cilia''), [[spiercontractie]] van de lichaamswand of contractie van myo-epitheliale cellen. Myo-epitheliale cellen zijn mesotheelcellen die een [[Spier (anatomie)|spierfunctie]]&lt;ins style="font-weight: bold; text-decoration: none;"&gt;,&lt;/ins&gt; ''myo-'' voor spier&lt;ins style="font-weight: bold; text-decoration: none;"&gt;,&lt;/ins&gt; hebben verworven en vaten met deze cellen vormden de eerste specifieke [[pomp (machine)|pomp]] en daarmee het eerste hart.&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;br /&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;Zo vormde zich de eerste circulatie waarmee de beperkingen van de directe diffusie overwonnen werden. Het coeloom bestaat echter vaak uit meerdere compartimenten, bij zoogdieren onder meer het [[Pericard|hartzakje]], de [[pleurale ruimte]] en de peritoneale ruimte. Door de compartimentalisering is coelomische circulatie beperkt tot binnen de compartimenten.&lt;/div&gt;&lt;/td&gt;
  &lt;td class="diff-marker"&gt;&lt;/td&gt;
  &lt;td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"&gt;&lt;div&gt;Zo vormde zich de eerste circulatie waarmee de beperkingen van de directe diffusie overwonnen werden. Het coeloom bestaat echter vaak uit meerdere compartimenten, bij zoogdieren onder meer het [[Pericard|hartzakje]], de [[pleurale ruimte]] en de peritoneale ruimte. Door de compartimentalisering is coelomische circulatie beperkt tot binnen de compartimenten.&lt;/div&gt;&lt;/td&gt;
&lt;/tr&gt;

&lt;!-- diff cache key nlwiki:diff:wikidiff2:1.12:old-64618060:rev-64618193:1.13.0 --&gt;
&lt;/table&gt;


