投稿時間:2023-06-09 01:24:53 RSSフィード2023-06-09 01:00 分まとめ(30件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
IT	気になる、記になる…	デスクトップ版｢Google ドライブ｣、今年8月で｢Windows 8/8.1｣のサポートを終了へ	https://taisy0.com/2023/06/09/172758.html	google	2023-06-08 15:50:12
AWS	AWS News Blog	A New Set of APIs for Amazon SQS Dead-Letter Queue Redrive	https://aws.amazon.com/blogs/aws/a-new-set-of-apis-for-amazon-sqs-dead-letter-queue-redrive/	A New Set of APIs for Amazon SQS Dead Letter Queue RedriveToday we launch a new set of APIs for Amazon Simple Queue Service Amazon SQS These new APIs allow you to manage dead letter queue DLQ redrive programmatically You can now use the AWS SDKs or the AWS Command Line Interface AWS CLI to programmatically move messages from the DLQ to their original queue or to …	2023-06-08 15:51:35
AWS	AWS Management Tools Blog	How to test your AWS Elastic Disaster Recovery implementation	https://aws.amazon.com/blogs/mt/how-to-test-your-aws-elastic-disaster-recovery-implementation/	How to test your AWS Elastic Disaster Recovery implementationMaintaining application and data resilience in the face of an ever evolving risk landscape is a challenge for applications with legacy architectures These risks can include ransomware attacks natural disasters user error hardware faults and many others Organizations want to recover workloads within appropriate timescales with minimal loss of data from an unforeseen event Organizations seek …	2023-06-08 15:47:56
AWS	AWS Mobile Blog	Next.js API Routes with AWS Amplify	https://aws.amazon.com/blogs/mobile/next-js-api-routes-with-aws-amplify/	Next js API Routes with AWS AmplifyNext js is a popular React framework that enables server side rendering and static site generation for React apps It makes building full stack React apps incredibly simple Developers love Next js over other solutions because it handles a lot of the difficult configuration required for server side rendering and static site generation automatically It has builtin support for styling …	2023-06-08 15:03:04
python	Pythonタグが付けられた新着投稿 - Qiita	二つの画像を分類する簡単なAIを作る	https://qiita.com/vwnnbb3/items/581e918930848e26e288	mnist	2023-06-09 00:22:18
AWS	AWSタグが付けられた新着投稿 - Qiita	【勉強会レポート】：2023/6/7【MIXI × Money Forward × NewsPicks共同開催】AWSコスト最適化夏祭り	https://qiita.com/mksamba/items/d988eb8f6b78e927d7f9	moneyforward	2023-06-09 00:26:21
AWS	AWSタグが付けられた新着投稿 - Qiita	大量のAWSアカウントから、aws cliで任意の情報を取得する（MFA対応）	https://qiita.com/mf_ko/items/0e006b3984569ffc9209	awscli	2023-06-09 00:08:33
golang	Goタグが付けられた新着投稿 - Qiita	A Tour of Goの英語版と日本語版のコマンドが違う	https://qiita.com/mitsuaki1229/items/91c8fca53e09fcc6a250	atourofgo	2023-06-09 00:56:35
golang	Goタグが付けられた新着投稿 - Qiita	goenvの導入手順	https://qiita.com/mitsuaki1229/items/f2763f026d70e37309f8	brewinstallgoenv	2023-06-09 00:44:28
Git	Gitタグが付けられた新着投稿 - Qiita	【Git】Gitで共同開発をするために覚えておくべき内容まとめ	https://qiita.com/tukapai/items/526a21e28c8eb2055fb6	共同開発	2023-06-09 00:53:43
Ruby	Railsタグが付けられた新着投稿 - Qiita	Rails6 x TypeScript x Reactで環境構築	https://qiita.com/h-taro/items/ebde6ca6676a798b5cbb	docker	2023-06-09 00:16:24
技術ブログ	Developers.IO	Lambdaで使用中のファイルディスクリプタを確認する	https://dev.classmethod.jp/articles/how-to-check-the-number-of-filedescriptors-in-use-in-lambda/	lambdanodejs	2023-06-08 15:21:41
海外TECH	Ars Technica	Damning probes find Instagram is key link connecting pedophile rings	https://arstechnica.com/?p=1946320	rings	2023-06-08 15:22:51
海外TECH	DEV Community	Top Security Vulnerabilities in React Applications	https://dev.to/scofieldidehen/top-security-vulnerabilities-in-react-applications-ogc	Top Security Vulnerabilities in React ApplicationsIn an increasingly interconnected digital landscape securing web applications is paramount React a popular JavaScript library for building user interfaces is not immune to security vulnerabilities This article highlights the top security vulnerabilities in React applications and provides actionable guidance to fortify your development practices ensuring a robust and secure framework Cross Site Scripting XSS AttacksCross Site Scripting XSS attacks remain a persistent threat to web applications including those built with React These attacks involve injecting malicious scripts into websites which can lead to data theft session hijacking or unauthorized actions To prevent XSS vulnerabilities developers must implement effective input sanitization techniques utilize output encoding and enforce stringent content security policies to mitigate script execution risks Cross Site Request Forgery CSRF VulnerabilitiesCross Site Request Forgery CSRF vulnerabilities can exploit users trust in a web application to perform unauthorized actions on their behalf React applications are not immune to CSRF attacks which can result in data manipulation unauthorized transactions or account compromise Implementing countermeasures such as employing anti CSRF tokens enforcing strict referer policies and validating requests can significantly reduce the risk of CSRF vulnerabilities Injection AttacksInjection attacks including SQL injection and command injection pose significant risks to the security of React applications These attacks occur when untrusted data is improperly handled and executed as code potentially leading to data breaches or system compromise Developers can mitigate the risks associated with injection vulnerabilities by adopting secure coding practices implementing input validation and utilizing parameterized queries Zip SlipZip Slip is a vulnerability that attackers can exploit to gain access to a React web application This is done by tricking the user into opening a malicious ZIP file The malicious ZIP file can then be used to execute malicious code which can then be used to access the React application Here are some additional details about how Zip Slip can be used to attack a React application The attacker creates a malicious ZIP file that contains a malicious file with a standard name such as index html The attacker tricks the user into opening the malicious ZIP file The malicious file is extracted from the ZIP file and executed on the user s computer The malicious file can then be used to access the React application Zip Slip attacks can be difficult to detect because they often do not leave any obvious traces However there are a few things that developers can do to help detect Zip Slip attacks Monitor the application for unusual activity If the application starts to exhibit unusual behavior such as a sudden increase in traffic or a decrease in performance this could be a sign of a Zip Slip attack Use a security scanner to scan the application for vulnerabilities A security scanner can help to identify vulnerabilities that Zip Slip attacks could exploit Insecure Data HandlingInadequate data storage and transmission practices can expose sensitive information to unauthorized access or interception React applications must employ robust encryption algorithms implement secure protocols for data transfer and carefully manage user session data to prevent session related vulnerabilities By adhering to industry best practices for secure data handling developers can protect sensitive user information and maintain the integrity of their applications Inadequate Authentication and AuthorizationWeak authentication and authorization mechanisms can compromise the security of React applications leading to unauthorized access or privilege escalation By implementing strong authentication measures such as multi factor authentication and secure password storage and enforcing granular authorization controls developers can ensure that only authorized users have access to sensitive functionality and data Vulnerabilities in Third Party DependenciesReact applications often rely on third party libraries and dependencies which can introduce additional security risks It is essential to assess the security posture of these dependencies conduct regular security audits and promptly address any identified vulnerabilities by keeping dependencies up to date By maintaining vigilance and adopting secure package management practices developers can reduce the potential attack surface and minimize the risk of supply chain attacks Ineffective Error Handling and LoggingProper error handling and logging mechanisms are crucial for promptly identifying and addressing security incidents React applications should avoid exposing sensitive information through error messages implement secure error handling practices and leverage centralized logging solutions for effective incident response and forensic analysis Frequently Asked Questions FAQ What are the common security vulnerabilities in React applications The common security vulnerabilities in React applications include Cross Site Scripting XSS attacks Cross Site Request Forgery CSRF vulnerabilities injection attacks insecure data handling inadequate authentication and authorization vulnerabilities in third party dependencies and ineffective error handling How can I prevent XSS attacks in my React application Implementing input sanitization techniques to prevent XSS attacks such as validating and encoding user input is crucial Additionally utilizing output encoding and enforcing strict content security policies can help mitigate the risk of XSS vulnerabilities What measures can I take to mitigate CSRF vulnerabilities in React applications To mitigate CSRF vulnerabilities you can implement anti CSRF tokens which verify the authenticity of requests Enforcing strict referer policies and validating requests can also help prevent unauthorized actions How can I protect my React application from injection attacks Protecting against injection attacks involves implementing secure coding practices like input validation and parameterized queries You can reduce the risk of injection vulnerabilities by validating and sanitising user input How should I ensure secure data handling in my React application Secure data handling involves encrypting sensitive data utilizing secure protocols for data transfer and carefully managing user session data Adhering to industry best practices can protect sensitive information and prevent session related vulnerabilities How can I enhance authentication and authorization security in my React application Consider implementing strong authentication measures like multi factor authentication and secure password storage to enhance authentication and authorisation security Enforcing granular authorization controls ensures only authorized users can access sensitive functionality and data How can I address vulnerabilities in third party dependencies in my React application To address vulnerabilities in third party dependencies regularly assess their security posture and conduct security audits Keep dependencies up to date to leverage security patches promptly and mitigate the risk of supply chain attacks What practices should I follow for effective error handling and logging in React applications Follow secure error handling practices that avoid exposing sensitive information Implement centralized logging solutions to capture and analyze logs for effective incident response and forensic analysis ConclusionSecuring React applications requires a proactive and comprehensive approach By understanding and addressing the top security vulnerabilities including XSS attacks CSRF vulnerabilities injection attacks insecure data handling inadequate authentication and authorization vulnerabilities in third party dependencies and ineffective error handling developers can fortify their React applications and ensure the confidentiality integrity and availability of data Stay vigilant adopt best practices and regularly update your security measures to stay one step ahead of potential threats in the ever evolving web application security landscape If you find this article thrilling discover extra thrilling posts like this on Learnhub Blog we write a lot of tech related topics from Cloud computing to Frontend Dev Cybersecurity AI and Blockchain Take a look at How to Build Offline Web Applications	2023-06-08 15:40:47
海外TECH	DEV Community	The Art of Managing Unfinished Tests: To Skip or To Soft Fail? 🏃‍♂️🧪	https://dev.to/ranggakd/the-art-of-managing-unfinished-tests-to-skip-or-to-soft-fail-2bb4	The Art of Managing Unfinished Tests To Skip or To Soft Fail ‍ ️ Outlines Introduction Skip Test vs Soft Fail at Method Level Skip Test vs Soft Fail at Class Level Conditionally Skipping Tests vs Soft Fail in Python Soft Fail A Closer Look Conclusion Introduction Please note that my understanding of Python s unittest module is still in its nascent stages Consequently my suggestions might seem radical especially to seasoned programmers but they are indeed inspired by a fresh perspective that a newcomer can bring to the table Hello As I tread on the enlightening path of understanding unit testing in Python I recently chanced upon a brilliant tutorial from PythonTutorial net that sheds light on the concept of skipping tests using Python s unittest module The unittest module is a versatile tool that provides us with three options to skip a test method or a test class the unittest skip decorator the skipTest method of the TestCase class orthe SkipTest exception It also allows us to conditionally skip tests using the unittest skipIf or unittest kipUnless decorators As a novice stepping into this expansive domain I discovered certain areas that seemed ripe for improvement So let s delve deeper into the subject Skip Test vs Soft Fail at Method Level In the world of development it is common practice to skip tests that are not yet ready or those that fail under specific conditions However merely skipping these tests without probing into or communicating their status could lead to an inefficient process We need a system that ensures that even skipped tests are taken into account and monitored so they do not fall through the cracks So here s a thought Instead of completely sidelining these tests what if we were to handle the exceptions that might cause a test to fail and report these exceptions as soft fails Let s first take a quick look at the three different ways in which a test can be skipped at the method level Skipping a Test Using a Decorator Skipping a Test Using a Method Skipping a Test Using an Exception All the above methods yield the same result test case test skipping test methods TestDemo test case oktest case test skipping test methods TestDemo test case skipped Work in progress Ran tests in sOK skipped Now let s consider the idea of a soft fail Instead of skipping a test it allows the test to run as planned and logs an issue if something doesn t go as expected This approach presents a balanced compromise between allowing a test to fail and skipping it outright Let s look at two ways to implement this Soft Fail Using the fail Method In this approach we use the fail method which allows us to flag a test case as a failure This would return test case test soft fail test methods TestDemo test case oktest case test soft fail test methods TestDemo test case FAIL FAIL test case test soft fail test methods TestDemo test case Traceback most recent call last File mnt d Repository unit test skipping tests test soft fail test methods py line in test case self fail f Soft fail Work In Progress AssertionError Soft fail Work In Progress Ran tests in sFAILED failures Take note of the fail failed and failures keywords Soft Fail Using an Exception In this approach we raise an exception when a test case is not yet ready for testing This would return test case test soft fail test methods TestDemo test case oktest case test soft fail test methods TestDemo test case ERROR ERROR test case test soft fail test methods TestDemo test case Traceback most recent call last File mnt d Repository unit test skipping tests test soft fail test methods py line in test case raise NotImplementedError Soft fail Work In Progress NotImplementedError Soft fail Work In Progress Ran tests in sFAILED errors Pay attention to the error failed and errors keywords Let s compile all of this information into a markdown table that compares the three different ways of skipping a test with the two methods of implementing a soft fail at the method level TechniqueResult KeywordSkip using decoratorskippedSkip using methodskippedSkip using exceptionskippedSoft fail using methodfailSoft fail using exceptionerrorIn real world applications soft failing a test provides similar functionality to unittest skip but with the added advantage of attempting to run the test under all circumstances We can then communicate to our team that tests marked with a Soft fail are essentially skipped but with the added visibility into any exceptions they raise upon execution This information could prove invaluable when it s time to revisit and repair these tests Skip Test vs Soft Fail at Class Level So far we ve explored the concept of skip test and soft fail at a method level However let s also delve into how we can utilize these principles at the class level Similar to the method level to skip a test class we can use the unittest skip decorator at the class level It denotes that all test methods within the class should be skipped This could be useful when a specific functionality under test is currently being developed or undergoing major changes Consider the following example where the unittest skip decorator is used at the class level As a result all tests within the TestDemo class are bypassed This would yield the following output test case test skipping test class TestDemo test case skipped Work in progress test case test skipping test class TestDemo test case skipped Work in progress Ran tests in sOK skipped Now that we ve explored how to skip tests at the class level let s examine how to apply a soft fail at the same level Again we have two strategies the first uses the fail method and the second raises an exception Soft Fail Using the fail Method The fail method enables us to flag all test cases within a test class as a soft fail It s invoked within the setUp method which is run before each test case Here s a sample implementation The output from the above code would be as follows test case test soft fail test class TestDemo test case FAILtest case test soft fail test class TestDemo test case FAIL FAIL test case test soft fail test class TestDemo test case Traceback most recent call last File mnt d Repository unit test skipping tests test soft fail test class py line in setUp self fail f Soft fail Work In Progress AssertionError Soft fail Work In Progress FAIL test case test soft fail test class TestDemo test case Traceback most recent call last File mnt d Repository unit test skipping tests test soft fail test class py line in setUp self fail f Soft fail Work In Progress AssertionError Soft fail Work In Progress Ran tests in sFAILED failures Notice the use of the fail failed and failures keywords Soft Fail Using an Exception Instead of using the fail method we can raise an exception to soft fail our test cases at the class level This way we signal that the tests are not ready for execution even if they are not complete Here s how it looks And the output would be test case test soft fail test class TestDemo test case ERRORtest case test soft fail test class TestDemo test case ERROR ERROR test case test soft fail test class TestDemo test case Traceback most recent call last File mnt d Repository unit test skipping tests test soft fail test class py line in setUp raise NotImplementedError Soft fail Work In Progress NotImplementedError Soft fail Work In Progress ERROR test case test soft fail test class TestDemo test case Traceback most recent call last File mnt d Repository unit test skipping tests test soft fail test class py line in setUp raise NotImplementedError Soft fail Work In Progress NotImplementedError Soft fail Work In Progress Ran tests in sFAILED errors Note the use of the error failed and errors keywords Let s compile all this information into a markdown table to compare the usage of skipping test vs soft fail fail vs soft fail using raise exception at the class level TechniqueResult KeywordSkip using decoratorskippedSoft fail using fail failSoft fail using exceptionerror Conditionally Skipping Tests vs Soft Fail in Python In certain scenarios we may want to skip a unit test conditionally This is usually applicable when a specific test is only applicable or valid under certain conditions or platforms Python s unittest module offers an elegant way to handle this via decorators like unittest skipIf and unittest skipUnless Conditional Skipping with unittest skipIf The unittest skipIf decorator allows us to skip a test case when a certain condition is met A typical use case is skipping a test if the test is running on a particular platform such as Windows Here s a simple illustration In this code the test case will be skipped if the test suite is running on a Windows platform The test result will display a message indicating the reason for the skipped test test case test skipping test condition TestDemo oktest case test skipping test condition TestDemo skipped Do not run on Windows Ran tests in sOK skipped Soft Fail with IF Condition As opposed to skipping a test we might want to denote a soft fail based on certain conditions This can be achieved using the fail method or by raising an exception When using the fail method in a conditional statement it will flag the test case as a soft fail if the condition is met In the example above test case will fail softly if the platform is Windows returning this output test case test soft fail test condition TestDemo oktest case test soft fail test condition TestDemo FAIL FAIL test case test soft fail test condition TestDemo Traceback most recent call last File D Repository unit test skipping tests test soft fail test condition py line in test case self fail Do not run on Windows AssertionError Do not run on Windows Ran tests in sFAILED failures Note the use of the fail failed and failures keywords in the output Alternatively we can cause a soft fail by raising an exception if the condition is true This would result in the following output test case test soft fail test condition TestDemo oktest case test soft fail test condition TestDemo ERROR ERROR test case test soft fail test condition TestDemo Traceback most recent call last File D Repository unit test skipping tests test soft fail test condition py line in test case raise EnvironmentError Do not run on Windows OSError Do not run on Windows Ran tests in sFAILED errors Again observe the use of error failed and errors keywords in the output Conditional Skipping with unittest skipUnless Now if we want to run a test unless a condition is met Python s unittest module offers the unittest skipUnless decorator For instance we might want to run a test only on a specific platform like Windows Here s how we would use unittest skipUnless in our code In this case test case will only be executed if the test suite is running on a Windows platform If not it will be skipped with a message displayed in the test result indicating the reason for skipping the test test case test skipping test condition TestDemo test case oktest case test skipping test condition TestDemo test case skipped Do not run unless on Windows Ran tests in sOK skipped Soft Fail with UNLESS Condition Similar to the conditional soft fail discussed above we can set up a soft fail that only triggers unless a certain condition is met This can be done using the fail method or by raising an exception in our test case In the code above if the platform is not Windows test case will return a soft fail as seen in the following output test case test soft fail test condition TestDemo test case oktest case test soft fail test condition TestDemo test case FAIL FAIL test case test soft fail test condition TestDemo test case Traceback most recent call last File mnt d Repository unit test skipping tests test soft fail test condition py line in test case self fail Do not run unless on Windows AssertionError Do not run unless on Windows Ran tests in sFAILED failures Note the use of the fail failed and failures keywords in the output Alternatively a soft fail can be triggered by raising an exception when the condition is not met This leads to a soft fail that manifests as an error test case test soft fail test condition TestDemo test case oktest case test soft fail test condition TestDemo test case ERROR ERROR test case test soft fail test condition TestDemo test case Traceback most recent call last File mnt d Repository unit test skipping tests test soft fail test condition py line in test case raise EnvironmentError Do not run unless on Windows OSError Do not run unless on Windows Ran tests in sFAILED errors Again note the use of error failed and errors keywords in the output Soft Fail A Closer Look The use of self fail introduces an informative layer to our testing practice Instead of merely stating that a test was skipped it provides a specific reason why the test was not successful By capturing exceptions as soft fails we can evaluate why certain tests may pose issues This information is immensely valuable when revisiting and refining these tests Deciding Between Test Skipping and Soft Fails First let s consider the situations where we might want to skip tests versus using soft fails When to Skip TestsWhen to Use Soft FailsWork in Progress If a feature or function being tested is incomplete it s reasonable to skip the test Running such tests only leads to predictable failures without adding value to our test suite Diagnosing Test Failures As highlighted earlier using self fail can be instrumental in understanding why a test is failing which aids in troubleshooting Platform or Environment Specific Tests If a test is only relevant to certain environments or platforms skipping it in incompatible scenarios saves computational resources and keeps the test report clean Flaky Tests For tests that fail inconsistently using a soft fail can capture the failure context without disrupting the entire test suite External Resource Dependency If a test relies on resources that may not always be available like a third party service or hardware it should be skipped when these resources are unavailable ensuring the efficiency of the testing process Future Functionality If we write tests for yet to be implemented features a soft fail serves as a reminder of the expected behavior acting as a form of documentation for future developers Experimental or Obsolete Features It may be wise to skip tests for experimental features or those testing obsolete functionality allowing focus on more relevant areas Conditional Fails Similar to conditionally skipping tests soft fails can conditionally allow a test to fail which is helpful in cases where the test may not always pass due to external conditions The choice between skipping a test or using a soft fail can be a judgment call dependent on project requirements team practices and the context of the test Our overarching goal should be to create a robust maintainable and useful test suite that assists in maintaining software quality Understanding Soft Fail Outcomes In a hypothetical scenario where we run tests which outcome is preferable successful tests with skipped testsor successful tests with soft failed tests The answer is largely situational and depends on the specifics of the tests and their context Key considerations include ConsiderationsExplanationNature of the TestsIf the tests are expected to fail or be skipped due to known conditions such as a pending feature implementation or a specific environment setup then both outcomes are reasonable The important thing is that the outcome aligns with our expectations Information GatheredA soft fail provides more information about the cause of failure If these tests are failing due to resolvable issues a soft fail could offer more insight into the problem Team MoraleAn abundance of soft failed tests can be demoralizing suggesting low code quality Conversely skipped tests might be seen as a sign of pragmatism acknowledging areas not currently under test Ultimately the ideal outcome would have all tests pass But in this hypothetical scenario neither outcome is inherently superior What matters is how we interpret these outcomes and the subsequent actions we take to improve our codebase and increase successful tests Selecting Between Soft Fail Implementations Our two soft fail examples namely the Only Exception Suggestion and the Only Method Suggestion each have their benefits ImplementationsExplanationOnly Exception SuggestionThis version uses Python s native exception handling and does not rely on the unittest self fail method It is a direct approach ideal when we aim to handle exceptions in a Pythonic way without worrying about customizing test result outputs Only Method SuggestionThis version employs the unittest s self fail method to handle exceptions suitable when we want to give a specific failure message when a test doesn t pass The self fail method is designed specifically for use in unittest test cases making it a more suitable way to indicate test failures Choosing between these two methods depends on our specific needs and the context of our test writing If we prioritize Python s idiomatic exception handling the Only Exception approach might be more suitable If we re more interested in customizing test results outputs the Only Method approach might serve us better Distinguishing Soft Fail and Hard Fail The terms soft fail and hard fail aren t standard in testing but for our discussion we can consider them as Fail TypesExplanationHard FailThis occurs when a test fails due to an assertion not being met or an unexpected exception being raised Essentially the system under test did not behave as expected indicating a potential problem Soft FailThis occurs when a test does not execute as planned due to an unmet external condition The test does not necessarily fail because of an assertion not being met or an unexpected exception raised rather it could not run to completion due to expected or acceptable reasons In our examples the EnvironmentError raised when a condition is not met can be considered a soft fail whereas if an assertion in a test fails or an unhandled exception is raised those would be hard fails This distinction is subjective and can vary based on our testing approach and test context Conclusion In essence understanding when and how to use soft fails in our testing can provide valuable insights into why tests fail and guide our problem solving efforts The concepts of soft fail and hard fail while not universally standard can help us categorize and understand the reasons behind our test outcomes better As a novice in unit testing I believe that sharing these insights might be beneficial for others embarking on their own unit testing journey Remember my understanding is still evolving and I am always open to feedback and suggestions Let s learn and grow together and kindly point out areas where I might be mistaken To stay updated with my learning journey follow me on Beacons for more Python and software development insights ranggakd Link in Bio amp Creator Tools Beacons ranggakd center details summary summary Oh hello there I m a an Programmer AI Tech Writer Data Practitioner Statistics Math Addict Open Source Contributor Quantum Computing Enthusiast details center beacons ai	2023-06-08 15:30:11
Apple	AppleInsider - Frontpage News	Apple's M2 MacBook Air 15-inch gets a new preorder discount at Amazon	https://appleinsider.com/articles/23/06/08/apples-m2-macbook-air-15-inch-gets-a-new-preorder-discount-at-amazon?utm_medium=rss	Apple x s M MacBook Air inch gets a new preorder discount at AmazonAmazon has already issued a cash discount on Apple s M MacBook Air inch with a preorder deal that s ringing in as the best available before the new Air hits store shelves Save on Apple s new MacBook Air inch If you re in the market for the new MacBook Air inch Amazon has dropped the preorder price by on the retail configurations Equipped with Apple s M chip and GB of memory both the GB and GB configurations are discounted Read more	2023-06-08 15:49:37
Apple	AppleInsider - Frontpage News	Apple & Epic Games both appealing 'Fortnite' App Store antitrust ruling	https://appleinsider.com/articles/23/06/08/apple-epic-games-both-appealing-fortnite-app-store-antitrust-ruling?utm_medium=rss	Apple amp Epic Games both appealing x Fortnite x App Store antitrust rulingApple and Epic Games have jointly requested an appeals court to review its decision that may compel Apple to alter its payment practices within the App Store for entirely different reasons Lawyers want an appeals court to reconsiderIn the April ruling by a panel of three judges it upheld a previous order from a California federal court in the lawsuit filed by Epic Games The lawsuit accused Apple of imposing unjust requirements on software developers compelling them to pay commissions of up to on in app purchases made by consumers Read more	2023-06-08 15:46:21
Cisco	Cisco Blog	Cisco and Amazon Web Services Working Together: If it’s cloud connected, it’s protected	https://feedpress.me/link/23532/16177153/cisco-and-amazon-web-services-working-together-if-its-cloud-connected-its-protected	Cisco and Amazon Web Services Working Together If it s cloud connected it s protectedCisco and AWS continue to work together tirelessly to help simplify and accelerate our mutual customers journeys to the cloud What does this involve	2023-06-08 15:00:57
Cisco	Cisco Blog	Secure Multicloud Infrastructure with Cisco Multicloud Defense	https://feedpress.me/link/23532/16177154/secure-multicloud-infrastructure-with-cisco-multicloud-defense	Secure Multicloud Infrastructure with Cisco Multicloud DefenseLearn how Cisco Multicloud Defense unifies security controls across cloud environments and protects workloads from every direction in this technical blog	2023-06-08 15:00:43
海外科学	NYT > Science	The Man Who Turned the World on to the Genius of Fungi	https://www.nytimes.com/2023/06/08/magazine/merlin-sheldrake-fungi.html	earth	2023-06-08 15:46:10
金融	◇◇　保険デイリーニュース　◇◇（損保担当者必携！）	保険デイリーニュース(06/09)	http://www.yanaharu.com/ins/?p=5216	業務提携	2023-06-08 15:37:08
金融	金融庁ホームページ	信用金庫連合会及び最終指定親会社に関する「レバレッジ比率規制に係る告示の一部改正（案）」に対するパブリック・コメントの結果等について公表しました。	https://www.fsa.go.jp/news/r4/ginkou/20230608/20230608.html	信用金庫連合会	2023-06-08 17:00:00
金融	金融庁ホームページ	バーゼル銀行監督委員会による議事要旨について掲載しました。	https://www.fsa.go.jp/inter/bis/20230608/20230608.html	議事	2023-06-08 17:00:00
金融	金融庁ホームページ	非常勤職員を募集しています。（国際関連業務に従事する専門調査員）	https://www.fsa.go.jp/common/recruit/r5/soumu-05/soumu-05.html	専門調査員	2023-06-08 16:00:00
ニュース	BBC News - Home	Kerri-Anne Donaldson: Former Britain's Got Talent contestant dies aged 38	https://www.bbc.co.uk/news/entertainment-arts-65847290?at_medium=RSS&at_campaign=KARANGA	finals	2023-06-08 15:12:58
ニュース	BBC News - Home	Matt Hancock feared being pushed down tube escalator, court hears	https://www.bbc.co.uk/news/uk-65846044?at_medium=RSS&at_campaign=KARANGA	tarjanyi	2023-06-08 15:43:52
ニュース	BBC News - Home	Declan Rice: West Ham chairman David Sullivan '99%' sure midfielder will leave	https://www.bbc.co.uk/sport/football/65843148?at_medium=RSS&at_campaign=KARANGA	declan	2023-06-08 15:22:57
ニュース	BBC News - Home	World Test Championship final: Virat Kohli out for 14 to 'unplayable' Mitchell Starc delivery	https://www.bbc.co.uk/sport/av/cricket/65849442?at_medium=RSS&at_campaign=KARANGA	World Test Championship final Virat Kohli out for to x unplayable x Mitchell Starc deliveryWatch as Australia pick up the huge wicket of Virat Kohli for thanks to an unplayable delivery from Mitchell Starc on day two of the World Test Championship final at The Oval	2023-06-08 15:35:40
Azure	Azure の更新情報	Announcing the new Azure Container Registry libraries	https://azure.microsoft.com/ja-jp/updates/announcing-the-new-azure-container-registry-libraries/	Announcing the new Azure Container Registry librariesWe re pleased to announce that version of the Azure Container Registry ACR libraries for NET Java JavaScript TypeScript and Python are now generally available	2023-06-08 16:00:12
IT	週刊アスキー	SIGMAが世界初の超広角＆大口径レンズ「SIGMA 14mm F1.4 DG DN | Art」発表	https://weekly.ascii.jp/elem/000/004/140/4140269/	sigma	2023-06-09 00:01:00