投稿時間:2023-01-06 03:35:21 RSSフィード2023-01-06 03:00 分まとめ(33件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
AWS	AWS Mobile Blog	re:Invent 2022 Wrapped: a Playlist for Web and Mobile App Developers	https://aws.amazon.com/blogs/mobile/reinvent-2022-wrapped-a-playlist-for-web-and-mobile-app-developers/	re Invent Wrapped a Playlist for Web and Mobile App DevelopersWith in the rear view re Invent attendees have since unpacked their swag and organized a few gigabytes of photos from presentations booth visits and evening events Those who attended virtually have long lists of notes bookmarks and questions for the AWS Amplify Discord Finally developers that weren t able to attend are likely asking “What …	2023-01-05 17:38:53
python	Pythonタグが付けられた新着投稿 - Qiita	[Python] TikTokAPI エラー KeyError: "name='ttwid', domain=None, path=None"	https://qiita.com/Qiitaman/items/a27202121679ef7840f0	fileddesarrollotiktoktik	2023-01-06 02:23:35
海外TECH	Ars Technica	Mercedes-Benz will build a $1 billion EV fast-charging network in the US	https://arstechnica.com/?p=1907866	chargepoint	2023-01-05 17:45:20
海外TECH	Ars Technica	Cadillac wants to enter Formula 1 with Andretti Global	https://arstechnica.com/?p=1907933	andretti	2023-01-05 17:37:52
海外TECH	MakeUseOf	RAM vs. HDD: What's the Difference?	https://www.makeuseof.com/ram-vs-hdd-differences/	different	2023-01-05 17:45:16
海外TECH	MakeUseOf	What Are WebRTC Leaks and How Can You Prevent Them?	https://www.makeuseof.com/what-are-webrtc-leaks-prevent-them/	webrtc	2023-01-05 17:30:16
海外TECH	MakeUseOf	Make Sure You Don’t Miss ESR at CES 2023	https://www.makeuseof.com/esr-gear-ces/	sure	2023-01-05 17:30:16
海外TECH	DEV Community	Fluid Pull Requests	https://dev.to/reviewpad/fluid-pull-requests-36a4	Fluid Pull RequestsBy Freddy MalletPull Requests have become the backbone of the DevOps movement the faster the safer the better But the code review step this systematic and synchronized communication task between humans inherited from ancient times slows down the overall development lifecycle for an illusion of safety It s time to introduce the Fluid Pull Requests paradigm Back in GitHub introduced the concept of Pull Request and by doing so significantly eased the contribution to open source projects For the first time it had never been so simple for two strangers to collaborate on the same code base At that time the only purpose of a Pull Request was to provide a safe way to suggest code changes and discuss them in a collaborative interface More than a decade later Million Pull Requests are created each year on private projects and Million on public projects So the concept has been embraced by the overall software industry and has become a de facto standard During the same period the DevOps movement took off and nowadays Pull Requests are the backbone of any automated SDLC Software Delivery LifeCycle On each Pull Request many highly valuable tasks are fully automated building testing static analysis to spot bugs deployment on staging environments etc All this DevOps movement could be summarized in one mantra “The faster the safer the better Starting in the DORA DevOps Research and Assessment team has identified four key metrics that indicate the performance of a software development team Three of those four metrics illustrate this mantra Deployment Frequency Lead Time for Changes and Time to Restore Service So today the lifecycle of a Pull Request should be a matter of a few hours but it is always a few days or even a few weeks Developers managed to automate many things but we still have in the middle of each PR lifecycle a systematic and synchronized communication task between humans the code review step This inflexible code review step inherited from slows down everything and is the main bottleneck Why do we keep on accepting to pay such a price Why do we keep on pushing the stop the line button on each PR Because no software no static analyzer nor AI will ever be able to formally prove that a code change is safe and maintainable Our tooling will keep evolving to spot more patterns but proving the absence of problems is an unsolvable challenge So we rely on humans to do so But humans are even less efficient at spotting problems tracking a flow of execution or keeping more than variables in our working memory This is especially true when each PR has to be reviewed Developers are progressively desensitized and LGTM symptoms arise We re just accepting to pay the price for an illusion of safety So what do we suggest doing As we said Pull Requests are nowadays the backbone of the DevOps infrastructure so we can t work without them Moreover today there is no code analyzer to prove the absence of bugs or vulnerabilities or critical design flaws so we still need developers to review some code changes The only problem is that this code review is done systematically regardless of the context and always involves synchronous communication between humans Here is where the Fluid Pull Requests paradigm knocks on the door At the core of this Fluid Pull Requests paradigm is the capacity to adjust the code review process based on the sensitivity of the code change either to lighten or strengthen it This sensitivity evaluation must take into account several different elements We can mention for instance the seniority of the developer on a code base the complexity of the code change or the history of changes Based on this sensitivity evaluation you can specify and automate several code review processes to automatically approve and merge do an asynchronous review assign several reviewers and spot the most sensitive parts of the code changes For instance if a database migration script is added it could be relevant to involve the database team but only to approve this piece of code I guess you got it Fluid Pull Requests is an extension of the Pull Request concept to increase both the throughput and safety of delivery We still rely on human review but only when it s the most relevant and in a very driven way Instead of reviewing everything every time we only have the most critical changes reviewed by the most impactful reviewers References Octoverse Report DevOps Research and Assessment	2023-01-05 17:32:00
海外TECH	DEV Community	MERN Interview Questions asked to me in Various Interviews.	https://dev.to/viveksinra/mern-interview-questions-asked-to-me-in-various-interviews-2c8j	MERN Interview Questions asked to me in Various Interviews JavaScript for the answer of these javascript Questions Click here Can you provide an overview of your experience with JavaScript Is JavaScript a statically or dynamically typed language Can you explain the difference between the slice and splice methods in JavaScript Why do we use both the POST and GET methods in HTTP and is it possible to perform all actions using only POST Can you provide an overview of how promises work in JavaScript Can you highlight some of the new features introduced in JavaScript ES Can you provide an example of class inheritance in JavaScript Can you describe the event loop in Node js and how it works Is Node js a single threaded or multi threaded language Can you compare and contrast the map and forEach methods in JavaScript What is the difference between JSON and BSON Can you define what a callback function is in JavaScript Can you explain the concept of callback hell in JavaScript Can you compare and contrast Angular and React Can you explain the concept of the Document Object Model DOM Can you differentiate between the virtual DOM and the real DOM in React Can you describe the differences between the find and filter methods in JavaScript How can we find the index of an element in an array in JavaScript Can you describe different techniques for removing elements from an array in JavaScript and how can we count the number of keys or properties in an object How can we delete a property from an object in JavaScript and how can we generate a random number Can you explain the difference between the spread operator and rest operator in JavaScript React for the answer of these React Questions Click here Can you provide an overview of your experience with React Can you explain the purpose of the ref attribute in the lifecycle of a functional component in React Can you explain the purpose and use of the Context API in React How does Redux differ from the useState hook in React and when should we use one over the other Can you describe the different types of components in React Can you explain the concept of a virtual DOM in React and its benefits Is the shadow DOM the same as the virtual DOM Can you list some common lifecycle methods in React Can you explain the concept of a pure component in React Can you describe the constructor in a React component and its purpose Can you explain the concept of data dependency injection in React Can you differentiate between function based and class based components in React Can you explain the differences between the useMemo and useRef hooks in React Can you list five popular libraries for React What is the useState method in React NodeJS for the answer of these NodeJS Questions Click here Can you provide an overview of your experience with Node js Can you explain the concept of middleware in Node js Can you describe the concept of a pipeline in Node js Can you explain the purpose of the Buffer class in Node js Can you explain the purpose of the module exports object in Node js How can we access the resolved value of a promise in Node js if one of the functions within the promise chain throws an error MongoDB for the answer of these MongoDB Questions Click here Can you provide an overview of your experience with MongoDB Can you explain the concept of indexing in MongoDB and how it can improve query performance Can you describe the purpose of aggregation in MongoDB and why it was introduced How can we merge two collections in MongoDB What is CORS and how does it relate to MongoDB	2023-01-05 17:31:28
海外TECH	DEV Community	GraphQL vs. REST	https://dev.to/appwrite/graphql-vs-rest-50j	GraphQL vs RESTGraphQL and REST are two different approaches to implementing web APIs that allow clients to access data from a server While both approaches have their own advantages and disadvantages they are often used to solve similar problems and can sometimes be used interchangeably Today we ll cover some of the differences between the two RequestsOne of the key differences between GraphQL and REST is the way that data is accessed In REST data is typically organized into a set of resources each with its own unique URL For example if an API exposes information about users and their addresses there might be separate URLs for accessing user data and address data such as Get user profile by ID id Get user address by ID id To retrieve data a client would make a request to one of these URLs using an HTTP method such as GET POST PUT or DELETE In contrast GraphQL uses a single endpoint for all data requests To retrieve data a client sends a GraphQL query to this endpoint specifying the data they want to retrieve The server then responds with the requested data in a JSON object Here is an example of a GraphQL query that could be used to retrieve information about a user with a given ID query usersGet id abc name email addresses city country In this example the query keyword indicates that we are making a query to the server meaning no data will be modified and the user and address fields specify the data we want to retrieve The id argument allows us to specify which user we want to retrieve data for The server will respond with a JSON object containing only the requested data like this data user name John Doe email johndoe example com addresses city New York country USA city Houston country USA By comparison here are examples of REST requests that could be used to retrieve the same information GET The server would first respond with a JSON object containing the user data like this name John Doe email johndoe example com To then retrieve the user s addresses the client would need to make another request to a different URL like this GET The server would then respond with a JSON object containing the address data like this city New York country USA city Houston country USA As you can see the GraphQL approach allows the client to specify the exact data they want to retrieve while the REST approach requires the client to make multiple requests to different URLs to retrieve the same data This can be more efficient for the client as it allows them to retrieve everything in a single round trip to the server StructureAnother key difference between GraphQL and REST is how data is structured on the server In REST the structure of the data is determined by the URL hierarchy and the HTTP methods used to access it For example in the REST example above the user and address data are accessed through different URLs and the POST method is used to create new addresses In GraphQL the structure of the data is determined by the schema defined on the server The schema defines the types of data that can be accessed as well as the fields and relationships between those types For example the types for the user and address data might be defined in the schema like this type User id ID name String email String addresses Address type Address id ID city String country String These types define the structure of the user and address data respectively The symbols denote a list of the enclosed type and the symbol indicates a non nullable field In addition to the User and Address types there must always be a Query type and optionally a Mutation type These two special types define all queries a client can execute for example type Query userGet id String User addressGet userId String Address type Mutation userCreate name String email String User addressCreate userId String city String country String Address With this schema in place the client can use GraphQL to access and modify the user and address data in a consistent and predictable way For example they could use the following mutation to create a new address mutation addressCreate userId abc city Cleveland country USA id city country In this example the mutation keyword indicates that we are modifying data on the server and the addressCreate field specifies the data we want to create The arguments allow us to specify the values for the new address and the id city and country fields specify the data we want to retrieve for the new address The server would respond with a JSON object containing the newly created address data like this data addressCreate id def city Cleveland country USA If the client did not need the address id or any other field it could be excluded from the field selection and it would not be included in the response In a REST API the client would need to make a POST request to a specific URL to create a new address like this POST userId abc city Cleveland country “USA EfficiencyIn some cases it would be useful to create multiple resources at the same time GraphQL allows this in a single request with query batching Given the schema above you could create multiple addresses for the same user in the same request with the following mutation mutation address addressCreate userId abc city Cleveland country USA city address addressCreate userId abc city Seattle country USA city Because we are requesting the result of two addressCreate fields we need a way to distinguish them in the response data This mutation uses a concept called aliasing to give different names to two field executions of the same name Given this query the server would respond with data address city Cleveland address city Seattle To achieve the same result with REST two consecutive requests would be made to the POST address endpoint ErrorsIn GraphQL error handling is done using the errors key in the response object Every response will use a status code of OK and the server will include any errors that occurred during the query in the errors array The data object entry for the field that encountered an error will have a null value and the error object will include the key in the path array This allows the client to identify any issues that may have occurred and handle them appropriately For example if creating an address failed because a user did not exist the response might look like this data addressCreate null errors message User does not exist path addressCreate For a REST API error handling is typically done using HTTP status codes When an error occurs the server will include the corresponding status code in the response The client can use this to determine what type of error has occurred and handle it accordingly regardless of whether the response includes a more descriptive message of the error Overall the main difference between the two approaches is that GraphQL provides more textual information about the errors that have occurred while REST relies on standardized HTTP status codes CachingWeb caching is a technique used to improve the performance and scalability of web applications by storing frequently accessed data in a cache This can help reduce the number of requests made to the server and improve the overall response time of the application With GraphQL web caching is typically handled using a technique called query caching This involves storing the results of frequently accessed queries in the cache and returning the cached results when the same query is made again This can greatly improve the performance of a GraphQL API as it reduces the number of times the server has to execute the same query Implementing a query cache requires a custom implementation which may not be trivial to develop In a REST API web caching is typically handled using HTTP caching headers These headers can be included in the response from the server to indicate whether and for how long the response can be cached by the client The client can then use this information to store the response in a cache and return the cached data when the same request is made again reducing the number of requests made to the server and improving the overall response time Which Do I Choose GraphQL is designed to enable clients to access and manipulate data in a more flexible and powerful way than is possible with REST In particular GraphQL allows clients to specify exactly which data they need and the server will return only that data in a single request This can make it easier for clients to access and manipulate data and can improve the performance and scalability of the API On the other hand REST is a more established and widely used approach to building APIs and it has a large ecosystem of tools and libraries that support it This means that it is often easier to get started with REST and it can be more straightforward to integrate with existing systems and infrastructure Both GraphQL and REST have their own unique strengths and weaknesses and the best choice for a particular project will depend on the specific requirements and use cases It is important to carefully evaluate both options and choose the one that is best suited to the needs of the project Learn moreYou can use the following resources to learn more and get help Appwrite GithubAppwrite DocsDiscord Community	2023-01-05 17:22:17
海外TECH	DEV Community	Appwrite vs. Hasura vs. Apollo	https://dev.to/appwrite/appwrite-vs-hasura-vs-apollo-5cb4	Appwrite vs Hasura vs ApolloThe recent release of Appwrite featuring GraphQL support may have piqued the interest of developers curious about how it compares to other solutions In this concise overview we will delve into the features and capabilities of Appwrite and compare it to several other popular GraphQL solutions By evaluating the pros and cons of each tool an objective comparison will be provided giving you a full understanding of the relative strengths and weaknesses of each option and helping you decide which GraphQL solution is the best fit for your project AppwriteAppwrite is an end to end backend server for Web Mobile Native or Backend apps packaged as a set of Docker microservices Appwrite abstracts the complexity and repetitiveness required to build a modern backend API from scratch and allows you to build secure apps faster Appwrite s GraphQL solution offers full coverage of all existing services allowing you to manage authentication databases functions storage and more using GraphQL queries and mutations HasuraHasura is a web service that provides a GraphQL API and optionally a REST API for accessing data from one or more sources It allows you to merge other REST or GraphQL APIs into a single data access hub by federating composing or stitching them together The service also includes a configurable authorization layer that enables you to set permissions for accessing both data sources and REST GraphQL API endpoints or resolvers at the schema table column or row level Apollo ServerApollo Server is a popular open source server side runtime for executing GraphQL queries It is designed to be flexible and easy to use and can be integrated into a variety of environments and architectures Built on top of the Express web framework Apollo Server supports a wide range of features and capabilities It allows developers to define a GraphQL schema and implement resolvers that specify how data is fetched and modified and it supports subscriptions caching and other advanced features Use CasesIt is impossible to draw a direct comparison between these three products as they are all fulfilling purposes at different levels Appwrite requires no configuration it just works out of the box with all the existing APIsHasura requires configuration of data sources but allows you to work with existing data and merge from multiple sources if requiredApollo only gives you a server side runtime but allows you to develop a fully custom solutionWhen deciding which solution is best for a specific project it is important to consider the needs and requirements of the project as well as the skills and resources available to the development team Appwrite and Hasura may be more suitable for projects that require a pre configured backend with a range of APIs and services while Apollo Server may be better suited to projects that require a fully custom solution or have more specialized or specific requirements Learn moreYou can use the following resources to learn more and get help Appwrite GithubAppwrite DocsDiscord Community	2023-01-05 17:22:14
海外TECH	DEV Community	Must know — Container Security Constructs: Namespace, SecComp, Control Groups, SELinux	https://dev.to/shweta_vohra/must-know-container-security-constructs-namespace-seccomp-control-groups-selinux-53ac	Must know ーContainer Security Constructs Namespace SecComp Control Groups SELinux SELinuxSELinux Security Enhanced Linux is a mandatory access control system for processes Linux kernel uses SELinux to protect processes from each other and to protect the host system from its running processes Processes run as a confined SELinux type that has limited access to host system resources Condition that brings SELINUX into action Check or configure file etc selinux config for possible SELINUX values SELINUX disabled orSELINUX enforcing orSELINUX permissive SeccompSeccomp stands for secure computing mode The seccomp system call operates on the Secure Computing seccomp state of the calling process Man page definitionSeccomp limits how processes could use system calls Seccomp defines a security profile for processes whitelisting the system calls parameters and file descriptors they are allowed to use SecComp defines which system calls should and should not be allowed to be executed by a container It restricts the calls a process continer able to make from userspace into the kernel NamespacesThe kernel can isolate specific system resources usually visible to all processes This is done by placing the resources within a namespace Inside a namespace only processes that are members of that namespace can see or utilize those resources Namespces help apply security restrictions to containers Below mentioned are major namespaces that help achieve boundaries and restrictions Cgroup ーCgroup root directoryIPC ーInter Process Communication POSIX message queuesNetwork ーNetwork devices stacks ports etc Mount ーMount pointsPID ーProcess IDsUser ーUser and group IDsUTS ーHostname and NIS domain name Control groups cgroups Control groups partition sets of processes and their children into groups to manage and limit the resources they consume Control groups place restrictions on the amount of system resources that processes can use Those restrictions keep one process container from using too many resources on the host CGroups Examples ーcpu sharesーcpuset cpusーmemory reservationーkernel memoryーblkio weight block IO ーdevice read iopsーdevice write iopsFor more information on this topic listen recorded session here Thankfully AWS EKS and other AWS container services are security hardened and therefore cannot be mis used by essential container constructs	2023-01-05 17:12:49
Apple	AppleInsider - Frontpage News	Peloton fined $19M over terrible handling of dangerous treadmills	https://appleinsider.com/articles/23/01/05/peloton-fined-19m-over-terrible-handling-of-dangerous-treadmills?utm_medium=rss	Peloton fined M over terrible handling of dangerous treadmillsTroubled exercise firm Peloton has agreed to pay a million civil penalty for how it illegally failed to immediately report its treadmill defects to the US Consumer Product Safety Commission CPSC Before the company benefited from coronavirus lockdowns and then later saw sales drop precipitously again Peloton treadmills featured a hazard that could cause serious injury In the CPSC issued an urgent warning saying the treadmill posed serious risks to children for abrasions fractures and death The authority advised owners to stop using the machine immediately if there were children or small pets in the home Read more	2023-01-05 17:38:16
Apple	AppleInsider - Frontpage News	Amazon will add Matter over Thread support to Echo and eero	https://appleinsider.com/articles/23/01/05/amazon-will-add-matter-over-thread-support-to-echo-and-eero?utm_medium=rss	Amazon will add Matter over Thread support to Echo and eeroAmazon is bringing support for networking standard Matter to various Echo and eero products in via the Thread protocol Amazon EchoThe company announced a gradual rollout of Matter support in saying it wanted to move slowly to ensure a smooth experience free of bugs or other issues At CES Amazon said that support for Matter will be added to Echo and Eero devices this year Read more	2023-01-05 17:01:37
Apple	AppleInsider - Frontpage News	Victrola Stream Onyx plays vinyl through Sonos smart speakers	https://appleinsider.com/articles/23/01/05/victrola-stream-onyx-plays-vinyl-through-sonos-smart-speakers?utm_medium=rss	Victrola Stream Onyx plays vinyl through Sonos smart speakersAt the CES Victrola expanded its turntable catalog with the Stream Onyx able to pipe audio from records through Sonos speakers Victrola Stream OnyxA continuation from the existing Stream turntable lineup the second iteration Stream Onyx is an upgrade from the Victrola Stream Carbon in build materials Made from aluminum plastic and MDF the turntable has premium metal turntable components inside a low resonance plinth Read more	2023-01-05 17:03:19
海外TECH	Engadget	Mercedes and Chargepoint team up to build 400 North American charging hubs	https://www.engadget.com/mercedes-and-chargepoint-team-up-to-build-400-north-american-hubs-171559321.html?src=rss	Mercedes and Chargepoint team up to build North American charging hubsIn July GM announced that it was partnering with EVGo to establish a quot coast to coast quot charging network for its electric vehicles On Thursday Mercedes Benz announced that it will be building a network of its own ーat least in partnership with Chargepoint ーthat will be accessible no matter what make or model of EV you drive nbsp Mercedes and Chargepoint plan to establish new charging hubs throughout the US and Canada ーthat s new DC fast chargers in all ー quot in key cities and urban population centers along major highway corridors and close to convenient retail and service destinations quot according to Thursday s announcement The automaker and MN Energy will finance the scheme while Chargepoint will supply the hardware and infrastructure Chargepoint in partnered with NATSO for a billion dollar project to install its chargers along rural highways Those effort continue nbsp The hubs and DC fast chargers will all be accessible by EV drivers of all stripes regardless of their vehicle type ーthe inverse of Tesla s proprietary network But since Mercedes is pulling the purse strings its customers can look forward to a few extra perks when they pull into a hub That includes being able to reserve a space ahead of time and automatic vehicle station handshake authentication nbsp Each charger can deliver up to V of power allowing V architecture vehicles like the Rivian RT to take full advantage of the increased power transmission while V vehicles like the Audi A e tron the Porsche Taycan Hyundai s Ioniq and Kia s EV will see improved charge times though not the upper limit of what their electrical systems can handle The company notes that these chargers are quot designed to easily scale to meet future demand as EV adoption and vehicle capability grows quot	2023-01-05 17:45:59
海外TECH	Engadget	New York State sues former Celsius CEO over alleged cryptocurrency fraud	https://www.engadget.com/new-york-celsius-ceo-crypto-fraud-lawsuit-171421110.html?src=rss	New York State sues former Celsius CEO over alleged cryptocurrency fraudCrypto lender Celsius Network is still facing the consequences of its tumultuous long after it declared bankruptcy New York State Attorney General Letitia James has sued former Celsius CEO Alex Mashinsky for allegedly defrauding investors out of quot billions of dollars quot in cryptocurrency The executive purportedly misled customers about Celsius worsening financial health and didn t register either as a salesperson or as a commodities and securities dealer The Attorney General s office claims Mashinsky falsely boasted of low risk investments and reliable lending partners while quot routinely quot exposing investors to high risk approaches that resulted in losses the company chief hid from customers He also made untrue statements about safety strategies and user numbers according to the lawsuit Celsius ex chief supposedly deceived hundreds of thousands of investors over in the state some of which James says suffered quot financial ruin quot New York hopes to ban Mashinsky from doing business in the state It also wants him to pay damages and otherwise compensate investors In a statement to Engadget Celsius would only reiterate that Mashinsky resigned as CEO in September and is quot no longer involved quot in managing the firm Celsius is one of the more prominent casualties of last year s crypto crash Its token s value plunged from in to just last spring That was particularly damaging to a company that offered loans with little collateral and promised yields as high as percent ーit didn t have the resources needed to endure the crisis It tried freezing withdrawals last June to stabilize its assets but opted for bankruptcy the following month to restructure and otherwise give it a better chance to regroup The lawsuit isn t likely to be the end of the fallout Several states are investigating Celsius practices and the Securities and Exchange Commission has been in touch Celsius isn t alone in dealing with legal repercussions Just this week the crypto exchange Coinbase reached a million settlement with New York over alleged financial rule violations However it s notable that the state is going after Mashinsky directly not just the business he once ran	2023-01-05 17:14:21
海外TECH	Engadget	Audio-Technica adapted its popular M50x headphones into headsets	https://www.engadget.com/audio-technica-headsets-m-50-x-content-creators-170054379.html?src=rss	Audio Technica adapted its popular Mx headphones into headsetsAt CES Audio Technica unveiled new StreamSet wired headsets that it designed with content creators in mind Based on the popular Mx headphones the MxSTS comes in two flavors One model has mm aux and XLR connectivity The other has a USB cable that enables some extra features but the two versions are otherwise very similar You ll get the same mm large aperture drivers with rare earth magnets and copper clad aluminum wire voice coils that are present in the Mx along with swappable earpads The Mx earpads are focused on audio quality and sound isolation while the mesh and leatherette earpads are all about breathability and comfort As for the microphone Audio Technica adopted a cardioid condenser from its Series models The mic which is said to offer studio level audio quality without background noise is on a boom arm Handily when you flip the boom up the headset will mute the mic One advantage that the MxSTS USB has over the mm model is that thanks to the sidetone circuitry you ll be able to hear your voice through the headset if you wish You can adjust that volume with an earcup dial The MxSTS has a two meter cable with a mm headphone input and for the mic an XLR output that you can connect to an audio interface or mixer The MxSTS USB version has a two meter cable as well but with a USB A connector you ll get a USB C adapter too The latter model also has an analog to digital converter with a sampling rate up to bits or kHz The MxSTS costs while the MxSTS USB will run you	2023-01-05 17:00:54
海外科学	NYT > Science	CVS and Walgreens Plan to Offer Abortion Pills Where Abortion Is Legal	https://www.nytimes.com/2023/01/05/health/abortion-pills-cvs-walgreens.html	CVS and Walgreens Plan to Offer Abortion Pills Where Abortion Is LegalThe two chains said they would begin the certification process under a new F D A regulation that will allow retail pharmacies to dispense the prescription pills for the first time	2023-01-05 17:51:58
ニュース	BBC News - Home	Employers could sue unions under planned anti-strike laws	https://www.bbc.co.uk/news/uk-politics-64173772?at_medium=RSS&at_campaign=KARANGA	minimum	2023-01-05 17:12:07
ニュース	BBC News - Home	Ukraine war: Kyiv rejects Putin's 'trivial' Christmas truce	https://www.bbc.co.uk/news/world-64178912?at_medium=RSS&at_campaign=KARANGA	propaganda	2023-01-05 17:54:16
ニュース	BBC News - Home	Six women arrested after boy, one, dies at Dudley nursery	https://www.bbc.co.uk/news/uk-england-birmingham-64178388?at_medium=RSS&at_campaign=KARANGA	dudley	2023-01-05 17:24:22
ニュース	BBC News - Home	El Chapo's son, Ovidio Guzmán-López, reportedly arrested amid violence in Sinaloa	https://www.bbc.co.uk/news/world-latin-america-64179356?at_medium=RSS&at_campaign=KARANGA	cartel	2023-01-05 17:53:19
ニュース	BBC News - Home	Keir Starmer embraces Brexit slogan with 'take back control' pledge	https://www.bbc.co.uk/news/uk-politics-64173370?at_medium=RSS&at_campaign=KARANGA	westminster	2023-01-05 17:01:05
ニュース	BBC News - Home	Carole Packman murder: Russell Causley to be released from prison	https://www.bbc.co.uk/news/uk-england-dorset-64179428?at_medium=RSS&at_campaign=KARANGA	carole	2023-01-05 17:03:35
ニュース	BBC News - Home	CES 2023: Sony unveils controller for disabled gamers	https://www.bbc.co.uk/news/technology-64176441?at_medium=RSS&at_campaign=KARANGA	accessible	2023-01-05 17:11:52
ビジネス	ダイヤモンド・オンライン - 新着記事	【ワークマン仕掛け人・新年特別講義】 物産時代は「俺についてこい！」 ワークマンでは私が「コーチ役」で社員が「主役」！ - ワークマン式「しない経営」	https://diamond.jp/articles/-/314073	さらに急成長の仕掛け人・ワークマンの土屋哲雄専務の白熱の処女作『ワークマン式「しない経営」ー億円の空白市場を切り拓いた秘密』も増刷を重ねている。	2023-01-06 02:55:00
ビジネス	ダイヤモンド・オンライン - 新着記事	【精神科医が教える】 誠意を見せないと訴えるぞ、責任をとれ…“ややこしい客”から真の問題解決を図る一流の対処法 - 精神科医Tomyが教える 心の執着の手放し方	https://diamond.jp/articles/-/314972	【精神科医が教える】誠意を見せないと訴えるぞ、責任をとれ…“ややこしい客から真の問題解決を図る一流の対処法精神科医Tomyが教える心の執着の手放し方誰しも悩みや不安は尽きない。	2023-01-06 02:50:00
ビジネス	ダイヤモンド・オンライン - 新着記事	元国立国会図書館司書が教える「最高の図書館」ベスト5 - 独学大全	https://diamond.jp/articles/-/315448	元国立国会図書館司書が教える「最高の図書館」ベスト独学大全『独学大全ー絶対に「学ぶこと」をあきらめたくない人のためのの技法』著者の読書猿さんが、「調べものの師匠」と呼ぶのが、元国会図書館司書の小林昌樹さんだ。	2023-01-06 02:45:00
ビジネス	ダイヤモンド・オンライン - 新着記事	【翁邦雄・元日本銀行金融研究所所長に聞く】日銀の「超低金利固定」からの脱却はなぜ「必要だが困難」なのか - 金利と経済　高まるリスクと残された処方箋	https://diamond.jp/articles/-/315477	引き上げ	2023-01-06 02:40:00
ビジネス	ダイヤモンド・オンライン - 新着記事	【並べ替え問題】「思考力」が身につく脳トレ - 1分間瞬読ドリル　超かんたん!入門編	https://diamond.jp/articles/-/315662	【並べ替え問題】「思考力」が身につく脳トレ分間瞬読ドリル超かんたん入門編「認知症、ボケ予防に役立つ」「記憶力や思考力がアップし、勉強に活かせる」「頭の回転が速くなった」「本が速く読めて、判断スピードがあがった」「モチベーションの向上、習慣化につながる」「持続力が増して途中で投げ出さなくなった」などの声が届いた、くり返し楽しんで使える『分間瞬読ドリル』に、超入門編が登場。	2023-01-06 02:35:00
ビジネス	ダイヤモンド・オンライン - 新着記事	「ヨルダンってどんな国？」2分で学ぶ国際社会 - 読むだけで世界地図が頭に入る本	https://diamond.jp/articles/-/315548		2023-01-06 02:30:00
Azure	Azure の更新情報	General availability: Apache log4J2 sink to Azure Data Explorer	https://azure.microsoft.com/ja-jp/updates/general-availability-apache-log4j2-sink-to-azure-data-explorer/	apache	2023-01-05 18:00:05