投稿時間:2023-03-23 18:33:32 RSSフィード2023-03-23 18:00 分まとめ(37件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
IT	気になる、記になる…	｢Google Pixel Tablet｣の専用スタンドの新たな写真が流出	https://taisy0.com/2023/03/23/169901.html	google	2023-03-23 08:55:54
IT	ITmedia 総合記事一覧	[ITmedia ビジネスオンライン] 「おとり物件に遭った」4割、部屋探しで困っていることは？	https://www.itmedia.co.jp/business/articles/2303/23/news173.html	itmedia	2023-03-23 17:41:00
IT	ITmedia 総合記事一覧	[ITmedia News] 「1000度の鉄球を〇〇に置いてみた」──町工場の動画がTwitterで話題　竹、せっけん、スライムなどで検証	https://www.itmedia.co.jp/news/articles/2303/23/news168.html	itmedia	2023-03-23 17:04:00
TECH	Techable（テッカブル）	音楽とノンアルコールの知られざる関係、シラフで捗るチル体験	https://techable.jp/archives/201622	専門商社	2023-03-23 08:30:13
TECH	Techable（テッカブル）	最大3画面で作業可能！モニター2台に映像を同時出力できる映像変換アダプター	https://techable.jp/archives/200519	displayport	2023-03-23 08:00:50
IT	情報システムリーダーのためのIT情報専門サイト IT Leaders	アドバンスト・メディア、小規模コンタクトセンター向けの音声認識システム、応対品質も評価 | IT Leaders	https://it.impress.co.jp/articles/-/24616	アドバンスト・メディア、小規模コンタクトセンター向けの音声認識システム、応対品質も評価ITLeadersアドバンスト・メディアは年月日、コンタクトセンター向け音声認識システム「TramRatepoweredbyAmiVoice」を発表した。	2023-03-23 17:49:00
js	JavaScriptタグが付けられた新着投稿 - Qiita	ページレイアウトのサイドバーにfiletreeを入れる	https://qiita.com/kaiyo_yume/items/c958c11ca4195966740e	chatgpt	2023-03-23 17:04:52
AWS	AWSタグが付けられた新着投稿 - Qiita	AWS Health APIを活用する	https://qiita.com/MakiMatsu/items/7b68c2b6b9705d92cb75	personalhealthdashboard	2023-03-23 17:04:28
技術ブログ	Developers.IO	[Tips] 親子レコード対応版: SOQLの結果からId型のリストを抽出する	https://dev.classmethod.jp/articles/tips-retrieve-ancestorids-from-result-of-soql/	fieldsl	2023-03-23 08:52:46
技術ブログ	Developers.IO	[アップデート] QuickSight の閾値アラートがテーブル/ピボットテーブルでも利用出来るようになりました	https://dev.classmethod.jp/articles/quicksight-threshold-alerts-table-pivot/	quicksight	2023-03-23 08:49:20
技術ブログ	Developers.IO	Amazon Athenaを使ってS3サーバーアクセスログをパースしてみた	https://dev.classmethod.jp/articles/s3-access-log-parsed-with-amazon-athena/	amazon	2023-03-23 08:31:26
技術ブログ	Developers.IO	【4/12（水）】Alteryx Designer Cloudはじめの一歩	https://dev.classmethod.jp/news/230412_alteryx/	alteryxdesignercloud	2023-03-23 08:26:28
技術ブログ	Developers.IO	สร้าง Dummy Data ง่ายๆด้วย ChatGPT	https://dev.classmethod.jp/articles/easily-create-dummy-data-with-chatgpt/	สร้างDummy Data ง่ายๆด้วยChatGPTเริ่มต้นวันนี้จะมาลองให้ChatGPT สร้างข้อมูลจำลอง Dummy Data สำหรับใช้ในการทดสอบกันครับผมต้องการทำให้สิ่งท	2023-03-23 08:12:04
海外TECH	DEV Community	Perfect UI library using Chat GPT	https://dev.to/shreyvijayvargiya/perfect-ui-library-using-chat-gpt-3ken	Perfect UI library using Chat GPTEasy to create and customise and build fast and performant UI interfaces Under the HoodThe story begins when I read the tweet about the new UI library using Tailwind CSS or new components using Tailwind CSS I applied synthesis thinking over here how can we synthesise one product using another product How can we use Chat GPT to create our own UI library using Tailwind CSS Well the question is good and what matters will beWhy do we need to create our own custom library Why only Tailwind CSS How Chat GPT will help All the questions will be answered and the reason How I am able to think like this is because of system thinking that gives one teaching of synthesis thinking that is applied over here Why UI library UI library basically helps to develop interfaces fast Easy to integrate and easy to use and has an easy learning curve Developing complex UI interfaces becomes a cakewalk if we already have an existing UI library with all the required components Why a new custom UI library But today s UI library comes with one bottleneck heavy dependency and huge package size affecting the performance also sometimes If we can create our own library with only the required custom components we can develop our application fast and performant How Well it s simple we will start with creating only basic components like Navar Footer Modal Search and Button component Remember that these UI components should resemble your needs meaning they should match somehow your website designs making things easy for production Steps to create your own UI library in your frontend code repositoryI prefer creating a dedicated folder called the UI libraryInside these will add all the required reusable UI components such as Navbar Modal Input and Buttons Now create a dedicated file for each of these componentsAnd lastly just add the corresponding code in the samemodules UI Navbar Button SearchInput ModalAbove is the directory structure but you can modify it according to your need How Chat GPT can help here Well it s simple instead of creating your own Button component we will simply ask chat GPT to give us React code for Button We can also prefer the styling library to provide CSS directly and chat GPT will help with that For example if we want to use Tailwind CSS as the styling library for our components I ll give Chat GPT the below prompt to get the Button component using Tailwind CSS Give me React Button code and style it using Tailwind CSS with the primary colour blue Of course you can improve the prompt according to your need and your React Button component is ready Simply copy and paste the code into your modules UI Button file and export it making it accessible to an entire code repository Follow the same pattern with other UI components such as Modal and Navbar Provide better prompts according to your need for example your UI component should be responsive and handle different themes so provide the prompt accordingly Once the components are ready you can also pass the props and children according to your UI designs For example Buttons can have left or right icons so pass the props accordingly Why Custom UI Library This can be argued but we need to understand that we only need certain components of the entire third party UI library and for that we ended up adding an entire module making the size bigger than required Too much dependency will make things slow and decrease the development time Own custom library gives complete control earlier developing our own custom library takes time but now we have chat GPT to write code for us Testing UI componentsThis is a very good approach to testing your own UI library before putting it in production I prefer using Storybook of course we need to integrate storybook and write code for each component to get rendered on storybook UI locally but that is a one time investment of time Storybook also provides documentation tools to write docs in markdown extension We can write docs for each UI component for the entire development team on how to use these components and what all props are available Below is the youtube video for the introduction to Storybook feel free to subscribe to my youtube channel for more such videos Introduction to StorybookDocumentation is important and won t take much time so try adding documentation if you are working in a team Or you can also prefer typescript to ensure all types checks are handled and required props are provided before pushing code in production Writing test casesThis can be optional but try to add these if you are working in a team Use react testing library to write basic test cases and you are good to go I am not going into much in detail because you can easily ask for test cases from chat GPT Open Source the LibraryThis is freelancers or a single developer If you are developing a lot of products and need a custom UI library in multiple projects simply open source your library on npm Now you can use your own custom library in multiple projects You can also copy paste the entire UI directory into multiple projects also if you don t have experience in open sourcing the module ConclusionTry to use Chat GPT as much as possible it will save a lot of time Create all the required components using Chat GPT and add them directly to your codebase Open source if possible to use the UI components in multiple projectsStorybook can be used to provide docs and showcase the UI components locallyWrite test cases and use chat GPT for writing test cases with any of the preferred libraries the choice is yours Chat GPT will make this entire time consuming process a cakewalk That s it for today for more such stories do subscribe Until next time have a good day peopleShreyiHateReading	2023-03-23 08:48:01
海外TECH	DEV Community	Effortless Language Redirection TYPO3 Extension	https://dev.to/visuellverstehen/effortless-language-redirection-typo3-extension-2514	Effortless Language Redirection TYPO Extension IntroductionHello fellow TYPO enthusiasts I had the pleasure of cooperating with my colleague malteriechmann to create a new TYPO extension called tlanguageredirection which provides an effortless and dependable way to redirect users to the preferred language version of your TYPO website In this blog post we will take a look at this fantastic project and reveal how it can add user friendliness to your multilingual website What does tlanguageredirection actually do This open source extension will configure a new frontend middleware that automatically redirects users to the appropriate language version of your website based on their browser s Accept Language header The LanguageRedirectionMiddleware is implemented using the PSR middleware interface making it easy to integrate into your existing TYPO project Why tlanguageredirection Unlike other TYPO redirection extensions tlanguageredirection does not require any additional configuration and is not dependent on the user s IP address Additionally it is designed to be independent of the underlying web servers providing a highly flexible and adaptable solution Say goodbye to complicated setups and hello to effortless language redirection Using tlanguageredirection will improve the user experience of a website and make it more accessible to a wider audience Whether your website is a small blog or a large e commerce site this extension is a nice to have tool for anyone looking to create a multilingual TYPO website How to use tlanguageredirection To get started simply install the extension using Composer composer require visuellverstehen tlanguageredirectionAfter installation the middleware will automatically handle language redirection of your website This means that visitors to your site will be redirected to the language version that best suits their needs without any additional effort on your part ConclusionThe tlanguageredirection extension simplifies the language redirection of your multilingual website with easy installation automatic redirection and seamless compatibility with any hosting environment The extension is still in the testing phase and we are constantly working to refine and improve its functionality Feel free to utilise it or to give us feedbacks and if you could star the repository we would appreciate it	2023-03-23 08:27:09
海外TECH	DEV Community	mTLS everywhere!	https://dev.to/apisix/mtls-everywhere-1k94	mTLS everywhere Security in one s information system has always been among the most critical Non Functional Requirements Transport Secure Layer aka TLS formerly SSL is among its many pillars In this post I ll show how to configure TLS for the Apache APISIX API Gateway TLS in a few wordsTLS offers several capabilities Server authentication the client is confident that the server it exchanges data with is the right one It avoids sending data which might be confidential to the wrong actorOptional client authentication the other way around the server only allows clients whose identity can be verifiedConfidentiality no third party can read the data exchanged between the client and the serverIntegrity no third party can tamper with the dataTLS works through certificates A certificate is similar to an ID proving the certificate s holder identity Just like an ID you need to trust who delivered it Trust is established through a chain if I trust Alice who trusts Bob who in turn trusts Charlie who delivered the certificate then I trust the latter In this scenario Alice is known as the root certificate authority TLS authentication is based on public key cryptography Alice generates a public key private key pair and publishes the public key If one encrypts data with the public key only the private key that generated the public key can decrypt them The other usage is for one to encrypt data with the private key and everybody with the public key to decrypt it thus proving their identity Finally mutual TLS aka mTLS is the configuration of two way TLS server authentication to the client as usual but also the other way around client authentication to the server We now have enough understanding of the concepts to get our hands dirty Generating certificates with cert managerA couple of root Certificate Authorities are installed in browsers by default That s how we can browse HTTPS websites safely trusting that is the site they pretend to be The infrastructure has no pre installed certificates so we must start from scratch We need at least one root certificate In turn it will generate all other certificates While it s possible to do every manually I ll rely on cert manager in Kubernetes As its name implies cert manager is a solution to manage certificates Installing it with Helm is straightforward helm repo add jetstack helm install cert manager jetstack cert manager namespace cert manager create namespace version v set installCRDs true set prometheus enabled false Add the charts repositoryInstall the objects in a dedicated namespaceDon t monitor in the scope of this postWe can make sure that everything works as expected by looking at the pods kubectl get pods n cert managercert manager cainjector fcc fcbk Running dh ago dcert manager ccbcf pt Running dh ago dcert manager webhook cdcbb tl Running dh ago dcert manager can sign certificates from multiple sources HashiCorp Vault Let s Encrypt etc To keep things simple We will generate our dedicated root certificate i e Self SignedWe won t handle certificates rotationLet s start with the following apiVersion cert manager io vkind ClusterIssuer metadata name selfsigned issuerspec selfSigned apiVersion vkind Namespacemetadata name tls apiVersion cert manager io vkind Certificate metadata name selfsigned ca namespace tlsspec isCA true commonName selfsigned ca secretName root secret issuerRef name selfsigned issuer kind ClusterIssuer group cert manager io apiVersion cert manager io vkind Issuer metadata name ca issuer namespace tlsspec ca secretName root secretCertificate authority that generates certificates cluster wideCreate a namespace for our demoNamespaced root certificate using the cluster wide issuer Only used to create a namespaced issuerNamespaced issuer Used to create all other certificates in the postAfter applying the previous manifest we should be able to see the single certificate that we created kubectl get certificate n tlsNAME READY SECRET AGEselfsigned ca True root secret sThe certificate infrastructure is ready let s look at Apache APISIX Quick overview of a sample Apache APISIX architectureApache APISIX is an API Gateway By default it stores its configuration in etcd a distributed key value store the same one used by Kubernetes Note that in real world scenarios we should set up etcd clustering to improve the resiliency of the solution For this post we will limit ourselves to a single etcd instance Apache APISIX offers an admin API via HTTP endpoints Finally the gateway forwards calls from the client to an upstream Here s an overview of the architecture and the required certificates Let s start with the foundational bricks etcd and Apache APISIX We need two certificates one for etcd in the server role and one for Apache APISIX as the etcd client Let s set up certificates from our namespaced issuer apiVersion cert manager io vkind Certificatemetadata name etcd server namespace tlsspec secretName etcd secret isCA false usages client auth server auth dnsNames etcd issuerRef name ca issuer kind Issuer apiVersion cert manager io vkind Certificatemetadata name apisix client namespace tlsspec secretName apisix client secret isCA false usages client auth emailAddresses apisix apache org issuerRef name ca issuer kind IssuerCertificate for etcdKubernetes Secret name see belowUsages for this certificateKubernetes Service name see belowReference the previously namespaced issuer created earlierCertificate for Apache APISIX as a client of etcdMandatory attribute for clientsAfter applying the above manifest we can list the certificates in the tls namespace kubectl get certificates n tlsNAME READY SECRET AGEselfsigned ca True root secret ms apisix client True apisix client secret ms etcd server True etcd secret ms Previously created certificateNewly created certificates signed by selfsigned ca cert manager s CertificatesSo far we have created Certificate objects but we didn t explain what they are Indeed they are simple Kubernetes CRDs provided by cert manager Under the cover cert manager creates a Kubernetes Secret from a Certificate It manages the whole lifecycle so deleting a Certificate deletes the bounded Secret The secretName attribute in the above manifest sets the Secret name kubectl get secrets n tlsNAME TYPE DATA AGEapisix client secret kubernetes io tls metcd secret kubernetes io tls mroot secret kubernetes io tls mLet s look at a Secret e g apisix client secret kubectl describe apisix client secret n tlsName apisix client secretNamespace tlsLabels controller cert manager io fao trueAnnotations cert manager io alt names cert manager io certificate name apisix client cert manager io common name cert manager io ip sans cert manager io issuer group cert manager io issuer kind Issuer cert manager io issuer name ca issuer cert manager io uri sans Type kubernetes io tlsData ca crt bytestls crt bytestls key bytesA Secret created by a Certificate provides three attributes tls crt The certificate itselftls key The private keyca crt The signing certificate in the certificate chain i e root secret tls crtKubernetes encodes Secret content in base To get any of the above in plain text one should decode it e g kubectl get secret etcd secret n tls o jsonpath data tls crt base BEGIN CERTIFICATE MIIDBjCCAegAwIBAgIQMJUR RvuUndjGK aOgzANBgkqhkiGwBAQsFADAYMRYwFAYDVQQDEwzZWxmclnbmVkLWNhMBXDTIzMDMxNjEwMTYyNoXDTIzMDYxNDEwMTYyNowADCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMQpMj giDVOjOosSRRKUwTzlWoRYYAeteOWfuMiAd XaBGmRO GWZQNtyRQpITMezBgogYAUUNcuqN UAsgH JMniMjZdjRKn itNjejFLtssnCnFfKJzRtYtySAgwtCwtXVXpmfCsfhPmnrGdWHXyYctzAZhqYfEswNhxpJZxRYVebWgDoPonpZo yYiMtoOimIprcmZYeWaiSQKDafUWlvUGQVVLzHPEdOMwbWcwiLqwUvTiKiCcyADwJOuPRFKKxxFnG lHlgJSisCpqocipEQ atOOyLMMECAwEAAaNkMGIwHQYDVRlBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMBMAwGAUdEwEB wQCMAAwHwYDVRjBBgwFoAUZaAdEficKUWPFRjdsKSEX lgbMwEgYDVRRAQH BAgwBoIEZXRjZDANBgkqhkiGwBAQsFAAOCAQEABcNvYTmZJejUqfdpNVulbUvloTpWxQjwXgcrhekSKUpZpIPwfauHLjceMFJLpteDifSQupeqXOofeyKSYjjyA aVfzMIReCCQtQuAVYyJWBlNLcXMMecbcpJLGtd OAZnKDeYYkUXcJwNWl wGLMlxsqDhEHEZwvGLDmsdHwhzSjdVmxsQgkhjVbNUKdBokUIvrPxDPaD FqGFyMssVOCHxtPxhOUA mDSrklfEFMcOfudZEbChOrJgVrUnYinRJbGQluEptYwPgyDdGMQEDDoLwp l NtTUqzWVlMxQ END CERTIFICATE Configuring mTLS between etcd and APISIXWith the certificates available we can now configure mutual TLS between etcd and APISIX Let s start with etcd apiVersion vkind Podmetadata name etcd namespace tls labels role configspec containers name etcd image bitnami etcd ports containerPort env name ETCD TRUSTED CA FILE value etc ssl private ca crt name ETCD CERT FILE value etc ssl private tls crt name ETCD KEY FILE value etc ssl private tls key name ETCD ROOT PASSWORD value whatever name ETCD CLIENT CERT AUTH value true name ETCD LISTEN CLIENT URLS value volumeMounts name ssl mountPath etc ssl private volumes name ssl secret secretName etcd secret Set the trusted CASet the certificateSet the private keyRequire clients to pass their certificate hence ensuring mutual authenticationMount the previously generated secret in the container for accessNow it s Apache APISIX s turn apiVersion vkind ConfigMap metadata name apisix config namespace tlsdata config yaml gt apisix ssl ssl trusted certificate etc ssl certs ca crt deployment etcd host https etcd tls cert etc ssl certs tls crt key etc ssl certs tls key admin allow admin https admin true admin api mtls admin ssl cert etc ssl private tls crt admin ssl cert key etc ssl private tls key admin ssl ca cert etc ssl private ca crt apiVersion vkind Podmetadata name apisix namespace tls labels role gatewayspec containers name apisix image apache apisix debian ports containerPort containerPort volumeMounts name config mountPath usr local apisix conf config yaml subPath config yaml name ssl mountPath etc ssl private name etcd client mountPath etc ssl certs volumes name config configMap name apisix config name ssl secret secretName apisix server secret name etcd client secret secretName apisix client secretApache APISIX doesn t offer configuration via environment variables We need to use a ConfigMap that mirrors the regular config yaml fileConfigure client authentication for etcdConfigure server authentication for the Admin APIRegular HTTPS portAdmin HTTPS portCertificates for server authenticationCertificates for client authenticationTwo sets of certificates are used one for server authentication for the Admin API and regular HTTPS and one for client authentication for etcd At this point we can apply the above manifests and see the two pods communicating When connecting Apache APISIX sends its apisix client certificate via HTTPS Because an authority signs the certificate that etcd trusts it allows the connection I ve omitted the Service definition for brevity s sake but you can check them in the associated GitHub repo NAME READY STATUS RESTARTS AGEapisix Running metcd Running m Client accessNow that we ve set up the basic infrastructure we should test accessing it with a client We will use our faithful curl but any client that allows configuring certificates should work e g httpie The first step is to create a dedicated certificate key pair for the client apiVersion cert manager io vkind Certificatemetadata name curl client namespace tlsspec secretName curl secret isCA false usages client auth emailAddresses curl localhost dev issuerRef name ca issuer kind Issuercurl requires a path to the certificate file instead of the content We can go around this limitation through the magic of zsh the syntax allows the creation of a temporary file If you re using another shell you ll need to find the equivalent syntax or download the files manually Let s query the Admin API for all existing routes This simple command allows checking that Apache APISIX is connected to etcd and it can read its configuration from there curl resolve admin https admin apisix admin routes cert kubectl get secret curl secret n tls o jsonpath data tls crt base d key kubectl get secret curl secret n tls o jsonpath data tls key base d cacert kubectl get secret curl secret n tls o jsonpath data ca crt base d H X API KEY eddcfffadbcf resolve avoids polluting one s etc hosts file curl will translate admin to localhost but the query is sent to admin inside the Kubernetes cluster thus using the correct ServiceGet the required data inside the Secret decode it and use it as a temporary fileIf everything works and it should the result should be the following total list No routes are available so far because we have yet to create any TLS with upstreamsLast but not least we should configure TLS for upstreams In the following I ll use a simple nginx instance that responds with static content Use it as an illustration for more complex upstreams The first step as always is to generate a dedicated Certificate for the upstream I ll skip how to do it as we already created a few I call it upstream server and its Secret unimaginatively upstream secret We can now use the latter to secure nginx apiVersion vkind ConfigMap metadata name nginx config namespace tlsdata nginx conf gt events worker connections http server listen ssl server name upstream ssl certificate etc ssl private tls crt ssl certificate key etc ssl private tls key root www data location index index json apiVersion vkind Podmetadata name upstream namespace tls labels role upstreamspec containers name upstream image nginx alpine ports containerPort volumeMounts name config mountPath etc nginx nginx conf subPath nginx conf name content mountPath www data index json subPath index json name ssl mountPath etc ssl private volumes name config configMap name nginx config name ssl secret secretName upstream secret name content configMap name nginx contentnginx doesn t allow configuration via environment variables we need to use the ConfigMap approachUse the key certificate pair created via the CertificateSome static content unimportant in the scope of this postThe next step is to create the route with the help of the Admin API We prepared everything in the previous step now we can use the API curl resolve admin https admin apisix admin routes cert kubectl get secret curl secret n tls o jsonpath data tls crt base d key kubectl get secret curl secret n tls o jsonpath data tls key base d cacert kubectl get secret curl secret n tls o jsonpath data ca crt base d H X API KEY eddcfffadbcf X PUT i d uri upstream scheme https nodes upstream tls client cert kubectl get secret curl secret n tls o jsonpath data tls crt base d client key kubectl get secret curl secret n tls o jsonpath data tls key base d Client auth for Admin API as aboveUse HTTPS for the upstreamConfigure key certificate pair for the route Apache APISIX stores the data in etcd and will use them when you call the route Alternatively you can keep the pair as a dedicated object and use the newly created reference just like for upstreams It depends on how many routes the certificate needs For more information check the SSL endpointFinally we can check it works as expected curl resolve upstream https upstream cert kubectl get secret curl secret n tls o jsonpath data tls crt base d key kubectl get secret curl secret n tls o jsonpath data tls key base d cacert kubectl get secret curl secret n tls o jsonpath data ca crt base d And it does hello world ConclusionIn this post I ve described a working Apache APISIX architecture and implemented mutual TLS between all the components etcd and APISIX client and APISIX and finally client and upstream I hope it will help you to achieve the same The complete source code for this post can be found on GitHub ajavageek tls apisix To go further How to Easily Deploy Apache APISIX in Kubernetescert managerA Simple CA Setup with Kubernetes Cert ManagerMutual TLS AuthenticationOriginally published at A Java Geek on March th	2023-03-23 08:24:03
海外TECH	Engadget	Meta's VR game publisher is now called 'Oculus Publishing'	https://www.engadget.com/metas-vr-game-publisher-is-now-called-oculus-publishing-080138830.html?src=rss	Meta x s VR game publisher is now called x Oculus Publishing x Meta s publishing arm for virtual reality games is now officially called Oculus Publishing It s a completely different division from Oculus Studios which is the company s label for first party games Oculus Publishing will instead support partner developers with conceptualization funding technological help as well as promotion and merchandising While the name is new the division itself isn t It had previously funded and supported over titles including Among Us VR Bonelab and The Walking Dead Saints amp Sinners The company has also revealed that Oculus Publishing has over titles currently in development which bodes well for the Quest that s expected to arrive this year Previous reports suggested that the next gen Quest will be thinner and more powerful than its predecessor and will have mixed reality capabilities That could mean that some of these new titles ーMeta unfortunately didn t name any of them in its announcement ーmay have features that weren t possible for older games nbsp At the moment users still have more than titles to choose from in the Meta Quest Store and they seem to be doing well Last year the company said the games and apps on the store had surpassed billion in revenue with titles grossing over million In addition the number of titles that had reached million in revenue had doubled year over year This article originally appeared on Engadget at	2023-03-23 08:01:38
ニュース	BBC News - Home	Mosque fire suspect charged with attempted murders	https://www.bbc.co.uk/news/uk-england-birmingham-65049307?at_medium=RSS&at_campaign=KARANGA	london	2023-03-23 08:53:17
ニュース	BBC News - Home	Cristiano Ronaldo: Portugal forward on brink of more international history	https://www.bbc.co.uk/sport/football/65037274?at_medium=RSS&at_campaign=KARANGA	portugal	2023-03-23 08:29:43
GCP	Google Cloud Platform Japan 公式ブログ	Built with BigQuery: 大規模に不正行為検出ワークフローのバックテストを行う Sift	https://cloud.google.com/blog/ja/products/data-analytics/how-sift-delivers-fraud-detection-workflow-backtesting-at-scale/	このサービスによりリクエストが解析され、BigQueryに対してすべてのクエリが正しい順序で実行されます。	2023-03-23 09:50:00
GCP	Google Cloud Platform Japan 公式ブログ	人命を救うことを目指す Sumitovant が 2 倍を超える研究成果を実現	https://cloud.google.com/blog/ja/products/data-analytics/sumitovant-chooses-looker-for-custom-queries/	チームの研究者、薬剤師、医療専門家、データサイエンティストの多様なニーズに応えるこのダッシュボードを使用することで、問いに対する答えを得るのに今までは何日もかかっていたのが、わずか数秒で答えを手にできるようになりました。	2023-03-23 09:40:00
GCP	Google Cloud Platform Japan 公式ブログ	初の「Google for Startups アクセラレータ: 欧州における気候変動」に選出されたチームのご紹介	https://cloud.google.com/blog/ja/topics/sustainability/fourteen-climate-startups-selected-to-google-european-accelerator/	適応策や気候対策に向けて画期的な技術で取り組むスタートアップ企業は、気候行動を加速させるうえで重要な役割を担っていますGoogleでは、AIを活用した技術によってサステナビリティを推進するスタートアップ企業の活発なエコシステムを育成するとともに、彼らの成長を支援するメンターシップの機会、技術的な専門知識、クラウドテクノロジーを提供する橋渡しをしたいと考えています。	2023-03-23 09:30:00
GCP	Google Cloud Platform Japan 公式ブログ	Kochava のモバイル分析プラットフォームを強化した Cloud Spanner	https://cloud.google.com/blog/ja/products/databases/kochava-mobile-analytics-platform-runs-on-cloud-spanner/	これを実現するため、Kochavaのお客様アカウントをプロビジョニングする際、自動的にSpannerリソースを作成します。	2023-03-23 09:20:00
GCP	Google Cloud Platform Japan 公式ブログ	ML を活用して天気と気候のリスクを予測	https://cloud.google.com/blog/ja/topics/sustainability/weather-prediction-with-ai/	また、より優れた予測モデルを構築するAI技術も、ディープラーニングと呼ばれるニューラルネットワークによって進化してきました。	2023-03-23 09:10:00
ニュース	Newsweek	魚が大量死...川を埋め尽くす2000万匹もの死骸...衝撃の光景　オーストラリア	https://www.newsweekjapan.jp/stories/world/2023/03/2000-23.php		2023-03-23 17:10:00
IT	週刊アスキー	この絶望は抗えない――『地球防衛軍6』追加ミッションパック第1弾「Lost Days」が本日配信！	https://weekly.ascii.jp/elem/000/004/129/4129799/	lostdays	2023-03-23 17:55:00
IT	週刊アスキー	菱洋エレクトロ、高いグラフィックス性能を有したビデオカード「NVIDIA RTX 4000 SFF Ada世代」を販売開始	https://weekly.ascii.jp/elem/000/004/129/4129790/	nvidiartxsffada	2023-03-23 17:40:00
IT	週刊アスキー	DMMプレミアムとDAZNがセットで2980円！　DMM×DAZNホーダイ提供開始	https://weekly.ascii.jp/elem/000/004/129/4129793/	提供開始	2023-03-23 17:40:00
IT	週刊アスキー	360度自在なカメラワークのリプレイが可能　キヤノンが東京ドームにボリュメトリックビデオシステムを納入	https://weekly.ascii.jp/elem/000/004/129/4129794/	日本テレビ	2023-03-23 17:30:00
IT	週刊アスキー	Mozilla、信頼できるAIを目指すスタートアップ「Mozilla.ai」を設立	https://weekly.ascii.jp/elem/000/004/129/4129800/	aitrustworthyai	2023-03-23 17:25:00
IT	週刊アスキー	小田急電鉄、特急ロマンスカー・VSE（50000形）などをデザインテーマにしたNFTを発売	https://weekly.ascii.jp/elem/000/004/129/4129737/	小田急電鉄	2023-03-23 17:20:00
マーケティング	AdverTimes	KIGIによるショップ「OFS」が移転、オープニングに服部一成展を開催	https://www.advertimes.com/20230323/article414421/	bluestract	2023-03-23 08:11:52
GCP	Cloud Blog JA	Built with BigQuery: 大規模に不正行為検出ワークフローのバックテストを行う Sift	https://cloud.google.com/blog/ja/products/data-analytics/how-sift-delivers-fraud-detection-workflow-backtesting-at-scale/	このサービスによりリクエストが解析され、BigQueryに対してすべてのクエリが正しい順序で実行されます。	2023-03-23 09:50:00
GCP	Cloud Blog JA	人命を救うことを目指す Sumitovant が 2 倍を超える研究成果を実現	https://cloud.google.com/blog/ja/products/data-analytics/sumitovant-chooses-looker-for-custom-queries/	チームの研究者、薬剤師、医療専門家、データサイエンティストの多様なニーズに応えるこのダッシュボードを使用することで、問いに対する答えを得るのに今までは何日もかかっていたのが、わずか数秒で答えを手にできるようになりました。	2023-03-23 09:40:00
GCP	Cloud Blog JA	初の「Google for Startups アクセラレータ: 欧州における気候変動」に選出されたチームのご紹介	https://cloud.google.com/blog/ja/topics/sustainability/fourteen-climate-startups-selected-to-google-european-accelerator/	適応策や気候対策に向けて画期的な技術で取り組むスタートアップ企業は、気候行動を加速させるうえで重要な役割を担っていますGoogleでは、AIを活用した技術によってサステナビリティを推進するスタートアップ企業の活発なエコシステムを育成するとともに、彼らの成長を支援するメンターシップの機会、技術的な専門知識、クラウドテクノロジーを提供する橋渡しをしたいと考えています。	2023-03-23 09:30:00
GCP	Cloud Blog JA	Kochava のモバイル分析プラットフォームを強化した Cloud Spanner	https://cloud.google.com/blog/ja/products/databases/kochava-mobile-analytics-platform-runs-on-cloud-spanner/	これを実現するため、Kochavaのお客様アカウントをプロビジョニングする際、自動的にSpannerリソースを作成します。	2023-03-23 09:20:00
GCP	Cloud Blog JA	ML を活用して天気と気候のリスクを予測	https://cloud.google.com/blog/ja/topics/sustainability/weather-prediction-with-ai/	また、より優れた予測モデルを構築するAI技術も、ディープラーニングと呼ばれるニューラルネットワークによって進化してきました。	2023-03-23 09:10:00