投稿時間:2023-06-13 22:22:04 RSSフィード2023-06-13 22:00 分まとめ(23件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
IT	気になる、記になる…	Nothing、新型スマホ｢Phone (2)｣を現地時間7月11日に正式発表へ	https://taisy0.com/2023/06/13/172956.html	nothing	2023-06-13 12:11:38
IT	InfoQ	Meta's Open-Source Massively Multilingual Speech AI Handles over 1,100 Languages	https://www.infoq.com/news/2023/06/meta-mms-speech-ai/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global	Meta x s Open Source Massively Multilingual Speech AI Handles over LanguagesMeta AI open sourced the Massively Multilingual Speech MMS model which supports automatic speech recognition ASR and text to speech synthesis TTS in over languages and language identification LID in over languages MMS can outperform existing models and covers nearly x the number of languages By Anthony Alford	2023-06-13 13:00:00
IT	ITmedia 総合記事一覧	[ITmedia News] 部屋干しは〇時間以内で　生乾き臭を抑えるために	https://www.itmedia.co.jp/news/articles/2306/13/news188.html	itmedia	2023-06-13 21:20:00
AWS	AWS Database Blog	Amazon RDS: Snapshot, restore, and recovery demystified	https://aws.amazon.com/blogs/database/amazon-rds-snapshot-restore-and-recovery-demystified/	Amazon RDS Snapshot restore and recovery demystifiedAmazon Relational Database Service Amazon RDS is a managed relational database service offering The managed service automation of Amazon Web Services AWS takes care of installation storage provisioning storage management OS and database patching and snapshot and restore of database instances Offloading the undifferentiated heavy lifting of database infrastructure management to AWS helps you focus …	2023-06-13 12:55:18
AWS	AWS Security Blog	Post-quantum hybrid SFTP file transfers using AWS Transfer Family	https://aws.amazon.com/blogs/security/post-quantum-hybrid-sftp-file-transfers-using-aws-transfer-family/	Post quantum hybrid SFTP file transfers using AWS Transfer FamilyAmazon Web Services AWS nbsp prioritizes security privacy and performance Encryption is a vital part of privacy To help provide long term protection of encrypted data AWS has been introducing quantum resistant key exchange in common transport protocols used by AWS customers In this blog post we introduce post quantum hybrid key exchange with Kyber the National Institute of Standards …	2023-06-13 12:59:54
AWS	AWS Security Blog	Post-quantum hybrid SFTP file transfers using AWS Transfer Family	https://aws.amazon.com/blogs/security/post-quantum-hybrid-sftp-file-transfers-using-aws-transfer-family/	Post quantum hybrid SFTP file transfers using AWS Transfer FamilyAmazon Web Services AWS nbsp prioritizes security privacy and performance Encryption is a vital part of privacy To help provide long term protection of encrypted data AWS has been introducing quantum resistant key exchange in common transport protocols used by AWS customers In this blog post we introduce post quantum hybrid key exchange with Kyber the National Institute of Standards …	2023-06-13 12:59:54
python	Pythonタグが付けられた新着投稿 - Qiita	Django学習備忘録 -models.pyで作成したDBへの保存方法-	https://qiita.com/tkiyo-pri/items/5493078ac93d8d6c9e8b	chatgpt	2023-06-13 21:00:57
js	JavaScriptタグが付けられた新着投稿 - Qiita	【CyberDefenders】RE101【Writeup】	https://qiita.com/schectman-hell/items/efc2f8f4e36f43164161	httpscyb	2023-06-13 21:19:14
Docker	dockerタグが付けられた新着投稿 - Qiita	react+express(docker)環境構築での問題	https://qiita.com/pappy/items/95edbb644ac12a35e259	express	2023-06-13 21:55:21
海外TECH	DEV Community	"OverAPI.com: Unlocking the Power of Comprehensive Code Reference"	https://dev.to/coderatul/overapicom-unlocking-the-power-of-comprehensive-code-reference-1kng	quot OverAPI com Unlocking the Power of Comprehensive Code Reference quot problemAs a developer it s Impossible to remember Functions syntax Formatting option sys variables methods etc OverAPI comcomes in handy It give you a productivity boost you get everything at a place linked to official documentation for further reference Pythoncheatsheet OverAPI comFor instance There are approximately string methods and I am sure many of them would be new to us so it also introduces us to new methods which could make our life easy checkout my previous blog contribute to open source for beginnersvisualize you re python code debugging for beginners	2023-06-13 12:42:43
海外TECH	DEV Community	Create and Publish your custom GitHub Action	https://dev.to/this-is-learning/create-and-publish-your-custom-github-action-4dfi	Create and Publish your custom GitHub ActionGitHub Actions are a powerful tool to automate your workflow They can be used to run tests deploy your code publish a package and much more The cool thing is there s a GitHub Actions Marketplace where you can find a lot of actions created by the community But what if you can t find the action you need You can create your own and publish it there In this tutorial we re going to see in detail how to Create a GitHub Action in TypescriptExpand our Action to support custom inputsIntegrate with GitHub s API to add labels to Pull RequestsUnit testing our actionDebugging in Visual Studio CodePublishing our action to the GitHub MarketplaceUsing our action in another repositorySome final touches to make our project more robust How to use this tutorialThis post will be much longer than usual you can skip through the chapters from the table of contents below but I d recommend you to follow each step and not skip anything One more great piece of advice is to create a new repository and follow along with the steps This way you ll have a working action at the end of the post and you ll be able to play with it and experiment rather than just reading a long tutorial and forgetting about of it The full code of this tutorial is available on GitHub on this repo so you can always refer to it if you get stuck Last but not least I also recorded a video version of this tutorial so if you prefer to watch it instead of reading you can do so here Table Of Contents How to use this tutorialBuilding an MVPAction DefinitionProject setupProject codeBuilding the actionCreating the repositoryRunning the ActionCreating a workflowRunning the workflowRunning the action locallyReading inputsAdd inputs to the action definitionRead the input in the action codeUpdate the workflowRun the hello actionUse case Adding a label to new Pull RequestsUpdate the action codeUpdate the action definitionUpdate the workflowRun the actionRun the action Testing the actionSetupAdditional changesWriting the testsRunning the testsDebugging the actionSetupDebuggingInputsPublishing the actionBrandingPublishingGoing live on the GitHub MarketplaceUsing your actionFinal touchesKeeping dist up to dateFormatting amp LintingClosing Building an MVPLet s begin with an MVP Minimum Viable Product of our GitHub Action We ll start simple with an action having only the required parts to understand the basics then we ll add more features to it Action DefinitionThe definition is stored in the action yml file put directly in the root of the repository name My Custom Action description Say Hello author Leonardo Montini runs using node main dist index js The most minimal action definition is composed of a name and a runs object to define how the action is executed and what file to run description and author are optional In case your action has some inputs they will be defined in the action yml file as well in the inputs object inputs name description The name of the person to greet required true default World When publishing the action to the store you might want to customize the appearance of the action in the marketplace This can be done by adding a branding object to the action yml file branding icon activity color green Anyway for this MVP the first snippet will be enough Project setupLet s create an empty node project with npm init y You can now open package json and add the build script scripts build tsc Since we want to use Typescript we ll need to install it as a dev dependency npm install D typescriptThen we ll create a tsconfig json by running npx tsc init and we ll edit it to match our needs compilerOptions target ES module commonjs outDir lib esModuleInterop true forceConsistentCasingInFileNames true strict true skipLibCheck true Project codeWe can now create the src index ts file and start writing our action console log Hello World We re building an MVP right So let s keep it simple for now and focus on all the required steps We ll have time to expand it later Building the actionWe can now build the action by running npm run build which will execute the tsc command as we defined in the package json file This will create a dist folder containing the compiled code dist└ーindex jsIn case you see index js generated in the root of the project or inside src you might want to add make sure the outDir option to the tsconfig json file is properly set to dist Creating the repositoryIn case you haven t done it yet it s time to create a git repository as we ll need to push our code to GitHub soon git initDon t forget to add a gitignore file to the project to avoid committing files that shouldn t be tracked by git for example the node modules folder A quick way to do it is by running npx gitignore node which will create a gitignore file with the most common entries for a node project Note in this particular case we want to push the dist folder to GitHub so we ll need to remove the dist entry from the gitignore file git add git commit m Initial commit git remote add origingit push u origin main Running the ActionWe re all set It s time to run our action Creating a workflowOn GitHub Actions are executed by workflows A workflow is defined in a yml file stored in the github workflows folder of the repository so let s create it mkdir p github workflowstouch github workflows greet ymlThe name of the file doesn t matter but it s good practice to give it a meaningful name What matters is the content of the file which defines the workflow To keep it simple here are the minimal instructions you need name Say Helloon workflow dispatch jobs run my action name Checks if this action works runs on ubuntu latest steps uses actions checkout v uses In this case the action will checkout the current repository and then run the action we just created We put as the action path because we want to run the action from the current repository but we could also use a different repository How does GitHub know what action to run It s defined in the action yml file we created earlier One more line worth mentioning is on workflow dispatch which tells GitHub to run the workflow when we manually trigger it from the Actions tab I recorded a dedicated video about running GitHub Actions manually if you want to learn more about it Running the workflowWe can now push our code to GitHub and see the action in action git add git commit m Add workflow git pushOnce the code is pushed we can go to the Actions tab and trigger the workflow manually The workflow will start running and we ll see the logs of the action in the console Congratulations You just created and ran your first GitHub Action Running the action locallyIn case you want to run the action locally without having to commit push every time you can use the act tool npm install g actThen you can run the action by executing act in the root of the repository actYou can find more in my video about running GitHub Actions locally Reading inputsLet s make our action a bit more interesting by reading an input from the workflow Add inputs to the action definitionAs usual the first step is to define the input in the action yml file inputs name description The name of the person to greet required true default World Read the input in the action codeThen we can read the input in the action code const name getInput name console log Hello name But where does the getInput function come from It s defined in the actions core package which we need to install npm install actions coreAnd then add the import on top of the index ts file import getInput from actions core Update the workflowFinally we need to update the workflow to pass the input to the action uses with name Leonardo By adding the with section we re passing the name input to the action Run the hello actionWe can now run the action again and see the input being passed to the action If it doesn t work Error Cannot find module actions core that s ok we ll fix it in the next section when we inluce vercel ncc in the workflow Use case Adding a label to new Pull RequestsWe learned the basics we have our MVP ready to be expanded so let s do it We ll create a new action that will automatically run every time a new Pull Request is created and it will add a needs review label to it Update the action codeIn order to add a label to a Pull Request we need to use the GitHub REST API We can use the Octokit client to make the API calls Luckily for us there s an official package we can use npm install actions githubThen we can import the Octokit client and use it to add the label to the Pull Request Here s the full code import getInput setFailed from actions core import context getOctokit from actions github async function run const token getInput gh token const label getInput label const octokit getOctokit token const pullRequest context payload pull request try if pullRequest throw new Error This action can only be run on Pull Requests await octokit rest issues addLabels owner context repo owner repo context repo repo issue number pullRequest number labels label catch error setFailed error as Error message Unknown error run What happened here We read the gh token and label inputs from the workflow The token is a personal access token that we need to create and pass to the action More on that later The label is the name of the label we want to add to the Pull Request We create an instance of the Octokit client using the token We get the Pull Request number from the context payload pull request object This object is only available when the action is triggered by a Pull Request event We call the octokit rest issues addLabels method to add the label to the Pull Request In case something fails we catch the error and we set the workflow as failed with the setFailed function also coming from the actions core package Update the action definitionWe also need to update the action definition to add the new inputs inputs gh token description The GitHub token for authentication required true label description The label to be applied to the pull request required true Update the workflowFinally we need to update the workflow to run when PRs are opened or reopened on pull request types opened reopened and to pass the new inputs to the action uses with gh token secrets GITHUB TOKEN label needs review We re passing the GITHUB TOKEN secret to the action It usually does not require you any extra action as GitHub automatically creates it for you In case you get an error that says Resource not accessible by integration you need to make sure your token on that repository has write access You can do that by going to the Settings tab gt Actions gt General and scroll down to the Workflow permissions section Setting it to Read and write permissions will be enough Run the actionWe can now run the action again and see the label is added to the Pull Request However let s not forget to run npm run build first then we can commit and push the changes The reason is that we told GitHub that the action is located in the dist folder so we need to make sure that folder is up to date npm run buildgit add git commit m Add label to new Pull Requests git pushCool We can now create a new branch change a file and open a Pull Request We ll see the action running and adding the label to the Pull Request aaaand Error Cannot find module actions core What happened here If you look at your file in dist index js you ll see that the actions core package is not there That s because we didn t tell TypeScript to include it in the build A good way to include packages and condense everything in one file is with the tool vercel ncc Let s install it npm install vercel nccThen we can update our build script in package json to use it build tsc amp amp ncc build lib index js We also need to change outDir in tsconfig json to lib outDir lib You might also want to double check that lib is in your gitignore file but dist is not This is our desired behavior as lib will only have our code in javascript but dist will have the whole action Run the action We can now run npm run build again then commit and push the changes Create a new branch change a file and open a Pull Request This time you ll see the action running and adding the label to the Pull Request Testing the actionYou wouldn t push code into production without testing it right So let s write some tests for our action SetupWe ll use Jest to write our tests It works out of the box with Javascript but needs a little bit of configuration to work with TypeScript npm install D jest ts jest types jestWe also need to create a new config file for jest in the root of our project called jest config json preset ts jest testEnvironment node collectCoverage true coverageReporters lcov text summary collectCoverageFrom src ts coveragePathIgnorePatterns node modules tests testPathIgnorePatterns node modules We re telling jest to use the ts jest preset to run the tests in node to collect coverage and to ignore some files Additional changesWithout any extra configuration the build will also include test files which we don t want On tsconfig json we can add a new exclude property exclude node modules test ts And also if we d run tests now everything would run twice Why Because at the end of our index ts file we re calling the run function This is the entry point of our action and we want to run it when the action is triggered However we don t want it to run by default when we import the file in our tests A possible solution is to wrap the call to run in an if statement that checks if a jest environment variable is set if process env JEST WORKER ID run Writing the testsWe can now create a new file called index test ts in the src tests folder This is where we ll write our tests I have to say I m a bit lazy so I asked GitHub Copilot to write the tests for me guess what I also made a video on this topic At first they were not passing but after a few tweaks I got them to pass Here s an extract but you can find the full file in the repository import run from index import getInput setFailed from actions core import context getOctokit from actions github Mock getInput and setFailed functionsjest mock actions core gt getInput jest fn setFailed jest fn Mock context and getOctokit functionsjest mock actions github gt context payload pull request number repo owner owner repo repo getOctokit jest fn describe run gt beforeEach gt Clear all mock function calls and reset mock implementation jest clearAllMocks it should add label to the pull request async gt Mock the return values for getInput getInput as jest Mock mockReturnValueOnce gh token value getInput as jest Mock mockReturnValueOnce label value context as any payload pull request number Mock the Octokit instance and the addLabels method const mockAddLabels jest fn const mockOctokit rest issues addLabels mockAddLabels getOctokit as jest Mock mockReturnValueOnce mockOctokit Run the function await run Assertions expect getInput toHaveBeenCalledWith gh token expect getInput toHaveBeenCalledWith label expect getOctokit toHaveBeenCalledWith gh token value expect mockAddLabels toHaveBeenCalledWith owner owner repo repo issue number labels label value expect setFailed not toHaveBeenCalled Running the testsNow it s finally time to get rid of that test echo Error no test specified amp amp exit script in package json Just replace it with test jest This will run jest with the configuration we just created If you want to run the tests in watch mode you can use jest watch We can now run npm test to run the tests You should see something like this Our action works as intended and we have some tests to prove it Debugging the actionOur favourite tool is flooding the code with console log but we all know there s a better way to debug code Let s see how we can debug our action with Visual Studio Code SetupTo get started we need one more package in our dev dependencies ts node This will allow us to run our action directly from the source code without having to build it first npm install D ts nodeWith vscode the launch configuration is stored in a file called launch json We can create it by clicking on the debug icon in the sidebar and then on the gear icon or manually by creating a vscode launch json file with this content version configurations name ts node type node request launch args src index ts runtimeArgs r ts node register cwd workspaceRoot internalConsoleOptions openOnSessionStart DebuggingYou can now put a breakpoint in your code and click on the play button in the debug sidebar This will start the debugger and run your action You can also use the F key to start the debugger In this specific example there isn t too much to debug but if you re working on a more complex action this can be a lifesaver InputsAh I almost forgot what if your action has some inputs How can you debug it You can store them directly in your launch configuration as environment variables with the following rules the will get picked up by getInput prefix the name of the input with INPUT name the input in uppercaseIn our example it would be something like this version configurations name ts node type node request launch args src index ts runtimeArgs r ts node register cwd workspaceRoot internalConsoleOptions openOnSessionStart env INPUT GH TOKEN secret token INPUT LABEL needs review If you now hit F to start the debugger you ll see that the environment variables are available in your action and are properly read by getInput Publishing the actionThe paragraph you ve all been waiting for I m sure you also skipped the previous one about debugging to jump straight to this one BrandingHold on for a second if you remember we mentioned the branding section in the action yml file Let s see what it s all about branding icon activity color green This will add a nice icon and a color to your action in the GitHub Marketplace You can find the list of available icons here PublishingOk here we are How do we publish our action Just look at your GitHub repo If you ve properly set up an action yml file you should see a banner at the top of the page like this one Going live on the GitHub MarketplaceClick on Draft a release and you will get to a page where you can set up all the required missing information for example a well written and informative README mdfile You can decide if you only want to make the action available to everyone or you also want it to be published and discoverable in the GitHub Marketplace You can also select a primary and a secondary category from the list of available ones The next step will be creating a tag and an official release for your action Almost there click the Publish release green button and you re done Congratulations you ve just published your first GitHub Action Using your actionNow that you ve published your action everyone can use it in their workflows Just create a new file in your repo for example github workflows label yml and add the following content name Label PRon pull request types opened reopened jobs label runs on ubuntu latest steps uses actions checkout main uses Balastrong gh aciton test latest with gh token secrets GITHUB TOKEN label needs reviewTo specify the version you can either use owner repo version with version being the tagged version on the repo like v or owner repo branch Final touchesThe action is complete it s live in the store and it works on all GitHub repositories but unless it s complete and you won t ever update it again you still have some room for improvements for a better developer experience DX is quite trending these days Keeping dist up to dateOne thing which will annoy you in this workflow is pushing new code and forgetting to also update the dist content I mean all you have to do is just make sure to run npm run build before pushing but if something relies on just remember to do it well good luck A simple way to solve this is to use a git hook You can use the pre commit hook to run a script at each commit in your repository This will work for you but what if you re working with other people Ah just kindly tell them to install the hook as well did I already say good luck A Dog Yes specifically a Husky Husky is a tool which allows you to easily add git hooks to your project It s very easy to set up and it will make sure that everyone who clones your repo will have the hooks installed as well as they are part of the project and get installed with the dependencies right after running npm install No need to rely on people remembering to install them Let s follow the official docs and install it npx husky init amp amp npm installYou will now find a husky folder in your project with a pre commit file in it Open it and replace the content with this npm run buildNow make sure to run npm install once to update the hook This will make sure that every time you commit the dist folder will be updated Formatting amp LintingSince we already set up our pre commit hook we can also add some formatting and linting to it This will make sure that the code is always properly formatted and that there are no linting errors Let s install Prettier and ESLint npm install D prettier eslint lint stagedWe will also need to install some plugins for ESLint npm install D typescript eslint eslint plugin latest eslint plugin jest latestWe can now configure eslint and prettier Create a eslintrc file in the root of your project and add the following content plugins jest typescript eslint parser typescript eslint parser extends eslint recommended plugin typescript eslint recommended env node true jest globals true ignorePatterns test ts Let s also add a prettierrc file trailingComma es printWidth tabWidth Last touch we want to run these two only on the staged files which means one more config file for lint staged Create a lintstagedrc file and add the following content src js ts prettier write eslint max warnings Now we can update our pre commit hook to run lint staged as well npx husky add husky pre commit npx lint staged One more npm install and we re done ClosingIf you followed all steps you now have a pretty solid GitHub Action published in the GitHub Marketplace which is automatically built and linted on each commit Ready to make a great Open Source project If you want to see the final result you can check out the GitHub Action I created while writing this article You can also use it as a reference if you missed some steps Want to see me following along the steps in this article Check out the video here What else to say I hope you enjoyed this article and that you learned something new If you have any questions feel free to add a comment below or reach out to me on Twitter This was much longer than usual I had a lot of fun writing it and I learned a lot myself in the process Would you like more long articles like this one Let me know See you next time Thanks for reading this article I hope you found it interesting I recently launched my Discord server to talk about Open Source and Web Development feel free to join Do you like my content You might consider subscribing to my YouTube channel It means a lot to me ️You can find it here Feel free to follow me to get notified when new articles are out Leonardo MontiniFollow I talk about Open Source GitHub and Web Development I also run a YouTube channel called DevLeonardo see you there	2023-06-13 12:27:12
海外TECH	Engadget	Nothing will reveal the Phone 2 on July 11th	https://www.engadget.com/nothing-will-reveal-the-phone-2-on-july-11th-120031997.html?src=rss	Nothing will reveal the Phone on July thAfter months of teases Nothing is finally ready to show its second smartphone to the world The company will hold a Nothing Phone launch event on July th at AM Eastern with a livestream available through the official website The preview image doesn t show much although we d note that the signature Glyph lights aren t quite the same as on the Phone The Phone may be more important than its predecessor for one main reason it s the first Nothing handset coming to the US Until now you ve had to either participate in a limited beta program or take a chance on an import If you ve made that leap you ve dealt with gaps in network coverage such as missing G and no real technical support An official US release should improve wireless support and reach a wider audience especially if carriers sell the phone themselves Nothing founder Carl Pei has described the Phone as a more premium device than last year s model which shipped with a Snapdragon G chip and other mostly mid range specs The company has already confirmed it will use the slightly old but noticeably faster Snapdragon Gen That will also deliver improved camera performance such as RAW HDR photos and K video at frames per second It s not certain if there are upgrades to the cameras themselves or other key components Software may also play an important role Inverseclaims Nothing OS will be more quot distinct quot on the Phone with a more polished experience developed in house rather than outsourced The phone maker reportedly has a much larger software team that now includes multiple veterans from OnePlus Pei s former outfit Whether or not Nothing makes a significant dent in the US market is another matter Apple and Samsung dominate the American phone landscape with even well known names like Google and Motorola trailing well behind OnePlus hasn t made significant inroads despite the backing of Chinese tech giant Oppo The Phone won t necessarily need to be a huge hit to succeed but Nothing is facing rivals with many more resources at their disposal This article originally appeared on Engadget at	2023-06-13 12:00:31
Cisco	Cisco Blog	Be Confident, Be Bold and Be Fearless with Cisco Secure Endpoint	https://feedpress.me/link/23532/16186255/be-confident-be-bold-and-be-fearless-with-cisco-secure-endpoint	Be Confident Be Bold and Be Fearless with Cisco Secure EndpointYou must enable hybrid work while defending your employees from cyberattacks This blog discusses how Cisco Secure Endpoint helps you protect	2023-06-13 12:00:49
Cisco	Cisco Blog	Global Week of Giving Champions Employee Volunteering	https://feedpress.me/link/23532/16188180/global-week-of-giving-champions-employee-volunteering	Global Week of Giving Champions Employee VolunteeringLearn how over Cisconians around the world contributed to their communities in person and virtually during Cisco Secure s Global Week of Giving	2023-06-13 12:00:46
Cisco	Cisco Blog	Threat Trends: Snort IPS	https://feedpress.me/link/23532/16188178/threat-trends-snort-ips	snort	2023-06-13 12:00:45
海外科学	NYT > Science	Black Rhinos, Horns Cut Off, Lose Some of Their Gusto	https://www.nytimes.com/2023/06/12/climate/black-rhinos-horns.html	networks	2023-06-13 12:47:15
ニュース	BBC News - Home	Alfie Steele: Mum and partner guilty of killing boy in bath	https://www.bbc.co.uk/news/uk-england-hereford-worcester-65857668?at_medium=RSS&at_campaign=KARANGA	discipline	2023-06-13 12:43:30
ニュース	BBC News - Home	Porthcawl: Aircraft crashes into sea off south Wales coast	https://www.bbc.co.uk/news/uk-wales-65887992?at_medium=RSS&at_campaign=KARANGA	aircraft	2023-06-13 12:24:17
ニュース	BBC News - Home	Southwark: Rare Roman mausoleum unearthed in London	https://www.bbc.co.uk/news/uk-england-london-65890080?at_medium=RSS&at_campaign=KARANGA	londonexcavators	2023-06-13 12:30:03
ニュース	BBC News - Home	Queens of the Stone Age frontman reveals he had cancer surgery	https://www.bbc.co.uk/news/entertainment-arts-65889069?at_medium=RSS&at_campaign=KARANGA	stone	2023-06-13 12:02:21
ニュース	BBC News - Home	NI police apologise to 'Hooded Men' over interrogations	https://www.bbc.co.uk/news/uk-northern-ireland-65892145?at_medium=RSS&at_campaign=KARANGA	interrogationsthe	2023-06-13 12:53:52
ニュース	BBC News - Home	Nottingham attacks: What we know so far	https://www.bbc.co.uk/news/uk-65890403?at_medium=RSS&at_campaign=KARANGA	centre	2023-06-13 12:06:20
IT	週刊アスキー	Nothing Phone (2)、7月12日発表会開催	https://weekly.ascii.jp/elem/000/004/140/4140821/	nothing	2023-06-13 21:10:00