投稿時間:2022-01-07 21:30:48 RSSフィード2022-01-07 21:00 分まとめ(35件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
IT	ITmedia 総合記事一覧	[ITmedia PC USER] RazerがPCを組み込んだゲーミングデスクの新コンセプトを公開　触覚フィードバック対応のゲーミングチェアも	https://www.itmedia.co.jp/pcuser/articles/2201/07/news159.html	itmediapcuserrazer	2022-01-07 20:45:00
python	Pythonタグが付けられた新着投稿 - Qiita	機械翻訳（Transformer）	https://qiita.com/MMsk0914/items/99a62ef0306ce3561ed0	printlenvocabjaprintlenvocaben文字列のインデックスの置き換えtransformjalambdaxvocabjatokenizejaxtransformenlambdaxvocabenltBOSgtvocabentokenizeenxvocabenltEOSgt置き換えの準備ができたので、パッディングを含めてインデックスへの置き換えを行います。	2022-01-07 20:35:04
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	数学の確率問題をプログラムで解きたい	https://teratail.com/questions/377098?rss=all	確率	2022-01-07 20:38:53
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	if文：return Trueやreturn Falseの使い方について	https://teratail.com/questions/377097?rss=all	以下のコードで書かれているif文のreturnnbspTrueやreturnnbspFalseの使い方がわかりません。	2022-01-07 20:35:46
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	pythonで複数のURLを取得	https://teratail.com/questions/377096?rss=all	pythonで複数のURLを取得前提・実現したいこと集英社のコミックという場所から本の発売日・タイトル・値段を取得するシステムを作っています。	2022-01-07 20:35:18
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	Rコマンダーが起動しない件について	https://teratail.com/questions/377095?rss=all	Rコマンダーが起動しない件について前提・実現したいことRコマンダーを起動したいです。	2022-01-07 20:19:46
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	【pandas/openpyxl】特定のセルに文字列を記入し、一つ下の行にdataframeを貼り付けたい	https://teratail.com/questions/377094?rss=all	【pandasopenpyxl】特定のセルに文字列を記入し、一つ下の行にdataframeを貼り付けたいエクセルファイルに以下の情報を順番に書き込みたいです。	2022-01-07 20:19:00
Ruby	Rubyタグが付けられた新着投稿 - Qiita	【Ruby】引数をデフォルトで指定するときはキーワード引数を使おう	https://qiita.com/kat0/items/4e5451d99ec18b1362aa		2022-01-07 20:15:11
Ruby	Railsタグが付けられた新着投稿 - Qiita	【Ruby】引数をデフォルトで指定するときはキーワード引数を使おう	https://qiita.com/kat0/items/4e5451d99ec18b1362aa		2022-01-07 20:15:11
技術ブログ	Developers.IO	[Snowflake新機能]テーブルごとのデータロードの履歴をGUIで確認できるIngestion Dashboardが使えるようになりました #SnowflakeDB	https://dev.classmethod.jp/articles/snowflake-ingestion-dashboard/	ingestiondashboard	2022-01-07 11:26:34
技術ブログ	Developers.IO	MediaTailor Channel Assembly を S3 オリジンのパターンで触りながら理解してみた	https://dev.classmethod.jp/articles/mediatailor-channel-assembly-s3-origin/	channelassembly	2022-01-07 11:17:14
技術ブログ	Developers.IO	BigQueryへフィールドが一部欠落しているJSON Linesデータをエラー抑止の上で正常転送させてみた	https://dev.classmethod.jp/articles/bq-json-transfer-option-with-nullable/	bigquery	2022-01-07 11:08:28
海外TECH	MakeUseOf	How CyberPowerPC's New Kinetic Series Case Will Improve PC Performance	https://www.makeuseof.com/cyberpowerpc-new-kinetic-series-case-improve-pc-performance/	How CyberPowerPC x s New Kinetic Series Case Will Improve PC PerformanceA case that automatically adapts to internal and external temperature That s exactly what CyberPowerPC has built and here s how it works	2022-01-07 11:35:11
海外TECH	MakeUseOf	AMD's New Ryzen 6000 and Ryzen 7000 Chips Are Here: Everything You Need to Know	https://www.makeuseof.com/amd-new-ryzen-6000-ryzen-7000-launch/	AMD x s New Ryzen and Ryzen Chips Are Here Everything You Need to KnowAs an answer to Intel s renewed competitiveness AMD showed a glimpse in the future at CES taking the veils off its Ryzen and chips	2022-01-07 11:30:26
海外TECH	MakeUseOf	NVIDIA Launches a Free Version of Omniverse for Creators	https://www.makeuseof.com/nvidia-launches-free-version-of-omniverse/	nvidia	2022-01-07 11:15:15
海外TECH	DEV Community	How to create a Custom VS Code Theme in 3 minutes	https://dev.to/virejdasani/how-to-create-a-custom-vs-code-theme-in-3-minutes-g75	thanks	2022-01-07 11:39:54
海外TECH	DEV Community	Advanced Practices for Nest.js + Next.js Projects	https://dev.to/yakovlev_alexey/advanced-practices-for-nestjs-nextjs-projects-36g9	Advanced Practices for Nest js Next js ProjectsThis is the second and final part in a series of articles about combining nest js and NEXT js In the first part we created a project and discovered a few basic SSR techniques for this stack At this point the project can already be used as a base for developing a real website However there are a few more things we can do enable Hot Module Replacement for nest next discover more reusable SSR techniques and learn of subdirectory deployments This post is a translation of the original articles by me on Habr The translation had no input from experienced tech writers or editors So any feedback towards correcting any mistakes is greatly appreciated Table of Contents Table of Contents Introduction CDN deployment HMR and NEXT js instance caching Hot Reload in nest js Caching NEXT js instance More SSR techniques Creating a configuration AOP for GSSP Accessing application context Client side navigation Subdirectory deployment Development proxy Adding basePath Proxy and basePath Fetch wrapper Proxy without rewrites Conclusion IntroductionI should remind you that the final application is available at my GitHub commit history mostly follows the flow of the article I assume that you are already finished with the first part of series and have the project at the relevant revision commit adf NEXT js and nest js are very similar in naming so I will be always typing NEXT js the React framework in uppercase and nest js the MVC backend framework in lowercase to differenciate between them more easily CDN deploymentLet s start simple NEXT js supports CDN Content Delivery Network deployments out of the box Simply put your path to statics as assetPrefix in your next config js when building for production Then upload next static to your CDN of choice It is important to note that assetPrefix also has to be set in the config when launching production nest js server HMR and NEXT js instance cachingAt the moment the application works really fast in dev mode Reboots should not take more than seconds and pages load up instantly However this might not be always that way large projects tend to have significantly crippled build procedures It is especially noticable for large frontends Every change to nest js server would reboot it and create a new NEXT js instance that would start recompiling your client almost from scratch This greatly degrades developer experience significantly increasing feedback cycles when developing complex solutions Let s fix this issue by implementing Hot Module Replacement in nest js and caching NEXT js instances between reloads Hot Reload in nest jsWe will first follow official documentation on Hot Reload in nest js I will not duplicate most of information from there just the more important parts For example we should use our own start dev script to accept a different tsconfig json package json start dev nest build webpack webpackPath webpack hmr config js path tsconfig server json watch It is important to pass tsconfig server json outside of a relative path ts loader will look up paths relative to the server executable If supply it just with the file name it will start searching in parent folders until it finds a matching file Next we should tackle Hot Reload in main ts src server main tsimport NestFactory from nestjs core import PORT from src shared constants env import AppModule from app module declare const module any async function bootstrap const app await NestFactory create AppModule await app listen PORT if module hot module hot accept module hot dispose gt app close bootstrap This implementation will works for us However make notice of old module disposal app close is called It causes all modules services and controller to cease Let s check if our server even works after adding HMR Boot the server and make changes to app controller ts It is important that the server will not reboot at all if you save the file without making any actual changes If you did indeed make changes to a file it should take seconds to reboot in small projects and no more than seconds in large ones It is a huge difference that significantly improve developer experience If any nest js modules were using dynamic import require they may not work after adding Webpack HMR due to bundling My solution was to boot tsc along with Webpack nest js executable since dynamically imported files were not frequently changed You may also need NODE PATH environment variable to properly resolve dynamic import paths prepend NODE PATH lt path gt to start dev script Caching NEXT js instanceStill we have not solved the bottleneck we had with new NEXT js instance for each reboot This may take up to a few seconds in large projects during initialization and page loads We will cache RenderModule from nest next between module reloads in app module ts For this we need nest js dynamic module initialization src server app module tsimport DynamicModule Module from nestjs common import Next from next import RenderModule from nest next import NODE ENV from src shared constants env import AppController from app controller import AppService from app service declare const module any Module export class AppModule public static initialize DynamicModule during initialization attempt pulling cached RenderModule from persisted data const renderModule module hot data renderModule RenderModule forRootAsync Next dev NODE ENV development viewsDir null if module hot add a handler to cache RenderModule before disposing existing module module hot dispose data any gt data renderModule renderModule return module AppModule imports renderModule controllers AppController providers AppService Update main ts to dynamically initialize AppModule src server main tsimport NestFactory from nestjs core import AppModule from app module const app await NestFactory create AppModule initialize To make sure everything works we may observe terminal outputs during nest js reboot If we succeeded we will not see compiling message produced when creating a new instance of NEXT js server This way we potentially saved hours of developers time More SSR techniquesOur original problem was that we did not want to have separate services for nest js and NEXT js It seems that at this point we removed all things that were blocking us from having a decent developer experience with our solution So how about leveraging our solution to have some advantages Earlier we declined the strategy of returning SSR data from controller handlers We also discovered how we can employ nest js interceptors to pass data to GSSP in a reusable way Why don t we use interceptors to pass some common initial data to our client This data may be user data or tokens translations configurations feature flags and so on Creating a configurationIn order to pass some configuration to our client we first need to create some configuration I will not create a separate module and service for accessing configuration in nest js but that is how you would do it in a proper application A simple file will suffice Our configuration will be populated with feature flags As an example we will use blog link flag toggling between two link display options src server config tsconst CONFIG features blog link true export CONFIG Let s create ConfigInterceptor that would put configuration to returned value and include it in UseInterceptors decorator Obviously in a real application you might pull feature flags from a separate service or website Luckily it s fairly easy to access request information in interceptors req and res HTTP contexts are available in them so you may execute some middlewares prior to executing interceptors src server config interceptor tsimport Injectable NestInterceptor ExecutionContext CallHandler from nestjs common import Observable from rxjs import map from rxjs operators import CONFIG from config Injectable export class ConfigInterceptor implements NestInterceptor intercept context ExecutionContext next CallHandler Observable lt unknown gt return next handle pipe map data gt data config CONFIG src server app controller tsimport ConfigInterceptor from config interceptor Get Render index UseInterceptors ParamsInterceptor ConfigInterceptor public home return Get id Render id UseInterceptors ParamsInterceptor ConfigInterceptor public blogPost return To make sure our interceptor works we may use console log ctx query in GSSP It is important not to include sensitive information in ctx query it is also serialized when generating HTML Therefore it is also not recommended to use ctx query to pass large items that are unused on the client As a workaround use ctx req to access such information during SSR it will be populated with your Express or fastify for that matter req from nest js AOP for GSSPNow we have reusable code to pass information to the client we should also add some reusable code to parse this information and do something with it Let s create buildServerSideProps wrapper for GSSP src client ssr buildServerSideProps tsimport ParsedUrlQuery from querystring import Config from src shared types config import GetServerSideProps GetServerSidePropsContext from src shared types next type StaticProps features Config features type StaticQuery config Config const buildServerSideProps lt P Q extends ParsedUrlQuery ParsedUrlQuery gt getServerSideProps ctx GetServerSidePropsContext lt Q gt gt Promise lt P gt GetServerSideProps lt Partial lt StaticProps gt amp P Partial lt StaticQuery gt amp Q gt gt return async ctx gt const features ctx query config const props await getServerSideProps ctx return props props features export buildServerSideProps If you are paying attention you may notice that buildServerSideProps recieves not a real GSSP but a simplified version that return just the props This stops you from using redirect and other properties in individual GSSPs To avoid that use a real GSSP as the param to buildServerSideProps In order to have helpful typings we should have a type for Config src shared types config tsexport type Config features Record lt string boolean gt src server config tsimport type Config from src shared types config const CONFIG Config features blog link true Also NEXT js GetServerSideProps does not quite suit us we can t really override Query type We will add types of our own src shared types next tsimport GetServerSidePropsResult GetServerSidePropsContext as GetServerSidePropsContextBase from next import ParsedUrlQuery from querystring export type GetServerSidePropsContext lt Q ParsedUrlQuery gt Omit lt GetServerSidePropsContextBase query gt amp query Q export type GetServerSideProps lt P Q ParsedUrlQuery gt ctx GetServerSidePropsContext lt Q gt gt Promise lt GetServerSidePropsResult lt P gt gt Update pages to use this new wrapper src pages index tsxexport const getServerSideProps buildServerSideProps lt THomeProps gt async gt const blogPosts await fetch api blog posts return blogPosts src pages id tsxexport const getServerSideProps buildServerSideProps lt TBlogProps TBlogQuery gt async ctx gt const id ctx query id const post await fetch api blog posts id return post It is once again important not to pass the entire config to your client It might contain sensitive information like tokens internal URLs and credentials or just make your payload larger Accessing application contextWe already can access features property on our pages But this might not be a very comfortable way of doing so We have to utilize prop drilling to pass it to deeply nested components To avoid that use global application context src shared types app data tsimport Config from config export type AppData features Config features src client ssr appData tsimport createContext from react import AppData from src shared types app data const AppDataContext createContext lt AppData gt as AppData export AppDataContext To not repeat application context mounting on every page put this logic in app tsx I will implement it using a class but it is not a requirement src pages app tsximport NextApp AppProps from next app import AppDataContext from src client ssr appData import AppData from src shared types app data class App extends NextApp lt AppProps gt appData AppData constructor props AppProps super props this appData props pageProps appData render const Component pageProps this props return lt AppDataContext Provider value this appData gt lt Component pageProps gt lt AppDataContext Provider gt export default App Update buildServerSideProps slightly src client ssr buildServerSideProps tsimport AppData from src shared types app data type StaticProps appData Partial lt AppData gt return props props appData features And create a hook to use AppDataContext easily src client ssr useAppData tsimport useContext from react import AppDataContext from appData const useAppData gt return useContext AppDataContext export useAppData Finally implement the useFeature hook and utilize it on the index page src client hooks useFeature tsimport useAppData from src client ssr useAppData const useFeature feature string defaultValue false gt return useAppData features feature defaultValue export useFeature src pages index tsxconst Home FC lt THomeProps gt blogPosts gt const linkFeature useFeature blog link return lt div gt lt h gt Home lt h gt blogPosts map title id gt lt div key id gt linkFeature lt gt title lt Link href id gt Link lt Link gt lt gt lt Link href id gt title lt Link gt lt div gt lt div gt Validate the changes in the browser localhost should display links according to the feature flag we set in the server configuration Update the configuration and check if after page refresh displayed link changes Client side navigationAfter makes such significant changes to our SSR pipelines and GSSP we surely have to check if client side navigations still work Our concerns are justified browsers will reload the page when making client side transitions In the terminal we would see an error we can t quite serialize appData features field It expectedly is undefined when making client side navigation Our nest js controller handlers do not get called when making client side transitions remember Only apply interceptors or req properties to pass actual initial data And never expect them to be available in GSSP functions Such data may be translations feature flags CSRF tokens and other configurations To solve our current issue let s sanitize buildServerSideProps return values src client ssr filterUnserializable tsconst filterUnserializable obj Record lt string unknown gt filteredValues unknown undefined Record lt string unknown gt gt return Object keys obj reduce lt Record lt string unknown gt gt ret key gt if typeof obj key object amp amp obj key null return ret key filterUnserializable obj key as Record lt string unknown gt else if filteredValues includes obj key return ret key obj key return ret export filterUnserializable src client ssr buildServerSidePropsimport filterUnserializable from filterUnserializable return props await getServerSideProps ctx appData filterUnserializable features as StaticProps appData This filterUnserializable implementation has some flaws It will show poor perfomance for large and nested objects For completeness and consistency between article versions I will leave the code as is to later return in a separate article on how to diagnose and profile such issues Let s test client side transitions once again should work now Having the ability to easily pass arbitary data to your client is one of the primary advantages nest next offers in my opinion Data may come from any source including middlewares mutating req properties You may leverage existing Express solutions in your nest next project and deliver changes to clients almost immediately Subdirectory deploymentIn some cases you might want your production application to be deployed in a subdirectory For example we are working on documentation and our service should be available at docs Or with our current application a blog section on a website with blog prefix What should we do to support such functionality It seems the only thing blocking us is API requests and client links Statics will be deployed on a CDN so it will not be a problem Seems like a fairly simple task at first But then we remember that NEXT js makes requests to an internal endpoint when making client side transitions Request handlers executes GSSP on the server and return JSON with data We are rather helpless when trying to change this And if we do not use a CDN the entire static will break This will not do for us Luckily in NEXT js docs we find basePath parameter It allows NEXT js to support subdirectory deployments out of the box adding it to every NEXT js server endpoint Great now we have a plan let s start Development proxyBefore we start coding anything we should provide a way to reproduce our production environment with subdirectory deployment For this we will use a simple proxy server Use Docker and nginx to implement and start a proxy Let s add proxy configuration nginx confserver listen location blog proxy pass http localnode proxy set header Host host proxy set header X Forwarded For proxy add x forwarded for proxy set header X Real IP remote addr It is important to understand that nginx will boot in a Docker container with a net of its own Therefore to properly proxy the request to the nest js server we would need an address for the host machine We will use localnode name for it I have not tested start proxy script on Windows machines Unless you are using WSL you may have some issues supplying the container with host machine address This configuration will allow proxy to handle requests to localhost blog and proxy them to localhost In package json add start proxy script to boot a Docker container with our proxy docker run name nest next example proxy v pwd nginx conf etc nginx conf d default conf ro add host localnode ifconfig en grep inet grep v inet awk print p d nginx Adding basePathAdd basePath to your server configuration Update typings and pull data from BASE PATH environment variable src shared types config tsexport type Config features Record lt string boolean gt basePath string src server config tsimport Config from src shared types config const CONFIG Config features blog link true basePath process env BASE PATH export CONFIG Create next config js to configure NEXT js Put basePath there as well next config jsmodule exports basePath process env BASE PATH Proxy and basePathCheck website on localhost blog after booting both server and proxy The request reaches nest js server but NEXT js static requests are unsuccessful NEXT js expects that the request comes with the desired basePath in req url But in our nginx proxy we cut it off Add a separate rule to proxy blog next requests without replacing our basePath server listen location blog next proxy pass http localnode proxy set header Host host proxy set header X Forwarded For proxy add x forwarded for proxy set header X Real IP remote addr location blog proxy pass http localnode proxy set header Host host proxy set header X Forwarded For proxy add x forwarded for proxy set header X Real IP remote addr Reboot Docker container and check the website in your browser Unfortunately we are out of luck again There was and still is to some extent a problem with nest next This package applies a filter that forwards unhandled s to NEXT js But only if the request starts with next Therefore NEXT js server expects a request that starts with basePath and nest next proxies only requests starting with next I submitted a PR to fix this issue and it was merged However package maintainer Kyle has not published a new version with this fix since then You may ask him to publish or use a compiled version from my GitHub yarn upgrade nest next Tag base path dist only includes the required files After bumping npm package check localhost blog in your browsers You should finally see a familiar Home page Client side navigations also work Fetch wrapperThe only thing left is to add basePath to fetch requests It seems that there is not need for that at the moment However that is only due to the fact that we call fetch only on the server and never from the client As soon as you start fetching from the client you start seeing errors Let s refactor buildServerSideProps a little Update typings for AppData and extract appData parsing from ctx query to a separate method src shared types app data tsimport Config from config export type AppData Pick lt Config basePath features gt src client ssr extractAppData tsimport GetServerSidePropsContext from src shared types next import AppData from src shared types app data import filterUnserializable from filterUnserializable import StaticQuery from buildServerSideProps const extractAppData ctx GetServerSidePropsContext lt Partial lt StaticQuery gt gt gt const features basePath ctx query config return filterUnserializable features basePath as Partial lt AppData gt export extractAppData Use new util in buildServerSideProps src client ssr buildServerSideProps tsimport extractAppData from extractAppData const buildServerSideProps lt P Q extends ParsedUrlQuery ParsedUrlQuery gt getServerSideProps ctx GetServerSidePropsContext lt Q gt gt Promise lt P gt GetServerSideProps lt Partial lt StaticProps gt amp P Partial lt StaticQuery gt amp Q gt gt return async ctx gt const props await getServerSideProps ctx return props props appData extractAppData ctx export buildServerSideProps Finally we may access basePath on the client The only thing left is to add this property to the actual fetch wrapper I will not create an ingenious solution and turn envAwareFetch into a function with side effects src shared utils fetch tsimport isServer PORT from constants env type FetchContext basePath string const context FetchContext basePath const initializeFetch basePath string gt context basePath basePath const getFetchUrl url string gt if isServer насерверененужнодобавлятьbasePath запросделаетсянечерезproxy return url startsWith http localhost PORT url url return url startsWith context basePath url url const envAwareFetch url string options Partial lt RequestInit gt gt const fetchUrl getFetchUrl url return fetch fetchUrl options then res gt res json export envAwareFetch as fetch initializeFetch Finally initialize fetch using initializeFetch It might seem that we should do that in GSSP however it is once again only run on the server Therefore use app tsx as the place to initialize fetch src pages app tsxconstructor props AppProps super props this appData props pageProps appData initializeFetch this appData basePath To check that everything works properly you add a fetch request in useEffect on one of the pages This way we can deploy nest next application in subdirectories without loosing any of the features or advantages we had Proxy without rewritesThere is also an option to use a proxy without rewrites Then all requests have to be handled with basePath on the server as well Proxy configuration would look like this server listen location blog proxy pass http localnode proxy set header Host host proxy set header X Forwarded For proxy add x forwarded for proxy set header X Real IP remote addr To prepend basePath to every nest js server endpoint you may employ something like nest router and use basePath as path parameter It is also important to initialize fetch before making any requests in GSSP And you would have to pull basePath from an environment variable or directly from config when running GSSP on client side transition Conclusionnest next allows you to have very reusable SSR pipelines with all the features of NEXT js and existing infrastructure you might have with nest js and Express Hopefully this series of articles helped you to better understand how you might leverage this technology to help you develop large applications Skills you might get from completing this tutorial can also be reused for configuring nest js with other purposes	2022-01-07 11:22:38
海外TECH	DEV Community	Learning Python Like a Pro in 2022: Getting Started	https://dev.to/emma_donery/learning-python-like-a-pro-in-2022-getting-started-28d	Learning Python Like a Pro in Getting StartedPython has become one of the most famous programming language in the world In this article you will get a hands on introduction in python programming language Whether you re new to programming or an experienced developer this article can help you get started with Python easily So lets jump right in What is pythonPython is a simple general purpose high level and object oriented programming language founded by Guido Van Rossum Python is also an interpreted programming language this means that as a developer you write Python py files in a text editor and then put those files into the python interpreter to be executed Features of pythonEasy to use and LearnExpressive LanguageInterpreted LanguageObject Oriented LanguageOpen Source LanguageExtensibleLearn Standard LibraryGUI Programming SupportIntegratedEmbeddableDynamic Memory AllocationWide Range of Libraries and Frameworks InstallationMany PCs and Macs will have python already installed To check whether python is installed on your system enter the following command on your terminalpython versionIf not installed Then you can download it for free from the following website Python versions Python vs Python The two versions Python and Python are very much different from each other I will not dive deep into the differences between the two However for the sake of this article we will be using python which is the most recent version Applications of PythonData ScienceDate MiningDesktop ApplicationsConsole based ApplicationsMobile ApplicationsSoftware DevelopmentArtificial IntelligenceWeb ApplicationsEnterprise ApplicationsD CAD ApplicationsMachine LearningComputer Vision or Image Processing Applications Speech RecognitionsNB There are many IDEs to run our python project However in these series of articles i will be using visual stusio code to write and run our projects There are great tools out there to run python programs you can test them out You can use any other editor or IDE that you prefer To install Visual studio code visit their website and follow the guidelines ConclusionThis article was basically giving a brief intro on what is python its features and application I am making a series on Learning Python Like a Pro in and on my next article i will be tackling on the basics of Python In the mean time feel free to connect with me on twitter and linkedinSee you om the next article Happy reading	2022-01-07 11:13:34
Apple	AppleInsider - Frontpage News	Tim Cook's net worth is now over $1 billion after 2021	https://appleinsider.com/articles/22/01/07/tim-cooks-net-worth-is-now-over-1-billion-after-2021?utm_medium=rss	Tim Cook x s net worth is now over billion after Apple s financial reports show that including a rare stock award CEO Tim Cook was paid in pushing his net worth over the billion mark Tim CookAs Apple s full SEC filing points out was Tim Cook s tenth year as CEO That meant he qualified for a delayed part of his incentive plan arranged when he took over from Steve Jobs in Read more	2022-01-07 11:44:31
Apple	AppleInsider - Frontpage News	Apple increases orders for AirPod chips ahead of 'AirPods Pro 2' launch	https://appleinsider.com/articles/22/01/07/apple-increases-orders-for-airpod-chips-ahead-of-airpods-pro-2-launch?utm_medium=rss	Apple increases orders for AirPod chips ahead of x AirPods Pro x launchFollowing the popularity of AirPods in the holiday season Apple has reportedly ordered more components in preparation for the launch of AirPods Pro later in Apple is still not expected to launch its more powerful AirPods Pro until the end of However a new supply chain report claims that Apple is already increasing its component orders According to Digitimes Apple has stepped up its chip orders after the current AirPods models saw strong sales leading up to the end of Unspecified sources within the industry also say that the increase is part of Apple s gearing up for the launch of the AirPods Pro Read more	2022-01-07 11:41:14
海外TECH	Engadget	Flexbooker online appointment service breach exposes data of 3.7 million users	https://www.engadget.com/flexbooker-online-appointment-service-breach-115040440.html?src=rss	Flexbooker online appointment service breach exposes data of million usersA group of hackers is trading a database of stolen information from FlexBooker a cloud based tool for scheduling appointments containing sensitive customer data According to BleepingComputer the company suffered a security breach before the holidays and notified its customers about the attack in an email where it revealed that its Amazon AWS servers were compromised on December rd It also admitted that its system data storage was accessed and downloaded Based on information from Have I Been Pwned the breach compromised million accounts containing email addresses names passwords phone numbers and partial credit card numbers BleepingComputer says a group called Uawrongteam took credit for the attack and shared links to archives with the stolen data which the group claimed also include users drivers licenses other IDs password salt and hashed passwords FlexBooker s typical customers are people who need to be able to quickly schedule appointments with clients such as doctors lawyers dentists gyms mechanics salons trainers therapists so and and so forth nbsp In Flexbooker s email to users it said the infiltrators failed to get quot any credit card or other payment card information quot We re guessing the company didn t take the stolen partial credit card numbers into account Before Flexbooker Uawrongteam previously claimed other data breaches and also traded databases with stolen information from its previous targets They include data from Racing com a digital TV network that broadcasts horse racing and from rediCASE Case Management Software solution for health services and other businesses nbsp nbsp New breach Online booking service FlexBooker had M accounts breached last month Data included email addresses names phone numbers and for some accounts partial credit card data were already in haveibeenpwnedーHave I Been Pwned haveibeenpwned January	2022-01-07 11:50:40
海外TECH	Engadget	Tinder's upcoming 'Swipe Party' feature lets friends help you choose dates	https://www.engadget.com/tinder-working-on-swipe-party-feature-that-lets-friends-help-you-vet-prospects-111130079.html?src=rss	Tinder x s upcoming x Swipe Party x feature lets friends help you choose datesTinder is working on a new feature called Swipe Party that will let you invite friends online to help you vet dates TechCrunch has reported The feature was first spotted in the app s code by the Dutch site Gratisdatingtips and has yet to be announced but Tinder confirmed that it s in in the works The feature would be not unlike Apple s SharePlay which lets you do watch parties with friends via FaceTime on supported apps like Disney and Hulu With Tinder you could similarly invite friends to your swiping sessions so they could help you pick a match A lot of folks already do that in person so the new feature bring that online ーhandy in the time of COVID nbsp Code snippets show that Swipe Party would let you invite friends to join a session by providing their phone number confirming it with a code then entering their name and date of birth If you want their help however you d need to give them access to your phone s camera and microphone Tinder recently let users add videos to their dating profiles and parent Match recently promised to introduce other audio and chat features to its dating apps While Tinder confirmed to TechCrunch that the feature was in development it didn t provide any additional details nbsp	2022-01-07 11:11:30
金融	RSS FILE - 日本証券業協会	協会員の異動状況等	https://www.jsda.or.jp/kyoukaiin/kyoukaiin/kanyuu/index.html	異動	2022-01-07 13:00:00
ニュース	BBC News - Home	Kazakhstan unrest: Troops ordered to fire without warning	https://www.bbc.co.uk/news/world-asia-59907235?at_medium=RSS&at_campaign=KARANGA	kazakhstan	2022-01-07 11:44:13
ニュース	BBC News - Home	Novak Djokovic visa: Australia says tennis star not being held captive	https://www.bbc.co.uk/news/world-australia-59903785?at_medium=RSS&at_campaign=KARANGA	controversy	2022-01-07 11:28:40
ニュース	BBC News - Home	Edward Colston statue case could be sent to appeal court	https://www.bbc.co.uk/news/uk-england-bristol-59909823?at_medium=RSS&at_campaign=KARANGA	braverman	2022-01-07 11:46:45
ニュース	BBC News - Home	Covid: Mask refusals in some of England's secondary schools spark parents' concern	https://www.bbc.co.uk/news/education-59898968?at_medium=RSS&at_campaign=KARANGA	children	2022-01-07 11:24:58
ニュース	BBC News - Home	Yiewsley death: Boy, 13, arrested over west London street stabbing	https://www.bbc.co.uk/news/uk-england-london-59906096?at_medium=RSS&at_campaign=KARANGA	early	2022-01-07 11:36:53
ニュース	BBC News - Home	Trippier's £12m move to Newcastle 'not for financial benefits', says Howe	https://www.bbc.co.uk/sport/football/59878158?at_medium=RSS&at_campaign=KARANGA	Trippier x s £m move to Newcastle x not for financial benefits x says HoweKieran Trippier has made his £m move to Newcastle United from Atletico Madrid for the challenge and not the financial benefits Eddie Howe says	2022-01-07 11:53:12
ニュース	BBC News - Home	Philippe Coutinho signs for Aston Villa on loan from Barcelona	https://www.bbc.co.uk/sport/football/59906213?at_medium=RSS&at_campaign=KARANGA	barcelona	2022-01-07 11:54:22
ニュース	BBC News - Home	Omicron: How do I get a lateral flow or PCR Covid test?	https://www.bbc.co.uk/news/health-51943612?at_medium=RSS&at_campaign=KARANGA	across	2022-01-07 11:39:59
LifeHuck	ライフハッカー［日本版］	レンジや食洗器使用OK！ 磁器製フラスク「Nest Cup」誕生	https://www.lifehacker.jp/2022/01/248292-machi-ya-nest-start.html	nestcup	2022-01-07 21:00:00
北海道	北海道新聞	ポケモン行司装束を披露、初場所　オリジナルの化粧まわしも	https://www.hokkaido-np.co.jp/article/631102/	両国国技館	2022-01-07 20:14:00
北海道	北海道新聞	Ｗ杯予選相手の入国許可へ　サッカー、公益性など考慮	https://www.hokkaido-np.co.jp/article/631099/	入国許可	2022-01-07 20:02:00
ビジネス	東洋経済オンライン	頑固汚れにトイレットペーパー！｢トイレ｣掃除術 1日1か所ゆるっと大掃除､プロが教えるコツ | Domani | 東洋経済オンライン	https://toyokeizai.net/articles/-/500701?utm_source=rss&utm_medium=http&utm_campaign=link_back	domani	2022-01-07 20:30:00