投稿時間:2023-08-18 02:18:48 RSSフィード2023-08-18 02:00 分まとめ(24件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
AWS	AWS DevOps Blog	How to add notifications and manual approval to an AWS CDK Pipeline	https://aws.amazon.com/blogs/devops/how-to-add-notifications-and-manual-approval-to-an-aws-cdk-pipeline/	How to add notifications and manual approval to an AWS CDK PipelineA deployment pipeline typically comprises several stages such as dev test and prod which ensure that changes undergo testing before reaching the production environment To improve the nbsp reliability and stability of release processes DevOps teams must review nbsp Infrastructure as Code IaC changes before applying them in production nbsp As a result implementing a mechanism for notification and manual approval …	2023-08-17 16:32:43
AWS	AWS Security Blog	How to Connect Your On-Premises Active Directory to AWS Using AD Connector	https://aws.amazon.com/blogs/security/how-to-connect-your-on-premises-active-directory-to-aws-using-ad-connector/	How to Connect Your On Premises Active Directory to AWS Using AD ConnectorAugust We updated the instructions and screenshots in this post to align with changes to the AWS Management Console April We ve updated this blog post to include more security learning resources AD Connector is designed to give you an easy way to establish a trusted relationship between your Active Directory and …	2023-08-17 16:36:48
AWS	AWS Security Blog	How to Connect Your On-Premises Active Directory to AWS Using AD Connector	https://aws.amazon.com/blogs/security/how-to-connect-your-on-premises-active-directory-to-aws-using-ad-connector/	How to Connect Your On Premises Active Directory to AWS Using AD ConnectorAugust We updated the instructions and screenshots in this post to align with changes to the AWS Management Console April We ve updated this blog post to include more security learning resources AD Connector is designed to give you an easy way to establish a trusted relationship between your Active Directory and …	2023-08-17 16:36:48
js	JavaScriptタグが付けられた新着投稿 - Qiita	GitHub Pagesを使用したWebページの公開	https://qiita.com/uuuDi_97722/items/5e47484678393ca38f4d	github	2023-08-18 01:38:03
Ruby	Rubyタグが付けられた新着投稿 - Qiita	[Rails]フォロー、フォロワー機能のアソシエーションについて	https://qiita.com/Pakku8914/items/951b6adeffc428b5c0fd	rails	2023-08-18 01:02:30
Docker	dockerタグが付けられた新着投稿 - Qiita	Next.js × Go のWebアプリをDocker上で作成してみませんか？ 〜DB編〜	https://qiita.com/takakou/items/4f8cd3686c7ec84c141d	docker	2023-08-18 01:17:28
golang	Goタグが付けられた新着投稿 - Qiita	Next.js × Go のWebアプリをDocker上で作成してみませんか？ 〜DB編〜	https://qiita.com/takakou/items/4f8cd3686c7ec84c141d	docker	2023-08-18 01:17:28
Git	Gitタグが付けられた新着投稿 - Qiita	GitHub Pagesを使用したWebページの公開	https://qiita.com/uuuDi_97722/items/5e47484678393ca38f4d	github	2023-08-18 01:38:03
Ruby	Railsタグが付けられた新着投稿 - Qiita	[Rails]フォロー、フォロワー機能のアソシエーションについて	https://qiita.com/Pakku8914/items/951b6adeffc428b5c0fd	rails	2023-08-18 01:02:30
技術ブログ	Developers.IO	Amazon Interactive Video Service(IVS) คืออะไร? การแนะนำฟังก์ชันล่าสุดของ AWS ในปี 2023	https://dev.classmethod.jp/articles/what-is-amazon-interactive-video-service-th/	Amazon Interactive Video Service IVS คืออะไร การแนะนำฟังก์ชันล่าสุดของAWS ในปีสวัสดีครับทุกท่านวันนี้อยากจะพาทุกท่านมาทำความรู้จักกับอีกหนึ่งบริการAWS ที่น่าสนใจAmazon Interactive Video	2023-08-17 16:37:09
技術ブログ	Developers.IO	Rancher Desktopに乗り換えたらAWS SAM CLIでDocker未起動扱いになっていたのでトラブルシュートした	https://dev.classmethod.jp/articles/aws-sam-cli-cannout-launch-on-rancher-desktop/	docker	2023-08-17 16:00:39
海外TECH	Ars Technica	Acura unveils its first GM-based electric vehicle, the new ZDX	https://arstechnica.com/?p=1961507	cadillac	2023-08-17 16:00:42
海外TECH	DEV Community	System Design Introduction	https://dev.to/rajrathod/system-design-introduction-9o8	System Design Introduction What is system design System design is the process of defining and planning the architecture components modules interfaces and interactions of a complex software or hardware system It involves making decisions about how different parts of a system will work together to achieve the desired functionality performance scalability reliability and maintainability The goal of system design is to create a blueprint or roadmap for building a system that meets the requirements and objectives of a project This includes breaking down the system into smaller subsystems modules or components and determining how they will communicate and collaborate to accomplish the overall goals System design takes into consideration various technical and non technical aspects such as Architecture Deciding on the overall structure of the system including high level components their relationships and how data flows between them This can involve choosing between different architectural patterns like monolithic microservices client server etc Components and Modules Identifying the individual pieces that will make up the system and defining their responsibilities and interactions This could include databases application servers user interfaces external APIs and more Data Management Designing the data model and storage mechanisms that will be used to store retrieve and manipulate data within the system This involves choosing appropriate databases data formats and storage strategies Communication and Interfaces Specifying how different components will communicate with each other including the protocols APIs and data formats they will use to exchange information Scalability and Performance Planning for the system s ability to handle increased load and traffic over time This might involve considerations for load balancing caching database optimization and other performance enhancing techniques Security Addressing potential security vulnerabilities and implementing measures to protect the system from unauthorized access data breaches and other security threats Reliability and Fault Tolerance Designing the system to be resilient in the face of failures ensuring that it can continue to function properly even when certain components or services fail Deployment and Infrastructure Defining how the system will be deployed on various environments development testing production and determining the required infrastructure such as servers networking and cloud services User Experience UX Considering how users will interact with the system including designing intuitive interfaces and workflows that provide a positive user experience Maintainability and Extensibility Creating a design that allows for easy maintenance updates and future enhancements without major disruptions to the system System design often involves collaboration among software architects engineers product managers and other stakeholders It s a crucial phase in the software development lifecycle as the decisions made during this stage have a significant impact on the system s overall quality and success How to approach System DesignApproaching system design requires a structured and thoughtful approach to ensure that you create a well designed and effective solution Here s a step by step guide to help you approach system design effectively Understand Requirements and Constraints Begin by thoroughly understanding the project requirements user needs and any constraints you need to work within This includes functional requirements what the system should do and non functional requirements how the system should perform Gather Information Research and gather information about the domain existing solutions and technologies that could be relevant to your system This helps you make informed design decisions Define Use Cases and User Stories Create a set of use cases or user stories that describe how different users will interact with the system This helps in identifying key features and workflows Identify Key Components Break down the system into high level components or modules Identify the major building blocks that will make up your system s architecture Choose Architecture and Patterns Select an appropriate architectural pattern e g monolithic microservices event driven based on the project s needs This choice influences how components interact and communicate Design Component Interfaces Define the interfaces and APIs for each component This includes specifying how data will be exchanged and how different modules will interact Data Modeling Design the data model that represents the structure of your application s data Choose appropriate databases and storage solutions based on the data requirements System Communication Plan how different components will communicate Consider protocols message formats and communication patterns Scalability and Performance Consider how the system will handle varying levels of load and traffic Design for scalability by incorporating techniques like load balancing caching and distributed architectures Security Measures Identify potential security risks and plan security measures such as authentication authorization encryption and data protection mechanisms Fault Tolerance and Reliability Design the system to handle failures gracefully Implement strategies like redundancy failover and error handling User Experience UX Design user interfaces that are intuitive user friendly and aligned with user expectations Consider user journeys and workflows Deployment Strategy Plan how the system will be deployed in different environments development testing production Consider deployment pipelines continuous integration and deployment automation Monitoring and Logging Define how you will monitor the system s performance collect logs and track metrics This is crucial for troubleshooting and optimizing the system Documentation Create detailed documentation that explains the system s design architecture components and interactions This helps with future maintenance and onboarding new team members Review and Iterate Conduct regular design reviews with your team to gather feedback and refine the design Be open to making adjustments based on insights from reviews Prototyping and Proof of Concept Depending on the complexity consider creating prototypes or proof of concept implementations to validate critical design decisions before proceeding with full development Testing Strategy Plan how you will test the system s functionality performance security and other aspects Consider automated testing approaches Feedback and Optimization Gather feedback from stakeholders and users as you implement the design Use this feedback to make improvements and optimizations Continuous Improvement System design is an ongoing process As the system evolves continue to assess and update the design to accommodate new features technologies and user needs Remember that effective system design requires collaboration creativity and a balance between various considerations It s also important to keep the system s goals and user needs at the forefront of your design decisions Performance vs ScalabilityPerformance and scalability are both important considerations in designing and building software systems but they address different aspects of system behavior Let s explore the differences between performance and scalability Performance Performance refers to how well a system performs a specific task or set of tasks It s a measure of how fast or responsive a system is in executing its operations Performance is often evaluated in terms of response time throughput latency and resource utilization High performance means that the system can handle a certain load while providing fast and efficient responses to user requests Factors that affect performance include Efficient algorithms and data structuresOptimized codeProper resource management CPU memory disk I O Caching mechanismsMinimized network latencyHardware capabilitiesScalability Scalability on the other hand is the system s ability to handle an increasing amount of work or traffic as demand grows It s about the system s capacity to handle more users requests or data without sacrificing performance Scalability is crucial to ensure that a system can accommodate growth without experiencing performance degradation Scalability can be categorized into two types Vertical Scalability Scaling Up This involves increasing the resources of a single server such as adding more CPU cores memory or storage It s a simpler approach but has limitations in terms of how much a single server can scale Horizontal Scalability Scaling Out This involves adding more servers to the system distributing the workload across multiple machines This approach allows for greater potential scalability but it often requires more complex architecture and handling of data synchronization Factors that affect scalability include Distributed architecture e g microservices Load balancing mechanismsData partitioning and shardingElastic scaling auto scaling based on demand Replication and synchronization strategiesCaching strategiesIn summary performance focuses on how well a system performs specific tasks in terms of speed and efficiency while scalability addresses the system s ability to handle increased load or demand Both factors are crucial and the challenge is to strike a balance between them A system that is highly performant but lacks scalability might perform well under light load but struggle when user numbers grow Conversely a highly scalable system might handle increased load but its performance might suffer due to the complexity of distributed processing Effective system design considers both performance and scalability requirements based on the anticipated usage patterns and growth projections of the application Latency vs ThroughputLatency and throughput are two important concepts in the realm of computing and system design especially when it comes to evaluating the performance of software systems Let s delve into the differences between latency and throughput Latency Latency refers to the amount of time it takes for a single unit of data such as a request to travel from the source to the destination and receive a response It is often measured in milliseconds ms or microseconds μs and is a key indicator of the responsiveness or speed of a system Low latency means that the system responds quickly to requests resulting in minimal delays In terms of latency it s important to consider Network Latency The time it takes for data to travel across a network This can be affected by factors like physical distance network congestion and routing Processing Latency The time it takes for a system to process a request or perform a computation This includes time spent executing code accessing data from memory or storage and any other processing steps User Experience Lower latency leads to a more responsive and interactive user experience which is critical for applications where real time or near real time interactions are important e g online gaming video conferencing financial trading platforms Throughput Throughput refers to the rate at which a system can process or handle a certain amount of work within a given period It s often measured in transactions per second TPS or requests per second RPS Throughput is an indicator of the system s capacity to handle a large number of requests or transactions effectively In terms of throughput it s important to consider Concurrency The ability of the system to handle multiple requests simultaneously Higher concurrency generally leads to higher throughput Processing Capacity The processing power of the system s components including CPU memory and storage A system with higher processing capacity can handle more requests per unit of time Parallelism The ability to perform multiple tasks in parallel Systems that can process tasks in parallel can achieve higher throughput Bottlenecks Identifying and addressing bottlenecks in the system s architecture such as network congestion slow database queries or resource limitations can improve overall throughput In summary latency focuses on the time it takes for a single unit of data to travel and receive a response affecting the system s responsiveness Throughput on the other hand focuses on the rate at which the system can handle a larger volume of work indicating its capacity Both concepts are crucial for designing and optimizing systems to provide a balance between responsiveness and processing capacity Availability vs Consistency Availability and Consistency are fundamental concepts in distributed systems and databases particularly in the context of the CAP theorem The CAP theorem also known as Brewer s theorem states that in a distributed system it s impossible to simultaneously achieve all three of the following goals Consistency Availability and Partition tolerance Here s a breakdown of these concepts Availability Availability refers to the system s ability to respond to requests and provide a meaningful response even in the presence of failures A highly available system is one that is operational and accessible most of the time ensuring that users can interact with it and receive responses to their requests Achieving high availability often involves redundancy fault tolerance load balancing and mechanisms for failover In an availability focused system Data might not be fully up to date or consistent across all nodes in the system at all times The system prioritizes remaining operational and providing responses even if those responses might not reflect the latest state of the system Consistency Consistency refers to the property that all nodes in a distributed system have the same view of the data at any given time In a consistent system all nodes will provide the same data in response to a query regardless of which node is queried Achieving strong consistency often involves synchronization mechanisms and coordination between nodes to ensure that updates are propagated consistently In a consistency focused system All nodes agree on the most recent data value providing a single version of the truth Ensuring consistency might involve trade offs in terms of availability and response times especially in the presence of network partitions or failures	2023-08-17 16:44:58
海外TECH	DEV Community	React useInView Hook - How to create useInView Hook in ReactJs	https://dev.to/gihanrangana/react-useinview-hook-how-to-create-useinview-hook-in-reactjs-1hp9	React useInView Hook How to create useInView Hook in ReactJsLearn how to create a powerful useInView hook in React using the Intersection Observer API Elevate your development skills as we guide you through step by step instructions to create a custom useInView hook Enhance user experience optimize performance and effortlessly track element visibility in your React projects Follow this video to step by step instructionsuseInView tsimport useRef useState useEffect RefObject from react interface IOptions root Element null undefined rootMargin string thresholds ReadonlyArray lt number gt type useInViewType inView boolean ref RefObject lt T gt null observe element RefObject lt T gt callback entries IntersectionObserverEntry gt void gt IntersectionObserver null unObserve observer IntersectionObserver gt void const useInView options IOptions useInViewType gt const inView setInView useState false const containerRef useRef null const callback entries IntersectionObserverEntry gt const entry entries setInView entry isIntersecting useEffect gt const observer new IntersectionObserver callback options if containerRef current observer observe containerRef current return gt if containerRef current observer unobserve containerRef current containerRef options For Manual observers const observe element RefObject lt T gt callback entries IntersectionObserverEntry gt void gt const observer new IntersectionObserver callback options containerRef current element current return observer const unObserve observer IntersectionObserver gt if containerRef current observer unobserve containerRef current return inView ref containerRef observe unObserve export default useInView Usage function App const data setData useState lt any gt const page setPage useState const ref inView useInView thresholds useEffect gt setData new Array page page useEffect gt if inView setPage prev gt prev inView return lt div className styles mainContainer gt data map row any index number gt return lt Card key card index toString index index gt lt button ref ref className styles loadMore gt Load More lt button gt lt div gt Working Demo	2023-08-17 16:41:13
海外TECH	DEV Community	Running React and Express with concurrently	https://dev.to/logrocket/running-react-and-express-with-concurrently-3m1k	Running React and Express with concurrentlyWritten by Vijit Ail️In modern web development it s common to build full stack applications that consist of a frontend framework like React and a backend framework like Express js In this model React contributes a robust and interactive user interface while Express handles server side logic data storage and API endpoints To efficiently develop and test these applications it s essential to run React and Express servers simultaneously One option is to manually start each server using separate terminal windows or tabs but this approach is cumbersome and inefficient An option is to use the concurrently or npm run all  CLI tools designed to run multiple npm scripts in parallel or sequentially In this article we ll explore how to set up and run React and Express together using the concurrently command line tool to achieve streamlined development workflow efficient management of frontend backend integration and enhanced productivity Jump ahead Getting to know concurrently Setting up the React frontend Setting up the Express js backend Integrating the React component with the API Installing and configuring concurrently Getting to know concurrently The concurrently command line tool allows you to run multiple commands or scripts simultaneously from a single terminal window providing a convenient way to manage and orchestrate different processes within a development environment concurrently is often used in the context of running React and Express together to streamline the development workflow Here s how concurrently simplifies the development process Single command execution Allows you to start both the React frontend and Express backend servers with a single command This simplifies the setup process and saves time and effort Streamlined development workflow Enables automatic restart of both servers whenever changes are made to the frontend or backend code Eliminating the need to manually stop and restart each server separately provides a seamless development experience and faster iteration Consolidated console output Merges the console output from multiple processes into a single terminal window Viewing logs and errors and debugging information from React and Express simultaneously makes it easier to track and debug issues during developmentconcurrently supports running multiple scripts or commands in parallel This means you can define separate scripts for starting the React and Express servers in your package json file and concurrently will execute them together For example in your package json file you can define scripts like so scripts start frontend react scripts start start backend node server js start concurrently npm run start frontend npm run start backend The start script uses concurrently to execute both the frontend and backend scripts simultaneously When you run the npm start command concurrently will start the React and Express servers allowing them to work together seamlessly Additionally concurrently provides options to customize behavior such as controlling the number of processes running simultaneously specifying custom names for processes and more These options allow you to fine tune the execution of multiple scripts based on your specific requirements Setting up the React frontend To set up the React frontend open your terminal navigate to the desired directory for your project and run the following commands gt yarn create react app concurrently app gt cd concurrently app gt mkdir server gt touch server index jsThe above code creates a React app as well as a server index js file inside the root directory for the backend application Setting up the Express js backend Next install the express and nodemon packages Nodemon is a tool that automatically restarts the server whenever changes are made facilitating a smoother development experience gt yarn add express gt yarn add D nodemonIn the server index js file add the following code server index jsconst express require express const users require users json const app express const PORT app get api users req res gt return res json users app listen PORT gt console log Listening on port PORT The code sets up an Express server that listens on port The server has a single API endpoint api users that responds with JSON data from the users json file When a request is made to the api users endpoint the server sends back the JSON data containing user information Integrating the React component with the API Now let s have a look at the React component src App jsimport useEffect useState from react import App css function App const users setUsers useState useEffect gt fetch api users then res gt res json then data gt setUsers data return lt div className App gt lt h gt Users lt h gt users map user gt lt p key user id gt user name lt p gt lt div gt export default App The lt App gt component fetches data from the backend using the fetch API and the api users endpoint and then renders the user names received from the backend API The useEffect Hook is used to fetch the data when the component mounts The fetched data is stored in the users state variable using the useState Hook Now add the following code to your package json file package json scripts start frontend react scripts start start backend nodemon server index js proxy http localhost The proxy field specifies the proxy server that will be used in development It is set to http localhost meaning any API requests made from the React frontend to endpoints starting with api will be automatically proxied to the Express backend server running on port Installing and configuring concurrently It s time to integrate the concurrently CLI Begin by installing concurrently as a development dependency in your project Open your terminal and run the following gt yarn add D concurrentlyThis command installs concurrently and makes it available for use in your project Next configure the scripts section of your project s package json file to use concurrently scripts start frontend react scripts start start backend nodemon server index js start concurrently npm run start frontend npm run start backend In the above configuration the start frontend script runs the React frontend using react scripts start and start backend script starts the Express backend using nodemon server index js In the start script Concurrently is used to execute both the start frontend and start backend scripts simultaneously After running the npm run start command in your terminal you should see the following output Here s what you ll see in the browser As you can see in the above terminal screen it can be challenging to identify the source of console output and to distinguish between the frontend and backend processes The basic configuration serves well for simple setups and fast initiation but concurrently provides additional customization and flexibility options to enhance the development experience To enable a custom configuration modify the start script according to the following snippet scripts start concurrently n FRONTEND BACKEND c red blue p name npm run start frontend npm run start backend Now when you run the npm run start command you ll see much clearer identification and differentiation between the frontend and backend processes in the console output Let s take a closer look at the command options n Specifies the names of the processes in this case FRONTEND and BACKEND are used allows us to customize the names of the concurrent processes for better clarity in the console output c Specifies the colors of the processes in this case red and blue are used helps differentiate the console output of the two processes for easier identification p Specifies the pattern for the console output in this case name is used with the name specified by the n option this pattern helps distinguish the output of each processThe custom configuration provides a foundation for scalability and adaptability As your application grows you can easily modify the names colors and patterns to accommodate additional concurrent processes or specific requirements It allows for easy customization based on your project s needs making it suitable for more advanced or complex applications ConclusionRunning React and Express with concurrently greatly simplifies the development process and enhances workflow when building full stack applications Developers can use concurrently to seamlessly run both the frontend and backend servers simultaneously from a single terminal window Whether using a basic configuration or opting for a more customized setup concurrently offers flexibility and convenience Devs can leverage the capabilities of concurrently to effectively construct and test full stack applications guaranteeing smooth integration between the React frontend and Express backend This streamlined approach enhances productivity enables rapid iteration and ultimately leads to better DevEx Get set up with LogRocket s modern React error tracking in minutes Visit to get an app ID Install LogRocket via NPM or script tag LogRocket init must be called client side not server side NPM npm i save logrocket Code import LogRocket from logrocket LogRocket init app id Script Tag Add to your HTML lt script src gt lt script gt lt script gt window LogRocket amp amp window LogRocket init app id lt script gt Optional Install plugins for deeper integrations with your stack Redux middleware ngrx middleware Vuex pluginGet started now	2023-08-17 16:31:54
海外TECH	DEV Community	Automate Your Git Workflow with this Simple Bash Script	https://dev.to/devrx/automate-your-git-workflow-with-this-simple-bash-script-5cm5	Automate Your Git Workflow with this Simple Bash ScriptThe github repository for this script gt ScriptHey there fellow coders Ever found yourself doing the same repetitive git commands every time you want to push some changes I know it can be a bit annoying But guess what Bash scripts to the rescue I know how you feel if you are remembering the repetative push and commits while reading these lines Simply put we have all been there So I decided that why not make a script of our own From then on I whipped up a neat little script that does the heavy lifting for you Let s dive right in What Does This Script Do This script aims to automate three core git actions Switching to the branch you specify Checking if there are any changes to commit Committing those changes with a message you provide and pushing to the specified branch Sounds fun right Breaking Down The Code bin bashThe shebang This tells the system that our script should run with the Bash shell Now the script first checks if you ve given it the required inputs a branch name and a commit message if ne then echo Usage lt branch name gt lt commit message gt exit fiThe magic gives us the count of arguments you ve passed in If it s not two the script will remind you how to use it branch name commit message Here we re just storing the arguments in nicely named variables to make things clearer later Now let s define our helper functions check changes This checks if there are any changes to commit If there aren t it ll let you know and end the script check changes if z git status porcelain then echo No changes to commit exit fi commit and push It does exactly what the name says First it stages all changes Then it commits with the message you provided Lastly it pushes to the branch commit and push git add git commit m commit message git push origin branch name Alrighty the main show The script first checks if you re inside a Git repository if git rev parse is inside work tree gt dev null gt amp then echo Error Current directory is not a Git repository exit fiIf you are it switches to the branch you mentioned git checkout branch name Then our good friend check changes checks if there are any well changes And finally commit and push comes into play and well commits and pushes the changes How Do I Use This Script Clone the given Github repository and navigate into the script directory To use it Make it executable chmod x git auto shRun the script git commit and push sh lt your branch name gt Your commit message over here Voila Less hassle more coding Wrapping UpThis script is a neat way to save some keystrokes and automate repetitive git actions Feel free to expand upon it or tailor it to better fit your workflow Happy coding and may the force of automation be with you P S Always remember to have backups and test new scripts in a safe environment before using them on critical projects	2023-08-17 16:23:54
ニュース	BBC News - Home	Cape Verde boat disaster: 'My brother died for a dream we all have'	https://www.bbc.co.uk/news/world-africa-66537871?at_medium=RSS&at_campaign=KARANGA	senegalese	2023-08-17 16:49:04
ニュース	BBC News - Home	Andy Malkinson: review body to examine its role in case	https://www.bbc.co.uk/news/uk-66537498?at_medium=RSS&at_campaign=KARANGA	conviction	2023-08-17 16:46:35
ニュース	BBC News - Home	Graham Linehan: Second venue cancels Father Ted writer's comedy show	https://www.bbc.co.uk/news/uk-scotland-66534454?at_medium=RSS&at_campaign=KARANGA	issues	2023-08-17 16:46:39
ニュース	BBC News - Home	Canada wildfire: Race to evacuate city as blaze approaches	https://www.bbc.co.uk/news/world-us-canada-66526554?at_medium=RSS&at_campaign=KARANGA	territories	2023-08-17 16:19:38
ニュース	BBC News - Home	The Hundred 2023: Trent Rockets hammer Manchester Originals to keep knockout hopes alive	https://www.bbc.co.uk/sport/cricket/66538266?at_medium=RSS&at_campaign=KARANGA	The Hundred Trent Rockets hammer Manchester Originals to keep knockout hopes aliveTrent Rockets keep their slim hopes of reaching The Hundred knockout stages alive as they hammer Manchester Originals at Trent Bridge	2023-08-17 16:30:37
ニュース	BBC News - Home	Cincinnati Open: Stefanos Tsitsipas wants spectator to be removed for making bee sounds	https://www.bbc.co.uk/sport/av/tennis/66539036?at_medium=RSS&at_campaign=KARANGA	Cincinnati Open Stefanos Tsitsipas wants spectator to be removed for making bee soundsWatch Stefanos Tsitsipas stop play during the second round of the Cincinnati Open as he alleges a spectator was making bee sounds	2023-08-17 16:52:15
ニュース	BBC News - Home	Six takeaways from A-level and other Level 3 results	https://www.bbc.co.uk/news/education-66534162?at_medium=RSS&at_campaign=KARANGA	resultsthis	2023-08-17 16:30:40
ビジネス	ダイヤモンド・オンライン - 新着記事	マイクロソフト、検索シェア拡大に苦戦　AIで先行も - WSJ発	https://diamond.jp/articles/-/327883	苦戦	2023-08-18 01:19:00