投稿時間:2023-05-31 19:34:21 RSSフィード2023-05-31 19:00 分まとめ(39件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
IT	気になる、記になる…	Belkin、コンパクトながら100W PD充電に対応した4ポートUSB-Cハブ｢Connect USB-C to 4ポートUSB-Cハブ｣を発売	https://taisy0.com/2023/05/31/172336.html	belkin	2023-05-31 09:33:35
IT	気になる、記になる…	Firefox、｢Windows 7/8/8.1｣のサポートを7月リリース予定のver.115で終了へ	https://taisy0.com/2023/05/31/172332.html	firefox	2023-05-31 09:17:49
IT	ITmedia 総合記事一覧	[ITmedia ビジネスオンライン] サブバンクの使い道　2位「クレカ引落し」、1位は？	https://www.itmedia.co.jp/business/articles/2305/31/news214.html	itmedia	2023-05-31 18:50:00
IT	ITmedia 総合記事一覧	[ITmedia News] 無料通話の「LINE Out」終了　コールクレジット残高は払い戻し	https://www.itmedia.co.jp/news/articles/2305/31/news217.html	払い戻し	2023-05-31 18:28:00
IT	ITmedia 総合記事一覧	[ITmedia Mobile] Motorola、内蔵ペン付きスマホ「moto G Stylus 5G（2023)」はSnapdragon 6 Gen 1搭載	https://www.itmedia.co.jp/mobile/articles/2305/31/news218.html	ITmediaMobileMotorola、内蔵ペン付きスマホ「motoGStylusG」はSnapdragonGen搭載MotorolaMobilityは、内蔵ペン付きスマートフォン「motoGStylusG」を発表した。	2023-05-31 18:27:00
IT	ITmedia 総合記事一覧	[ITmedia ビジネスオンライン] エクサウィザーズ、企業向けの生成・対話型AIサービスを開始　独自機能を搭載	https://www.itmedia.co.jp/business/articles/2305/30/news075.html	aipoweredbygpt	2023-05-31 18:27:00
IT	ITmedia 総合記事一覧	[ITmedia News] PayPay、「あなたのまちを応援プロジェクト」の7月追加分発表　福島県など　最大30％のポイント付与	https://www.itmedia.co.jp/news/articles/2305/31/news215.html	itmedianewspaypay	2023-05-31 18:25:00
TECH	Techable（テッカブル）	ドラム演奏で簡単に認知症重症度をスクリーニング、ウェラブルデバイス「Moffバンド」を研究に使用	https://techable.jp/archives/209541	重症	2023-05-31 09:40:36
TECH	Techable（テッカブル）	Astar Network参画Web3セミナーが6月開催。ブロックチェーン活用事例などを紹介	https://techable.jp/archives/209522	astarnetwork	2023-05-31 09:20:28
TECH	Techable（テッカブル）	体験は360°で残す時代。編集・配信クラウドサービス「WHERENESS」提供開始	https://techable.jp/archives/209651	whereness	2023-05-31 09:00:19
IT	情報システムリーダーのためのIT情報専門サイト IT Leaders	住友重機械工業、日本とアジア地域の1万5000人が使うインターネットゲートウェイを「Menlo Security」で刷新 | IT Leaders	https://it.impress.co.jp/articles/-/24894	住友重機械工業、日本とアジア地域の万人が使うインターネットゲートウェイを「MenloSecurity」で刷新ITLeaders住友重機械工業本社東京都品川区は、インターネット接続のセキュリティを確保するゲートウェイ環境を刷新し、クラウド型のセキュリティゲートウェイサービス「MenloSecurity」を導入した。	2023-05-31 18:25:00
AWS	lambdaタグが付けられた新着投稿 - Qiita	AWS Lambda のデプロイ（CLI）	https://qiita.com/KUROMAGOORO/items/87b936a57b76686c5d0b	awslambda	2023-05-31 18:34:38
AWS	lambdaタグが付けられた新着投稿 - Qiita	AWS Lambda のデプロイ（コンソール）	https://qiita.com/KUROMAGOORO/items/fa2610f734fce8b27497	awslambda	2023-05-31 18:33:50
python	Pythonタグが付けられた新着投稿 - Qiita	Tobii製アイトラッカーで動画再生中の視線追跡（2/3，動画再生中の視線追跡）	https://qiita.com/takahashiMamo/items/da88d9e5b5c0bccd9804	tobii	2023-05-31 18:54:36
python	Pythonタグが付けられた新着投稿 - Qiita	PDFファイルを分割するpythonスクリプト	https://qiita.com/n-taishi/items/c7b7e006d985df29b874	acrobat	2023-05-31 18:03:58
AWS	AWSタグが付けられた新着投稿 - Qiita	AWS Lambda のデプロイ（CLI）	https://qiita.com/KUROMAGOORO/items/87b936a57b76686c5d0b	awslambda	2023-05-31 18:34:38
AWS	AWSタグが付けられた新着投稿 - Qiita	AWS Lambda のデプロイ（コンソール）	https://qiita.com/KUROMAGOORO/items/fa2610f734fce8b27497	awslambda	2023-05-31 18:33:50
Docker	dockerタグが付けられた新着投稿 - Qiita	WSL2上、docker buildでgo mod downloadしたとき"x509: certificate signed by unknown authority" error	https://qiita.com/s-park/items/0689ce7449ec509e3645	dockerbuild	2023-05-31 18:35:20
Docker	dockerタグが付けられた新着投稿 - Qiita	「そのコンテナのデータ、消えるよ……」とさせないための、イメージ図＋実践で理解するDockerストレージ【Dockerコンテナ・グレートジャーニー③】	https://qiita.com/Toyo_m/items/95a2543c07dc5b126208	docker	2023-05-31 18:24:26
技術ブログ	Mercari Engineering Blog	「Merpay Tech Openness Month 2023」開催のお知らせ	https://engineering.mercari.com/blog/entry/20230531-notice-merpay-tech-openness-month-2023/	hellip	2023-05-31 10:00:13
技術ブログ	Developers.IO	AWS Step FunctionsのエラーをAWS User Notificationsを使って簡単に通知してみた(メール・Slack)	https://dev.classmethod.jp/articles/aws-step-functions%e3%81%ae%e3%82%a8%e3%83%a9%e3%83%bc%e3%82%92aws-user-notifications%e3%82%92%e4%bd%bf%e3%81%a3%e3%81%a6%e7%b0%a1%e5%8d%98%e3%81%ab%e9%80%9a%e7%9f%a5%e3%81%97%e3%81%a6%e3%81%bf/	awsawsstepfun	2023-05-31 09:32:49
技術ブログ	Developers.IO	【Security Hub修復手順】[CloudFront.10] CloudFront ディストリビューションは、エッジロケーションとカスタムオリジン間に非推奨の SSL プロトコルを使用しないでください	https://dev.classmethod.jp/articles/securityhub-fsbp-remediation-cloudfront-10/	【SecurityHub修復手順】CloudFrontCloudFrontディストリビューションは、エッジロケーションとカスタムオリジン間に非推奨のSSLプロトコルを使用しないでくださいこんにちは、AWS事業本部福岡オフィスのべこみんbecominnです。	2023-05-31 09:17:22
海外TECH	DEV Community	Flutter Column Widget Example	https://dev.to/realnamehidden1_61/flutter-column-widget-example-14em	Flutter Column Widget Exampleimport package flutter material dart void main runApp MyApp class MyApp extends StatelessWidget This widget is the root of your application override Widget build BuildContext context return MaterialApp title Flutter Demo theme ThemeData This is the theme of your application Try running your application with flutter run You ll see the application has a blue toolbar Then without quitting the app try changing the primarySwatch below to Colors green and then invoke hot reload press r in the console where you ran flutter run or simply save your changes to hot reload in a Flutter IDE Notice that the counter didn t reset back to zero the application is not restarted primarySwatch Colors blue home ColumnWidget class ColumnWidget extends StatelessWidget const ColumnWidget super key override Widget build BuildContext context return Scaffold appBar AppBar title Text Column Widget body Container width child Column mainAxisAlignment MainAxisAlignment start crossAxisAlignment CrossAxisAlignment stretch children Container height width color Colors red Container height width color Colors black Container height width color Colors amber	2023-05-31 09:45:21
海外TECH	DEV Community	Types of Entities in Entity Framework	https://dev.to/sardarmudassaralikhan/types-of-entities-in-entity-framework-3f52	Types of Entities in Entity FrameworkIn Entity Framework EF there are mainly three types of entities that are commonly used Persistent Entities These entities represent the data model and correspond to tables in the database They are mapped to database tables and have a one to one mapping with the underlying database schema Persistent entities are typically annotated with attributes or configured using fluent API to define their mappings to database tables Complex Types Complex types are classes that are used as properties within persistent entities They are not mapped to their own tables in the database but rather stored as part of the parent entity s table Complex types are used to encapsulate a group of related properties that logically belong together Enumerations Enums Enums are a special type of entity in EF that represent a fixed set of named values They can be used to define properties on persistent entities that have a limited set of possible values Enums are often used to provide more meaningful and type safe representations for certain properties These three types of entities are the basic building blocks used in Entity Framework to model and interact with data in a database Certainly Here are the types of entities in Entity Framework with examples Persistent Entities Person Represents a person with properties like Id Name Age etc public class Person public int Id get set public string Name get set public int Age get set Product Represents a product with properties like Id Name Price etc public class Product public int Id get set public string Name get set public decimal Price get set Complex Types Address Represents an address with properties like Street City State etc Used as a complex type within another entity public class Address public string Street get set public string City get set public string State get set OrderItem Represents an item in an order with properties like ProductId Quantity Price etc Used as a complex type within the Order entity public class OrderItem public int ProductId get set public int Quantity get set public decimal Price get set Enumerations Enums Gender Represents the gender of a person with values Male Female and Other public enum Gender Male Female Other OrderStatus Represents the status of an order with values Pending Shipped Delivered etc public enum OrderStatus Pending Shipped Delivered These are just examples to illustrate the different types of entities in Entity Framework In practice you would define your own entities based on your application s requirements and domain model	2023-05-31 09:16:03
海外TECH	DEV Community	There is no right or wrong, as long as it works - Actually how you use DynamoDB makes a lot of difference!	https://dev.to/aws-builders/there-is-no-right-or-wrong-as-long-as-it-works-actually-how-you-use-dynamodb-makes-a-lot-of-difference-2668	There is no right or wrong as long as it works Actually how you use DynamoDB makes a lot of difference Some time ago a friend of mine asked me for advice about a serverless app he was working on He had always worked as frontend developer but due to some layoffs in his company he had to fix add features to the backend too The backend consisted of a simple ApiGateway Lambda Dynamo and specifically he was dealing with an issue aggregating data from multiple tables and editing records He was struggling in understanding how things were done and most importantly why they were done that way his experienced developer s th sense warned him about something fishy but when you start with something new be it a language or framework and you happen to be working on an existing codebase that has been running on production for at least a couple of years you tend to assume that what you see is the way to go and you tend to learn from those examples and the patterns you find That s why he approached me Just by looking at the some metrics in AWS Cloudwatch and at the AWS Cost Explorer it was pretty evident that something was off in the way the database had been modeled or at least in how it was queried compared to the number of requests to the backend the number of Read and Write Capacity Units consumed was very very high Nothing is wrong here Before we dive into the coding part let me tell you a story I am a passionate climber and recently wanting to push a bit beyond my current skills I decided to hire a trainer After one of the first climbs she asked me how it went if I noticed something in the way I approached and concluded the route How did it go Not really great I made some mistakes while passing the crux But you reached the top That s what matters wasn t that your goal Naaa I really got the beta wrong But you managed it so why do you think you did it wrong Because I was slow my movements were not elegant at all and I felt really pumped long before the top Alright but that it s not a matter of right or wrong You reached the top so you did good You haven t climbed wrong you just climbed inefficiently You had not properly visualised your movements before you started you tried different moves along the route used your body weight and positioned your hands and foot in a way that costed you time and therefore energy If your goal is to climb faster longer or harder you need to pay more attention at how efficient you move and at how you utilise your resources vision breathing explosive energy stamina mental strength recovery time and so on It s working who cares about how That immediately reminded me at the many times when during meetings at work be it discussions about the possibility of a refactor a code review or just the estimate of a new feature someone dropped the classic nobody cares about the code as long as it satisfies the users needs works and it shipped on time Who cares if it s NodeJs or Python if it uses DynamoDB or PostgreSQL if it s Clean Code or a Big ball of Mud if it has tests or if it s an undocumented untestable mess as long as it works it s OK As long as it works Of course no one cares as long as it works because no one will notice how things are done until a big bug happens on production or the Cloud bill starts growing wild or any new feature start taking ages to be implemented and introduces exponentially more bugs Technical Debt creeps in sprint after sprint and it poor code quality or wrong bad sorry inefficient not sustainable unscalable architectural choices show their nefarious only after weeks or months or even years Will it become a problem we don t know but we might know if we reason about our goals and about purpose Is this piece of code a temporary feature Is this app just a proof of concept Do I need to hit the market as fast as possible will it need to scale How much will it cost Am I taking into account the possibility that if everything goes well I will need some future buffer to fix the shortcuts I am taking In the case of my friend code base the backend was written by a contractor engaged to write a proof of concept The code was then simply pushed to production and new functionality added by unexperienced backend developers like my friend following the poor coding practices of a prototype not the best practices a production app should have That resulted in an undocumented untestable mess that indeed absolutely did the job but at the expenses of the poor developers that had to maintain it and of the management that paid the AWS bill who did not know and does not care as long the app is making profit So what was wrong inefficient in my friend s code base It turned out thatthe Database model was inappropriate considering how the app grew since the prototype using NoSQL with more than tables and different secondary indexes the queries to gather data with was sort of relational were not optimised properly being run simply in a sequence those queries were returning way more data that was needed with considerable weight and complexity in aggregating filtering out data that was not necessarysince edit operation always overwrote the entire row loading the row was necessary in order to just edit a couple of propertiesthere was no caching whatsoever Deep Dive into DynamoDBLet s take a closer look about the advice I gave to my friend to improve the code base reduce latency and cut costs altogether Favour Single Table DesignI won t go into the details of Single Table Design vs Multi Table design too much since AWS Hero Alex De Brie wrote extensively about it you can read really interesting stuff here and here and watch this mindblowing talk by Rick Houlihan but to put it simply using a Single Table Design means that you have rows containing different data and you use specific access patterns with Partition and Sort Keys and prefixes and Secondary indexes to load all only the data you need Starting out with multiple tables can be simpler need to store app configuration here a configTable need to store user data here a userDataTable need to add user friends here a userFriendsTable for you need to add user orders tadaa a userOrdersTable ready for you and so on in a very much Relational way of doing things This approach is not only not leveraging NoSQL and the amazing capabilities of DynamoDB but will also in the long run actually pretty soon reveal quite impractical and require to make multiple requests to multiple tables and aggregate join data on your side which bring us to the next point Optimise queries to DynamoDB tablesWhen the app needed some aggregation of data the backend was often querying multiple tables at once then compose an object with all the needed props and returning it to the client Continuing the example above to gather all UserData with friends and orders you need to retrieve the right row from UserData table the Orders of that UserID using a secondary index because OrderTable has a PK with orderId and then friends from Friends Table The implementation was suboptimal requests were done in order one after another only to aggregate data when everything was finally available like in this pseudo code simplified way const userData loadUser id then loadTheirOrders then loadTheirFriends orconst userData await loadUser id const userFriends await loadFriends userData id const userOrders await loadOrders userData id const fullUserData basicData userData friends userFriends orders userOrders Much better would have been to make requests in parallel so that you wait only for the one taking the longest not for the sum of the const promises loadUser id loadFriends userData id loadOrders userData id const fullUser await Promise all promises you still need to grab and aggregate the result from all the promises but hopefully you got what i meanMuch much better run single call to dynamo with aBatchGetItemCommand const batchGetItemInput RequestItems table one Keys YOUR PRIMARY KEY S id YOUR SORT KEY S sortValue here you can even load multiple users at the same time table two Keys YOUR PRIMARY KEY S id Add more key value pairs as needed Add more table names and keys as needed const batchResponse await dynamoDocClient send new BatchGetItemCommand batchGetItemInput return response Responses you still need to grab your data and combine it as you like it but you get everything loaded at once with just one request Batch Commands can be very powerful Especially for Transactions and multiple operations at once I really recommend to check them outSmall note weirdly I was not able to use the BatchCommand without specifying the DynamoDataTypes in the KeyValueAttributes something that normally using the DocumentClient is not necessary Load only what you needIn many cases the backend code was loading the entire row from a table even though the data that was necessary was just one property To read data from a table you use operations such as GetItem Query or Scan Amazon DynamoDB returns all the item attributes by default To get only some rather than all of the attributes use a projection expression So if you just need the score and the language of a user you don t need to load the entire user data but just those two attributes it is as simple as specifying those properties in the GetItemCommandInputProjectionExpression score language I know I know using Projection Expression does not any effect whatsoever in the cost of your request like Filters they are applied after the data has been retrieved by DynamoDB therefore there is no difference in terms of RCUs Read Capacity Units Nevertheless there is less data sent out over the wire which can have positive effects on latency and on your users data plan consumption and in my opinion makes manipulating the response easier and the code cleaner Update only what changedAssuming you want to change the email address or update the user loyalty points of user you would ideally receive from the client just the user id and the new value and you would then update just those properties in the database Similarly to the way the request were sequentially made to multiple tables and entire data was passed around editing operation were written in a very simple and un optimised way Query the entire rowEdit a couple of properties in the loaded objectOverwrite the row with the modified object const parameters TableName table Key UserId id const user await dynamoDocClient send new GetCommand parameters user emailAddress newEmailAddressuser score const parameters TableName table Item user const response await dynamoDocClient send new PutCommand parameters DynamoDB though has an UpdateItemCommand that allows us exactly to update only specific attributes of a record without requiring us to query for it assuming we know its partition key and eventually the sort key const parameters Key USER ID id SK sk sort key if you have one TableName YOUR TABLE NAME ReturnValues ALL NEW UpdateExpression ADD score v score ExpressionAttributeNames score score ExpressionAttributeValues v score scoreChange const response await dynamoDocClient send new UpdateCommand parameters return response AttributesDynamo comes with different handy UpdateExpressions Set to modify a value ADD to increase decrease numbers REMOVE to remove attributes entirely and so on and most importantly you can even use ConditionExpressions to determine which items should be modified If the condition expression evaluates to true the operation succeeds otherwise the operation fails I wrote a post some time ago about how to dynamically create Dynamic Update Expression from an object of modified properties read it here Want to know how that is affecting costs A strongly consistent read request of an item up to KB requires one read request unit An eventually consistent read request of an item up to KB requires one half read request unit A transactional read request of an item up to KB requires two read request units If you need to read an item that is larger than KB DynamoDB needs additional read request units from the docsAfter a simple refactoring we changed the previous update method which was every time loading the entire row to edit just a couple of properties and the overwrite the entire row with the modified object into a smaller method whose responsibility was receiving the PK and SK and the props values that had change and taking advantage of the UpdateItem method of DynamoDB In our samples where the rows had just a few attributes and very little data this was the difference get edit put ms gt WCU and RCUupdate ms gt WCUPremature optimisation Just overkill to shave off few milliseconds At the time of the prototype or when the application was launched to production probably it could have been considered so but looking at how the app usage has increased and the code has evolved thousands of requests per minute and records requiring RCU each time a really meaningful change I agree the syntax of Update Expressions is not the best and it is definitely uglier and more complicated than editing a javascript object Just compare pseudocodeconst object getItem id obj name new name obj address new address obj orders writeItem obj to UpdateExpression set name v name address v address ExpressionAttributeNames name name address address ExpressionAttributeValues v name new name v address new address updateItem params but UdpateExpressions allow to express intent more clearly and most importantly leverage the capabilities of DynamoDB Some more findingsSomething interesting I found out while writing some sample for this post is the difference between List and StringSet in the DynamoDB DataTypes Since I always used NodeJs and the DynamoDBDocumentClient I never had to bother about Marshalling and Unmarshalling and defining the data types just pass a json or a JS object and DynamoDBDocumentClient takes care of everything While testing the Update Expression though I struggled with the removing of items from an array list Adding is simple you don t need to know the previous list of orders to be able to push a new one and overwrite the data on the database just create an Update Expression with the new order id and dynamo will append it to the list when updating the item more in the docs Expression SET orders list append orders v orderId ExpressionAttributeNames orders orders ExpressionAttributeValues v orderId orderChange id To remove an item on the other hand you need to specify the index which is not something very handy or something that you have might know UpdateExpression REMOVE orders ExpressionAttributeNames orders orders The docs state that in case of Sets you can actually use the DELETE operator but whatever I tried was failing due to Incorrect operand type for operator or function operator DELETE operand type LIST typeSet ALLOWED FOR DELETE OPERANDIn fact checking my record in the Dynamo UI Console my orders were a simple List not a String Set When I tried to create manually from the console a new Attribute as a String Set I noticed that suddenly the console was not giving me the possibility to switch off the View DynamoDB JSON thus forcibly showing the data types moarOrders SS orders L S S instead of the simplified orders Apparently then if using DynamoDBDocumentClient which has the advantage of saving you the marshalling unmarshalling you also loose some of the DynamoDB DataTypes and thus you can t take advantage of specific update expressions Drop a comment with a snippet if you know how to do that it would be highly appreciated Cache what does not change frequentlySome of the data that was loaded from Dynamo and returned to the Client was not user specific it could be generic app configuration lists of available products to buy feature flags stats from the previous day and so on But they were loaded from DynamoDB every time for every user connecting Having Cloudfront before your API Gateway could be a valid solution to cache data and reduce the number of requests hitting your endpoint gt lambda gt dynamo Of course Cloudfront is not free and you need to understand how frequently your data changes and if it makes sense to shift costs to the CDN but having data cached would also have benefits on the responsiveness of your app If you can t or don t want to use a CDN you can consider other in memory caches to avoid sending the requests to Dynamo the risk of having stale data among Lambdas or different containers is high though so unless you have a Fat Lambda and you need the same data for multiple endpoints methods managed by the same handler I would not suggest it But there are also other solutions that come at a cost like Momento or AWS DAX RecapIn this post I wanted to highlight the fact that usually it is really not that important how things are done But at some point we need to consider where we want to go next we need to reconsider the choices we have made and we might need to face the fact that before moving on some changes are necessary Overall my advice is take time to thinkstart simple and iteratetake the time to tackle tech debtRTFM often when dealing with new problems or starting out with new languages we stick with what we know and use old approaches This is the case with DynamoDB if you always used relational Databases or with functional programming if you come from strictly type and object oriented languages or when adopting a serverless event driven mindset Invest some time in reading the docs and understanding the tool you are using avoid judgement and blame often when looking at some legacy code we tend to ask ourselves gt how the heck could that guy end up writing this crap how is it even possible that the architect tech lead made this silly decision the answer is that they did not know what we know now in hindsight everything is obvious and simple they could not predict if their proof of concept would evolve into a full blown production app nor if that app would have users per day or thousand per minute Always be patient and forgiving about whatever you find in a legacy code base and whoever was responsible for writing it Specifically to DynamoDB these are my suggestions use Single Table Design use Batch whenever possibleleverage UpdateExpression and Condition ExpressionsHope it helps Other related articles you might find interesting DynamoDB dynamic method to insert or edit an itemStop Think Code IterateMake mistakes and ask questions It s OK Strive for simplicityKeep your Ego away from codingSoftware Engineering is about trade offs make sure you have options architecture patterns comparison Working on legacy code bases can make us better developers here is why Foto von lee attwood auf UnsplashThe crux is the hardest part of a route  to climb a route also referred as to solve the problem you have to visualise the movements you will make the beta is climbing  tight swollen burning and sometimes painful feeling that occurs in our forearms when we re climbing as a result of lactic acid build up	2023-05-31 09:10:39
海外TECH	Engadget	Google has officially stopped supporting the first-gen Chromecast	https://www.engadget.com/google-has-officially-stopped-supporting-the-first-gen-chromecast-095205330.html?src=rss	Google has officially stopped supporting the first gen ChromecastIt s officially the end of an era for the original Google Chromecast with the first generation model no longer receiving any updates or support toGoogle reports Chromecast first came on the scene in as a key sized device that promised to provide a Smart TV experience for and it has done just that Google has upgraded the initial Chromecast s hardware throughout the years to keep up with streaming denands but is now leaving it behind for good In a release on Chromecast s informational hub Google asserted that quot Support for Chromecast st gen has ended which means these devices no longer receive software or security updates and Google does not provide technical support for them Users may notice a degradation in performance quot Google last updated Chromecast s support page back in April meaning the announcement has gone unnoticed for some time now nbsp Through the lens of Google alone a complete pull back on the year old Chromecast original has been a long time coming The company has only looked after the first gen s bug and security issues rather than larger scale updates since The last update came in November and was the first in three years Google has also released newer versions since the first gen like the cheaper Chromecast with Google TV HD and the K model nbsp If you re a loyal first gen Chromecast user the only thing to do now is to make sure it s fully upgraded and hope for the best nbsp This article originally appeared on Engadget at	2023-05-31 09:52:05
海外科学	NYT > Science	Honoring the Body Donors Who Are a Medical Student’s ‘First Patient’	https://www.nytimes.com/2023/05/31/science/donor-bodies-medical-school-appreciation.html	Honoring the Body Donors Who Are a Medical Student s First Patient Gratitude ceremonies give students and faculty members a chance to recognize the sacrifice of those who gave their bodies for medical research and education and the loved ones they left behind	2023-05-31 09:30:19
海外科学	NYT > Science	State Farm Stops Offering Insurance in California	https://www.nytimes.com/2023/05/31/climate/climate-change-insurance.html	State Farm Stops Offering Insurance in CaliforniaThe largest insurer in California said it would stop offering new coverage It s part of a broader trend of companies pulling back from dangerous areas	2023-05-31 09:01:12
金融	JPX マーケットニュース	[東証]監理銘柄（確認中）の指定：（株）ビジョナリーホールディングス	https://www.jpx.co.jp/news/1023/20230531-12.html	監理銘柄	2023-05-31 18:30:00
金融	金融庁ホームページ	無登録で金融商品取引業を行う者の名称等を更新しました。	https://www.fsa.go.jp/ordinary/chuui/mutouroku.html	金融商品取引業	2023-05-31 11:00:00
金融	ニッセイ基礎研究所	再び動き出すガソリン価格～補助金縮小・終了で上昇余地が発生	https://www.nli-research.co.jp/topics_detail1/id=74961?site=nli	「燃料油価格激変緩和事業」という名称が示す通り、当初の建付けではガソリン価格の「変動」を抑制する仕組みとなっており、補助金額の算定基準となる基準価格はリットル円から段階的に引き上げられるつまり、補助後のガソリン価格が緩やかに上昇する予定となっていた。	2023-05-31 18:20:13
ニュース	BBC News - Home	Train strikes this week to hit FA Cup final and Epsom Derby	https://www.bbc.co.uk/news/business-65762990?at_medium=RSS&at_campaign=KARANGA	derbytrain	2023-05-31 09:46:59
ニュース	BBC News - Home	CBI president in early exit as lobby giant fights to survive	https://www.bbc.co.uk/news/business-65756123?at_medium=RSS&at_campaign=KARANGA	mcbride	2023-05-31 09:47:08
ニュース	BBC News - Home	Rhodes death: Liverpool man 'struck by lightning while paddleboarding'	https://www.bbc.co.uk/news/uk-england-merseyside-65763189?at_medium=RSS&at_campaign=KARANGA	local	2023-05-31 09:19:59
ニュース	BBC News - Home	Rhys Webb: Scrum-half announces Wales retirement aged 34	https://www.bbc.co.uk/sport/rugby-union/65762861?at_medium=RSS&at_campaign=KARANGA	world	2023-05-31 09:11:40
ビジネス	不景気.com	日本和装が東南アジア子会社を解散、コロナで継続困難 - 不景気com	https://www.fukeiki.com/2023/05/nihon-wasou-liquidate-asia-pacific.html	日本和装	2023-05-31 09:27:56
ビジネス	不景気.com	23年4月の失業率は2.6%に改善、求人倍率は横ばい - 不景気com	https://www.fukeiki.com/2023/05/unemployment-rate-23-04.html	労働力調査	2023-05-31 09:15:45
IT	週刊アスキー	ついにFinal！『モンハンサンブレイク』映像番組が6月7日23時より配信決定	https://weekly.ascii.jp/elem/000/004/139/4139052/	final	2023-05-31 18:35:00
IT	週刊アスキー	LG、165Hz駆動の27型WQHDゲーミングディスプレー「27GR75Q-B」	https://weekly.ascii.jp/elem/000/004/139/4139034/	lgultragear	2023-05-31 18:30:00