AWS |
AWSタグが付けられた新着投稿 - Qiita |
Amazon Redshift で ダイナミックデータマスキング |
https://qiita.com/suzukihi724/items/f7f8a1b53c36a82e4659
|
amazonredshift |
2022-09-23 20:21:59 |
golang |
Goタグが付けられた新着投稿 - Qiita |
Go言語、Visual Studio Code でのデバッグ方法を調べる |
https://qiita.com/muzudho1/items/23e682b1a89e55136c64
|
visualstudio |
2022-09-23 20:56:14 |
GCP |
gcpタグが付けられた新着投稿 - Qiita |
業務負荷を減らすwebアプリ【vote】の紹介 |
https://qiita.com/narunblog/items/e70a60e96a56a5372229
|
部署 |
2022-09-23 20:43:47 |
海外TECH |
MakeUseOf |
What Is the Tesla Semi and When Is It Launching? |
https://www.makeuseof.com/what-is-tesla-semi-when-launching/
|
electric |
2022-09-23 11:15:14 |
海外TECH |
DEV Community |
process.env as feature flags |
https://dev.to/woovi/processenv-as-feature-flags-nf
|
process env as feature flagsAt Woovi we are always looking to optimize our processes We want to improve the DX to increase the productivity of every software engineer We want to make everything faster consuming fewer memory and also providing the best usability Experimentation leads to innovation However experimentation can also break what is stable To avoid breaking any core process of our software engineer team we release new DX improvement behind feature flags that can be turned on using process env Below is an example of our Jest config that enable the developer to decide which jest transformer to use Esbuild and SWC are faster transformer than babel jest although it breaks a few of our tests const jestTransformer gt if process env JEST TRANSFORMER process env JEST TRANSFORMER babel jest return js ts tsx babel jest if process env JEST TRANSFORMER esbuild jest return js ts tsx esbuild jest if process env JEST TRANSFORMER swc jest return js ts tsx swc jest sourceMaps true jsc parser syntax typescript tsx true What experimentation and DX improvement are you doing in your codebase If you care about DX and wanna work with us we are hiring |
2022-09-23 11:33:01 |
海外TECH |
DEV Community |
How To Start Testing React Apps (And Why I Recommend Cypress To Beginners) |
https://dev.to/profydev/how-to-start-testing-react-apps-and-why-i-recommend-cypress-to-beginners-5el5
|
How To Start Testing React Apps And Why I Recommend Cypress To Beginners You know that you should write tests for your React applications But reality shows that most Junior developers never have written a test And to be honest it doesn t feel easy to start You have to decide between a gazillion tools Writing tests feels very different than writing your normal frontend code It s awkward And frustrating Strange errors everywhere that you don t know how to debug But once you get used to it you won t wanna miss it You ll feel much safer because code changes won t break your app No need for endless manual tests anymore Not only that Writing tests is best practice in many companies and lets you stand out as a candidate if you re looking for your first developer job And turns out it doesn t have to be that hard If you pick the right tools to start with and get a bit of guidance On this page you can find exactly that We cover why Cypress is a great tool especially for developers who are new to testing We start by writing a few simple UI tests We move on to more complex tests involving data from API requests Finally we learn how to debug our way through problems But hold on This is not a theoretical lesson where you simply lean back and enjoy the content I prepared a project that you can use to follow along It s a Next js app that needs some testing love We ll write a few tests together but in the end I ll leave a few test cases for you to implement on your own The goal is that you leave this tutorial with the skills to start testing your own applications This is your chance to get hands on testing experience I hope you re thrilled IntroductionWhy CypressThe Project Used In This TutorialWhat To TestTesting Navigation LinksOpening A URL With CypressAccessing An Element GloballySwitching ViewportsAccessing A Specific Element By TextInteracting With Elements ClickingCypress Helps With DebuggingAccessing The URLExerciseTesting That The Navigation Is CollapsibleClicking A ButtonWhat To TestTesting The LinksTesting That Elements Are HiddenTesting Pages With API RequestsWhat To TestAccessing Elements Within A ParentIterating Over A List Of ElementsDetour Different Types Of TestingMocking Requests Responses With CypressAsserting Against The Mock DataDebugging Broken TestsUsing Chrome Dev ToolsSetting BreakpointsInpsecting VariablesInspecting DOM ElementsYour Turn More Exercises Introduction Why CypressAs with everything JavaScript there are tons of testing tools in the React and web dev ecosystem Some are outdated like Enzyme Some are super popular but somewhat hard on beginners like React Testing Library And one testing tool is popular in real world projects AND has a relatively low learning curve CypressThe big advantage and reason why I recommend it to beginners is the level of visual feedback and interactivity The problem with other testing frameworks like RTL is thatWriting tests feels different from your usual frontend code All the output is in the terminal while you re used to looking at the browser for feedback The debugging experience is vastly different More like debugging Node js servers than React apps With Cypress you only have the first point Once you get used to writing tests you can transfer this knowledge to other frameworks like RTL and get comfortable with the debugging experience there And that s surely a good idea since most tests are likely written with React Testing Library nowadays But one step at a time Let me show you why Cypress is so powerful On your local machine it has a separate UI where all the tests are run Next to a browser window where you can watch your tests step by step You can click on each step of the tests and get some additional information You can even open the Chrome dev tools in the browser read the console output inspect elements and use the debugger I hope the advantages are clear You re likely used to a lot of this stuff already So it s mostly Cypress and its API that you have to get used to On top of that Cypress is super easy to set up In your project you can simply runnpm install save dev cypressThat s it The Project Used In This TutorialAs I mentioned I created a Next js app that we ll use as an existing codebase to cover with tests on this page It s an error tracking tool similar to Sentry or Rollbar You can find the running app here The app belongs to the React Job Simulator program where you can learn and apply professional React dev skills like testing I personally am a learning by doing type So I highly recommend following along with this tutorial From my experience just reading only gets you this far But applying the newly gained knowledge will make it stick To get the source code drop your email below What To TestIn this tutorial we will test two things The navigation bar see screenshot below and a list of issues that you can see here Let s start with the navigation bar With Cypress as well as React Testing Library we typically test an application the same way a user would interact with it For example we click on an element and see if the browser shows the correct result The purpose of a test is to ensure that a feature works correctly Not that a component gets the right props or a certain callback was run That s not what the user sees or is interested in Shortly it s irrelevant There are lots of things that we could potentially test But it s a good idea to focus on the important parts of a feature s functionality In this case the sidebar navigation serves its purpose ifthe links send the user to the correct pagethe navigation bar is collapsible These are relatively simple UI tests that we ll implement in the following two sections Testing the issues page is a bit more complex as it involves API requests We ll have a look at that in the th section Testing Navigation LinksFirst let s focus on the links in the navigation Here is one way of testing them We get the links in the navigation We click each link We check the URL to ensure that the correct page has opened Opening A URL With CypressFirst we need to do some setting up Before each test we need to open the application from within Cypress here the home page works well This is done via the cy visit command Open the file cypress integration navigation spec ts and add the following code describe Sidebar Navigation gt beforeEach gt cy visit http localhost dashboard But how do we get the links First it s a good idea to get an overview of the navigation DOM structure In our normal browser we can open the dev tools and inspect the navigation Accessing An Element GloballyAll the links are grouped in a nav tag Since there are other links on the page it s smart to start with that group We can access an element with the cy get command This command accepts a selector as a parameter the tag nav here and returns all corresponding elements on the website describe Sidebar Navigation gt beforeEach gt cy visit http localhost dashboard it links are working gt cy get nav Easy Now let s double check that everything s working fine In the Cypress UI we click on navigation spec ts This should run the tests which looks like this If Cypress doesn t find the element in question it throws an error But the test passes so everything is alright Accessing the nav element via cy get nav worked Switching ViewportsBut wait Where is the navigation bar Have a close look at the Cypress browser This is the mobile view And on mobile the navigation is hidden That means we first need to set the viewport to desktop That can be done with the cy viewport command describe Sidebar Navigation gt beforeEach gt cy viewport cy visit http localhost dashboard it links are working gt cy get nav When you save the file the test should automatically re run Now our Cypress UI should show this Accessing A Specific Element By TextNow let s test the first link Since the “Projects link points to the route which is the current route we test the “Issues link first The problem is that there are multiple links in the navigation The cy get command that we used before doesn t work well in this case It would get all links on the whole page But we want a specific one The one inside the navigation that says “Issues To get an element by its text content we can use the contains command To make it even more specific we can chain it with the get command it links are working gt check that issues link leads to the right page cy get nav contains Issues Interacting With Elements ClickingNow we should have access to the Issues link and can interact with it To click the link we can simply use the click command it links are working gt check that issues link leads to the right page cy get nav contains Issues click The test should run again and hopefully pass Cypress Helps With DebuggingIt s time for some Cypress magic In the screenshot above do you see what happens when you hover over the “click step on the left It highlights the element that was clicked in the browser This is super helpful to understand what s going on and debug issues Accessing The URLOK looks like everything is fine for now The last step to test the link is to check that the correct page is opened As mentioned above we can simply check the URL We can use the cy url command and test its value with the should command it links are working gt check that issues link leads to the right page cy get nav contains Issues click cy url should eq http localhost dashboard issues The test passes Everything is as expected yay ExerciseNow is your chance to get your hands dirty We created a test for the first link here But there are a few links that need to be tested as well ProjectsAlertsUsersSettingsNote You can add all these tests to the same it links are working test case Testing That The Navigation Is CollapsibleNow let s test a dynamic part of the sidebar navigation When you click the Collapse button at the bottom left either on your local machine or here you should see the navigation bar collapse Clicking A ButtonWe start with another it wrapper Same as in the tests before we get the nav element and find the “Collapse button inside using cy get and cy contains Finally we click it it is collapsible gt collapse navigation cy get nav contains Collapse click When you check the Cypress UI the test passes and the navigation is collapsed Everything seems to work fine Again you can hover on each of the steps on the left to see what happened in the UI What To TestNow how do we test that the navigation is collapsed and ensure that it works There are two things that seem sufficient to me Check that all links are rendered and work correctly Check that the text next to the icon is hidden Testing The LinksLet s start with the links Since we tested each link s target in the previous test I don t think we need to do that again Instead we can check that the correct number of links is rendered and that any of these is works correctly To get all links we can use the cy find command it is collapsible gt collapse navigation cy get nav contains Collapse click check that links still exist cy get nav find a should have length Now we can take any one of these links and check that it still leads the user to the correct page To access a specific element from an array Cypress provides the first eq or last commands cy first doesn t work in our case since that would be the “Projects link which is the current page The test would pass even if the link didn t do anything cy last seems a bit more fragile It would break if we d add another link to the navigation So let s settle for cy eq This would still break if we change the order of the links but seems like the least fragile option it is collapsible gt collapse navigation cy get nav contains Collapse click check that links still exist and are functional cy get nav find a should have length eq click cy url should eq http localhost dashboard issues Testing That Elements Are HiddenFinally let s check that the user only sees the icons and not the text next to them Testing one link should be the same as they re handled by a single component So let s use the “Issues link it is collapsible gt collapse navigation cy get nav contains Collapse click check that links still exist and are functional cy get nav find a should have length eq click cy url should eq http localhost dashboard issues check that text is not rendered cy get nav contains Issues should not exist Great we added our first simple UI tests There are other things that we could test like the navigation on mobile devices But more on that later Let s continue with testing data driven components Testing Pages With API RequestsIf you visit the app s projects page and look carefully or with a sufficiently slow internet connection you can see this loading state This indicates that the page loads data from an API To be fair this is not the best loading indicator but that s a task for the React Job Simulator Once the data is loaded we see the projects rendered on the page What To TestNow how do we test this data Again like a user would use the app We get the elements on the page here the project cards and check that the correct values are rendered First let s again get an overview of the DOM structure When you inspect the first project card in your dev tools you ll see this We can see that each project card is wrapped in a li tag This seems like a good selector for our tests Accessing Elements Within A ParentThe problem is that we know from the previous tests that there are li elements in the navigation bar as well So when we try to access the project cards we need to be careful not to grab the navigation links The easiest way to prevent this is to identify a suitable parent element of the project cards and access this first Here the main element seems like a good fit since the navigation is rendered outside of it That s enough information for now Open the file cypress integration project list spec ts and add the following code describe Project List gt beforeEach gt cy viewport cy visit http localhost dashboard it renders the projects gt get all project cards cy get main find li Iterating Over A List Of ElementsNow we can make use of the each el ⇒… command to iterate through this list The first parameter el of the callback function allows us to access each element So to test that e g the first card contains the project title “Frontend Web it makes sense to simply try to write el contains Frontend Web Unfortunately this gives us an error The type of the parameter el is JQuery lt HTMLElement gt And this doesn t support the Cypress commands like contains Looking at the docs there is a simple solution though we can just wrap el with cy wrap and access all Cypress commands as we re used to So let s test the first project card For now we simply hard code the expected values describe Project List gt beforeEach gt cy viewport cy visit http localhost dashboard it renders the projects gt get all project cards cy get main find li each el index gt only test the first project card if index cy wrap el contains Frontend Web cy wrap el contains React cy wrap el contains cy wrap el contains cy wrap el contains Error cy wrap el find a should have attr href issues Ok all tests pass That tells us that the overall approach works But obviously hard coding the expected data and wrapping it in an if clause isn t really an option There are two problems The tests would get unnecessarily long What happens when the data returned by the server changes The tests would fail Detour Different Types Of TestingIn order to make these tests pass reliably we need to always have the same data There are two ways of achieving thatwe have a server that always delivers the expected datawe mock the responsesIn larger projects you often find test environments that include databases servers and so on This is a great way to test the application from the database to the frontend These tests are also called “end to end test Here we don t have such a test server so we ll mock the responses This way we only test the frontend isolated from the rest of the system This is called an integration test If you want to read more about the different types of testing and their advantages read this awesome blog post by Kent C Dodds As a summary he argues that integration tests usually get you the most bang for the buck They are relatively performant better than end to end tests but worse than unit tests and give you good confidence that your application is functioning less than ee but more than unit tests Note that Cypress is probably not the best tool to use for perfomant tests That would rather be Jest React Testing Library But as I said earlier it s a better option for beginners due to the easy setup and visual feedback Mocking Requests Responses With CypressSo we decided to write integration tests by mocking out our API requests The first step is preparing our mock data There are a few options Write the data by hand Use a tool to create random data from a schema Use existing API data In our case we already have a working API So we can simply copy our mock data from one of the requests The easiest way to access this data is via the browser s dev tools To get data from any request in Chrome simply follow these steps Open the “Network tab Filter the requests by “Fetch XHR Click on the “project request Open the “Preview tab Right click below the data and click “Copy object Cypress has a separate folder for mock data at cypress fixtures A fixture in our case is simply the mock data that makes our tests repeatable Create a file in that folder called projects json and paste the data you copied above there Mocking the response to this request is now simple with the cy intercept command You can get the URL of the API endpoint again from the network tab in the browser s dev tools beforeEach gt setup request mock cy intercept GET fixture projects json as getProjects set desktop viewport cy viewport cy visit http localhost dashboard wait for the projects response cy wait getProjects In the above code we also use the as command to create an alias We can use this alias to wait for the response before the tests start This is useful to prevent the tests from randomly failing due to timing issues aka making them less “flaky When you re run the test now you should receive the mock data You can double check that the test doesn t send real requests either by changing something inside the mock data orchecking the request in the Cypress UI as shown in the screenshot below Asserting Against The Mock DataRemember that we hard coded the expected data for the first project card in the test Now we can replace it with the data from our fixture import capitalize from lodash capitalize import mockProjects from fixtures projects json import ProjectLanguage from features projects types project types describe Project List gt beforeEach gt setup request mock cy intercept GET fixture projects json as getProjects cy viewport cy visit http localhost dashboard cy wait getProjects it renders the projects gt const languageNames ProjectLanguage react React ProjectLanguage node Node js ProjectLanguage python Python get all project cards cy get main find li each el index gt const projectLanguage mockProjects index language as ProjectLanguage check that project data is rendered cy wrap el contains mockProjects index name cy wrap el contains languageNames projectLanguage cy wrap el contains mockProjects index numIssues cy wrap el contains mockProjects index numEventsh cy wrap el contains capitalize mockProjects index status cy wrap el find a should have attr href issues Note that we need to add some additional logic The reason is that in some cases the data is changed by the frontend before displaying it to the user For example the project language can be node in the response data but will be displayed as Node js Debugging Broken TestsWhen you write your own tests you will run into problems at some point So it s important that you know how to debug your tests I prepared an example for a failing test in the file cypress integration issue list spec ts for us to debug together it renders the issues gt cy get main find tr each el index gt const issue mockIssues items index const firstLineOfStackTrace issue stack split n trim cy wrap el contains issue name cy wrap el contains issue message cy wrap el contains issue numEvents cy wrap el contains firstLineOfStackTrace This looks pretty similar to the test for the project pages It s supposed to check that the data inside the issues table is rendered correctly But when you run it you ll see that there s an error Note you can tell Cypress to only run a certain test or set of tests by appending only to describe or it This way you don t have to wait for all tests to run while you re working on a single test In our case we can write it only renders the issues gt The error above looks strange Cannot read properties of undefined reading stack It s not immediately clear what that means So let s dig deeper But how to debug your tests Using Chrome Dev ToolsThe answer is simple You can do the same things that you can do in your normal Chrome browser as well For example Inspect DOM elementsPrint out variables with console log from either your code or your testsAdd breakpoints to stop code executionIn our case we can start by investigating the test file We could add console log statements in the code But let s be a bit more professional and use the debugger Setting BreakpointsFirst open the dev tools inside your Cypress UI You can do that either with your usual key combination or by right clicking somewhere in the browser window and clicking “Inspect Next click on the “Sources tab You should see a hint on how to open a file in my case ⌘ P Now you start typing the file name you want to investigate In this case “issue list should be sufficient to get the correct results Note that you can also open the React component issue list tsx which means you can also debug your application codeOnce you opened the file you can add a breakpoint The error message at the left of the Cypress UI tells us that something is wrong in the each loop So let s start there Note that I only added one breakpoint The second appeared by itself I guess that s because internally we debug a JS file that is mapped back to its original TS source Now we can re run the test by pressing the refresh button inside the top bar The code execution should stop within the each loop Inpsecting VariablesNow isn t this magic We can inspect the variables specifically el in the right side menu We can already see from the class name that this is the header row of the table But when we hover over the class name it even highlights the element in the UI above The problem is clear now at least to me since I wrote the test We wanted to test that the data inside the table is rendered correctly But the first item we get is the header row which doesn t contain any data Inspecting DOM ElementsAs we ve done before we need to narrow down the search for the correct elements Let s look at the DOM structure again to see our options When you inspect the table with your dev tools you can see this The table rows that contain the data are wrapped in a lt tbody gt tag So we can use this information to filter out the table header row from our test it renders the issues gt cy get main find tbody find tr each el index gt const issue mockIssues items index const firstLineOfStackTrace issue stack split n trim cy wrap el contains issue name cy wrap el contains issue message cy wrap el contains issue numEvents cy wrap el contains firstLineOfStackTrace The test should pass now Your Turn More ExercisesIf your fingers are itchy and you want to try this stuff out yourself here is the good news There are a few test cases left that you can implement yourself The issue list has a pagination at the bottom You can test that the buttons are working correctly and that the right data is rendered The page number of this pagination should persist after a refresh On mobile devices the sidebar navigation should not be visible initially and be toggled by the menu button in the header Note that the last test is a bit more complex Cypress doesn t have a native way to test if an element is outside the viewport I found this GitHub issue to be helpful If you want to try these exercises you can either implement the tests against the deployed version of the app that I shared at the beginning of the page Or you drop you email below to get access to the source code There you can also find my implementations of these tests |
2022-09-23 11:30:40 |
Apple |
AppleInsider - Frontpage News |
Apple Watch Series 8 review: Another year, another Apple Watch |
https://appleinsider.com/articles/22/09/23/apple-watch-series-8-review-another-year-another-apple-watch?utm_medium=rss
|
Apple Watch Series review Another year another Apple WatchApple Watch Series is a jack of all trades for your average user though a lack of new features is a bit more apparent than in years past Apple Watch Series mm in silverThe rate of iteration on the standard Apple Watch seems to be slowing The biggest changes in come from watchOS which delivered long awaited features such as low power mode improved workouts and better tracking with the Compass app Read more |
2022-09-23 11:56:53 |
Apple |
AppleInsider - Frontpage News |
How to use the Action button on Apple Watch Ultra |
https://appleinsider.com/articles/22/09/23/how-to-use-the-action-button-on-apple-watch-ultra?utm_medium=rss
|
How to use the Action button on Apple Watch UltraThe Action Button is only one extra control on the Apple Watch Ultra but there are great benefits that can be had with it if you know how to set it up and use it After seven years of the Apple Watch with its Digital Crown and its side button Apple has introduced a model with a third control The new Action button is big orange and powerful In theory the new button gives divers extreme sports people and athletes a way to specifically launch one of half a dozen Watch features like starting a workout In practice though one option is to use it to launch a Shortcut ーwhich means a single press can start all of the new functions and just about anything else the Watch can do Read more |
2022-09-23 11:08:26 |
Apple |
AppleInsider - Frontpage News |
Apple Music sponsoring NFL's Super Bowl half-time show |
https://appleinsider.com/articles/22/09/23/nfl-apple-music?utm_medium=rss
|
Apple Music sponsoring NFL x s Super Bowl half time showBack in the s Apple poached John Sculley from Pepsi Now for Apple Music is replacing the soft drink firm as sponsor of what the NFL claims is the most watched musical performance of the year In February Pepsi pulled out of sponsoring the halftime show though it will continue to sponsor the NFL NBC Sports reported then that the NFL was looking for a replacement willing to sponsor the show for between million and million per year Now while it has not disclosed any of the terms of the deal the NFL has announced that Apple Music will sponsor the minute show Read more |
2022-09-23 11:57:54 |
海外TECH |
Engadget |
The Morning After: Google's cheaper $30 Chromecast with Google TV |
https://www.engadget.com/the-morning-after-googles-cheaper-30-chromecast-with-google-tv-111544466.html?src=rss
|
The Morning After Google x s cheaper Chromecast with Google TVGoogle has unveiled another streaming dongle The Chromecast with Google TV HD device manages to offer a lot of the features from the K model at a significantly cheaper price Unlike the older Chromecast it comes with a remote control that eliminates the need for a smartphone though you can still control it with your phone There is a drawback that lower p resolution but there s HDR support It also comes with six months of Peacock Premium free The lack of a remote controller was a frustration for many people looking for a plug and stream stick and at this price it s a pretty tempting streaming solution if you haven t already picked up a Chromecast Roku or something else Mat SmithThe biggest stories you might have missedTesla to recall more than a million vehicles over pinchy windowsMoog once again revives the Model its first compact modular synth Meta ordered to pay million in patent infringement caseNothing reveals the charging case for its next earbudsThe best smartphones you can buy right nowNASA and Hideo Kojima team up for a Ludens inspired watch Yale s redesigned door lock will be one of the first Matter compatible smart home devicesByteDance s Pico reveals its latest VR headset as it aims to compete with Meta Quest Apple s nd gen AirPods Pro reviewBig improvements all on the inside EngadgetYes they still have stems Yes there s still active noise cancellation Yes they might be worth upgrading from the original AirPods Pro Apple has included of the conveniences from the model alongside additions like Adaptive Transparency Personalized Spatial Audio and a new touch gesture in tow There s room to further refine the familiar formula so read on for the full review Continue reading This turntable can connect to any Sonos speakerIf you love vinyl and streaming music the Stream Carbon might be for you VictrolaA lot of connected smart speakers don t work with turntables which can make things complicated during the continued resurgence of vinyl Victrola which has made record players for more than years is mostly known for entry level turntables with built in speakers but it s now revealed the Stream Carbon a turntable that can directly connect to a Sonos system which means you ll be able to stream your records all over your home Victrola says this is just the first of more planned devices in the Stream lineup Continue reading The FDA may have unintentionally made NyQuil Chicken go viral on TikTokTikTok says interest spiked only after the FDA s warning You ve probably heard something about “NyQuil Chicken a supposedly viral TikTok “challenge of cooking chicken in a marinade of cold medicine Not only disgusting as the FDA recently reminded the public it s just as toxic as it looks The agency s bizarrely timed warning may have backfired making the meme more popular than ever TikTokconfirmed that on September th the day before the FDA notice there were only five searches for “NyQuil chicken in the app But by September st that number skyrocketed “by more than times according to BuzzFeed News Continue reading Instagram is working on nudity protection technologyIt s focused on unwanted DMs An early screengrab tweeted by researcher Alessandro Paluzzi indicates that Instagram is working on quot Nudity protection quot technology that quot covers photos that may contain nudity in chat quot giving users the option to view them or not Instagram parent Meta confirmed to The Verge that it s in development Meta said the aim is to help shield people from nude images or other unsolicited messages As further protection the company said it can t view the images itself nor share them with third parties Continue reading Facebook violated Palestinians right to free expression according to MetaMany users accounts were hit with quot false strikes quot last year due to Meta s policies Meta has released the findings of an outside report that examined how its content moderation policies affected Israelis and Palestinians amid an escalation of violence in the Gaza Strip last May The report said that Facebook s approach appears “to have had an adverse human rights impact on the rights of Palestinian users to freedom of expression freedom of assembly political participation and non discrimination and therefore on the ability of Palestinians to share information and insights about their experiences as they occurred Continue reading |
2022-09-23 11:15:44 |
ニュース |
BBC News - Home |
Chancellor Kwasi Kwarteng hails 'new era' as he unveils tax cuts |
https://www.bbc.co.uk/news/uk-politics-63005302?at_medium=RSS&at_campaign=KARANGA
|
economic |
2022-09-23 11:08:00 |
ニュース |
BBC News - Home |
Wolf Hall author Hilary Mantel dies aged 70 |
https://www.bbc.co.uk/news/entertainment-arts-63007307?at_medium=RSS&at_campaign=KARANGA
|
trilogy |
2022-09-23 11:40:50 |
ニュース |
BBC News - Home |
Pound sinks as markets react to mini-budget |
https://www.bbc.co.uk/news/business-63009173?at_medium=RSS&at_campaign=KARANGA
|
economic |
2022-09-23 11:48:54 |
ニュース |
BBC News - Home |
Alcohol duty: Chancellor Kwasi Kwarteng scraps planned increase |
https://www.bbc.co.uk/news/uk-politics-63007279?at_medium=RSS&at_campaign=KARANGA
|
chancellors |
2022-09-23 11:34:05 |
ニュース |
BBC News - Home |
Khayri Mclean: Second teen arrested after boy stabbed to death |
https://www.bbc.co.uk/news/uk-england-leeds-63009233?at_medium=RSS&at_campaign=KARANGA
|
huddersfield |
2022-09-23 11:45:32 |
ニュース |
BBC News - Home |
Ukraine war: Crown prince crucial in Ukraine prisoner deal, Saudis say |
https://www.bbc.co.uk/news/world-europe-63004964?at_medium=RSS&at_campaign=KARANGA
|
foreign |
2022-09-23 11:17:16 |
ニュース |
BBC News - Home |
Molly Russell inquest: Instagram clips seen by teenager were 'most distressing' |
https://www.bbc.co.uk/news/uk-england-london-62998484?at_medium=RSS&at_campaign=KARANGA
|
distressing |
2022-09-23 11:24:35 |
ニュース |
BBC News - Home |
Kwasi Kwarteng's mini-budget is admission of Tory economic failure, Labour says |
https://www.bbc.co.uk/news/uk-politics-63007423?at_medium=RSS&at_campaign=KARANGA
|
rewards |
2022-09-23 11:05:18 |
ニュース |
BBC News - Home |
What is universal credit and who qualifies for it? |
https://www.bbc.co.uk/news/uk-41487126?at_medium=RSS&at_campaign=KARANGA
|
people |
2022-09-23 11:45:16 |
北海道 |
北海道新聞 |
玉鷲11勝目、14日目にもV 1差に高安と北勝富士 |
https://www.hokkaido-np.co.jp/article/735408/
|
両国国技館 |
2022-09-23 20:22:29 |
北海道 |
北海道新聞 |
長万部の水柱、勢い弱まる? 騒音測定結果が軒並み低下 |
https://www.hokkaido-np.co.jp/article/735411/
|
長万部町 |
2022-09-23 20:13:48 |
北海道 |
北海道新聞 |
日高管内41人感染 新型コロナ |
https://www.hokkaido-np.co.jp/article/735410/
|
新型コロナウイルス |
2022-09-23 20:08:46 |
北海道 |
北海道新聞 |
「チベットの文化破壊」 亡命政府首相が批判 |
https://www.hokkaido-np.co.jp/article/735416/
|
亡命政府 |
2022-09-23 20:08:00 |
コメント
コメントを投稿