投稿時間:2022-06-27 00:12:20 RSSフィード2022-06-27 00:00 分まとめ(19件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
Ruby	Rubyタグが付けられた新着投稿 - Qiita	複合テストコードのまとめ	https://qiita.com/NaoyukineoG/items/83d57a781eddc0a28fcb	部分	2022-06-26 23:43:35
Ruby	Railsタグが付けられた新着投稿 - Qiita	複合テストコードのまとめ	https://qiita.com/NaoyukineoG/items/83d57a781eddc0a28fcb	部分	2022-06-26 23:43:35
技術ブログ	Developers.IO	AWS Step FunctionsでPayloadサイズ上限256KBを超えた際の挙動を確認してみた	https://dev.classmethod.jp/articles/the-operation-when-the-maximum-payload-size-limit-of-256kb-was-exceeded-in-aws-step-functions/	whatisawsste	2022-06-26 14:53:50
技術ブログ	Developers.IO	CloudFrontでモバイルデバイスのOS判別ができるCloudFront-Is-Android-Viewer/CloudFront-Is-IOS-Viewerヘッダを確認してみた	https://dev.classmethod.jp/articles/cloudfront-mobile-os-detection/	amazon	2022-06-26 14:41:30
海外TECH	MakeUseOf	How to Enable the Last Active Click Feature for Taskbar Icons on Windows 10 & 11	https://www.makeuseof.com/windows-last-active-click-taskbar/	windows	2022-06-26 14:15:13
海外TECH	DEV Community	New lessons on React and Programming Memes.	https://dev.to/prudence97/new-lessons-on-react-and-programming-memes-5fg	New lessons on React and Programming Memes I had a very busy codeful week and I learnt a lot I m hoping that I could share them in detail soon but today I ll be sharing a summary of my findings or lessons I learnt that there was a difference between External and Internal Link in React In simpler terms using NavLink and Link tags should be used for internal pages and a href tag would be used for external pages I ve been struggling with a particular error TypeError can t read properties of Null reading id I was on stack overflow a lot last week I think I ll figure it out this week I think I m getting a hang of Supabase It was really difficult at first then I found a few resources that helped However I m still unsure about my SQL policies and how I can get them to work with my tables Again I m hopeful I ll figure it out this week Finally DOM Purifiers I think it s something that can help make input unreadable to script and tags That is it ll help to protect inner HTML s from reacting to Programming languages I guess I don t know if it works with React or if React is already protected in anyway Finally Dear Developer I think Bugs Errors and problems would always come but we ll always figure it out Don t get a burnout Do what you love See a movie or two Live Until next week OhI promised Memes Image Credit Google Image Credit Google Image Credit Google Image Credit Dunsin codes on Image Credit euboid on ️ ️Until later and yes Leave a comment or share a meme	2022-06-26 14:48:55
海外TECH	DEV Community	Run Docker based GitHub runner containers on Azure Container Apps (ACA)	https://dev.to/pwd9000/run-docker-based-github-runner-containers-on-azure-container-apps-aca-1n13	Run Docker based GitHub runner containers on Azure Container Apps ACA OverviewAll the code used in this tutorial can be found on my GitHub project docker github runner linux Welcome to Part of my series Self Hosted GitHub Runner containers on Azure In the previous part of this series we looked at how we can use Azure CLI or CI CD workflows in GitHub using GitHub Actions to run self hosted GitHub runner docker containers as Azure Container Instances ACI in Azure from a remote container registry also hosted in Azure ACR One of the drawbacks of having self hosted agent runners are if no GitHub Action Workflows or Jobs are running the GitHub runner will just sit there idle consuming cost whether that self hosted GitHub runner be an ACI or a docker container hosted on a VM So following on from the previous part we will look at how we can use Azure Container Apps ACA to run images from the remote registry instead and also demonstrate how we can automatically scale our self hosted GitHub runners from no runners or up and down based on load demand using Kubernetes Event driven Autoscaling KEDA This will allow us to save on costs and only provision self hosted GitHub runners only when needed NOTE At the time of this writing Azure Container Apps supports Any Linux based x linux amd container image Containers from any public or private container registry There are no available KEDA scalers for GitHub runners at the time of this writing Proof of ConceptBecause there are no available KEDA scalers for GitHub runners at the time of this writing we will use an Azure Storage Queue to control the scaling and provisioning of our self hosted GitHub runners We ll create the Container App Environment and Azure Queue then create an Azure Queue KEDA Scale Rule that will have a minimum of and maximum of self hosted runner containers It is possible to scale up to a max of We ll use the Azure Queue to associate GitHub workflows as queue messages to provision scale self hosted runners using an external GitHub workflow Job that will signal KEDA to provision a self hosted runner on the fly to use on any subsequent workflow Jobs inside of the GitHub Workflow After all subsequent workflow Jobs have finished running the queue message associated with the workflow will be removed from the queue and KEDA will scale back down destroy the self hosted runner container essentially scaling back down to if there are no other GitHub workflows running Pre RequisitesThings we will need to implement this container app proof of concept Azure Container Apps deployment Resource Group Optional Azure Container Registry ACR See Part of this blog series Admin account needs to be enabled GitHub Service Principal linked with Azure See Part of this blog series Log Analytics Workspace to link with Azure Container Apps Azure storage account and queue to be used for scaling with KEDA Azure Container Apps environment Container App from docker image self hosted GitHub runner stored in ACR For this step I will use a PowerShell script Deploy ACA ps running Azure CLI to create the entire environment and Container App linked with a target GitHub Repo where we will scale runners using KEDA Log into Azure az login Add container app extension to Azure CLIaz extension add name containerapp Variables ACA randomInt Get Random Maximum region uksouth acaResourceGroupName Demo ACA GitHub Runners RG Resource group created to deploy ACAs acaStorageName acakedascaler randomInt Storage account that will be used to scale runners KEDA queue scaling acaEnvironment gh runner aca env randomInt Azure Container Apps Environment Name acaLaws acaEnvironment laws Log Analytics Workspace to link to Container App Environment acaName myghprojectpool Azure Container App Name Variables ACR ACR Admin account needs to be enabled acrLoginServer registryname azurecr io The login server name of the ACR all lowercase Example myregistry azurecr io acrUsername acrAdminUser The Admin Account Username on the ACR acrPassword acrAdminPassword The Admin Account Password on the ACR acrImage acrLoginServer pwd github runner lin Image reference to pull Variables GitHub pat ghPatToken GitHub PAT token githubOrg Pwd ML GitHub Owner Org githubRepo docker github runner linux Target GitHub repository to register self hosted runners against appName GitHub ACI Deploy Previously created Service Principal linked to GitHub Repo See part of blog series Create a resource group to deploy ACAaz group create name acaResourceGroupName location region acaRGId az group show name acaResourceGroupName query id output tsv Create an azure storage account and queue to be used for scaling with KEDAaz storage account create name acaStorageName location region resource group acaResourceGroupName sku Standard LRS kind StorageV https only true min tls version TLS storageConnection az storage account show connection string resource group acaResourceGroupName name acaStorageName output tsv storageId az storage account show name acaStorageName query id output tsvaz storage queue create name gh runner scaler account name acaStorageName connection string storageConnection Create Log Analytics Workspace for ACAaz monitor log analytics workspace create resource group acaResourceGroupName workspace name acaLaws acaLawsId az monitor log analytics workspace show g acaResourceGroupName n acaLaws query customerId output tsv acaLawsKey az monitor log analytics workspace get shared keys g acaResourceGroupName n acaLaws query primarySharedKey output tsv Create ACA Environmentaz containerapp env create name acaEnvironment resource group acaResourceGroupName logs workspace id acaLawsId logs workspace key acaLawsKey location region Grant AAD App and Service Principal Contributor to ACA deployment RG Storage Queue Data Contributor on Storage accountaz ad sp list display name appName query appId o tsv ForEach Object az role assignment create assignee role Contributor scope acaRGId az role assignment create assignee role Storage Queue Data Contributor scope storageId Create Container App from docker image self hosted GitHub runner stored in ACRaz containerapp create resource group acaResourceGroupName name acaName image acrImage environment acaEnvironment registry server acrLoginServer registry username acrUsername registry password acrPassword secrets gh token pat storage connection string storageConnection env vars GH OWNER githubOrg GH REPOSITORY githubRepo GH TOKEN secretref gh token cpu memory Gi min replicas max replicas NOTES Before running the above PowerShell script you will need to enable the Admin Account on the Azure Container Registry and make a note of the Username and Password as well as the LoginSever and Image reference as these needs to be passed as variables in the script Variables ACR ACR Admin account needs to be enabled acrLoginServer registryname azurecr io The login server name of the ACR all lowercase Example myregistry azurecr io acrUsername acrAdminUser The Admin Account Username on the ACR acrPassword acrAdminPassword The Admin Account Password on the ACR acrImage acrLoginServer pwd github runner lin Image reference to pullYou will also need to provide variables for the GitHub Service Principal AppName we created in Part of the blog series that is linked with Azure a GitHub PAT token and specify the Owner and Repository to link with the Container App Variables GitHub pat ghPatToken GitHub PAT token githubOrg Pwd ML GitHub Owner Org githubRepo docker github runner linux Target GitHub repository to register self hosted runners against appName GitHub ACI Deploy Previously created Service Principal linked to GitHub Repo See part of blog series See creating a personal access token on how to create a GitHub PAT token PAT tokens are only displayed once and are sensitive so ensure they are kept safe The minimum permission scopes required on the PAT token to register a self hosted runner are repo read org Let s look at what this script created step by stepIt created a resource group called Demo ACA GitHub Runners RG containing the Azure Container Apps Environment linked with a Log Analytics Workspace an Azure Storage Account and a Container App based of a GitHub runner image pulled from our Azure Container Registry In addition the GitHub service principal created in Part of this series has also been granted access on the Resource Group as Contributor and Storage Queue Data Contributor on the storage account we will use for scaling runners It also created an empty queue for us gh runner scaler that we will use to associate running GitHub Workflows as queue messages once we start running and scaling GitHub Action Workflows Container AppLets take a deeper look at the created container app itself Create Container App from docker image self hosted GitHub runner stored in ACRaz containerapp create resource group acaResourceGroupName name acaName image acrImage environment acaEnvironment registry server acrLoginServer registry username acrUsername registry password acrPassword secrets gh token pat storage connection string storageConnection env vars GH OWNER githubOrg GH REPOSITORY githubRepo GH TOKEN secretref gh token cpu memory Gi min replicas max replicas As you can see the Container App created is scaled at and we do not yet have a scale rule configured You ll also notice that the GitHub repository we configured as the target to deploy runners to also has no runners yet because our scaling is set to If you have been following along this blog series you should know that when we want to provision a self hosted GitHub runner using the image we created through docker or as an ACI we had to pass in some environment variables such as GH OWNER GH REPOSITORY and GH TOKEN to specify which repo the runners needs to be registered on You ll notice that these variables are stored inside of the Container App configuration Notice that the GH TOKEN is actually referenced by a secret The script also sets the Azure Queue Storage Account Connection String as a secret because we will need this to set up our KEDA scale rule next Create a scale ruleNext we will create a KEDA scaling rule In the Azure portal navigate to the Container App Go to Scale and click on Edit and deploy Then click on the Scale tab and select Add This will bring up the scaling rule configuration pane Fill out the following KeyValueDescriptionRule Name queue scaling Name for scale ruleType Azure queue Type of scaler to useQueue name gh runner scaler Azure storage queue name created by scriptQueue length Trigger threshold Each workflow run Then click on Add on the Authentication section Under Secret reference you will see a drop down to select the storage connection string secret we created earlier For the Trigger parameter type connection Then click on Add and Create After a minute you will see the new scale rule have been created NOTE When you create the scale rule for the first time when the container app is being provisioned you will notice there will be a short lived runner that will appear on the GitHub repo The reason for this is that the provisioning process will provision at least x instance momentarily and then scale down to after about minutes Running and Scaling WorkflowsNext we will create a GitHub workflow that will use an external Job to associate our workflow run with an Azure Queue message that will automatically trigger KEDA to provision a self hosted runner inside of our repo for any subsequent workflow Jobs As you can see we currently have no self hosted runners on our GitHub repository You can use the following example workflow kedaScaleTest ymlname KEDA Scale self hostedon workflow dispatch env AZ STORAGE ACCOUNT acakedascaler AZ QUEUE NAME gh runner scalerjobs External Job to create and associate workflow with a unique QueueId on Azure queue to scale up KEDA scale keda queue up runs on ubuntu latest steps name Login via Azure CLI uses azure login v with creds secrets AZURE CREDENTIALS name scale up self hosted id scaleJob run OUTPUT az storage message put queue name env AZ QUEUE NAME content github run id account name env AZ STORAGE ACCOUNT echo set output name scaleJobId echo OUTPUT grep id sed s sed s g echo set output name scaleJobPop echo OUTPUT grep popReceipt sed s sed s g outputs scaleJobId steps scaleJob outputs scaleJobId scaleJobPop steps scaleJob outputs scaleJobPop Subsequent Jobs runs on self hosted Job Job JobN etc etc testRunner needs scale keda queue up runs on self hosted steps uses actions checkout v name Install Terraform uses hashicorp setup terraform v name Display Terraform Version run terraform version name Display Azure CLI Version run az version name Delay runner finish min run sleep m Remove unique QueueId on Azure queue associated with workflow as final step to scale down KEDA name Login via Azure CLI uses azure login v with creds secrets AZURE CREDENTIALS name scale down self hosted run az storage message delete id needs scaleJob outputs scaleJobId pop receipt needs scaleJob outputs scaleJobPop queue name env AZ QUEUE NAME account name env AZ STORAGE ACCOUNT NOTE On the above GitHub workflow replace the environment variables with your Azure Storage Account and Queue name env AZ STORAGE ACCOUNT acakedascaler AZ QUEUE NAME gh runner scaler Let s take a look at what this workflow does step by step Job jobs External Job to create and associate workflow with a unique QueueId on Azure queue to scale up KEDA scale keda queue up runs on ubuntu latest steps name Login via Azure CLI uses azure login v with creds secrets AZURE CREDENTIALS name scale up self hosted id scaleJob run OUTPUT az storage message put queue name env AZ QUEUE NAME content github run id account name env AZ STORAGE ACCOUNT echo set output name scaleJobId echo OUTPUT grep id sed s sed s g echo set output name scaleJobPop echo OUTPUT grep popReceipt sed s sed s g outputs scaleJobId steps scaleJob outputs scaleJobId scaleJobPop steps scaleJob outputs scaleJobPop The first Job called scale keda queue up will use an external runner to send a queue message to the Azure Queue and then save the unique Queue Id and Queue popReceipt as an output that we can later reference in other Jobs This unique queue message will represent the workflow run KEDA will see this queue message based on the scale rule we created earlier and then automatically provision a GitHub self hosted runner for this repo whilst the queue has messages Notice if we run a few more workflows whilst the current workflow is running using th same technique more messages will appear on the azure queue These queue messages which represents our workflows will automatically cause KEDA to scale up and create more self hosted runners on our repository based on the demand load of workflows Job lt gt Job nAny subsequent jobs on the workflow can use the self hosted runner as we can see from the following Job on the workflow as it i set to runs on self hosted Subsequent Jobs runs on self hosted Job Job JobN etc etctestRunner needs scale keda queue up runs on self hosted steps uses actions checkout v name Install Terraform uses hashicorp setup terraform v name Display Terraform Version run terraform version name Display Azure CLI Version run az version name Delay runner finish min run sleep m Remove unique QueueId on Azure queue associated with workflow as final step to scale down KEDA name Login via Azure CLI uses azure login v with creds secrets AZURE CREDENTIALS name scale down self hosted run az storage message delete id needs scaleJob outputs scaleJobId pop receipt needs scaleJob outputs scaleJobPop queue name env AZ QUEUE NAME account name env AZ STORAGE ACCOUNT This second Job in our workflow will run on the self hosted GitHub runner that KEDA scaled up on the Azure Container Apps and installs Terraform as well as display the version of Terraform and Azure CLI The last step on the workflow called scale down self hosted will remove the queue message on the azure queue to signal that the workflow has completed and remove the unique queue message This will cause KEDA to scale back down to if there are no more workflows running All messages are cleared on the azure queue name scale down self hosted run az storage message delete id needs scaleJob outputs scaleJobId pop receipt needs scaleJob outputs scaleJobPop queue name env AZ QUEUE NAME account name env AZ STORAGE ACCOUNT Once the workflow is finished and the Azure Queue is cleared you ll notice that KEDA has scaled back down and our self hosted runners have also been cleaned up and removed from the repo ConclusionAs you can see it was pretty easy to provision an Azure Container Apps environment and create a Container App and KEDA scale rule using azure queues to automatically provision self hosted GitHub runners onto a repository of our choice that has or no runners at all There are a few caveats and pain points I would like to highlight in this proof of concept implementation and hopefully these will be remediated soon Once they are I will create another part to this blog series once the following pain points have been fixed or improved Issue Azure Container Apps doesn t fully yet allow us to use the Container Apps system assigned managed identity to pull images from Azure Container Registry This means that we have to enable the ACRs Admin Account in order to provision images from the Azure Container Registry You can follow this GitHub issue regarding this bug Issue As mentioned earlier there are no available KEDA scalers for GitHub runners at the time of this writing This means that we have to utilise an Azure Storage Queue linked with our GitHub workflow to provision scale runners with KEDA using an external GitHub workflow Job by sending a queue message with our workflow for KEDA to be signalled to provision a self hosted runner on the fly for us to use in any subsequent GitHub Workflow Jobs One benefit of this method however is that we can have a minimum container count of which means we won t ever have any idle runners doing nothing consuming unnecessary costs thus essentially only paying for self hosted runners when they are actually running This method will only create self hosted GitHub runners based on the Azure Queue length essentially associating our workflow run with a queue item Once the GitHub Workflow finishes it will remove the queue item and KEDA will scale back down to if there are no GitHub workflows running That concludes this five part series where we took a deep dive in detail on how to implement Self Hosted GitHub Runner containers on Azure I hope you have enjoyed this post and have learned something new You can find the code samples used in this blog post on my GitHub project docker github runner linux ️ AuthorLike share follow me on GitHub Twitter LinkedIn Marcel LFollow Microsoft DevOps MVP Cloud Solutions amp DevOps Architect Technical speaker focussed on Microsoft technologies IaC and automation in Azure Find me on GitHub	2022-06-26 14:28:55
海外TECH	DEV Community	Using an Array as Function Parameter in JavaScript	https://dev.to/smpnjn/using-an-array-as-function-parameter-in-javascript-33jo	Using an Array as Function Parameter in JavaScriptIn Javascript we often have data stored as arrays and functions we want to call Sometimes the data in our arrays is exactly the data we want to pass to a function Fortunately there are ways in Javascript to use arrays as the input values for functions Let s look at how to use arrays as function parameters How to use arrays as function parametersWhen we have a function we want to pass an array to the most basic way to do it would be like this let numbers let myFunction x y z gt return x y z Returns let getCalculation myFunction numbers numbers numbers Of course this can be quite annoying especially when working with functions which have very long lists of properties As such Javascript provides us with two ways to use arrays as function parameters in Javascript apply and the spread operator Passing arrays to functions with the spread operatorThe modern and easiest way to pass an array to a function is to use the spread operator The spread operator is simply added before the array Using our previous example it looks like this let numbers let myFunction x y z gt return x y z Returns let getCalculation myFunction numbers We can also directly add the array into the function without needing a variable For example let myFunction x y z gt return x y z Returns let getCalculation myFunction If you want to learn everything the spread operator can do check out my guide on that here Passing arrays to functions using apply The other way to do this is to use apply If you re unfamiliar with the main use case of apply check out my full guide on Javascript s this object here Ultimately apply lets us take a function and pass an array into it The first attribute of apply actually refers to the this object we want to use on the function The second argument is an array of all the parameters for that function That means you can define the structure of this as well as pass an array into the function itself This obviously has some specific benefits when compared to the spread operator so it may be more suitable depending on what you want to achieve Using our previous example we can pass an array into our function like so let myFunction x y z gt return x y z Returns let getCalculation myFunction apply Here I am leaving the this object empty so if we did use this in myFunction it d be an empty object that s what the first argument of apply does The second is our array referring to x y and z respectively	2022-06-26 14:12:22
Apple	AppleInsider - Frontpage News	Apple TV with A14 & new HomePod with Apple Watch S8 chip rumored for 2023	https://appleinsider.com/articles/22/06/26/apple-tv-will-get-a14-update-new-homepod-to-use-s8-chip?utm_medium=rss	Apple TV with A amp new HomePod with Apple Watch S chip rumored for Apple s next model of Apple TV will use the A chip and be more gaming capable according to a report while a new third HomePod could use the same chip as the Apple Watch Series Apple stayed relatively quiet about the Apple TV during WWDC but it is still planning updates to the streaming set top box as part of its home entertainment updates For the next model Apple may be planning to offer more performance in the device According to Mark Gurman s Power On newsletter for Bloomberg Apple s next Apple TV is codenamed J and is currently being developed with the A chip Not only is it an upgrade from the A used in the model but it also includes an extra gigabyte of memory Read more	2022-06-26 14:32:35
Apple	AppleInsider - Frontpage News	Mac mini, 14-inch & 16-inch MacBook Pro rumored to get M2 Pro in the next year	https://appleinsider.com/articles/22/06/26/mac-mini-may-gain-m2-pro-alongside-14-inch-macbook-pro-16-inch-macbook-pro?utm_medium=rss	Mac mini inch amp inch MacBook Pro rumored to get M Pro in the next yearApple is rumored to be working on Apple Silicon M Pro Mac mini inch MacBook Pro and inch MacBook Pro models ーand also a Mac Pro tower equipped with a M Ultra and M Extreme chips Apple s WWDC keynote featured the unveiling of the M chip generation of Apple Silicon as well as new models of the MacBook Air and inch MacBook Pro using the chip While the Mac mini was included in the first wave of M devices its absence from M may not last too long The product roadmap for M Macs will include new Mac mini models sporting the latest generation of chip according to Mark Gurman s Power On newsletter for Bloomberg For the Mac mini it will apparently be offered with M and M Pro chips while the inch MacBook Pro and inch MacBook Pro will have M Pro and M Max variants available Read more	2022-06-26 14:16:28
海外TECH	Engadget	Hitting the Books: Why lawyers will be essential to tomorrow's orbital economy	https://www.engadget.com/hitting-the-books-the-end-of-astronauts-goldsmith-rees-belknap-press-140056539.html?src=rss	Hitting the Books Why lawyers will be essential to tomorrow x s orbital economyThe skies overhead could soon be filled with constellations of commercial space stations occupying low earth orbit while human colonists settle the Moon with an eye on Mars if today s robber barons have their way But this won t result in the same freewheeling Wild West that we saw in the th century unfortunately as tomorrow s interplanetary settlers will be bringing their lawyers with them nbsp In their new book The End of Astronauts Why Robots Are the Future of Exploration renowned astrophysicist and science editor Donald Goldsmith and Martin Rees the UK s Astronomer Royal argue in favor of sending robotic scouts ーwith their lack of weighty necessities like life support systems ーout into the void ahead of human explorers But what happens after these synthetic astronauts discover an exploitable resource or some rich dork declares himself Emperor of Mars In the excerpt below Goldsmith and Rees discuss the challenges facing our emerging exoplanetary legal system Harvard University PressExcerpted from The End of Astronauts Why Robots Are the Future of Exploration by Donald Goldsmith and Martin Rees published by the Harvard University Press by Donald Goldsmith and Martin Rees Almost all legal systems have grown organically the result of long experience that comes from changes in the political cultural environmental and other circumstances of a society The first sprouts of space law deserve attention from those who may participate in the myriad activities envisioned for the coming decades as well perhaps from those who care to imagine how a Justinian law code could arise in the realm of space Those who travel on spacecraft and to some degree those who will live on another celestial object occupy situations analogous to those aboard naval vessels whose laws over precedents to deal with crimes or extreme antisocial behavior These laws typically assign to a single officer or group of officers the power to judge and to inflict punishment possibly awaiting review in the event of a return to a higher court This model seems likely to reappear in the first long distance journeys within the solar system and in the first settlements on other celestial objects before the usual structure of court systems for larger societies appears on the scene As on Earth however most law is civil law not criminal law A far greater challenge than dealing with criminal acts lies in formulating an appropriate code of civil law that will apply to disputes whether national or international arising from spaceborne activities by nations corporations or individuals For half a century a small cadre of interested parties have developed the new specialty of “space law some of which already has the potential for immediate application What happens if a piece of space debris launched by a particular country or corporation falls onto an unsuspecting group of people or onto their property What happens if astronauts from different countries lay claim to parts of the moon or an asteroid And most important in its potential importance if not in its likelihood who will speak for Earth if we should receive a message from another civilization Conferences on subjects such as these have generated more interest than answers Human exploration of the moon brought related topics to more widespread attention and argument During the s the United Nations seemed the natural arena in which to hash them out and those discussions eventually produced the outcomes described in this chapter Today one suspects almost no one knows the documents that the United Nations produced let alone has plans to support countries that obey the guidelines in those documents Our hopes for achieving a rational means to define and limit activities beyond our home planet will require more extensive agreements plus a means of enforcing them Non lawyers who read existing and proposed agreements about the use of space should remain aware that lawyers typically define words relating to specialized situations as “terms of art giving them meanings other than those that a plain reading would suggest For example the word “recovery in normal discourse refers to regaining the value of something that has been lost such as the lost wages that arise from an injury In more specialized usage “resource recovery refers to the act of recycling material that would otherwise go to waste In the vocabulary of mining operations however “recovery has nothing to do with losing what was once possessed instead it refers to the extraction of ore from the ground or the seabed The word s gentle nature contrasts with the more accurate term “exploitation which often implies disapproval though in legal matters it often carries only a neutral meaning For example in the United Nations Convention on the Law of the Sea established an International Seabed Authority ISA to set rules for the large portion of the seabed that lies beyond the jurisdiction of any nation By now countries have signed on to the convention but the United States has not According to the ISA s website its Mining Code “refers to the whole of the comprehensive set of rules regulations and procedures issued by ISA to regulate prospecting exploration and exploitation of marine minerals in the international seabed Area In mining circles no one blinks at plans to exploit a particular location by extracting its mineral resources Discussions of space law however tend to avoid the term “exploitation in favor of “recovery	2022-06-26 14:00:56
ニュース	BBC News - Home	Ukraine war: Keep up unity amid war fatigue, says PM	https://www.bbc.co.uk/news/uk-61938351?at_medium=RSS&at_campaign=KARANGA	costs	2022-06-26 14:00:49
ニュース	BBC News - Home	Roe v Wade: US firms pledge to pay staff travel expenses for abortions	https://www.bbc.co.uk/news/business-61941591?at_medium=RSS&at_campaign=KARANGA	expenses	2022-06-26 14:30:50
ニュース	BBC News - Home	South African police investigate nightclub deaths	https://www.bbc.co.uk/news/world-africa-61941170?at_medium=RSS&at_campaign=KARANGA	deaths	2022-06-26 14:32:28
ニュース	BBC News - Home	Roe v Wade: What the Supreme Court decision means for US mid-terms	https://www.bbc.co.uk/news/world-us-canada-61939185?at_medium=RSS&at_campaign=KARANGA	abortion	2022-06-26 14:33:24
ニュース	BBC News - Home	England v New Zealand: Sam Billings removes Neil Wagner with bizarre catch in third Test	https://www.bbc.co.uk/sport/av/cricket/61942912?at_medium=RSS&at_campaign=KARANGA	England v New Zealand Sam Billings removes Neil Wagner with bizarre catch in third TestWatch the moment Sam Billings takes a bizarre catch to remove New Zealand s Neil Wagner on day four of the third Test at Headingley	2022-06-26 14:46:05
北海道	北海道新聞	北海道内、連日の暑さ　真夏日３６地点　２７日は大気不安定	https://www.hokkaido-np.co.jp/article/698312/	北海道内	2022-06-26 23:47:52
北海道	北海道新聞	柔らかく新しいデザインを評価　台湾の学生２人に最高賞　「隈研吾＆東川町」ＫＡＧＵデザインコンペ	https://www.hokkaido-np.co.jp/article/698324/	上川管内	2022-06-26 23:08:00
海外TECH	reddit	Hi～～～～～～！🌸	https://www.reddit.com/r/Hololive/comments/vl64dp/hi/	Hi It s been a long time submitted by u momosuzunene to r Hololive link comments	2022-06-26 14:38:41