投稿時間:2022-02-14 22:28:14 RSSフィード2022-02-14 22:00 分まとめ(33件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
AWS	lambdaタグが付けられた新着投稿 - Qiita	AWSのチュートリアルでハマった話	https://qiita.com/ideon-sys/items/807ac25dcb744afbc0d5	AWSのチュートリアルでハマった話チュートリアルなのにハマるAWSは一年ほど前に少しだけ勉強したことがあったので、簡単って言ってるlambdaなら楽勝でしょから、数時間ハマったので備忘録として投稿試したチュートリアルテストでエラーチュートリアル通りに進めて行って、「コンソールでテストする」の箇所でエラー。	2022-02-14 21:04:43
python	Pythonタグが付けられた新着投稿 - Qiita	MMCVのインストール時エラー(MacOSX)	https://qiita.com/typecprint/items/02d000cabdda1dd27c0a	これを実行すると、cmath関係のエラーが出まくる。	2022-02-14 21:57:55
python	Pythonタグが付けられた新着投稿 - Qiita	scikit-learnのロジスティック回帰の正則化項ハマった話	https://qiita.com/mizomouse/items/961e08e90c8045155bfd	scikitlearnのロジスティック回帰の正則化項ハマった話完全に値分類できる問題があったとする。	2022-02-14 21:40:50
python	Pythonタグが付けられた新着投稿 - Qiita	[python]オブジェクト指向で記述するgithubのURLのあれこれを取得	https://qiita.com/tat_mae084/items/bdc24c8af7cafaf94519	やっていることとしては、アカウント名とリポジトリ名を取得する事。	2022-02-14 21:30:18
Ruby	Rubyタグが付けられた新着投稿 - Qiita	解決方法_Webpacker::Manifest::MissingEntryError	https://qiita.com/TAKE1219/items/9ac3ce49a7e3c9b3499b	削除せずにyarninstallすると、先ほどの変更が反映されないため。	2022-02-14 21:17:29
Linux	Ubuntuタグが付けられた新着投稿 - Qiita	Ubuntu Software(Ubuntuソフトウェアセンター)の installed タブが読み込まれないときの対処	https://qiita.com/H-Kz/items/2e793b35b94bca041ae0	killallsnapstoreこのコマンドで開きっぱなしだったUbuntuSoftwareが終了し、次に起動したときには自動的にネットからカタログをDLした上で動いた感想askUbuntuのコメントによると、ThisisduetoaconflictintheSoftwareCenterらしい。	2022-02-14 21:30:55
AWS	AWSタグが付けられた新着投稿 - Qiita	Everything (It's you)をComprehendしてみた	https://qiita.com/h2m_kinoko/items/86459ad337d2bf49c087	APIResponsejsonLanguagesLanguageCodejaScorePII個人識別情報を検出できるようですが、日本語はまだ未対応のようです。	2022-02-14 21:43:43
AWS	AWSタグが付けられた新着投稿 - Qiita	AWSのチュートリアルでハマった話	https://qiita.com/ideon-sys/items/807ac25dcb744afbc0d5	AWSのチュートリアルでハマった話チュートリアルなのにハマるAWSは一年ほど前に少しだけ勉強したことがあったので、簡単って言ってるlambdaなら楽勝でしょから、数時間ハマったので備忘録として投稿試したチュートリアルテストでエラーチュートリアル通りに進めて行って、「コンソールでテストする」の箇所でエラー。	2022-02-14 21:04:43
Docker	dockerタグが付けられた新着投稿 - Qiita	dockerでの環境構築時に出る、PHP Fatal error: require(): Failed opening required '/var/www/public/../vendor/autoload.php' の解決方法	https://qiita.com/koudai_kumazaki/items/2decc223c8701f0a123f	最後に、composerinstallを行って、他のライブラリをインストールする。	2022-02-14 21:57:20
Ruby	Railsタグが付けられた新着投稿 - Qiita	解決方法_Webpacker::Manifest::MissingEntryError	https://qiita.com/TAKE1219/items/9ac3ce49a7e3c9b3499b	削除せずにyarninstallすると、先ほどの変更が反映されないため。	2022-02-14 21:17:29
技術ブログ	Developers.IO	サーベイとアンケートは Java と JavaScript どころではない違いがあります	https://dev.classmethod.jp/articles/diff-of-survey-and-questionnaire/	従業員目線	2022-02-14 12:14:35
技術ブログ	Developers.IO	Google Analytics and Google Tag Manager setup into React Project	https://dev.classmethod.jp/articles/google-analytics-and-google-tag-manager-setup-into-react-project/	Google Analytics and Google Tag Manager setup into React ProjectIntroduction Nowadays most web applications add Google Analytics GA as a feature that helps us identify the t	2022-02-14 12:06:10
海外TECH	MakeUseOf	What Is a Blockchain ETF?	https://www.makeuseof.com/what-is-blockchain-etf/	blockchain	2022-02-14 12:15:22
海外TECH	MakeUseOf	Is the Doogee V20 Smartphone the Ultimate Survivor?	https://www.makeuseof.com/doogee-v20-review/	Is the Doogee V Smartphone the Ultimate Survivor If you want the sort of smartphone that won t care if you accidentally drop it times a day then the Doogee V is probably the phone for you	2022-02-14 12:06:12
海外TECH	DEV Community	Enter the Cloud Native Dojo: Blackbelt-Level Debugging	https://dev.to/codenameone/enter-the-cloud-native-dojo-blackbelt-level-debugging-3cp5	Enter the Cloud Native Dojo Blackbelt Level DebuggingDebugging is often viewed as an art form or a craft This is true for most engineering related troubleshooting processes e g art of motorcycle maintenance We re usually indoctrinated into the basic moves by a senior developer and are then thrown into the proverbial pool As a result even senior engineers sometimes have gaps in their debugging skills There are very few university courses or books on the subject so it s really hard to blame them In his book “Why Programs Fail ーA Guide to Systemic Debugging Andreas Zeller told a story from his youth working at a computer store A customer walked into the store with a new Commodore computer For context The computers back then booted directly to a basic interpreter basic would accept line numbers as the first argument He tried inputting this valid basic line print “Hello World And he got a syntax error He was surprised since the program seemed correct and it isn t exactly complex You can probably understand it without knowing any Basic…In debugging and in programming in general we need to break down a problem into smaller components So he typed in An empty statement It turned out that the user was used to typewriters where he d type a lowercase L and the letter O to type the numbers one and zero He followed the same practice on the computer and just typed “lo When I read that story I laughed out loud but I also thought This isn t a story about debugging But it is debugging is about the unexpected It s about narrowing or slicing the problem until we have a distilled problem we can observe At this point the solution presents itself to us In this article I want to go over three big challenges we face when debugging modern applications Polyglot DebuggingDebugging the UnreproducibleData Pollution Polyglot DebuggingThis isn t a new problem As a person who used to build JVMs for a living I would occasionally “meta debug debugging the debug support for the JVM That sent me between Java and native code with both debuggers running and stepping through That s to be expected when building low level VM code But it s something that s becoming more common across the board A server might be written in Python or Java with a JavaScript front end We might track an issue through a frontend debugger all the way to the backend Similarly in a microservice deployment each service might be implemented in a different language In theory we can test everything in isolation In practice that s just unrealistic Bugs happen By their definition they are unexpected With serverless this problem has become even worse Reproducing a serverless environment locally is so challenging we hear arguments that local debugging serverless is an anti pattern Remote debugging is problematic risky and it can t scale for complex deployments So a lot of developers limit themselves to logging and maybe some observability tools While that can help with some problems these are poor replacements to local debugging Continuous observability tools provide us with a way to go beyond simple monitoring We can get source level debugging similar to traditional debuggers on production servers Debugging the UnreproducibleThere are two types of unreproducible bugs those we can t reproduce locally and those we can t reproduce at all If we can reproduce the issue in production we can use a continuous observability tool to inspect the server However if we can t we re effectively stuck with log and observability analysis We end up looking through forensic information like police crime scene investigators At this point it s a bit late to do something so we need to make sure we have new logs in place for the “next time this happens As developers we need to fight the culture of closing bugs with “can t reproduce This is a cop out A can t reproduce scenario should add logs or similar guards to verify assumptions held by the developer That way we won t get caught again with the can t reproduce conundrum Data PollutionWe often think of bugs as failures crashes and downtime While those are indeed bad they are often the best bugs We know there s a problem and the solution is usually obvious and immediate Data pollution is insidious It s remarkably hard to debug and incredibly hard to fix after the fact as fixing the code just isn t enough So what is a data pollution bug This is a bug that results in bad data That in itself isn t a big problem…The problem is that this data propagates possibly between microservices and into the database At this point it becomes a huge problem The bad data is a problem but the bug that caused it can be anywhere even on a different server It s like looking for a needle in a haystack These bugs are particularly insidious since they often only occur in production and the cleanup after them could be worse than the problem itself A good example of this is “undefined which pollutes databases everywhere as it propagates from bad JavaScript code and somehow wiggles its way into databases The way these are usually debugged after the fact is by placing a stack log in the place that writes or sends the data Use a condition there to verify that this is indeed invalid data and detect that violation This can be done with code and also with continuous observability tools such as Lightrun TL DRDebugging is a skill that we use daily but still don t invest enough time honing We end up using the same tools and techniques over and over We fall back to using logs and don t use sophisticated capabilities that have been around for years Unfortunately bugs aren t standing still As we scale our infrastructure with amazing container technology the bugs scale with our distributed solutions They become more insidious at scale We need new tools and new technologies to handle the bug scalability in the same way we handle container scaling Originally published at The New Stack	2022-02-14 12:30:30
海外TECH	DEV Community	How I structure my react components	https://dev.to/itsrakesh/how-i-structure-my-react-components-aef	How I structure my react componentsReact is all about components Better structure helps you to easily debug your app understand how the flow is going on and also as your project grows it becomes easy to manage everything Now React doesn t care how you structure your project and components So in this blog I am going to share how I structure my project and components Let s get started Before we startIn this article I don t use any styling framework just plain CSS sass Also plain react File structureIf you like this structure you can download it from here Apart from configurations actual react project starts from the src folder So let s directly jump into it └ーsrc ├ーapp ├ーassets │└ーimages ├ーcommon │├ーFooter ││└ーcomponents │├ーHooks │├ーNavigation ││└ーcomponents │├ーUIElements ││└ーLoadingAnimations │└ーUtil ├ーpages │├ー │├ーAbout ││├ーcomponents ││└ーAbout jsx │├ーContact ││├ーcomponents ││└ーContact jsx │└ーHome │├ーcomponents │└ーHome jsx └ーstyles ├ー mixins scss └ー variables scssI always separate client and server logic even for a small project because it helps to focus on one thing and it makes the project less messy Quickly know what each folder contains app This folder contains actual react app common This folder contains components that can be used anywhere in the project pages This folder contains all the common pages of the website assets All the assets like images audios etc styles This folder contains global styles like Sass variables mixins functions etc Let s dig deep Pages └ーpages ├ーcomponents │├ーHero jsx │├ーHero scss │├ーCTA jsx │└ーCTS scss └ーHome jsxSo here Home jsx is a route and page The idea is to imagine each page as a separate HTML file and it contains different sections as components Common └ーcommon ├ーFooter ├ーHooks ├ーNavigation ├ーUIElements └ーUtil Common folder contains components that are used by other components like loading animations custom buttons custom hooks etc AppThe app folder contains the main app with all the features like the dashboard profile page etc So you can think app folder like the actual app that unlocks after login Component StructureNow let s take a look at how I structure a component NamingComponent name the file name that contains the component style sheet file name of the respective component will be the same Here s how I structure a component For example import react useState useEffect from React import axios from axios import CompName scss const CompName props gt const visits setVisits useState const color setColor useState red const name Cat useEffect gt setVisits const someFunction gt do something return lt div gt lt h gt Visits visits lt h gt lt div gt export default CompName That s it ️Tool of the week ️Checklist designWhile designing a website we get confused about what to include on different pages For example what all things need to be included on the pricing page Here comes this website to rescue Thanks for reading follow for more	2022-02-14 12:27:07
海外TECH	DEV Community	Automated Terraform Tests for Azure using GitHub Actions	https://dev.to/pwd9000/automated-terraform-tests-for-azure-using-github-actions-4349	Automated Terraform Tests for Azure using GitHub Actions OverviewThis tutorial uses examples from the following GitHub project Terraform module repository Dynamic Subnets In the previous tutorial on this blog series Using Terraform on GitHub we looked at how to automate terraform module releases on the public registry using GitHub In todays tutorial we will build on the same topic but take a look at how we can also perform full end to end automation that includes Automated dependency checks for Terraform modules using GitHub dependabot Triggering an automated Terraform test when dependabot opens a Pull Request PR on the version change Test if the terraform code changes in the PR will work If all tests are successful automatically merge the PR Once the PR is merged automatically create a new release of the public module on the public Terraform registry Public Marketplace GitHub ActionsI actually wrote a public GitHub action which I will use in this tutorial to demonstrate the automated tests The Github action we will be using is called Terraform Tests for AZURE DependabotIf you look at the following GitHub project Terraform module repository Dynamic Subnets you will see there is a special folder path called github and inside that folder is a YAML file called dependabot yml version updates package ecosystem terraform See documentation for possible values directory Location of terraform version file schedule interval daily This dependabot file enables dependabot on our GitHub project repository and will daily check our repository root folder directory for any terraform files that have provider versions configured and checks if the provider versions are the latest version We discussed dependabot in much more detail on the previous tutorial automate terraform module releases on the public registry using GitHub so take a look at the previous tutorial for more details on enabling dependabot Automated TestingAs we know dependabot will automatically open a PR if it detects that a version change is available for our terraform module and also show us the file changes It is important to note that Dependabot will only open a PR and nothing else Normally after a PR has been opened a user will look at the PR perform a code review and have to also manually go and test whether the changes in that PR will actually work before merging the PR and then creating a new release using the new version of the code What we will do instead is automate the entire process from the moment the PR is opened by dependabot by creating a workflow to trigger and run based on the Pull Request event NOTE In this tutorial we look at PRs opened by dependabot but the testing action can be used in other contexts as well where a user developer makes any sort of changes additions configs to a module for example if new resources are added to a module The same testing GitHub Action Terraform Tests for AZURE can also be used in such cases to test if those changes will work Creating the WorkflowIn our GitHub project Terraform module repository Dynamic Subnets inside of the github folder path you will see another folder path called workflows there is a YAML workflow called dependency tests yml This workflow will run only when Dependabot opens a PR on master Full integration test is done by doing a plan build and destroy of config under tests auto test If tests are successful the PR is automatically merged to master If the merge was completed the next patch version is released and the patch is bumped and pushed to terraform registry name Automated Dependency Tests and Release on workflow dispatch pull request branches masterjobs Dependabot will open a PR on terraform version changes this dependabot job is only used to test TF version changes by running a plan apply and destroy in sequence dependabot plan apply destroy runs on ubuntu latest permissions pull requests write issues write actions read if github actor dependabot bot steps name Checkout uses actions checkout v name Run Dependency Tests Plan AND Apply AND Destroy uses Pwd ML terraform azurerm tests v with test type plan apply destroy Required Valid options are plan plan apply plan apply destroy Default plan path tests auto test Optional Specify path to test module to run tf version latest Optional Specifies version of Terraform to use e g Default latest tf vars file testing tfvars Required Specifies Terraform TFVARS file name inside module path Testing vars tf key tf mod tests dyn subn Required AZ backend Specifies name that will be given to terraform state file and plan artifact testing state az resource group TF Core Rg Required AZ backend AZURE Resource Group hosting terraform backend storage account az storage acc tfcorebackendsa Required AZ backend AZURE terraform backend storage account az container name ghdeploytfstate Required AZ backend AZURE storage container hosting state files arm client id secrets ARM CLIENT ID Required Dependabot Secrets ARM Client ID arm client secret secrets ARM CLIENT SECRET Required Dependabot Secrets ARM Client Secret arm subscription id secrets ARM SUBSCRIPTION ID Required Dependabot Secrets ARM Subscription ID arm tenant id secrets ARM TENANT ID Required Dependabot Secrets ARM Tenant ID github token secrets GITHUB TOKEN Required Needed to comment output on PR s secrets GITHUB TOKEN already has permissions If dependency tests are successful merge the pull request merge pr needs dependabot plan apply destroy runs on ubuntu latest permissions pull requests write contents write if github actor dependabot bot steps name Dependabot metadata id metadata uses dependabot fetch metadata v with github token secrets GITHUB TOKEN name Auto merge PR after tests run gh pr merge auto merge PR URL env PR URL github event pull request html url GITHUB TOKEN secrets GITHUB TOKEN Create and automate new release based on next patch version of releases release new version needs merge pr runs on ubuntu latest permissions contents write if github actor dependabot bot steps name Determine version id version uses zwaldowski semver release action v with bump patch dry run true github token secrets GITHUB TOKEN name Create new release and push to registry id release uses ncipollo release action v with generateReleaseNotes true name v steps version outputs version tag steps version outputs version token secrets GITHUB TOKEN This workflow will only trigger if a Pull Request is opened on the master branch name Automated Dependency Tests and Release on workflow dispatch pull request branches masterIt consists out of jobs dependabot plan apply destroy merge pr and release new version Lets take a closer look at each job dependabot plan apply destroy This first job uses my public github action Terraform Tests for AZURE Dependabot will open a PR on terraform version changes this dependabot job is only used to test TF version changes by running a plan apply and destroy in sequence dependabot plan apply destroy runs on ubuntu latest permissions pull requests write issues write actions read if github actor dependabot bot steps name Checkout uses actions checkout v name Run Dependency Tests Plan AND Apply AND Destroy uses Pwd ML terraform azurerm tests v with test type plan apply destroy Required Valid options are plan plan apply plan apply destroy Default plan path tests auto test Optional Specify path to test module to run tf version latest Optional Specifies version of Terraform to use e g Default latest tf vars file testing tfvars Required Specifies Terraform TFVARS file name inside module path Testing vars tf key tf mod tests dyn subn Required AZ backend Specifies name that will be given to terraform state file and plan artifact testing state az resource group TF Core Rg Required AZ backend AZURE Resource Group hosting terraform backend storage account az storage acc tfcorebackendsa Required AZ backend AZURE terraform backend storage account az container name ghdeploytfstate Required AZ backend AZURE storage container hosting state files arm client id secrets ARM CLIENT ID Required Dependabot Secrets ARM Client ID arm client secret secrets ARM CLIENT SECRET Required Dependabot Secrets ARM Client Secret arm subscription id secrets ARM SUBSCRIPTION ID Required Dependabot Secrets ARM Subscription ID arm tenant id secrets ARM TENANT ID Required Dependabot Secrets ARM Tenant ID github token secrets GITHUB TOKEN Required Needed to comment output on PR s secrets GITHUB TOKEN already has permissions As you can see we have an if expression to say that the job should only run if the PR was opened by dependabot also note that the action I am using in this job will need the ability to add comments issues on the Pull Request to display any issues and the plans from the terraform runs To do this a special token called GITHUB TOKEN is needed by default this token in the context of dependabot will be read only and so we can give the token additional permissions as you can see from the following YAML code permissions pull requests write issues write actions readif github actor dependabot bot NOTE To see what extra permissions can be granted to the GITHUB TOKEN see Permissions for the github tokenThe automated tests are then run using the action uses Pwd ML terraform azurerm tests v The following inputs can be used InputRequiredDescriptionDefaulttest typeFALSESpecify test type Valid options are plan plan apply plan apply destroy plan pathFALSESpecify path to Terraform module relevant to repo root Test module tf versionFALSESpecifies the Terraform version to use latest tf vars fileTRUESpecifies Terraform TFVARS file name inside module path Test vars N Atf keyTRUEAZ backend Specifies name that will be given to terraform state file and plan artifactN Aaz resource groupTRUEAZ backend AZURE Resource Group name hosting terraform backend storage accountN Aaz storage accTRUEAZ backend AZURE terraform backend storage account nameN Aaz container nameTRUEAZ backend AZURE storage container hosting state filesN Aarm client idTRUEThe Azure Service Principal Client IDN Aarm client secretTRUEThe Azure Service Principal SecretN Aarm subscription idTRUEThe Azure Subscription IDN Aarm tenant idTRUEThe Azure Service Principal Tenant IDN Agithub tokenTRUESpecify GITHUB TOKEN only used in PRs to comment outputs such as plan fmt init and validate secrets GITHUB TOKEN already has permissions but if using own token ensure repo scope N AThis action has a special input called test type which can be used to run different types of tests test type plan This test type will only perform a terraform plan ONLY against a terraform configuration test type plan apply This test type will perform a terraform plan AND a terraform apply in sequence against a terraform configuration test type plan apply destroy This test type will perform a terraform plan a terraform apply AND a terraform destroy in sequence against a terraform configuration WARNING Apply tests will create resources in your environment Please be aware of cost and also please be aware of the environment used When applying new resources ensure you are using a test subscription or test resource group inside of your test configuration file being targeted by the path input or by using testing vars via a test TFVARS file It is also really important to mention that the tests action requires a few secrets to be set on the GitHub repository such as ARM CLIENT ID ARM CLIENT SECRET ARM SUBSCRIPTION ID ARM TENANT ID by navigating to Settings gt Security gt Secrets Also note that dependabots secrets are managed separately to actions secrets So if the tests action is used in normal Actions PRs then the secrets needs to be added to the Actions secrets but because we are working with PRs made by Dependabot specifically we have to add these secrets to the Dependabot secrets As you can see I have written a terraform test in the path path tests auto test terraform backend azurerm provider azurerm features MODULE TO TEST module dynamic subnets test source network address ip var network ip network address mask var network mask virtual network rg name var resource group name virtual network name var vnet name subnet config var subnet config As you can see my terraform test is a simple terraform configuration using a source source which will target the root module hosted at the root of my project The test actually involves creating a terraform plan followed by an apply followed by a destroy in sequence as I selected input test type plan apply destroyAny issues or plans during the tests are then added to the PR as well as artifacts on the workflow merge pr The next job in our workflow will only be called if the previous job that did the tests were successful using needs dependabot plan apply destroy If dependency tests are successful merge the pull request merge pr needs dependabot plan apply destroy runs on ubuntu latest permissions pull requests write contents write if github actor dependabot bot steps name Dependabot metadata id metadata uses dependabot fetch metadata v with github token secrets GITHUB TOKEN name Auto merge PR after tests run gh pr merge auto merge PR URL env PR URL github event pull request html url GITHUB TOKEN secrets GITHUB TOKEN This job will automatically merge the Pull Request opened by dependabot and the PR will be closed as all tests were successful Again we need to give the GITHUB TOKEN some additional permissions to be able to merge and close the PR release new version The last job in our workflow will only be called if the previous job was successful in merging the PR needs merge pr Create and automate new release based on next patch version of releases release new version needs merge pr runs on ubuntu latest permissions contents write if github actor dependabot bot steps name Determine version id version uses zwaldowski semver release action v with bump patch dry run true github token secrets GITHUB TOKEN name Create new release and push to registry id release uses ncipollo release action v with generateReleaseNotes true name v steps version outputs version tag steps version outputs version token secrets GITHUB TOKEN This job will look at the project releases and determine what the next release version semantic versioning should be and then creates a new release automatically We can decide what we want to increment the version by specifying bump patch This can also be bump minor or bump major depending on how you want to perform your releases but because this use case is just a version change of the terraform provider dependency a patch increment should be fine As you can see a new release will automatically be created and reflected on the terraform registry I hope you have enjoyed this post and have learned something new You can find the code samples used in this blog post on my GitHub project Terraform module repository Dynamic Subnets ️If you are interested in checking out my public terraform modules on the registry here they are AZURE Dynamic SubnetsAZURE Secure BackendI will be adding a few more cool modules on the public registry in due course AuthorLike share follow me on GitHub Twitter LinkedIn ltag user id follow action button background color cbb important color important border color cbb important Marcel LFollow Cloud Solutions amp DevOps Architect	2022-02-14 12:03:25
海外TECH	Engadget	Uber CEO says you'll eventually be able to pay with cryptocurrency	https://www.engadget.com/uber-ceo-says-youll-eventually-be-able-to-pay-with-crypto-124035256.html?src=rss	Uber CEO says you x ll eventually be able to pay with cryptocurrencyUber users will eventually be able to pay for rides using cryptocurrency CEO Dara Khosrowshahi told Bloomberg However the company is essentially taking the same tack as Tesla by waiting for changes that will lower transaction fees and make it more environmentally friendly nbsp quot Is Uber going to accept crypto in the future Absolutely at some point quot Khosrowshahi said quot As the exchange mechanism becomes less expensive becomes more environmentally friendly I think you will see us lean into crypto a little bit more quot nbsp If Uber does jump onto the crypto train it would be joining a number of firms that already accept Bitcoin most notably Microsoft AT amp T and Wikipedia Other major companies have been more reluctant however as cryptocurrencies along with related products like NFTs have been under fire for using massive amounts of energy generated in part by burning fossil fuels nbsp Tesla was the highest profile company to accept Bitcoin as payment for its EVs but it suspended the practice saying it would only use it again quot as mining transitions to more sustainable energy quot However the company recently started accepting Dogecoin payments for some of its merch like the Cyberquad for Kids with CEO Elon Musk tweeting that it s quot better suited for transactions quot nbsp	2022-02-14 12:40:35
海外TECH	Engadget	The Morning After: Our verdict on ‘Horizon Forbidden West’	https://www.engadget.com/the-morning-after-our-verdict-on-horizon-forbidden-west-121548966.html?src=rss	The Morning After Our verdict on Horizon Forbidden West Finally the two newest consoles are hitting their exclusive game groove Microsoft finally has its Halo and while Forbidden West is available on PlayStation it was made to sing on the more powerful PS Senior Editor Jessica Conditt has spent some time with the game ahead of its launch later this week ーread her full review right here ーand well she likes it What s not to like about an underwater Vegas It s going to be a busy few weeks for gamers Destiny s latest expansion the Witch Queen lands alongside the hugely anticipated Elden Ring which is coming to both Xbox and PlayStation Meanwhile I m going low fi and playing through Earthbound nbsp ーa game from ーon my Switch ーMat SmithThe biggest stories you might have missedDon t blame SpaceX for that rocket on a collision course with the MoonAmazon is reportedly fast tracking a live action Blade Runner seriesMy iPhone knows my inside leg measurementWith Google s Valentine s Day doodle you can help two lovelorn hamsters reunite Uncharted s Nathan Drake heads to Fortnite on February thWatch the first trailer for The Lord of the Rings The Rings of Power The second teaser dropped at Super Bowl LVI AmazonAmazon s epic is almost here The series is set in the Second Age of Middle Earth thousands of years before the events of The Lord of the Rings It will be drawing material from J R R Tolkien s The Silmarillion which details key events like Sauron s story and the forging of the rings of power To whet your appetite check out the minute long teaser from this weekend s Super Bowl Continue reading VR related insurance claims increased by percent in in the UKInsurance companies are seeing a lot of claims for cracked TVs UK insurer Aviva said last year it saw a percent increase in home contents claims involving VR headsets and a percent overall increase since In the average claim for VR related accidental damages was about £ or and most incidents involved cracked TVs screens It s reflecting a boom in VR On Christmas Day the Oculus app hit the top of Apple s App Store charts for the first time Please remember where you are folks Continue reading Facebook removed anti vaccine trucker protest groups run by foreign actorsMany of the pages were scams from Vietnam and Romania Facebook has recently removed several “trucker convoy groups and pages run by scammers in Vietnam Bangladesh Romania and other countries The company said many of those groups had recently changed their names to adopt ones that use terms like “trucker “freedom and “convoy in hopes of taking advantage of the sudden interest in the rallies occurring in Canada Many of those same pages included links to websites that sold pro Trump and anti vaccine merchandise At the same time most of the accounts that took part in those groups were tied to real people Continue reading Lamborghini wants to continue manufacturing gas powered cars into the sOf course it does Lamborghini hopes to continue producing cars with internal combustion engines ICE into the next decade CEO Stephan Winkelmann told German newspaper Welt am Sonntag this week “After hybridization we will wait to see whether it will be possible to offer vehicles with an internal combustion engine beyond he said in the interview Even if Lamborghini continues producing ICE cars into the s it may not be able to sell those vehicles in many places In the US and other parts of the world governments have moved to ban the sale of gasoline powered cars by mid decade Continue reading	2022-02-14 12:15:48
医療系	医療介護 CBnews	薬局薬剤師の業務見直し、4つのテーマで検討開始-厚労省作業部会、6月に取りまとめへ	https://www.cbnews.jp/news/entry/20220214213645	作業部会	2022-02-14 21:50:00
ニュース	BBC News - Home	Petrol and diesel prices reach new record high	https://www.bbc.co.uk/news/business-60375568?at_medium=RSS&at_campaign=KARANGA	highthe	2022-02-14 12:16:11
ニュース	BBC News - Home	Camilla tests positive for coronavirus	https://www.bbc.co.uk/news/uk-60377261?at_medium=RSS&at_campaign=KARANGA	covid	2022-02-14 12:45:23
ニュース	BBC News - Home	Post Office scandal ruined lives, inquiry hears	https://www.bbc.co.uk/news/business-60374182?at_medium=RSS&at_campaign=KARANGA	postmasters	2022-02-14 12:18:47
ニュース	BBC News - Home	Sir Keir Starmer confirms he had death threats after PM's Jimmy Savile claim	https://www.bbc.co.uk/news/uk-politics-60373912?at_medium=RSS&at_campaign=KARANGA	jimmy	2022-02-14 12:39:24
ニュース	BBC News - Home	The Beatles: Rare hand-written Hey Jude lyrics to go on display	https://www.bbc.co.uk/news/uk-england-merseyside-60376363?at_medium=RSS&at_campaign=KARANGA	beatles	2022-02-14 12:18:51
北海道	北海道新聞	中道リース新社長に関崇博専務が昇格	https://www.hokkaido-np.co.jp/article/645630/	代表取締役	2022-02-14 21:17:00
北海道	北海道新聞	五輪商標登録「断固取り締まる」　中国知財局、選手やマスコット	https://www.hokkaido-np.co.jp/article/645629/	北京冬季五輪	2022-02-14 21:16:00
北海道	北海道新聞	旭川市の新規感染９２人　新型コロナ	https://www.hokkaido-np.co.jp/article/645442/	上川管内	2022-02-14 21:11:14
北海道	北海道新聞	コロナ自宅療養、最多５４万人超　病床使用率５０％超、２０都府県	https://www.hokkaido-np.co.jp/article/645624/	自宅療養	2022-02-14 21:10:00
北海道	北海道新聞	介護担当の女性から現金引き出しか　老人ホーム職員を逮捕　札幌南署	https://www.hokkaido-np.co.jp/article/645620/	引き出し	2022-02-14 21:05:00
北海道	北海道新聞	函工工業化学科０．２ポイント増　道南公立高出願変更　倍率変動少なく	https://www.hokkaido-np.co.jp/article/645621/	工業化学科	2022-02-14 21:05:00
北海道	北海道新聞	ＪＲ路線５７％で利用低水準　４千人未満、コロナ影響	https://www.hokkaido-np.co.jp/article/645619/	路線	2022-02-14 21:05:00
マーケティング	AdverTimes	ヤマダHD、大塚家具をヤマダデンキに吸収合併	https://www.advertimes.com/20220214/article376951/	吸収合併	2022-02-14 12:17:42